[Gelöst] watchdog bringt FHEM nach Update zum Absturz

Begonnen von Ascos, 15 April 2015, 20:39:41

Vorheriges Thema - Nächstes Thema

Ascos

Hi,

ich habe gestern Abend ein FHEM Update durchgeführt.
Soweit ich getestet hatte, lief auch alles.
Ich habe einen Watchdog für meine Anwesenheitserkennung, der via Bluetooth mein iPhone erkennt.

Als ich heute früh das Haus verließ, fiel mein FHEM in der Sekunde aus,  als der Watchdog meinen Status auf Abwesend schalten sollte.
Dies habe ich eben nochmals getestet und der FEhler trat wieder auf.

Im Log erschienen zum Zeitpunkt des absturzes folgende Meldungen:

2015.04.15 20:34:24 1: PERL ERROR: Can't locate object method "tid" via package "threads" at /usr/share/perl/5.14/XSLoader.pm line 95.

2015.04.15 20:34:24 3: stacktrace:
2015.04.15 20:34:24 3:     main::__ANON__                      called by /usr/share/perl/5.14/XSLoader.pm (95)
2015.04.15 20:34:24 3:     (eval)                              called by /usr/share/perl/5.14/XSLoader.pm (95)
2015.04.15 20:34:24 3:     XSLoader::load                      called by /usr/lib/perl5/Net/SSLeay.pm (364)
2015.04.15 20:34:24 3:     (eval)                              called by /usr/lib/perl5/Net/SSLeay.pm (366)
2015.04.15 20:34:24 3:     (eval)                              called by /usr/share/perl5/IO/Socket/SSL.pm (18)
2015.04.15 20:34:24 3:     IO::Socket::SSL::BEGIN              called by /usr/lib/perl5/Net/SSLeay.pm (0)
2015.04.15 20:34:24 3:     (eval)                              called by /usr/lib/perl5/Net/SSLeay.pm (0)
2015.04.15 20:34:24 3:     (eval)                              called by (eval 423) (2)
2015.04.15 20:34:24 3:     main::BEGIN                         called by /usr/lib/perl5/Net/SSLeay.pm (0)
2015.04.15 20:34:24 3:     (eval)                              called by /usr/lib/perl5/Net/SSLeay.pm (0)
2015.04.15 20:34:24 3:     (eval)                              called by FHEM/HttpUtils.pm (183)
2015.04.15 20:34:24 3:     main::HttpUtils_Connect2            called by FHEM/HttpUtils.pm (174)
2015.04.15 20:34:24 3:     main::HttpUtils_Connect             called by FHEM/HttpUtils.pm (371)
2015.04.15 20:34:24 3:     main::HttpUtils_BlockingGet         called by FHEM/HttpUtils.pm (406)
2015.04.15 20:34:24 3:     main::CustomGetFileFromURL          called by FHEM/HttpUtils.pm (423)
2015.04.15 20:34:24 3:     main::GetFileFromURL                called by ./FHEM/70_Pushover.pm (128)
2015.04.15 20:34:24 3:     main::Pushover_HTTP_Call            called by ./FHEM/70_Pushover.pm (277)
2015.04.15 20:34:24 3:     main::Pushover_Set_Message          called by ./FHEM/70_Pushover.pm (107)
2015.04.15 20:34:24 3:     main::Pushover_Set                  called by fhem.pl (2966)
2015.04.15 20:34:24 3:     main::CallFn                        called by fhem.pl (1458)
2015.04.15 20:34:24 3:     main::DoSet                         called by fhem.pl (1488)
2015.04.15 20:34:24 3:     main::CommandSet                    called by fhem.pl (996)
2015.04.15 20:34:24 3:     main::AnalyzeCommand                called by fhem.pl (869)
2015.04.15 20:34:24 3:     main::AnalyzeCommandChain           called by fhem.pl (2983)
2015.04.15 20:34:24 3:     main::fhem                          called by (eval 422) (1)
2015.04.15 20:34:24 3:     (eval)                              called by fhem.pl (917)
2015.04.15 20:34:24 3:     main::AnalyzePerlCommand            called by fhem.pl (937)
2015.04.15 20:34:24 3:     main::AnalyzeCommand                called by fhem.pl (869)
2015.04.15 20:34:24 3:     main::AnalyzeCommandChain           called by ./FHEM/91_notify.pm (92)
2015.04.15 20:34:24 3:     main::notify_Exec                   called by fhem.pl (2971)
2015.04.15 20:34:24 3:     main::CallFn                        called by fhem.pl (2894)
2015.04.15 20:34:24 3:     main::DoTrigger                     called by fhem.pl (3658)
2015.04.15 20:34:24 3:     main::readingsEndUpdate             called by fhem.pl (3811)
2015.04.15 20:34:24 3:     main::readingsSingleUpdate          called by ./FHEM/98_dummy.pm (32)
2015.04.15 20:34:24 3:     main::dummy_Set                     called by fhem.pl (2966)
2015.04.15 20:34:24 3:     main::CallFn                        called by fhem.pl (1458)
2015.04.15 20:34:24 3:     main::DoSet                         called by fhem.pl (1488)
2015.04.15 20:34:24 3:     main::CommandSet                    called by fhem.pl (996)
2015.04.15 20:34:24 3:     main::AnalyzeCommand                called by fhem.pl (869)
2015.04.15 20:34:24 3:     main::AnalyzeCommandChain           called by ./FHEM/91_watchdog.pm (145)
2015.04.15 20:34:24 3:     main::watchdog_Trigger              called by fhem.pl (2574)
2015.04.15 20:34:24 3:     main::HandleTimeout                 called by fhem.pl (540)
2015.04.15 20:34:29 1: CallBlockingFn: Can't connect to localhost:38378: IO::Socket::INET: connect: Connection refused
2015.04.15 20:34:29 1: PERL ERROR: Can't use an undefined value as a symbol reference at FHEM/Blocking.pm line 125.

