Welcome, Guest. Please login or register.
Did you miss your activation email?


Login with username, password and session length

Search

 
Advanced search

8043 Posts in 1856 Topics- by 2099 Members - Latest Member: roi
« previous next »
Pages: [1]   Go Down
Print
Author Topic: Can't install  (Read 583 times)
0 Members and 1 Guest are viewing this topic.
KnightWolfJK
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« on: March 14, 2003, 05:13:00 PM »
I installed and originally received the "Your server does not provide the PATH_TRANSLATED or SCRIPT_FILENAME environment variables" error.

Per instructions, I edited to include:

code:
$BASE_DIR = "/home/planetjk/www/calendarscript/";
Now, running 'perl -wT calendar.cgi' results in
[CODE]perl -wT calendar.cgi
Unquoted string "false" may clash with future reserved word at /home/planetjk/www/cgi-bin/calendarscript/lib/SimpleDateFormat.pm line 187.
Unquoted string "false" may clash with future reserved word at /home/planetjk/www/cgi-bin/calendarscript/lib/SimpleDateFormat.pm line 190.
Unquoted string "false" may clash with future reserved word at /home/planetjk/www/cgi-bin/calendarscript/lib/SimpleDateFormat.pm line 194.
Name "main::now_yd" used only once: possible typo at calendar.cgi line 470.
Name "main::tmp_parsed_template" used only once: possible typo at calendar.cgi line 64.
Name "main::now_ss" used only once: possible typo at calendar.cgi line 470.
Name "main::now_mi" used only once: possible typo at calendar.cgi line 470.
Name "User::MSG_LOGGED_IN_SUCCESSFULLY" used only once: possible typo at calendar.cgi line 361.
Name "main::now_dst" used only once: possible typo at calendar.cgi line 470.
Name "main::now_wd" used only once: possible typo at calendar.cgi line 470.
Name "main::now_hh" used only once: possible typo at calendar.cgi line 470.
Name "Template::QUERY_STRING" used only once: possible typo at calendar.cgi line 346.

as well as about 300 other lines of errors (if someone REALLY wants the full output, let me know) and the browser returns a 500.

Any ideas?  Yes, I have uploaded in ASCII, CHMOD'd correctly, and checked the path to Perl.  Running debug.pl returns a 500 as well.
Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #1 on: March 14, 2003, 06:19:00 PM »
** Now, running 'perl -wT calendar.cgi' results in **

Well the -w Perl switch tells Perl to print warnings about the script (which it is doing) so you probably don't want to use that. I don't know if the T for taint checking is required either.

What happens when you try running the script without any of those switches?

Dan O.

------------------
Logged
KnightWolfJK
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #2 on: March 14, 2003, 08:05:00 PM »
Running perl calendar.cgi

code:
Content-type: text/html
<HTML>
<HEAD>
        <TITLE>Calendar</TITLE>
<META HTTP-EQUIV="expires" CONTENT="now">

etcetera...

Just FYI, I'm using the .cgi extension and I've installed 25+ scripts on this server

Any ideas?

------------------
Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #3 on: March 15, 2003, 12:27:00 PM »
That looks to be what it should be outputting (web page source code).

Dan O.

------------------
Logged
KnightWolfJK
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #4 on: March 16, 2003, 10:44:00 PM »
Unfortunately I'm still getting a 500

------------------
Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #5 on: March 17, 2003, 07:52:00 PM »
If the script runs properly from telnet (the command line) but generates a 500 server error
when called from a browser, that is most likely caused by incorrect file or directory permissions.

Dan O.

[This message has been edited by DanO (edited March 17, 2003).]
Logged
KnightWolfJK
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #6 on: March 18, 2003, 05:48:00 AM »
I verified the permissions a few days ago... 755 on 'calender.cgi' and 'calendar_admin.cgi,' and 777 on the 'calendarscript' folder.

To double-check, I just reset the permissions to 777 on both .cgi files and the directory... Still a 500 error.

I'm sure this doesn't mean much, but I'll mention it anyway.  When viewing in the browser, the browser screen goes to a blank white screen for a few seconds, then returns the 500 error.  Does that mean anything in particular?

Thanks for your time

------------------
Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #7 on: March 18, 2003, 12:45:00 PM »
** I just reset the permissions to 777 on both .cgi files and the directory **

Not all servers allow files or directories to be chmod to 777. Check you host's CGI FAQs.

** When viewing in the browser, the browser screen goes to a blank white screen for a few seconds, then returns the 500 error. Does that mean anything in particular? **

Not that I know of.

Dan O.

------------------
Logged
KnightWolfJK
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #8 on: March 18, 2003, 12:59:00 PM »
I've used 777 numerous times before, so far I've had no errors associated with it (that I know of).  My host's FAQ (http://help2.hostway.com/documents/unixplatform/online/Ch0414.html#529405) doesn't mention anything about restricting 777, either.

I tried setting /calendarscript to 744, still no luck.

------------------
Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #9 on: March 18, 2003, 06:54:00 PM »
Sorry but I don't know what else to tell you. Maybe someone else will offer a suggestion?

Dan O.

------------------
Logged
Pages: [1]   Go Up
Print
« previous next »
Jump to: