[LCDProc] - Could not read config file

djmixman · Nov 5, 2014, 1:47 AM

No matter what I do I can not get lcdproc to start. If I try to launch it from the services menu it just says "Stopped"

Even after dropping to the shell, manually updating config file to reflect new lib paths, and trying to launch it with command line parms I get:


[2.2-BETA][root@rt1.atx1.local]/usr/local/etc(305): ls -l
-rw-r--r--  1 root  wheel   700 Nov  4 19:24 LCDd.conf

[2.2-BETA][root@rt1.atx1.local]/usr/pbi/lcdproc-amd64/bin(282): ./LCDd
Could not read config file: /usr/local/etc/LCDd.conf
Critical error while processing settings, abort.

[2.2-BETA][root@rt1.atx1.local]/usr/local/etc(290): LCDd -d curses -f -a 127.0.0.1 -p 13666 -u nobody -w 5
Could not read config file: /usr/local/etc/LCDd.conf
Critical error while processing settings, abort.

[2.2-BETA][root@rt1.atx1.local]/usr/local/etc(291): LCDd -c null -d curses -f -a 127.0.0.1 -p 13666 -u nobody -w 5
Could not read config file: null
Critical error while processing settings, abort.

I have no idea what else I can do to help and i'm not sure if it would fix these problems or not, but is it possible that lcdproc could get updated to the latest version, 0.5.7, as of this posting…

charliem · Nov 6, 2014, 9:25 PM

Which did you install LCDproc or LCDproc-dev?

I don't have the HW to test properly, but the LCDproc-dev installed OK for me. When I start it, it fails gracefully because it cannot find the bogus hardware I configured. Webgui gets it right, showing it's not running.

But /usr/local/etc/LCDd.conf definitely exists, is readable, and has correct-looking content in my tests.

Can 'cat /usr/local/etc/LCDd.conf'?

~~I did notice that lcdproc does show up in the status_services.php page, but not in the services widget on the dashboard page.~~ <– seems it shows up on the widget if you tick 'enable at startup', but shows up in status_services in either case.

Also, the latest seems to be 0.5.6 according to the links on the pfsense package page, not sure where you are seening 0.5.7.

stephenw10 · Nov 6, 2014, 9:48 PM

0.5.6 is the latest lcdproc stable release but there is a 0.5.7 version avilable. It hasn't made it into a pfSense package yet though.

When you first install the lcdproc package it will not run at all until you have configured both a hardware type and some screens. Doing that generates the rc files required to start it.

Steve

djmixman · Nov 8, 2014, 9:06 PM

@charliem:

Which did you install LCDproc or LCDproc-dev?

I have tried both versions in the pfsense package system.

@charliem:

Can 'cat /usr/local/etc/LCDd.conf'?


Running ls -l /usr/local/etc/LCD*

-rw-r--r--  1 root  wheel  627 Nov  8 14:32 /usr/local/etc/LCDd.conf
-rwxr-xr-x  1 root  wheel  627 Nov  4 19:04 /usr/local/etc/LCDd.conf.orig

Running LCDd

Could not read config file: /usr/local/etc/LCDd.conf
Critical error while processing settings, abort.

Cat /usr/local/etc/LCDd.conf
[server]
DriverPath=/usr/local/lib/lcdproc/
Driver=hd44780
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
ToggleRotateKey=Enter
PrevScreenKey=Left
NextScreenKey=Right
ScrollUpKey=Up
ScrollDownKey=Down
[menu]
MenuKey=Escape
EnterKey=Enter
UpKey=Up
DownKey=Down
[hd44780]
driverpath=/usr/local/lib/lcdproc/
ConnectionType=mplay
Device=/dev/ugen1.2
Port=0x378
Speed=0
Keypad=yes
Contrast=850
Brightness=800
OffBrightness=0
Backlight=yes
OutputPort=no
Charmap=hd44780_default
DelayMult=1
DelayBus=true
Size=20x2

@stephenw10:

