Firebox LCD Driver for LCDProc

theeddie

seems the driver with the lcd time out disabled is gone

anyone got a copy, or maybe a driver with a 5 min timeout.

Topper727

2.2 RC 64 bit here and using crystalfontz 735 display but seems server starts with jimp's fix but not the client.. shows client 0 on screen.. I can start it manually with /usr/bin/nice -20 /usr/local/bin/lcdproc C T U & but not with gui in pfsense. so i lose the LED's I fixed while back showing status (the 4 on side that show CPU gateway and stuff) But I must say the options that show other things using the command line are much nicer then the package usually has. Wish they make it show this kind of info..

hornpipe2

Yeah, I've found that using the method to call via Shellcmd works for about 2 seconds… server starts, client connects, about the time the device is "creating RRD graphs" according to serial port. A few seconds later, boot completes, we get the startup jingle played, and the client dies.

Server stays running though.

You can then use the command manually to restart the client and it'll run forever. Not sure what causes it to die early in the startup...

EDIT: my eBay purchases came in, I got 1.4ghz SL6BY and 512MB now... just had to share ;D

stephenw10

The client is killed because there is still a startup script running when packages are restarted at that point that kills it. Check in /usr/local/ect/rc.d for an lcdproc.sh script that should be removed when you disable the options in the menu but sometimes isn't.

Steve

lharris428

Ever since the new LCDProc package was released it was working for me until I decided to change up some stuff… At first I thought it was because I had activated an interface OPT1 and then changed my mind and disabled it. I figured I had maybe messed up the firewall. Then changed changed my IP range of the LAN from 192.168.0.0/24 to 10.3.0.0/23, after that I noticed LCDProc wouldn't work anymore...even on a fresh install. Going to nuke the box again and do more testing. It's the old "LCDproc unable to connect to localhost:13666" issue coming back to haunt me... and it's aggravating.

With this latest reformat, the only thing I've done is set the IP range, installed shellcmd, aprwatch, and bandwidthd. Going to nuke the box again tomorrow and install LCDProc first. If that doesn't work, I'll nuke the box and install LCDProc again and set the LAN IP to 192.168.0.1 again.

I've been trying to read up on this thread and another that is currently retired. I assume the firewall can't actually interfere can it? Am I crazy here? Can anything I do to the LAN interface screw up LCDProc's server?

stephenw10

Is it trying to connect to IPv6 localhost?

Steve

lharris428

@stephenw10:

Is it trying to connect to IPv6 localhost?

Steve

I didn't think of that. You know, everytime the box asks me anything about IPv6, I just ignore it for now… so that could be it. I'll have to check that out or specify an IPv4 address in the conf or something. It's getting late, but I'll try that now.

lharris428

I just nuked the box and started over. I did absolutely nothing but enter in my pppoe credentials, completed the setup wizard, installed LCDProcDev, set parallel/driver in the config section and enabled some screens. I then rebooted to be sure and still no luck.

I stopped LCDProc at the services screen on the webpage and ran the commands below in SSH. I still have to learn about IPV6, but I don't have it enabled anywhere. This plugin still seems a bit flaky… any ideas?


[2.2-RELEASE][admin@pfSense.hnet.home]/usr/local/etc/rc.d: ps aux | grep LCD
[2.2-RELEASE][admin@pfSense.hnet.home]/usr/local/etc/rc.d: ./lcdproc.sh start
[2.2-RELEASE][admin@pfSense.hnet.home]/usr/local/etc/rc.d: ps aux | grep LCD
nobody  39082   0.0  0.1 10308  2072  -  SNs   3:50AM 0:00.00 /usr/local/sbin/LCDd -c /usr/pbi/lcdp
[2.2-RELEASE][admin@pfSense.hnet.home]/usr/local/etc/rc.d:
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

EDIT: I searched around between all the various LCDProc threads and I tried Borage's approach that is mentioned on post 70 of this thread - "[LCDProc] - Could not read config file" and it worked. So my question is, I am not setting up something right where "localhost" is not working? I am installing direct to HD which I mentioned how I did it via the firebox x550e thread here. I am just doing a simple install, so I don't understand what could be going wrong? Could it really be defaulting to IPv6 or something else whacky?

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');
« Last Edit: December 30, 2014, 11:47:23 am by Borage »

bennyc

Got it working, but a bit simpler.
-> System>Advanced>Networking>IPv6 Options: check Prefer IPv4 over IPv6
This got me a working LCDproc-dev on my x1250e with 2.2 and lcdproc-0.5.7_2 pkg v. 0.9.11. (before it simply crashed after service start)

stephenw10

The PHP client does seem to have that problem, in the dev package at least. The standard lcdproc client runs fine.

Steve

tozx

Hi everyone!
I have my WG Xtm505 with pfsense 2.2 on it. Everything is fine, but LCDProc won't work.

Mar 23 16:34:14	php-fpm[98065]: lcdproc: Stopping service: no com port selected
Mar 23 16:34:14	php-fpm[98065]: lcdproc: The chosen lcdproc driver is not a valid choice

But in settings I have (https://drive.google.com/file/d/0B7V4t4POELQwMlp6V2xvMkJOYlk/view?usp=sharing).
There is no such driver "watchguard" in drivers' list.

lcdproc-0.5.7_2 pkg.v.1.0.2

stephenw10

You have to use the lcdproc-dev package to get the sdeclcd driver.

Steve

tozx

@stephenw10:

You have to use the lcdproc-dev package to get the sdeclcd driver.

Steve

Thank you, Steve! But I was thinking that never version has a full pack of drivers =) (dev version is older than stable)

stephenw10

Yes, the dev version is now older that the original package. ::)
However it's still only the dev version that has the sdcelcd driver and the additional code to allow you to select it.

Steve

browntown

Updated to 2.2 with the fun hint pio4 change. Wasted an hour because I had my son reading the lines as I typed into putty and I kept on typing PI zero instead of oh.

I know better. I know what PIO is but I was tired. Anywho, got things running. Oddly wgxepc still works with shellcmd uninstalled, so it is in the start sequence even without it.

LCDproc-dev installed through the gui, and I have the clock I've always had, but the screen choices that I'm given in the gui don't show up. Odd. Posting then restarting…...

I'll be back.

Steve, merge the packages once and for all.

Because firebox in a suburban home office is completely rational:

![2015-03-28 23.11.59.jpg](/public/imported_attachments/1/2015-03-28 23.11.59.jpg)
![2015-03-28 23.11.59.jpg_thumb](/public/imported_attachments/1/2015-03-28 23.11.59.jpg_thumb)

stephenw10

I'm not the packager maintainer nor have I proven any good at packages so I don't think it would be great plan for me to do that. ;)
It would be nice for something to happen though I agree.

The shellcmd package just makes it easier to insert command into the config file much like the cron package. The commands are still there in the file and still get interpreted at boot. Technically you don't need the package at all.

Nice pic. :)

Steve

Guest

I like to piggy back on this since I have posted a similar topic concerning a NmediaPC Pro LCD. I am trying to follow what's going on in this thread but I'm getting lost.

SKiZZ

I am unable to get lcdproc dev to start on 2.2.6-RELEASE

Installed and uninstalled and re-installed package and still no go. Whats the proper way to install and config?
What should I be looking for?

SKiZZ

@SKiZZ:

I am unable to get lcdproc dev to start on 2.2.6-RELEASE

Installed and uninstalled and re-installed package and still no go. Whats the proper way to install and config?
What should I be looking for?

Looks like the config file may be missing, any ideas how to generate it?

chpalmer

Did you config the service and save?