Demon Commerce Web Server Perl CGI question

Thread View: demon.tech.unix

4 messages

[T] Back to Threads [V] Tree View [G] Group Articles

4 total messages Started by Pak Chan Fri, 14 Jul 2000 00:00

#234

Author: Pak Chan
Date: Fri, 14 Jul 2000 00:00

21 lines
1623 bytes

HELP!

I'm having problems with a set of Perl CGI scripts I've uploaded to the 
Demon web server (uk-upload.demon.co.uk). The scripts have been checked 
and work perfectly on my test rig (Apache 1.3, Perl 5.004); however they 
fail with an Internal Server Error when run on the Demon server.

I've contacted Demon commercial tech support, but they have absolutely no 
idea (clue?) as to why it fails to work. The only thing that they can 
think of is that I'm loading the CGI library module in my scripts 
(perfectly understandable, given that they are CGI scripts!). They have 
assured me that the scripts look fine in their Perl script verification 
tool, and that their installation of Perl on that machine is standard. I 
can't verify this as users on that system do not have access to Perl, or 
even most of the standard Unix tools (ed, vi, sed, ...).

Does anyone have experience of perl CGI scripts on Demon?

-- 
Pak Chan                     IT Techie Consultant.
No C++ question too hard, no Cobol topic too easy.

Re: Demon Commerce Web Server Perl CGI question

#236

Author: Pak Chan
Date: Mon, 17 Jul 2000 00:00

44 lines
2629 bytes

In article <x7vgy8fd3v.fsf@indy1.watching.org>, jrg@blodwen.demon.co.uk 
says...
> Pak Chan <Pak.Chan@metameme.demon.co.uk> writes:
> > I've contacted Demon commercial tech support, but they have absolutely no 
> > idea (clue?) as to why it fails to work. The only thing that they can 
> > think of is that I'm loading the CGI library module in my scripts 
> > (perfectly understandable, given that they are CGI scripts!). They have 
> 
> 'Internal server' errors generally mean that something is being output
> at an inappropriate moment - mixing up errors with where the HTTP
> headers are supposed to be.
> 
> You could try, before any of the 'use' statements, something like
> 
> 	BEGIN {
> 		$| = 1;
> 		print "Content-Type: text/plain\r\n\r\n";
> 	}
> 
> in an effort to print a valid content-type header before anything else
> fails to initialise correctly and prints out error messages.
> 
> Or, look for information on the 'xx-' debugging feature on Demon's
> servers.  (I don't know if it's mentioned in the documentation -
> anyone?)

Thanks. I've just tried the xx- feature, and it's quite illuminating:

parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 22, 
next 2 tokens "use CGI"
parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 30, 
next 2 tokens "new CGI"
parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 34, 
next 2 tokens "->"
parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 36, 
next 2 tokens "->"
parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 38, 
next 2 tokens "->"
parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 54, 
next 2 tokens "->"
Execution of /www/cgi-bin/www.lawsoncars.com/xx-sm.pl aborted due to compilation errors.

I was given the impression that Demon ran Perl 5 on their servers. Is 
this not the case? Anyone from Demon Internet care to confirm this?

Re: Demon Commerce Web Server Perl CGI question

#253

Author: Richard Clayton
Date: Fri, 21 Jul 2000 00:00

42 lines
2499 bytes

In article <MPG.13dcd9ad722cdebc989689@news.demon.co.uk>, Pak Chan
<Pak.Chan@metameme.demon.co.uk> writes

>I was given the impression that Demon ran Perl 5 on their servers. Is 
>this not the case? Anyone from Demon Internet care to confirm this?

[this is the sort of question to ask in demon.ip.www where there's
significantly greater chance of experts seeing it!]

This is the latest info I have ... things may have moved on!

<--->

Support is provided for Perl v4 and upwards.  In particular the latest
version of Perl on the old servers (retired late 99) was Perl v5.001m.
On the servers being run since then, the latest version is Perl
v5.005_03.

Scripts that start with #!/bin/perl5 will automatically use the very
latest version. Since Perl is upwards compatible this should give no
problems. Anyone who is particularly concerned to use exactly the same
Perl interpreter as on the old servers will need to alter their scripts
to start with a #!/bin/perl5.001m line.

Scripts that start #!/bin/perl will continue to use Perl 4 just as on
the old servers.

Demon Internet uses a standard installation of Perl, with nothing added
(from CPAN or wherever) but nothing taken away either! Newer versions of
Perl have many more modules shipped with them as standard, so this may
give customers the opportunity of simplifying their scripting.

Full details of the differences between versions of Perl, and
documentation for all the standard Perl modules, can be found on the web
at http://www.perl.com/.

<--->

-- 
richard                       writing to inform and not as company policy
     want to have an influence on ICANN ?  http://members.icann.org/
"Assembly of Japanese bicycle require great peace of mind" quoted in ZAMM

Re: Demon Commerce Web Server Perl CGI question

#256

Author: hypo
Date: Sun, 23 Jul 2000 00:00

58 lines
3146 bytes

Pak Chan <Pak.Chan@metameme.demon.co.uk> wrote in message
news:MPG.13dcd9ad722cdebc989689@news.demon.co.uk...
> In article <x7vgy8fd3v.fsf@indy1.watching.org>, jrg@blodwen.demon.co.uk
> says...
> > Pak Chan <Pak.Chan@metameme.demon.co.uk> writes:
> > > I've contacted Demon commercial tech support, but they have absolutely
no
> > > idea (clue?) as to why it fails to work. The only thing that they can
> > > think of is that I'm loading the CGI library module in my scripts
> > > (perfectly understandable, given that they are CGI scripts!). They
have
> >
> > 'Internal server' errors generally mean that something is being output
> > at an inappropriate moment - mixing up errors with where the HTTP
> > headers are supposed to be.
> >
> > You could try, before any of the 'use' statements, something like
> >
> > BEGIN {
> > $| = 1;
> > print "Content-Type: text/plain\r\n\r\n";
> > }
> >
> > in an effort to print a valid content-type header before anything else
> > fails to initialise correctly and prints out error messages.
> >
> > Or, look for information on the 'xx-' debugging feature on Demon's
> > servers.  (I don't know if it's mentioned in the documentation -
> > anyone?)
>
> Thanks. I've just tried the xx- feature, and it's quite illuminating:
>
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 22,
> next 2 tokens "use CGI"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 30,
> next 2 tokens "new CGI"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 34,
> next 2 tokens "->"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 36,
> next 2 tokens "->"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 38,
> next 2 tokens "->"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 54,
> next 2 tokens "->"
> Execution of /www/cgi-bin/www.lawsoncars.com/xx-sm.pl aborted due to
compilation errors.
>
> I was given the impression that Demon ran Perl 5 on their servers. Is
> this not the case? Anyone from Demon Internet care to confirm this?
>

I'm not sure the CGI package is part of the standard perl distribution.
But the error doesn't look like a missing package - normally it says "cant
locate XXX.pm at script line yy".
Maybe you need to be explicit about perl5.

Paul

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads