Firebox LCD Driver for LCDProc
-
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?
-
Is it trying to connect to IPv6 localhost?
Steve
-
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.
-
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 »
-
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) -
The PHP client does seem to have that problem, in the dev package at least. The standard lcdproc client runs fine.
Steve
-
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
-
You have to use the lcdproc-dev package to get the sdeclcd driver.
Steve
-
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)
-
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
-
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) -
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
-
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.
-
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? -
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?
-
Did you config the service and save?
-
-
Is anyone else having issues with lcdproc-dev when disconnecting/reconnecting patch cables ?
It seems like everytime the link state changes it reloads the php lcdproc script and creates a ton of errors in my syslog. Simply restarting the service doesn't work, but killing all the php scripts from the console and restarting the service fixes the issue.
Typical errors I see after disconnecting/reconnecting a cable :
Feb 14 23:25:38 php: lcdproc: Failed to connect to LCDd process Connection reset by peer (54) Feb 14 23:25:38 php: lcdproc: Failed to connect to LCDd process Connection reset by peer (54) Feb 14 23:25:38 php: lcdproc: Failed to connect to LCDd process Connection reset by peer (54) Feb 14 23:25:38 php: lcdproc: Failed to connect to LCDd process Connection reset by peer (54) Feb 14 23:25:38 php: lcdproc: Failed to connect to LCDd process Connection reset by peer (54) Feb 14 23:25:38 php: lcdproc: Too many errors, the client ends. Feb 14 23:25:38 php: lcdproc: Too many errors, the client ends. Feb 14 23:25:38 php: lcdproc: Too many errors, the client ends. Feb 14 23:25:38 php: lcdproc: Too many errors, the client ends. Feb 14 23:25:38 php: lcdproc: Too many errors, the client ends. Feb 14 23:25:38 LCDd: Connect from host 127.0.0.1:27434 on socket 16 Feb 14 23:25:38 LCDd: Connect from host 127.0.0.1:33965 on socket 17 Feb 14 23:25:38 LCDd: Connect from host 127.0.0.1:60566 on socket 18 Feb 14 23:26:42 LCDd: Server shutting down on SIGTERM Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 LCDd: sock_send: socket write error Feb 14 23:26:42 php: lcdproc: Start client procedure. Error counter: (0) Feb 14 23:26:42 php: lcdproc: Start client procedure. Error counter: (0) Feb 14 23:26:42 php: lcdproc: Start client procedure. Error counter: (0) Feb 14 23:26:42 php: lcdproc: Connection to LCDd process lost () Feb 14 23:26:42 php: lcdproc: Start client procedure. Error counter: (0) Feb 14 23:26:43 php: lcdproc: Connection to LCDd process lost () Feb 14 23:26:43 php: lcdproc: Start client procedure. Error counter: (0) Feb 14 23:26:43 php: lcdproc: Connection to LCDd process lost () Feb 14 23:26:43 php: lcdproc: Start client procedure. Error counter: (0) Feb 14 23:26:53 php: lcdproc: Failed to connect to LCDd process Operation timed out (60) Feb 14 23:26:53 php: lcdproc: Start client procedure. Error counter: (1) Feb 14 23:26:53 php: lcdproc: Failed to connect to LCDd process Operation timed out (60) Feb 14 23:26:53 php: lcdproc: Start client procedure. Error counter: (1) Feb 14 23:26:53 php: lcdproc: Failed to connect to LCDd process Operation timed out (60) Feb 14 23:26:53 php: lcdproc: Start client procedure. Error counter: (1) Feb 14 23:26:53 php: lcdproc: Failed to connect to LCDd process Operation timed out (60) Feb 14 23:26:53 php: lcdproc: Start client procedure. Error counter: (1) Feb 14 23:26:54 php: lcdproc: Failed to connect to LCDd process Operation timed out (60) Feb 14 23:26:54 php: lcdproc: Start client procedure. Error counter: (1) Feb 14 23:26:54 php: lcdproc: Failed to connect to LCDd process Operation timed out (60) Feb 14 23:26:54 php: lcdproc: Start client procedure. Error counter: (1)
And the list of processes :
[2.2.6-RELEASE][admin@pfSense.localdomain]/root: ps aux | grep lcd root 12587 0.0 1.6 87052 33412 - SN 3:47PM 0:07.32 /usr/local/bin/php -f /usr/local/pkg/lcdproc_client.php root 50205 0.0 1.6 87052 33448 - SN 4:11PM 0:06.95 /usr/local/bin/php -f /usr/local/pkg/lcdproc_client.php nobody 50226 0.0 0.1 10300 2064 - SNs 11:25PM 0:00.06 /usr/local/sbin/LCDd -c /usr/pbi/lcdproc-i386/local/etc/LCDd.conf -u nobody root 50280 0.0 1.6 87052 33400 - SN 4:22PM 0:06.78 /usr/local/bin/php -f /usr/local/pkg/lcdproc_client.php root 50300 0.0 1.6 82956 33168 - SN 11:25PM 0:00.23 /usr/local/bin/php -f /usr/local/pkg/lcdproc_client.php root 71083 0.0 1.6 87052 33100 - SN Sat04PM 0:35.50 /usr/local/bin/php -f /usr/local/pkg/lcdproc_client.php root 87732 0.0 1.6 87052 33432 - SN 3:48PM 0:07.28 /usr/local/bin/php -f /usr/local/pkg/lcdproc_client.php
Is there any workaround for this? I am trying to read through posts but can't seem to find the solution
-
@cii:
@pyroblast:
Hello Steve,
thanks for your fast answer.
Too bad. I hoped, to let the backlight always on.
If i didn't use the LCDproc the backlight is always on, but it shows this annoying "Booting OS…"pyro
ps. runnung pfsense on a X1250e
I've rebuilt the code from github to force the backlight always on.
You can grab the file from https://www.dropbox.com/s/6ilykwt1p6zn4rm/sdeclcd.so, sadly Dropbox doesn't work nicely with fetch…
You'll need to drop this in /usr/pbi/lcdproc-i386/lib/lcdproc/ and chmod 555 the file. Don't forget to back up your original! Once you reboot the backlight should be on.
such the link direct to sdeclcd.so is not working , is anyone has this file already compile so the LCD of my watchguard stay always on?
thanks!
-
Is anyone else having issues with lcdproc-dev when disconnecting/reconnecting patch cables ?
It seems like everytime the link state changes it reloads the php lcdproc script and creates a ton of errors in my syslog. Simply restarting the service doesn't work, but killing all the php scripts from the console and restarting the service fixes the issue.
Hi vizi0n,
yes same problem here, which is somewhat annoying…