[vz-users] plötzlicher logging stop

[René W]

Hallo,
der vzlogger Dienst lief nicht. Werde das aber beim nächsten Stopp
verifizieren. Hier der relevante auszug aus der syslog:

> Dec  6 22:56:01 raspberrypi CRON[31020]: (root) CMD (/root/bin/get1wire.pl
> >/dev/null 2>&1)
> Dec  6 22:57:01 raspberrypi CRON[31032]: (root) CMD (/root/bin/get1wire.pl
> >/dev/null 2>&1)
> Dec  6 22:57:34 raspberrypi kernel: [391791.845030] cp210x ttyUSB0:
> usb_serial_generic_read_bulk_callback - urb stopped: -32
> Dec  6 22:57:34 raspberrypi kernel: [391791.845140] cp210x ttyUSB0:
> usb_serial_generic_read_bulk_callback - urb stopped: -32
> Dec  6 22:57:34 raspberrypi kernel: [391792.050923] usb 1-1.4: USB
> disconnect, device number 4
> Dec  6 22:57:34 raspberrypi kernel: [391792.051582] cp210x ttyUSB0: failed
> set request 0x7 status: -19
> Dec  6 22:57:34 raspberrypi kernel: [391792.051605] cp210x ttyUSB0: failed
> set request 0x12 status: -19
> Dec  6 22:57:34 raspberrypi kernel: [391792.051616] cp210x ttyUSB0: failed
> set request 0x0 status: -19
> Dec  6 22:57:34 raspberrypi kernel: [391792.052069] cp210x ttyUSB0: cp210x
> converter now disconnected from ttyUSB0
> Dec  6 22:57:34 raspberrypi kernel: [391792.052214] cp210x 1-1.4:1.0:
> device disconnected
> Dec  6 22:57:34 raspberrypi systemd[1]: vzlogger.service: Main process
> exited, code=killed, status=11/SEGV
> Dec  6 22:57:34 raspberrypi systemd[1]: vzlogger.service: Failed with
> result 'signal'.
> Dec  6 22:57:35 raspberrypi kernel: [391792.352397] usb 1-1.4: new
> full-speed USB device number 6 using dwc_otg
> Dec  6 22:57:35 raspberrypi kernel: [391792.487166] usb 1-1.4: New USB
> device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
> Dec  6 22:57:35 raspberrypi kernel: [391792.487180] usb 1-1.4: New USB
> device strings: Mfr=1, Product=2, SerialNumber=3
> Dec  6 22:57:35 raspberrypi kernel: [391792.487190] usb 1-1.4: Product:
> CP2104 USB to UART Bridge Controller
> Dec  6 22:57:35 raspberrypi kernel: [391792.487200] usb 1-1.4:
> Manufacturer: Silicon Labs
> Dec  6 22:57:35 raspberrypi kernel: [391792.487209] usb 1-1.4:
> SerialNumber: 01066A08
> Dec  6 22:57:35 raspberrypi kernel: [391792.488919] cp210x 1-1.4:1.0:
> cp210x converter detected
> Dec  6 22:57:35 raspberrypi kernel: [391792.492252] usb 1-1.4: cp210x
> converter now attached to ttyUSB0
> Dec  6 22:57:35 raspberrypi mtp-probe: checking bus 1, device 6:
> "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
> Dec  6 22:57:35 raspberrypi mtp-probe: bus: 1, device: 6 was not an MTP
> device
> Dec  6 22:57:35 raspberrypi mtp-probe: checking bus 1, device 6:
> "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
> Dec  6 22:57:35 raspberrypi mtp-probe: bus: 1, device: 6 was not an MTP
> device
> Dec  6 22:58:01 raspberrypi CRON[31050]: (root) CMD (/root/bin/get1wire.pl
> >/dev/null 2>&1)
> Dec  6 22:59:01 raspberrypi CRON[31073]: (root) CMD (/root/bin/get1wire.pl
> >/dev/null 2>&1)
> Dec  6 22:59:22 raspberrypi dhcpcd[571]: eth0: DHCPv6 REPLY: in stateless
> mode
> Dec  6 23:00:01 raspberrypi CRON[31094]: (pi) CMD (php /var/www/
> volkszaehler.org/bin/aggregate run -m delta -l minute >/dev/null)
> Dec  6 23:00:01 raspberrypi CRON[31095]: (root) CMD (
> PATH="$PATH:/usr/local/bin/" pihole updatechecker local)
> Dec  6 23:00:01 raspberrypi CRON[31097]: (root) CMD (/root/bin/get1wire.pl
> >/dev/null 2>&1)
> Dec  6 23:01:01 raspberrypi CRON[31136]: (pi) CMD (php /var/www/
> volkszaehler.org/bin/aggregate run -m delta -l hour >/dev/null)
> Dec  6 23:01:01 raspberrypi CRON[31137]: (root) CMD (/root/bin/get1wire.pl
> >/dev/null 2>&1)
> Dec  6 23:02:01 raspberrypi CRON[31159]: (root) CMD (/root/bin/get1wire.pl
> >/dev/null 2>&1)
>

Am Mo., 9. Dez. 2019 um 08:34 Uhr schrieb Andreas Goetz <cpuidle at gmail.com>:

> Dein Screenshot ist unleserlerlich. Läuft der Daemon Prozess nich wenn das
> log stoppt?
>
> Am 09.12.2019 um 07:14 schrieb René W. <tylonhh at gmail.com>:
>
> 
>
> Guten Morgen,
>
>
>
> mein vzlogger hat nun zum zweiten mal getoppt zu loggen. Es läuft über ein
> RPi3 mit externer Synology Datenbank. Nach einem reboot oder manuellen
> Start des Dienstes läuft der Log weiter. Im frontend sind aber Lücken zu
> sehen.
>
> Da der verbose debug recht niedrig ist, habe ich hier eine log ausm
> /var/log/sys.log
>
> <F59D64FD9B984906BE521F9A5F7F7D59.jpg>
>
>
>
> Ich werde da nicht ganz schlau daraus und was ich als nächstes machen
> sollte. Könnt ihr mir helfen?
>
>
>
> Gruß René
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://demo.volkszaehler.org/pipermail/volkszaehler-users/attachments/20191209/4d0dadfa/attachment.html>