When you first install the lcdproc package it will not run at all until you have configured both a hardware type and some screens. Doing that generates the rc files required to start it.

I've clicked and unclicked stuff in both tabs in the menu.. Nothing I do makes a difference when trying to launch LCDd.. :(

Here are the screen shots of my configuration:
http://i.imgur.com/Lg9oPD5.png and http://i.imgur.com/CNQOahW.png

Edit:
I've also tried this:


[2.2-BETA][root@rt1.atx1.local]/usr/local/etc(62): LCDd -c LCDd.conf

Could not read config file: LCDd.conf
Critical error while processing settings, abort.

[2.2-BETA][root@rt1.atx1.local]/usr/local/etc(63): cat LCDd.conf

[Server]
DriverPath=/usr/pbi/lcdproc-amd64/lib/lcdproc/
Driver=text
Bind=127.0.0.1
Port=13666
ReportLevel=5
ReportToSyslog=no
User=nobody
Foreground=yes
Hello="This is a"
Hello="test!"
WaitTime=4
AutoRotate=yes
ServerScreen=yes
Backlight=on
Heartbeat=on

[text]
Size=20x4

stephenw10 · Nov 9, 2014, 3:13 PM

Are you running all of this on 2.2beta 64bit?

Steve

charliem · Nov 9, 2014, 3:14 PM

Are you sure that's the right endpoint and device number?

