LCDproc Looses Connection - Restarting service Fixes but goes down again shortly after

[ngr2001]

PFSense+ 24.11-RELEASE
LCDproc 0.12_2

LCDproc is working just fine with my CrystalFontz LCD, however after what appears to be only a few hours, LCDproc looses its connection and the LCD stops displaying data. If I restart the LCDproc services everything starts working again. A few hours later the service looses connection again and the LCD goes dead.

Error In Log:

Config Below:

[elvisimprsntr]

@ngr2001

I use the following port.

USB COM port 1 (/dev/cuaUO)

[ngr2001]

@elvisimprsntr

I have a hunch that maybe resetting the firewall states breaks the LCDproc connection. I've been bouncing that a lot lately for some rule testing, perhaps this was self inflected. I will continue to monitor. I think the port is really tied to your specific hardware setup, but if it dies again ill give that a go for sure.

[elvisimprsntr]

@ngr2001

it's the same physical port just a different kernel driver. From what I read tty is for dial-in devices and cua is for dial-out devices.

[ngr2001]

@elvisimprsntr

Well you learn something new each day.

I flipped it, still works, ill leave it your way and see how it goes.

thanks.

[jimp]

Firewall states wouldn't affect LCDProc since it's not a TCP connection, it's local serial.

You should definitely be using cuaU0 or a cuaU<n> port, though, not a TTY.

I have LCDProc going on two systems, one with a crystalfontz display and another with an adafruit LCD+Backpack setup. Both work great and never lose connection.

[fireodo]

@jimp

Hi,

as far as I know the lcd driver (LCDd) is connected to the display via USB/Serial/Parallel but the lcdproc process is connected to the driver in this way:

Bind=127.0.0.1
Port=13666

Extract from pfctl -ss:

lo0 tcp 127.0.0.1:20639 -> 127.0.0.1:13666       ESTABLISHED:ESTABLISHED
lo0 tcp 127.0.0.1:13666 <- 127.0.0.1:20639       ESTABLISHED:ESTABLISHED

So there could be a possibility to loose connection when states get killed ... IMHO (If I'm wrong please correct)

EDIT: I cleared all states and this made the lcdproc also to loose connection flooding the syslog. After restarting lcdproc all fine again.

Regards,
fireodo

[stephenw10]

Yup the php client doesn't seem to be honouring the error count correctly. It should just reconnect when the state is closed. Digging...

[ngr2001]

@stephenw10

Also,

LCDProc seems to go bananas when my modem loses internet. If there is a provider outage and there is no WAN connection the display on LCDproc keeps rebooting itself in a loop. I typically have to reboot modem 1st and let that get all lit up. Then I have to reboot PFSense 2nd, otherwise stuff generally gets all squirely.

[jimp]

There is definitely an issue somewhere with LCDProc when a WAN goes offline and recovers. I've seen it end up with multiple client processes several times before. The problem is there is code which should be preventing that, and I can never reproduce it in the lab. It only seems to happen on my edge system, and never when I'm watching it.

[fireodo]

@jimp said in LCDproc Looses Connection - Restarting service Fixes but goes down again shortly after:

and I can never reproduce it in the lab.

Hi, if you go to Diagnostics -> States and kill all states you get the "running wild" and flooding syslog lcdproc-client.

(Maybe also of interest: LcdProc)

Regards,
fireodo