LCDdProc seems to be broken on 25.07.1-RELEASE

timecode

Was getting hundreds of these messages in logs.

64880 lcdproc: Connection to LCDd process lost ()

Uninstalled the package and reinstalled it. Now it won't even start.
Anyone else seeing an issue with LCDd process?

Should mention, no more log entries however after the reinstall either.

timecode

Anther uninstall/reinstall and enabling and disabling of the package - seems to have sorted it. No weird logs either.
Odd. But it seems fixed.

fireodo

@timecode said in LCDdProc seems to be broken on 25.07.1-RELEASE:

Anyone else seeing an issue with LCDd process?

Yes. If you kill all states (on all interfaces - and specially on "lo0") you get flooded by these messages too ... (its the only way to reliable reproduce the fenomen ...)
In your case I suppose it was a "hiccup" ...

Regards,
fireodo

Edit: Just for information (as I understand the mecanism) The lcdproc package consist in 2 parts:

the LCDd daemon who makes the physical connection between the LCD-Panel and the hardware port (USB, Serial etc.) and established a Server (see: /usr/local/etc/LCDd.conf) that binds on:

Bind=127.0.0.1
Port=13666

the lcdproc client that establish a connection to that port (13666) and deliver informations from the pfsense to the LCD-Panel. If this connection (for whatevers reason) get lost, the client cannot reestablish that connection and it comes to the syslog flooding with those, up in the post, mentioned messages.

Edit: Could the culprit be in the code of "/usr/local/pkg/lcdproc_client.php" between line 389-398? My PHP-Skills are very poor ...

stephenw10

Mmm, it's working for me in 25.07.1 and 2.8.1-beta. Not seeing an issue currently.

fireodo

@stephenw10 said in LCDdProc seems to be broken on 25.07.1-RELEASE:

Mmm, it's working for me in 25.07.1 and 2.8.1-beta. Not seeing an issue currently.

Try (just for fun) to kill all states (Diagnostics -> States) on all interfaces ... or just on lo0 ...

stephenw10

Well, yeah, if you kill the connection between the client and server it does stop.

The interesting thing is that it doesn't just re-open the connection.

Resaving the Screens tab restarts the php client and opens a new connection.

fireodo

@stephenw10 said in LCDdProc seems to be broken on 25.07.1-RELEASE:

The interesting thing is that it doesn't just re-open the connection.

Yepp, thats what I dont understand neither and in the "/usr/local/pkg/lcdproc_client.php" script seams that the error reporting code-part is running wild ... (IMHO)

stephenw10

Mmm, it should increment the error counter until it reaches 3 and then restart the client but....

fireodo

@stephenw10 said in LCDdProc seems to be broken on 25.07.1-RELEASE:

Mmm, it should increment the error counter until it reaches 3 and then restart the client but....

Thats how I have read the code too ...

Edit: I had a other situation when after a reboot the lcdproc client floodet right after reboot the log and kill 9 or pkill nothing helped - I had to reboot again, then it stopped and get back to normal operation ... odd ...

Edit: This problem was raised also here: LCDproc

stephenw10

Ok let's continue there then. It's definitely not working as intended.