Re: [mh] random crashing of MH

Timothy Spaulding <[email protected]>
Newsgroups gmane.comp.misc.misterhouse.user
Message-ID <BY5PR01MB579520689BC69065D0E7BF2FCD8F0@BY5PR01MB5795.prod.exchangelabs.com>
Thanks, I'll disable homebridge for a while.

From: H Plato <[email protected]>
Sent: Tuesday, September 17, 2019 1:30 PM
To: Timothy Spaulding <[email protected]>
Cc: The main list for the MisterHouse home automation program <[email protected]>
Subject: Re: [mh] random crashing of MH

Weird, quickly looking at the errors, It looks like the homebridge request for status, has sent a http_process_request with an undefined socket.

main::http_process_request(undef, "GET /SUB?hb_status%28Master_Suite_Sitting_Lights,light%29 HTT"...)

Try disabling homebridge, (or take the hb_status items out of the config.json file)  to see if this is the root cause.


On Sep 17, 2019, at 7:47 AM, Timothy Spaulding <[email protected]<mailto:[email protected]>> wrote:

Hi All,

I have a puzzling issue that I have no clue how to resolve.

Environment:
I moved MH to a Raspberry PI where I have added a USB network adapter to attached to a second VLAN.  This VLAN has all of my IOT/Automation type devices.  The only device on that VLAN that really talks to MH (via the additional USB network adapter) is the SmartThings Hub to call URLs on MH to set status on objects

Problem:
Periodically, and seemingly random times, MH will crash with he following messages on the console:

Can't call method "peername" on an undefined value at /mnt/syn/autopi/misterhouse/bin/../lib/http_server.pl line 153.
at /mnt/syn/autopi/misterhouse/bin/mh line 31.
        main::__ANON__("Can't call method \"peername\" on an undefined value at /mnt/sy"...) called at /mnt/syn/autopi/misterhouse/bin/../lib/http_server.pl line 153
        main::http_process_request(undef, "GET /SUB?hb_status%28Master_Suite_Sitting_Lights,light%29 HTT"...) called at /mnt/syn/autopi/misterhouse/bin/mh line 2541
        main::check_for_socket_data_http called at /mnt/syn/autopi/misterhouse/bin/mh line 1688
        main::check_for_action called at /mnt/syn/autopi/misterhouse/bin/mh line 3778
        main::monitor_commands called at /mnt/syn/autopi/misterhouse/bin/mh line 7783
        (in cleanup) Can't call method "setcflag" on an undefined value at /mnt/syn/autopi/misterhouse/bin/../lib/site/Device/SerialPort.pm line 452 during global destruction.
at /mnt/syn/autopi/misterhouse/bin/mh line 31.
        main::__ANON__("Can't call method \"setcflag\" on an undefined value at /mnt/sy"...) called at /mnt/syn/autopi/misterhouse/bin/../lib/site/Device/SerialPort.pm line 452
        Device::SerialPort::write_settings(Device::SerialPort=HASH(0x338b350)) called at /mnt/syn/autopi/misterhouse/bin/../lib/site/Device/SerialPort.pm line 1926
        Device::SerialPort::close(Device::SerialPort=HASH(0x338b350)) called at /mnt/syn/autopi/misterhouse/bin/../lib/site/Device/SerialPort.pm line 1958
        Device::SerialPort::DESTROY(Device::SerialPort=HASH(0x338b350)) called at /mnt/syn/autopi/misterhouse/bin/mh line 0
        eval {...} called at /mnt/syn/autopi/misterhouse/bin/mh line 0
        (in cleanup) Can't call method "setcflag" on an undefined value at /mnt/syn/autopi/misterhouse/bin/../lib/site/Device/SerialPort.pm line 452 during global destruction.
at /mnt/syn/autopi/misterhouse/bin/mh line 31.
        main::__ANON__("Can't call method \"setcflag\" on an undefined value at /mnt/sy"...) called at /mnt/syn/autopi/misterhouse/bin/../lib/site/Device/SerialPort.pm line 452
        Device::SerialPort::write_settings(Device::SerialPort=HASH(0x2418068)) called at /mnt/syn/autopi/misterhouse/bin/../lib/site/Device/SerialPort.pm line 1926
        Device::SerialPort::close(Device::SerialPort=HASH(0x2418068)) called at /mnt/syn/autopi/misterhouse/bin/../lib/site/Device/SerialPort.pm line 1958
        Device::SerialPort::DESTROY(Device::SerialPort=HASH(0x2418068)) called at /mnt/syn/autopi/misterhouse/bin/mh line 0
        eval {...} called at /mnt/syn/autopi/misterhouse/bin/mh line 0

I get this in the mh.log file:
09/17/19 12:17:00 AM [Socket_Item] client start error: could not start a tcp client socket - host=MisterHouse port=9191: IO::Socket::INET: connect: Connection timed out
09/17/19 12:17:00 AM The http server MisterHouse:9191 is down.  Restarting
Display call with tk disabled (-tk 0).  Text=text 09/17/19 12:17:00 AM: The http server MisterHouse:9191 is down.  Restarting
time 0 window_name http down log append bottom

Any thought/ideas (wild or otherwise) would be most appreciated.

Tim
________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.