Can you increase the debug output level with "-r 5"? (Do it on the command line; setting it in the config file won't work if the file is not found or processed correctly).

Also, when you try running it from the command line, put in the full path to the config file with the -c argument.

djmixman · Nov 13, 2014, 3:58 PM

@stephenw10:

Are you running all of this on 2.2beta 64bit?

Steve

Yes.. 2.2 beta, 64bit…

[2.2-BETA][root@rt1.atx1.local]/var/log(67): uname -a
FreeBSD rt1.atx1.local 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #28 30e366f(HEAD)

Version 2.2-BETA (amd64)
built on Fri Sep 19 23:21:59 CDT 2014
FreeBSD 10.1-PRERELEASE

@charliem:

Are you sure that's the right endpoint and device number?

I've tried text, curses and the driver for my LCD and all give the same error…

@charliem:

Can you increase the debug output level with "-r 5"? (Do it on the command line; setting it in the config file won't work if the file is not found or processed correctly).

Also, when you try running it from the command line, put in the full path to the config file with the -c argument.

It does not matter if I put anything on the command line or use full paths I still get the same "Could not read config file:" Even when doing -r 5 on the command line I do not get any additional information. Seems to completely ignore what I tell it..

charliem · Nov 13, 2014, 6:00 PM

@djmixman:

[2.2-BETA][root@rt1.atx1.local]/var/log(67): uname -a
FreeBSD rt1.atx1.local 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #28 30e366f(HEAD)

Version 2.2-BETA (amd64)
built on Fri Sep 19 23:21:59 CDT 2014
FreeBSD 10.1-PRERELEASE

Long shot, but try a newer beta version. Today's snapshot uses FreeBSD 10.1 Release; you are using an early prerelease, and there've been quite a few FreeBSD changes since then. If you have the resources, you could see if you could duplicate the problem on a VM with either a fresh pfSense or a vanilla FreeBSD 10.1 image.

stephenw10 · Nov 15, 2014, 12:32 AM

Ok, I've tested this using a recent snapshot and I was able to start it.
How are you generating the LCDd.conf file?

Steve

chpalmer · Nov 15, 2014, 5:16 AM

@stephenw10:

Ok, I've tested this using a recent snapshot and I was able to start it.
How are you generating the LCDd.conf file?

Steve

64 bit or 32?

[2.2-BETA][admin@testbox.labbox]/root: LCDd -c /usr/local/etc/LCDd.conf
Could not read config file: /usr/local/etc/LCDd.conf
Critical error while processing settings, abort.

My LCDd.conf file already existed and compares exactly to the one you attached in the hardware thread.

stephenw10 · Nov 15, 2014, 9:15 AM

64bit.

jjstecchino · Nov 24, 2014, 5:04 AM

Same here. latest 2.2 beta i386. Same error. recreated LCDd.conf by hand using vi. permission are ok. LCDd cannot read config file. Very weird.

stephenw10 · Nov 24, 2014, 12:52 PM

Using the dev package?

Steve

jjstecchino · Nov 25, 2014, 3:05 AM

Yup.
Need dev to drive the firebox display. Having said that, I tried the non dev version of the package. LCDd is same version and it cannot read the config file too. not in the /usr/local/etc directory or doesn't matter if I create the config anywhere else. Tried with the config created by pfsense and also recreated it from scratch using vi. even chmod 777 the file just to make sure it did not need write privileges on the file. My pfsense is i386 since it is on a firebox x-core-e.
This is too bad as I have the firebox all tweaked up on 2.2. NICs blinking right, your fan control and status light program working like a charm and even IPV6 with 6RD now working. A working LCD is what is missing now.
I read on a previous post of yours that it is working for you. Was it a new install? My is an upgrade from 2.1. It shouldn't matter though. I wonder if LCDd is using some weird library that is screwing things up.

PS a big THANKS for the work you did to make a firebox an excellent pfsense platform for all of us

stephenw10 · Nov 25, 2014, 3:18 AM

Hmm. I updated my xtm5 today and after a couple of reboots the LCD came back up. It's running 64bit though.
I have the filesystem set to permanent read-write. I can't really see what bearing that might have here but it's an easy test.
I'll have to fire up my test x550e and put 2.2 on it.

Steve

jjstecchino · Nov 25, 2014, 4:37 AM

If you have time, let me know how it goes. I am curious. I think it is a problem with the LCDd executable. Wonder if a fresh install would help. Although a fresh install vs update should not make any difference.

stephenw10 · Nov 27, 2014, 11:53 AM

Ok, I upgraded my test X550e to todays snapshot (32bit obviously) 1G NanoBSD.

[2.2-BETA][root@pfSense.localdomain]/root: uname -a
FreeBSD pfSense.localdomain 10.1-RELEASE FreeBSD 10.1-RELEASE #0 29f4af5(releng/10.1)-dirty: Thu Nov 27 01:06:40 CST 2014     root@pfsense-22-i386-builder:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_wrap.10.i386  i386

After the upgrade the lcdproc-dev package was not re-installed installed because it's not signed. I set the allow unsigned packages check and installed lcdproc-dev and rebooted. It came back up no problem. I did nothing else. That's suing the same LCDd.conf file and Shellcmd instructions that were carried across the upgrade from 2.1.5.

It's working fine for me both 32 and 64bit.

Are you still seeing this problem?

Steve

jjstecchino · Nov 27, 2014, 8:51 PM

Still having the problem. In my case the package was reinstalled after upgrade from 2.1 (after that deleted and reinstalled numerous times). Where do you set to allow unsigned packages? I didn't have to do that and maybe this is the problem.
I am upgrading to Nov 27 snapshot so we are on the same version

stephenw10 · Nov 29, 2014, 9:01 PM

It's in System: Advanced: Miscellaneous:
If you don't have that checked it should fail the install in a pretty obvious way with authentication errors. The fact that yours didn't must surely be clue, or maybe that mine did. Perhaps you have a cached pbi? That shouldn't be possible on Nano though. Are you running Nano?

Steve

Edit: an obvious fail

jjstecchino · Nov 28, 2014, 4:38 AM

Yes, I had the install unsigned package already checked. I guess it carried over from the upgrade.
I am running nano 4gb i386.
At this point I guess the only thing left is to try a fresh install. Don't know if it is going to help. My understanding is that all of the freebsd comes with the new nano image, configuration file get upgraded to the new version and packages get reinstalled during upgrade. No system software other than what is in cf/media get carried over. I am puzzled to say the least.