On Sat, Dec 15, 2001 at 06:06:59PM +0100, Greennet wrote: > Merry Christmas All!
And a Merry Christmas to you too. > Sorry if this is the wrong list. I'm new to Perl, CGI, and web service > providers so I'm not sure if this is the right list to post my question to. > If it's not will someone let me know where I should post to get an answer > and I'll send it there. It probably isn't the right list, but I can't really think of a better, and it does involve Perl, so... > I wrote a Perl script using Perl 5.6.1 and it didn't work with my web host > provider. It worked fine on my machine with that version of Perl and Apache > 1.3. It turns out my web service provider is using Perl 5.005_03. I think > the problem revolves around Exporter::Heavy.pm The full error message > along with help desk correspondence is listed below. Your provider is more than likely using Perl 5.6.0. Given the error message: > [Sun Dec 9 11:20:22 2001] [error] Can't locate Exporter/Heavy.pm in @INC > (@INC contains: /usr/local/plesk/apache/lib/perl/5.00503/ > /usr/local/plesk/apache/lib/perl/site_perl/5.005//i386-linux > /usr/local/plesk/apache/lib/perl/site_perl/5.005/ > /usr/lib/perl5/5.6.0/i386-linux /usr/lib/perl5/5.6.0 > /usr/lib/perl5/site_perl/5.6.0/i386-linux /usr/lib/perl5/site_perl/5.6.0 > /usr/lib/perl5/site_perl . /usr/local/plesk/apache/ > /usr/local/plesk/apache/lib/perl /usr/local/plesk/apache/lib/perl/5.00503/ > /usr/local/plesk/apache/lib/perl/site_perl/5.005/) at > /usr/local/plesk/apache/lib/perl/5.00503//Exporter.pm line 15. > BEGIN failed--compilation aborted at > /usr/local/plesk/apache/lib/perl/site_perl/5.005//i386-linux/Apache/Registry > ..pm line 4. > Compilation failed in require at (eval 30) line 3. You'll notice there are paths with "5.6.0" in them. I would verify this by running perl -v on the command-line, and printing $] in a CGI script. The person who installed this Perl set it up so that it looks for modules in both 5.005 directories, as well as 5.6.0. This is an option provided in the configuration process, and is there for backwards compatability. You appear to have two problems. The installation of Perl appears to be broken; Exporter::Heavy is a part of Perl 5.6.0, if it's not there something wasn't installed correctly. Also, paths are being appended to @INC that shouldn't be. Notice the first three elements: /usr/local/plesk/apache/lib/perl/5.00503/, /usr/local/plesk/apache/lib/perl/site_perl/5.005//i386-linux, and /usr/local/plesk/apache/lib/perl/site_perl/5.005/. This means Perl 5.005 directories will be used in preference to 5.6.0 directories; this will likely cause more issues, if it hasn't already. Given that they have "apache" in them the paths are probably being added by a script executed by mod_perl. > Before I go off the deep end and shop around for another web service > provider I'd like to know if I'm being unreasonable or if my analyisis of > the problem is wrong. It would appear, to me, that you're being unreasonable, and your analysis of the problem is wrong. I say that in the nicest possible way, of course. :) First, you're not even certain what Perl version they're running. Find out; run perl -v on the command-line; print out $] in a CGI script. The versions may be different, because mod_perl may be out of sync. Second, you're approaching these people without a clear idea of what the problem is. Along the way you're asking them for clarification on some things, and then going on to tell them what to do. From their perspective, you clearly don't know what you're doing, and, given their responses, they don't know enough about the problem to judge what the right answers are. Ask to speak to the admin; if you can't, then explore the problem more fully, figure out why it doesn't work, perhaps even test it. Then, approach them to -tell- them why it's not working, and what can be done to fix it. If you need to fill out a trouble ticket for them to take it seriously, do so. Eventually it should get to someone who knows what he/she/it's doing, and they'll take it from there. > I feel as if I'm getting a run-around here. I've asked them to upgrade > their version of Perl to 5.6.1 as I think that will eliminate the problem > or to install Exporter::Heavy.pm for 5.005_03 on their servers. Both can > be downloaded from www.cpan.org I realize that may be a daunting task but > isn't Perl downloaded from CPAN safe enough to be used on production > servers? How about the Exporter module; isn't that safe? Is Perl 5.6.1 > backward compatible with 5.0005_03? What is a reasonable period of time > to do a full hacker/security etc check on a Perl upgrade? Actually, Exporter::Heavy cannot be downloaded seperately from CPAN; it's a core module, and thus requires you install perl to get it. It could, technically, be extracted seperately, but I wouldn't suggest going down that path. Perl downloaded from CPAN is safe enough to use in production, provided it's the stable version. That's not the issue. The issue is compatability with the other scripts in use on that server, put there by their other customers. An ISP isn't going to just upgrade a piece of software without first making sure it's going to work, especially on so many servers, and most especially given that the person requesting the upgrade only thinks that's the answer. > Should I start shopping for a new web service provider? If you feel you've been given the run-around then go somewhere else. From where I sit it appears they've been trying to help you, but you are the best judge about how much hassle they've been. > How much time should I give them? I don't know how much time you should give them. It depends on how receptive they are to your requests, how well they meet their time estimates, how much time you need, and how much time it should reasonably take. Michael -- Administrator www.shoebox.net Programmer, System Administrator www.gallanttech.com -- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
