[LCDProc] - Could not read config file
-
I helped improve this package with my limited skills and time back in 2.1 but now in 2.2 it will only work somewhat if I do those commands you did to get it working. Specify a config in the /conf folder that I moved not in the normal location. Glad to see it doing something but not 100% normal looking.
I run a crystal fonts 735 display
-
@Steve and Topper, maybe we can put our heads together and fix this package
-
I am not that good at fixing it.. I need to relearn since I forgot a few things over the years
I don't know the new php stuff they just changed to in new version .. never used before.. -
What did you update from/to? What method were you using to start lcdd?
Steve
-
The lcdproc_client.php does not even start after the last three updates. It looks like the client is unable to connect, but this is bullshit because the other client /usr/pbi/lcdproc-i386/bin/lcdproc works like a treat.
Hm, it looks like i also found a bug in the php file. :)
[2.2-RC][admin@pfsense.localdomain]/root: /usr/bin/nice -20 /usr/local/bin/php -f /usr/local/pkg/lcdproc_client.php Warning: fsockopen(): unable to connect to localhost:13666 (Operation timed out) in /usr/local/pkg/lcdproc_client.php on line 915 Warning: stream_set_timeout() expects parameter 1 to be resource, boolean given in /usr/local/pkg/lcdproc_client.php on line 916
-
Using the lcdproc or lcdproc-dev package? What hardware?
Steve
-
I use lcdproc-dev and my hardware is a Watchguard X1000. I found something strange in the file LCDd.conf, the path to the drivers seem to be wrong.
LCDd.conf
[server] DriverPath=/usr/local/lib/lcdproc/ Driver=sdeclcd Bind=127.0.0.1 Port=13666 ReportLevel=3 ReportToSyslog=yes User=nobody Foreground=no ServerScreen=no GoodBye="Thanks for using" GoodBye=" pfSense " WaitTime=5 PrevScreenKey=Down NextScreenKey=Up [menu] MenuKey=Left EnterKey=Right UpKey=Up DownKey=Down [sdeclcd]
It seems to work after I changed the path to the following. I rebooted my firewall several times and no problem whatsoever with the lcdproc_client.php.
DriverPath=/usr/pbi/lcdproc-i386/local/lib/lcdproc/
-
I'm using /usr/local/lib/lcdproc/ and it's working fine. I'm not using the php client though.
The path to the driver cannot affect the client directly but it could stop the daemon running. Did you see the lcdproc server start?Steve
-
I have no drivers in this path, only in /usr/pbi/lcdproc-i386/local/lib/lcdproc/. The lcdproc started, I can see that in the LCD display and with the ps command.
-
I have no drivers there either. It shouldn't matter because the PBI system is supposed to take care of that. When you call the LCDd executable it is actually a link to file within the PBI subdirectories. From there the relative path results in the location you are entering.
Was LCDd starting before you changed the driver path?
Steve
-
My LCD started every time before i changed the path, except that the display showed zero screens (the LCD screen showed only LCDproc Server Cli: 0 Scr: 0).
The only problem for now, if the service dies I cannot simply restart it to get the displays back. In the previous pfSense version, I just ran the following script to solve the problem. Now I only get the message unable to connect to localhost:13666.
/usr/local/etc/rc.d/lcdproc.sh restart
-
Have you read the rest of this thread where I talked about having to use a different startup procedure? I suspect that if you're still using the package method you probably have two copies of LCDd running on different ports one of which isn't responding.
Steve
-
Only one process when i ran this command.
[2.2-RC][admin@pfsense.localdomain]/root: pgrep -anx LCDd 70130
Something changed in one of the latest updates, now I cannot restart the service like before. The only way to get the screens back is to reboot pfsense.
[2.2-RC][admin@pfsense.localdomain]/root: /usr/local/etc/rc.d/lcdproc.sh restart [2.2-RC][admin@pfsense.localdomain]/root: Warning: fsockopen(): unable to connect to localhost:13666 (Operation timed out) in /usr/local/pkg/lcdproc_client.php on line 915 Warning: stream_set_timeout() expects parameter 1 to be resource, boolean given in /usr/local/pkg/lcdproc_client.php on line 916
-
I disabled the firewall with the following command, but it is not possible to connect to localhost.
'pfctl -d
Everything works as expected after that I changed the LCDd daemon to listen on the LAN IP address and the client to connect to the same address.
Edit:
I permanently fixed the problem by editing the following file.
/usr/local/pkg/lcdproc.inc
define('LCDPROC_HOST','localhost'); define('LCDPROC_PORT','13666');
My changes: See line 36
define('LCDPROC_HOST','127.0.0.1'); define('LCDPROC_PORT','13666');
-
I made those code changes in /usr/local/pkg/lcdproc.inc and changes in the LCDd.conf file.
I am using LCDproc-dev
DriverPath=/usr/pbi/lcdproc-amd64/local/lib/lcdproc
This is where my drivers are in the 64 bit version.
When I start the service I get
Could not read config file: /usr/local/etc/LCDd.conf
Critical error while processing settings, abort.but I have the file there. It has 644 permissions to the Proxy group
I get nothing back when I run pgrep -anx LCDd
I ran the service by
/usr/local/etc/rc.d/lcdproc.sh restartand got
Could not read config file: /usr/local/etc/LCDd.conf
Critical error while processing settings, abort.Warning: fsockopen(): unable to connect to 127.0.0.1:13666 (Operation timed out) in /usr/local/pkg/lcdproc_client.php on line 915
Warning: stream_set_timeout() expects parameter 1 to be resource, boolean given in /usr/local/pkg/lcdproc_client.php on line 916
If someone gets me the fix code I will put it into the version and have it merged so it will be updated for everyone
-
When I start the service I get
Could not read config file: /usr/local/etc/LCDd.confFor some reason the conf file must be located in the following path.
32-bit
/usr/pbi/lcdproc-i386/local/etc/
64-bit
/usr/pbi/lcdproc-amd64/local/etc
-
More accurately you can put the conf file anywhere but /usr/local/etc because if you do LCDd will look in the wrong place. This appears to be an issue with the pbi packaging.
Steve
-
Has someone started to work on this or not.. I wish I had this working.. if working i might spend some effort to make some new features for it
-
BUMP
-
Not much motivation since it works fine if you don't use the php client and move the config file, which is how I'm running it. ;)
Since this appears to be a PBI problem do we have a link to some PBI docs? pfSense is moving away from PBIs in the future so it may be solved by that anyway.
Steve