Below is my error log from the day Links 2 was installed. All functions of the program appear to work. However, when selecting Build and related, some other functions as well, I get sent to an ISP error screen noting something is wrong in the scripts
even though the function occurs properly.
Building gets me a Build and an error.

Can anyone shed some light on this?
Concerning Perl, I have 5.003. Is that one of my problems? Do you need more info from me?

Thanks,

Dave

[Sat Apr 17 15:06:17 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 15:19:47 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 15:37:09 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 15:46:03 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 16:02:15 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 16:17:18 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 16:20:35 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 16:20:52 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 16:32:40 1999] [error] malformed header from script. Bad header=Perl 5.004 required--this is o: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 16:33:38 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 16:35:16 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 16:40:26 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 17:02:28 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 17:13:56 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 17:17:26 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 17:22:03 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 17:27:07 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 17:31:19 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 17:34:08 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 18:14:18 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 18:21:34 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 18:44:12 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 19:26:57 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 19:31:07 1999] [error] malformed header from script. Bad header=Perl 5.004 required--this is o: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:03:49 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:08:47 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:10:14 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:14:35 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:17:51 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:18:31 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:22:46 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:23:57 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:44:19 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:53:10 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:54:33 1999] [error] malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:54:40 1999] [error] malformed header from script. Bad header=Perl 5.004 required--this is o: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:54:49 1999] [error] malformed header from script. Bad header=Perl 5.004 required--this is o: /usr/local/apache/cgi-bin/exec
[Sat Apr 17 20:54:52 1999] [error] malformed header from script. Bad header=Perl 5.004 required--this is o: /usr/local/apache/cgi-bin/exec

While some part of Links will work with an earlier build of perl, you really do need Perl 5.004 for it to work right everywhere.

Thanks for the reply Bobsie,

Is my Perl 5.003 the cause of all the problems I have been reading about and experiencing such as, under Building, all function/execution seems to be there, but I get sent to the "something is wrong in this script" page at my ISP when I click any of these cgi links. Same thing with the Verifying Links area, all send me to a bad page.

Will sweet talking my ISP into Perl 5.004 eliminate these problems?

Do you think it's ok to run Links like this with these Perl errors?

You may view the errors if you need to at
http://www.eastcoastweb.com/cgi-bin/exec/dcds/links/admin/admin.cgi

I haven't pword protected it yet. It's a test area of the program before actually purchasing it.

Thanks again,

Dave

Hi,

You are running under CGIWrap. There is a special version of cgiwrap for running non parsed header scripts (nph- scripts). Check with your ISP, usually it's called nph-cgiwrap, but might be something different on your system.

If your ISP isn't helpful, you can rename your nph-build.cgi to just build.cgi and update any paths. It will work but will just be a little less responsive then the nph version.

Hope this helps,

Alex

Thanks Alex.
I emailed my ISP for more info on nph-cgiwrap.

Thanks

Dave

Problem was: Build functions worked but didn't disply on the page. Got a cgi error page instead.

Problem was related to nph-cgiwrap because my ISP didn't have it turned on I guess. My ISP is working with me and tried to fix his UNIX installation of cgiwrap to include nph-cgiwrap so that the nph files in Links 2.0 would work.

So I replaced my Links.cfg path info with the new data supplied by the ISP, instead of /exec/ I used /nph-exec/.

Build functions now display data on page properly.

Two new problems created, why I'm not sure yet and need input.

1st problem:
Strange new text added in upper left of Admin screen directly above "Links Administration Menu and says "Content-type: text/html" This pushed the info in the top frame on the Admin page down one line.

2nd problem:
With the nph-cgiwrap thing in my path and Build now displying something, my homepage index.html file has gone to a 0 kbyte file completely blank, losing all of the test catagorys I put in, the other pages and links are still there.

Try to fix:
Changed the links.cfg back to what it used to be. Index.html still completey blank when trying to Build and of course the cgi error is back.

Could it be related to the Admin.cgi and the nph-build.cgi etc nph files being in the same directory and executing admin.cgi via the nph-exec program?

I think I broke it. :-)
Should I just re-install Links 2 and start over?

Sorry for bugging you via direct email Alex. Patience isn't my best virtue, but I'm working on it.

Any input appreciated.

Thanks,

Dave

Ok, I gave up and re-installed all files.
Now I'm back to square 1.

I still have an nph-cgiwrap problem. If I re-name the nph files as Alex suggested which paths do I need to update and in which cgi files or other files.

Thanks,

Dave