Lightsquid show me "500 - Internal Server Error" in graphics tab

[scooterdouglas]

Check the following directories for any perl symlinks:

/usr/bin
  /usr/local/bin

Delete any that you find, then:

cd /usr/bin

ln -s /usr/local/bin/perl /usr/bin/perl

ls -ltr | grep -i perl

lrwxr-xr-x  1 root  wheel      19 Sep 11 23:02 perl -> /usr/local/bin/perl

That is how I solved the Error 500 message.

;)

[xeneize]

Thank's for reply. I will try it.
Thank's again.

[xeneize]

Can you explain these commands to better understand?

[jikjik101]

@scooterdouglas:

Check the following directories for any perl symlinks:

/usr/bin
  /usr/local/bin

Delete any that you find, then:

cd /usr/bin

ln -s /usr/local/bin/perl /usr/bin/perl

ls -ltr | grep -i perl

lrwxr-xr-x  1 root  wheel       19 Sep 11 23:02 perl -> /usr/local/bin/perl

That is how I solved the Error 500 message.

;)

Questions:
1. is perl symlink a file?
2. Are these codes needed to be copied verbatim in Diagnostics>Command Prompt>Execute shell command?

cd /usr/bin

ln -s /usr/local/bin/perl /usr/bin/perl

ls -ltr | grep -i perl

lrwxr-xr-x  1 root  wheel      19 Sep 11 23:02 perl -> /usr/local/bin/perl

[jimp]

The graphics tab not working may be something else entirely. The perl-related 500 error made it not work at all.

There is probably some graphing library that tab tries to use that isn't being pulled in.

[johnnybe]

I have the same "500 - Internal Server Error" when I try to see Lightsquid Report.
2.0-RC2 (i386) built on Tue Jun 14 11:14:26 EDT 2011
It was working before updating to the version above.
Remove package, reinstalled and the error persist.

[jimp]

you could try to force it a bit:

uninstall lightsquid, squidguard, and squid

Then go to Diagnostics > Command or the shell, and type:

pkg_delete -f \*squid\* perl\*

And then reinstall squid, squidguard, and lightsquid.

[ethermcman]

The symlink trick and the reinstall trick didn't work either…
I'm really surprised that the Team did not fix this!
We are many people using pfsense in this configuration : squid > squidguard > lightsquid
This problem remains since the 1.2.3.
Any xml fix could be considered?

Thanks for all your hard work making us love pfSense.

[jimp]

If you reinstall the lightsquid package now, does it behave any differently?

I made some fixes yesterday, though I haven't tested it out on a fresh 1.2.3 vm.

[Pistolero]

@jimp:

If you reinstall the lightsquid package now, does it behave any differently?

I made some fixes yesterday, though I haven't tested it out on a fresh 1.2.3 vm.

I am having the very same issue, where the whole report page has been replaced by a "500 - Internal Server Error" in 2.0 RC1 version from yesterday. reinstalling makes no difference, sadly.

Is there a way we could fix this?

Thanks!

[jimp]

I know for a fact it's fine on 2.0. Update to RC3 (it's out officially) and if it doesn't work after the packages reinstall there (should happen automatically with the firmware update), try what I mention earlier in the thread (quoted below).

@jimp:

uninstall lightsquid, squidguard, and squid

Then go to Diagnostics > Command or the shell, and type:

pkg_delete -f \*squid\* perl\*

And then reinstall squid, squidguard, and lightsquid.

[Hugovsky]

2.0-RC3 (amd64)
built on Fri Jun 24 09:54:09 EDT 2011

squid + Lightquid + squidguard it's working perfectly. No special install order.

[jikjik101]

I still have this 500 ERROR.

Already tried:
@jimp:

I know for a fact it's fine on 2.0. Update to RC3 (it's out officially) and if it doesn't work after the packages reinstall there (should happen automatically with the firmware update), try what I mention earlier in the thread (quoted below).

@jimp:

uninstall lightsquid, squidguard, and squid

Then go to Diagnostics > Command or the shell, and type:

pkg_delete -f \*squid\* perl\*

And then reinstall squid, squidguard, and lightsquid.

Also tried install order but to no avail.

[vladick0732]

In the directory "/usr/bin" file appeared "perl  0 B 1970.01.01 03:00:00 (0) ? –- --- ---",
selected on the picture and you can not delete it, because it says that the file is not correct. What can I do?

[vladick0732]

Hi all!

After several re-installation of packages Squid and Lighsquid, it worked.
File has the normal value. What's the problem I still do not understand.

[cyber7]

What I did to get this working was:
ln -s /usr/local/bin/perl5.12.4 /usr/bin/perl
(after deleting the link: /usr/bin/perl)

Kind regards
Aubrey Kloppers
Cape Town

[pdamianov]

@cyber7:

What I did to get this working was:
ln -s /usr/local/bin/perl5.12.4 /usr/bin/perl
(after deleting the link: /usr/bin/perl)

Kind regards
Aubrey Kloppers
Cape Town

You are grate man. This solve my problem.

[dmenezes]

the problem is about the perl version or symlink to the perl subversion if u have more the one version installed on your system.
something like that

[2.0.1-RELEASE][root@pfsense.backbone]/usr/bin(41): pkg_info |grep perl
p5-GD-2.46          A perl5 interface to Gd Graphics Library version2
perl-5.10.1_3      Practical Extraction and Report Language
perl-5.12.3        Practical Extraction and Report Language
perl-5.12.4_3      Practical Extraction and Report Language

[2.0.1-RELEASE][root@pfsense.backbone]/usr/bin(17): ls -al /usr/local/bin/perl5*
lrwxr-xr-x  1 root  wheel    25 Feb  1 15:47 /usr/local/bin/perl5 -> /usr/local/bin/perl5.12.3
-rwxr-xr-x  1 root  wheel  7248 Feb 11  2011 /usr/local/bin/perl5.10.1
-rwxr-xr-x  2 root  wheel  7304 Jun 29  2011 /usr/local/bin/perl5.12.3
-rwxr-xr-x  1 root  wheel  7304 Jan 27 09:19 /usr/local/bin/perl5.12.4

change it:
from /usr/local/bin/perl5.12.3
to /usr/local/bin/perl5.12.4

[2.0.1-RELEASE][root@pfsense.backbone]/usr/bin(40): ls -al /usr/bin/perl*
lrwxr-xr-x  1 root  wheel  25 Apr  2 13:10 /usr/bin/perl -> /usr/local/bin/perl5.12.4
lrwxr-xr-x  1 root  wheel  25 Apr  2 13:23 /usr/bin/perl5 -> /usr/local/bin/perl5.12.4

[arenasa]

@cyber7:

What I did to get this working was:
ln -s /usr/local/bin/perl5.12.4 /usr/bin/perl
(after deleting the link: /usr/bin/perl)

Kind regards
Aubrey Kloppers
Cape Town

This works on 2.1 also.  Shouldn't this placed as a bug somewhere so they fixed on the package?.

Regards,

Andrés.

[jimp]

It works fine on 2.1, at least it did every time I tested it. It also works fine for most people on 2.0.x. This isn't a general issue with the lightsquid package, so there isn't really anything to "fix". It's some odd combination of installed packages/files and ordering and who knows what, but most people have no problems with it.