2015.04.15 20:34:29 3: stacktrace:
2015.04.15 20:34:29 3:     main::__ANON__                      called by FHEM/Blocking.pm (125)
2015.04.15 20:34:29 3:     main::BlockingInformParent          called by FHEM/Blocking.pm (94)
2015.04.15 20:34:29 3:     main::BlockingCall                  called by ./FHEM/73_PRESENCE.pm (530)
2015.04.15 20:34:29 3:     main::PRESENCE_StartLocalScan       called by fhem.pl (2574)
2015.04.15 20:34:29 3:     main::HandleTimeout                 called by fhem.pl (540)


Leider bin ich mit FHEM noch nicht so bewandert, als das ich damit etwas anfangen könnte.
Kann mir jemand helfen und sagen, was da nicht mehr funktioniert?

Viele Grüße
Ascos
1x RaspberryPi 3, HMUART, HMLAN
4x HM-CC-RT-DN, 4x HM-Sec-SCo, 4x HM-TC-IT-WM-W-EU, 1 Jeelink, 4 Lacrosse Fühler, 2 LD382A
1x ZBox mit Kodibuntu, mehrere schaltbare Steckdosen

Ascos

Ok, hat sich erledigt.
Habe gesehen, das in den Fehlermeldungen sehr oft die fhem.pl erwähnt wurde.
Nach einem weiteren Update Check heute sah ich, das die wieder aktualisiert werden kann.
Das habe ich getan und nun geht alles wieder.
1x RaspberryPi 3, HMUART, HMLAN
4x HM-CC-RT-DN, 4x HM-Sec-SCo, 4x HM-TC-IT-WM-W-EU, 1 Jeelink, 4 Lacrosse Fühler, 2 LD382A
1x ZBox mit Kodibuntu, mehrere schaltbare Steckdosen

Gueco315

Hallo,

H I L F E, ähnlich wie bei dem obigen Beitrag startet mein Fhem nach einer xrdp(Remote Desktop Installation) auf meinen Raspi 2 nicht mehr. Im Log steht:
2015.04.17 11:23:58 1: PERL ERROR: Can't locate object method "tid" via package "threads" at /usr/share/perl/5.14/XSLoader.pm line 95. 
Das Verzeichnis 5.14 gibt es bei mir nicht, nur 5.14.2. Was kann ich tun?
Habe das Paket xrdp mit remove gelöscht, hat aber nichts gebracht.
Fhem 6.0, JeeLink, CUL 868 auf Raspi 4, Buster, IT-1500, 4x SB_Player, Squeezebox auf Raspi 4, 3x Fritzbox,  WIFI Light, EGPM2LAN, ENIGMA, Sec-SCO,CC-RT-DN,TC-IT-WM-W-EU,SEN-Wa-Od,ES-PMSw1-PW,HM-SE, Sonoff, Shelly,SMA