Facebook
Twitter
Hi,
I took the plunge and upgraded my CentOS 5.7 box from Plesk from 10.3.1 to 10.4.4 today. Everything seemed to go well, until I get a call from a client whose YaBB forum (programmed in Perl) had stopped working, giving a 500 error. It was working fine before the upgrade.
Now, I don't know much about Perl. Looking at the error log I can see the following each time a page is requested:
We have substituted the $vardir variable for the full path and it still can't find the file.
Running the YaBB.pl script in the terminal via SSH, it executes fine and returns the HTML code for the page as excepted.
I tried turning Perl off for the domain in question and disabling mod_perl in Apache. The strange thing is, even with all that turned OFF, the script still runs and returns the error. Surely that shouldn't happen if Perl is disabled for the domain?
I created a new domain for testing and ran some test scripts. Any Perl script that tries to include or require another file will fail with above error that it can't locate the file.
Obviously something has gone wrong with the Perl configuration on the server, but I have no idea what or why. All I know for sure is it was fine until the Plesk 10.4.4 update...
Anybody have any ideas?
Cheers,
JMB
I took the plunge and upgraded my CentOS 5.7 box from Plesk from 10.3.1 to 10.4.4 today. Everything seemed to go well, until I get a call from a client whose YaBB forum (programmed in Perl) had stopped working, giving a 500 error. It was working fine before the upgrade.
Now, I don't know much about Perl. Looking at the error log I can see the following each time a page is requested:
Line 53 in YaBB.pl is:
We have substituted the $vardir variable for the full path and it still can't find the file.
Running the YaBB.pl script in the terminal via SSH, it executes fine and returns the HTML code for the page as excepted.
I tried turning Perl off for the domain in question and disabling mod_perl in Apache. The strange thing is, even with all that turned OFF, the script still runs and returns the error. Surely that shouldn't happen if Perl is disabled for the domain?
I created a new domain for testing and ran some test scripts. Any Perl script that tries to include or require another file will fail with above error that it can't locate the file.
Obviously something has gone wrong with the Perl configuration on the server, but I have no idea what or why. All I know for sure is it was fine until the Plesk 10.4.4 update...
Anybody have any ideas?
Cheers,
JMB
Last edited:
