ioBroker Absturz um 0.00 Uhr
-
2023-03-17 22:44:50.111 - info: bsblan.0 (524) Sending write request for bsblan.0.Betriebsart_(700) (value: 2) 2023-03-17 22:45:00.035 - info: host.iobroker instance system.adapter.ical.1 started with pid 14356 2023-03-17 22:45:00.738 - warn: fullybrowser.0 (539) updateDeviceERROR 192.168.40.124 2023-03-17 22:45:10.737 - info: host.iobroker instance system.adapter.ical.1 terminated with code 0 (NO_ERROR) 2023-03-17 22:50:03.171 - info: iot.0 (671) Connection changed: disconnect 2023-03-17 22:50:03.173 - info: iot.0 (671) Connection lost 2023-03-17 22:50:08.512 - info: iot.0 (671) Connection changed: connect 2023-03-17 22:54:50.422 - info: bsblan.0 (524) Sending write request for bsblan.0.Betriebsart_(700) (value: 2) 2023-03-17 23:30:10.827 - warn: fullybrowser.0 (539) updateDeviceERROR 192.168.40.124 2023-03-17 23:30:10.873 - info: host.iobroker instance system.adapter.ical.1 terminated with code 0 (NO_ERROR) 2023-03-17 23:45:00.033 - info: host.iobroker instance system.adapter.ical.1 started with pid 18620 2023-03-17 23:45:02.358 - warn: fullybrowser.0 (539) updateDeviceERROR 192.168.40.124 2023-03-17 23:45:10.939 - info: host.iobroker instance system.adapter.ical.1 terminated with code 0 (NO_ERROR) 2023-03-17 23:45:15.847 - warn: fullybrowser.0 (539) updateDeviceERROR 192.168.40.124 -
-
@haselchen sagte in ioBroker Absturz um 0.00 Uhr:
Hm, okay, ich hab den Eintrag in dem Pfad nicht
oder :
root@iobrokerv6:/opt/iobroker/node_modules/winston-daily-rotate-file# ls -lh total 40K -rw-rwxr-- 1 iobroker iobroker 11K Jul 5 2022 daily-rotate-file.js -rw-rwxr-- 1 iobroker iobroker 4,3K Jul 5 2022 index.d.ts -rw-rwxr-- 1 iobroker iobroker 192 Jul 5 2022 index.js -rw-rwxr-- 1 iobroker iobroker 1,1K Jul 5 2022 LICENSE -rw-rwxr-- 1 iobroker iobroker 1,2K Jul 5 2022 package.json -rw-rwxr-- 1 iobroker iobroker 6,0K Jul 5 2022 README.md -
23.45 bis 0:00 ist nichts im log.
-
-
@andyf2000 sagte in ioBroker Absturz um 0.00 Uhr:
2023-03-17 23:30:10.873 - info: host.iobroker instance system.adapter.ical.1 terminated with code 0 (NO_ERROR)
2023-03-17 23:45:10.939 - info: host.iobroker instance system.adapter.ical.1 terminated with code 0 (NO_ERROR)
Ändert sich dein Kalender jede 15 Minuten , weil du Ihn so abfragst !?
Hast du auch bei anderen Adapter - Instanzen es so eingestellt ...!?
-
Ich denke wir haben den Übeltäter
https://github.com/ioBroker/ioBroker.js-controller/issues/2092
closed ioBroker crashes during log file rotation #2092
-
das kommt mir bekannt vor - klingt so wie mein Fehler
-
Es IST Dein Fehler
Hab ins Issue dort geschrieben.
Musste auf Abhilfe warten.
Vermutlich mit der nächsten JS Controller Version. -
Danke fürs recherchieren und suchen.
-
@haselchen Irgendwie gleicht das Problem oben dem Problem, das bei mir gerade mehrfach in den letzten Wochen aufgeschlagen ist. Ca. alle 14 Tage um 0:00 Uhr hängt sich mein ioBroker (latest-V9 im Container Manager auf Synology mit JS-Controller 5.0.16) auf, ist nicht mehr über die Weboberfläche ansprechbar und schreibt keine Daten mehr in die InfluxDB. Nach Neustart funktioniert ioBroker wieder für ein paar Tage.
Beim Googeln bin ich auf diesen Thread gestoßen, hilft mir aber auch gerade nicht weiter.
Was kann ich machen?
2023/11/28 00:00:01,stdout,} 2023/11/28 00:00:01,stdout, path: [32m'/opt/iobroker/log/iobroker.2023-11-27.log'[39m 2023/11/28 00:00:01,stdout," code: [32m'ENOENT'[39m," 2023/11/28 00:00:01,stdout," syscall: [32m'unlink'[39m," 2023/11/28 00:00:01,stdout," errno: [33m-2[39m," 2023/11/28 00:00:01,stdout,[90m at node:internal/fs/streams:421:7[39m { 2023/11/28 00:00:01,stdout,[90m at node:internal/fs/streams:465:5[39m 2023/11/28 00:00:01,stdout,[90m at onwrite (node:internal/streams/writable:480:7)[39m 2023/11/28 00:00:01,stdout,[90m at afterWrite (node:internal/streams/writable:507:3)[39m 2023/11/28 00:00:01,stdout,[90m at finishMaybe (node:internal/streams/writable:733:9)[39m 2023/11/28 00:00:01,stdout,[90m at finish (node:internal/streams/writable:748:10)[39m 2023/11/28 00:00:01,stdout,[90m at WriteStream.emit (node:domain:489:12)[39m 2023/11/28 00:00:01,stdout,[90m at WriteStream.emit (node:events:529:35)[39m 2023/11/28 00:00:01,stdout, at WriteStream.<anonymous> [90m(/opt/iobroker/[39mnode_modules/[4mwinston-daily-rotate-file[24m/daily-rotate-file.js:140:28[90m)[39m 2023/11/28 00:00:01,stdout,[90m at Object.unlinkSync (node:fs:1883:3)[39m 2023/11/28 00:00:01,stdout,"Error: ENOENT: no such file or directory, unlink '/opt/iobroker/log/iobroker.2023-11-27.log'" 2023/11/28 00:00:01,stdout, at node:internal/fs/streams:421:7 2023/11/28 00:00:01,stdout, at node:internal/fs/streams:465:5 2023/11/28 00:00:01,stdout, at onwrite (node:internal/streams/writable:480:7) 2023/11/28 00:00:01,stdout, at afterWrite (node:internal/streams/writable:507:3) 2023/11/28 00:00:01,stdout, at finishMaybe (node:internal/streams/writable:733:9) 2023/11/28 00:00:01,stdout, at finish (node:internal/streams/writable:748:10) 2023/11/28 00:00:01,stdout, at WriteStream.emit (node:domain:489:12) 2023/11/28 00:00:01,stdout, at WriteStream.emit (node:events:529:35) 2023/11/28 00:00:01,stdout, at WriteStream.<anonymous> (/opt/iobroker/node_modules/winston-daily-rotate-file/daily-rotate-file.js:140:28) 2023/11/28 00:00:01,stdout, at Object.unlinkSync (node:fs:1883:3) 2023/11/28 00:00:01,stdout,"Error: ENOENT: no such file or directory, unlink '/opt/iobroker/log/iobroker.2023-11-27.log'" 2023/11/28 00:00:01,stdout,"ENOENT: no such file or directory, unlink '/opt/iobroker/log/iobroker.2023-11-27.log'"
