Serial node glitch under docker ?!

Hello to all.

Since a few weeks, I have been focusing my flows on NR docker.
I am using the serial node I/O and I am experiencing random faults on this port since this change.
Moreover it runs in an orangePi. So a different architecture :thinking:

When NR was fully installed, I never had any communication problems with the USB/Serial port of a rapsberry Pi3+

So maybe it's due to docker or orangepi.

I know it's not a Nodered specific problem but if you have any ideas on how to debug this, I'd love to hear from you. I'm interested.

Here is what I find in the logs.

10 Jun 09:06:54 - [info] Starting flows
10 Jun 09:06:56 - [info] Started flows
10 Jun 09:06:56 - [info] serial port /dev/tty-onduleur opened at 2400 baud 8N1
10 Jun 09:06:56 - [info] [mqtt-broker:MQTT-Onduleur] Connected to broker: mqtt://mosquitto:1883
10 Jun 09:28:07 - [error] serial port /dev/tty-onduleur closed unexpectedly
10 Jun 09:28:22 - [info] serial port /dev/tty-onduleur opened at 2400 baud 8N1

If you look in syslog at that time (assuming the OS has a syslog) at that time do you see anything relevant?

Hello Colin

Thanks for pointing me to this system log file

I didn't know this log existed, here it is at the time of the problem with the serial port. Does it give an explanation?
This looks like a hardware problem.

Jun 10 09:25:01 Onduleur CRON[32154]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun 10 09:28:07 Onduleur kernel: [19664.593380] usb usb7-port1: disabled by hub (EMI?), re-enabling...
Jun 10 09:28:07 Onduleur kernel: [19664.593405] usb 7-1: USB disconnect, device number 4
Jun 10 09:28:07 Onduleur kernel: [19664.593780] cp210x ttyUSB0: failed set request 0x7 status: -19
Jun 10 09:28:07 Onduleur kernel: [19664.593793] cp210x ttyUSB0: failed set request 0x12 status: -19
Jun 10 09:28:07 Onduleur kernel: [19664.593800] cp210x ttyUSB0: failed set request 0x0 status: -19
Jun 10 09:28:07 Onduleur kernel: [19664.594137] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Jun 10 09:28:07 Onduleur kernel: [19664.594205] cp210x 7-1:1.0: device disconnected
Jun 10 09:28:07 Onduleur kernel: [19664.927352] usb 7-1: new full-speed USB device number 5 using ohci-platform
Jun 10 09:28:07 Onduleur kernel: [19665.155736] usb 7-1: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Jun 10 09:28:07 Onduleur kernel: [19665.155750] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 10 09:28:07 Onduleur kernel: [19665.155757] usb 7-1: Product: CP2102 USB to UART Bridge Controller
Jun 10 09:28:07 Onduleur kernel: [19665.155763] usb 7-1: Manufacturer: Silicon Labs
Jun 10 09:28:07 Onduleur kernel: [19665.155768] usb 7-1: SerialNumber: 0001
Jun 10 09:28:07 Onduleur kernel: [19665.159954] cp210x 7-1:1.0: cp210x converter detected
Jun 10 09:28:07 Onduleur kernel: [19665.170927] usb 7-1: cp210x converter now attached to ttyUSB0
Jun 10 09:28:59 Onduleur systemd[1]: run-docker-runtime\x2drunc-moby-0ae3e6830707fbbcc46e3f206fe7715ff33b9a6630ab39219fc7f4fd1231323d-runc.JvwIPh.mount: Suc$
Jun 10 09:28:59 Onduleur systemd[1]: run-docker-runtime\x2drunc-moby-f1826b9468740d7ff3fbaa667fe7422bbc530aaa83a28abe249e63532d327794-runc.3LxV9a.mount: Suc$
Jun 10 09:30:01 Onduleur CRON[1687]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
Jun 10 09:35:01 Onduleur CRON[3863]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun 10 09:43:19 Onduleur webhook[555]: [webhook] 2021/06/10 09:43:19 Started GET /hooks/oled-status
Jun 10 09:43:19 Onduleur webhook[555]: [webhook] 2021/06/10 09:43:19 [b261fc] incoming HTTP request from 172.18.0.5:42416

I think the USB disconnect message is the key one. I don't know how that might relate to docker though, if it does. I think you might have to try an orange pi forum, if there is one.

indeed googling "disabled by hub (EMI?), re-enabling..." would seem to indicate some sort of hardware level fault causing it to reset...

Yes I looked at that too.
I'll switch back to the raspberry and look for it later.
The OrangePi forum is not very active.
Thanks to you guys