Gossamer Forum: Products: Links 2.0: Installation -- Unix: telnet nph-verify stops with "Broken Pipe" (marinedesign)

I just moved from CIhost to FutureQuest.net, and while nph-verify.pl worked on my 1132 link database via telnet on CIhost (perl 5.004) on Futurequest.net (perl 5.005) nph-verify verifies 10-12 links over a period of 10 seconds, then sits for 5 minutes, and then returns "BROKEN PIPE" and ends back to the command prompt.

Here is an example:

In Reply To:

$ perl nph-verify.pl
HTTP/1.0 200 OK
Content-type: text/html

Link Checking started: 4-Jun-2000 20:27:35
Registering URLs ...
100 200 300 400 500 600 700 800 900 1000 1000
1100
Done.

Links to check '1113' using HEAD method. Please be patient...

Checked 504 - Success (200). Message: OK
Checked 110 - Success (200). Message: OK
Checked 7 - Success (200). Message: OK
Checked 6 - Success (200). Message: OK
Checked 3 - Success (200). Message: OK
Checked 2 - Success (200). Message: OK
Checked 1 - Success (200). Message: OK
Checked 5 - Success (200). Message: OK
Checked 4 - Success (200). Message: OK
Checked 8 - Success (200). Message: OK
Checked 10 - Success (200). Message: OK
Broken Pipe
$

I asked Futurequest, and here is their response:

In Reply To:

I strace() the program and found it hanging on the following IP:
216.3.41.56

It should timeout and resume operation, but for some unknown reason, the Links include perl modules/libraries are in fact not timing out...

For some reason, the alarm() is set, but somewhere in your program that signal $SIG{'ALRM'} is being masked...

You may want to use our FQuest core modules instead as LWP is fully installed, as well as many many others...

If you want to see the results, just view the following file:
trace.one

I tried to run this 3 times, and all 3 times it failed on the same IP...

Hope this helps...

Can anyone who knows more than I shed some light on what is going on, or advise me how to modify nph-verify.pl to correspond to Futurequest's recommendation? (The same database and nph-verify.pl works on the other server, so I don't think the database is corrupt. I have the badlinks mod installed, so I tried returning to the original nph-verify.cgi but this yielded the same result.)

Thanks for any ideas or suggestions in advance.

Subject	Author	Views	Date
telnet nph-verify stops with "Broken Pipe"	marinedesign	1739	Jun 4, 2000, 6:44 PM

Re: telnet nph-verify stops with "Broken Pipe"	Stealth	1673	Jun 5, 2000, 6:23 PM

Same here - nph-verify stops with "Broken Pipe"	RTM111	1670	Jun 11, 2000, 9:28 AM

Re: Same here - nph-verify stops with "Broken Pipe"	Stealth	1659	Jun 11, 2000, 10:39 AM

Re: Same here - nph-verify stops with "Broken Pipe"	marinedesign	1652	Jun 11, 2000, 11:02 PM