Is it just those specific modules you cannot access, or can you not access any module you install via cPanel? Oftentimes with cPanel, you either have to use #!/usr/bin/perlml in your shebang instead of perl, or you can use cPanelUserConfig;, in order to correctly point perl to the user-installed modules. If you cannot access any of the user-installed modules, it may be that when your host changed upstream providers, they might have changed either the shebang requirements or the name of the cPanelUserConfig (I think I remember my webhost changing the name of the use-file at one point).
On my webhost's cPanel, the "install perl modules" task shows me both the shebang and the use ... methods, and it also shows the installation path for the modules it installs. You might make sure you match what's listed there... and you might even try a simple delme.pl:
#!/usr/bin/perlml # or whatever your cPanel says use CGI::Carp qw/fatalsToBrowser/; use CGI; # later: add other use BLAH; here print "Content-type: text/plain;\n\n"; print join "\n", @INC; printf "%-20s => %s\n", $_, $INC{$_} for keys %INC; or #!/usr/bin/perl use CGI::Carp qw/fatalsToBrowser/; use CGI; use cPanelUserConfig; # later: add other use BLAH; here print "Content-type: text/plain;\n\n"; print join "\n", @INC; printf "%-20s => %s\n", $_, $INC{$_} for keys %INC;
... to find out your @INC and %INC, then slowly add in your other use-statements where indicated.
Alternately, cPanel should give you a way to look at your log files -- in mine, it's cPanel: statistics: error logs for the host-level logs, or one of the stats packages might give you filtered data.
In reply to Re: GD and LWP giving 500 errors
by pryrt
in thread GD and LWP giving 500 errors
by Schmunzie
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |