Fhem webserver plötzlich nicht mehr erreichbar

[spel]

Hallo,

seit heute irgendwann ist Fhem bei mir nicht mehr funktional. Keine Steuerung mehr, keine Erreichbarkeit des Webservers.

Code Auswählen Erweitern

Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-165-generic x86_64)

Code Auswählen Erweitern

user@fhem:~$ sudo systemctl status fhem
[sudo] password for user:
● fhem.service - FHEM Home Automation
     Loaded: loaded (/etc/systemd/system/fhem.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2023-10-29 23:41:29 CET; 2min 33s ago
    Process: 1288 ExecStart=/usr/bin/perl fhem.pl fhem.cfg (code=exited, status=0/SUCCESS)
   Main PID: 1303 (perl)
      Tasks: 1 (limit: 4510)
     Memory: 126.3M
     CGroup: /system.slice/fhem.service
             └─1303 /usr/bin/perl fhem.pl fhem.cfg

Oct 29 23:41:28 fhem systemd[1]: Starting FHEM Home Automation...
Oct 29 23:41:29 fhem systemd[1]: Started FHEM Home Automation.


Code Auswählen Erweitern

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
   1303 fhem      20   0  143088 138036  10260 R 100.0   3.5   2:59.79 perl


Code Auswählen Erweitern

2023.10.29 23:41:42 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2023.10.29 23:41:42 1: usb create starting
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS0
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS1
2023.10.29 23:41:42 1: PERL WARNING: can't getattr: Input/output error at ./FHEM/DevIo.pm line 598.
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS1: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS10
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS10: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS11
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS11: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS12
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS12: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS13
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS13: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS14
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS14: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS15
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS15: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS16
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS16: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS17
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS17: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS18
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS18: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS19
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS19: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS2
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS2: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS20
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS20: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS21
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS21: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS22
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS22: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS23
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS23: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS24
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS24: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS25
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS25: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS26
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS26: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS27
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS27: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS28
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS28: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS29
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS29: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS3
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS3: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS30
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS30: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS31
2023.10.29 23:41:42 1: CUL: Can't open /dev/ttyS31: Input/output error
2023.10.29 23:41:42 3: Probing CUL device /dev/ttyS5
2023.10.29 23:41:43 3: Probing CUL device /dev/ttyS6
2023.10.29 23:41:43 1: CUL: Can't open /dev/ttyS6: Input/output error
2023.10.29 23:41:43 3: Probing CUL device /dev/ttyS7
2023.10.29 23:41:43 1: CUL: Can't open /dev/ttyS7: Input/output error
2023.10.29 23:41:43 3: Probing CUL device /dev/ttyS8
2023.10.29 23:41:43 1: CUL: Can't open /dev/ttyS8: Input/output error
2023.10.29 23:41:43 3: Probing CUL device /dev/ttyS9
2023.10.29 23:41:43 1: CUL: Can't open /dev/ttyS9: Input/output error
2023.10.29 23:41:43 1: usb create end
2023.10.29 23:41:44 3: ledStripe01 low level cmd queue send ERROR 31000000ff000f3f, qlen 1 (reconnect giving up)
2023.10.29 23:41:44 0: Featurelevel: 6
2023.10.29 23:41:44 0: Server started with 304 defined entities (fhem.pl:24810/2021-07-29 perl:5.030000 os:linux user:fhem pid:1303)
2023.10.29 23:41:44 1: PERL WARNING: Argument "92,7" isn't numeric in multiplication (*) at ./FHEM/73_GasCalculator.pm line 1111.

Hier einige Auszüge. Augenscheinlich passt da was mit der CPU-Last und den seriellen Devices, CUL, nicht. Ich habe 3 USB Adapter per ser2net angebunden.
Dort scheint aber alles auf dem ser2net Gerät (Ubuntu Linux) aber alles zu laufen.

Neustarts etc. natürlich durchgeführt.

Meine Anlage steht still. Vielleicht kann mir hier jmd. aufgrund der o. g. Daten helfen.

Vielen Dank und
Gruß

[spel]

Und noch vom ser2net Host:

Code Auswählen Erweitern

user@usbhost:~$ systemctl status ser2net
● ser2net.service - LSB: Allows network connections to serial ports
     Loaded: loaded (/etc/init.d/ser2net; generated)
     Active: active (running) since Sun 2023-10-29 23:41:23 CET; 17min ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 1 (limit: 4333)
     Memory: 2.0M
     CGroup: /system.slice/ser2net.service
             └─763 /usr/sbin/ser2net -c /etc/ser2net.conf -P /run/ser2net.pid

Oct 29 23:41:22 usbhost systemd[1]: Starting LSB: Allows network connections to serial ports...
Oct 29 23:41:22 usbhost ser2net[698]:  * Starting Serial port to network proxy ser2net
Oct 29 23:41:23 usbhost ser2net[698]:    ...done.
Oct 29 23:41:23 usbhost systemd[1]: Started LSB: Allows network connections to serial ports.
Oct 29 23:41:31 usbhost ser2net[763]: Could not turn off break for device /dev/ttyACM0 port 2002: Broken pipe


[spel]

Hallo,

also geholfen hat jetzt ein:

Code Auswählen Erweitern

attr initialUsbCheck disable 1
aber was ist da falsch gelaufen..

Ausgabe nun vom ser2net Host:

Code Auswählen Erweitern

user@usbhost:~$ systemctl status ser2net
● ser2net.service - LSB: Allows network connections to serial ports
     Loaded: loaded (/etc/init.d/ser2net; generated)
     Active: active (running) since Sun 2023-10-29 23:41:23 CET; 21min ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 1 (limit: 4333)
     Memory: 2.0M
     CGroup: /system.slice/ser2net.service
             └─763 /usr/sbin/ser2net -c /etc/ser2net.conf -P /run/ser2net.pid

Oct 29 23:41:22 usbhost systemd[1]: Starting LSB: Allows network connections to serial ports...
Oct 29 23:41:22 usbhost ser2net[698]:  * Starting Serial port to network proxy ser2net
Oct 29 23:41:23 usbhost ser2net[698]:    ...done.
Oct 29 23:41:23 usbhost systemd[1]: Started LSB: Allows network connections to serial ports.
Oct 29 23:41:31 usbhost ser2net[763]: Could not turn off break for device /dev/ttyACM0 port 2002: Broken pipe
Oct 29 23:59:26 usbhost ser2net[763]: read error for port 2001: Connection reset by peer
Oct 30 00:00:25 usbhost ser2net[763]: Could not turn off break for device /dev/ttyACM0 port 2002: Broken pipe