Gossamer Forum
Home : Products : Links 2.0 : Discussions :

Verifying Links

Quote Reply
Verifying Links
When I run verifying links I get this message
...
Registering URLs ...
100 200 300 400 500 600 700 800 900 1000 1000
Checked - Request Failed (501). Message: Unknown Scheme:
...

verifying starts, but stoped after 200 records

Any idea?

Michael



Quote Reply
Re: Verifying Links In reply to
This sounds like a script timeout problem. See if you host can increase the amount of time it waits for a response from the script. You might also look at the setting you can adjust in nph-verify.cgi and see if you can overcome this problem.

- Bobsie
bobsie@orphanage.com
http://goodstuff.orphanage.com/
Quote Reply
Re: Verifying Links In reply to
Have you tried the new Links v2.01? It has a new nph-verify.cgi script.

- Bobsie
bobsie@orphanage.com
http://goodstuff.orphanage.com/
Quote Reply
Re: Verifying Links In reply to
>Have you tried the new Links v2.01? It has a new nph-verify.cgi script

hmmm...I was not aware of a new version.

I hope that this fixes the problems with the nph-verify and Deletes that I am having.



Quote Reply
Re: Verifying Links In reply to
Fantastic !!!

Now it runs like a dream.

Thanks for the advise about the update.

Michael

Quote Reply
Re: Verifying Links In reply to
Just a brief question: can the Bad Links Summary report also be used along with the new nph-verify.cgi?

Thomas
http://www.japanreference.com
Quote Reply
Re: Verifying Links In reply to
Not at this time. I need to put another version of it up as soon as I can that will work with the new nph-verify.cgi. It would have already been done but I wasn't aware that nph-verify.cgi had been updated until I looked at the new Links version 2.01. The announcement I read didn't say anything about it.

I'll post an announcement in this forum as soon as it is ready.

- Bobsie
bobsie@orphanage.com
http://goodstuff.orphanage.com/
Quote Reply
Re: Verifying Links In reply to
I am a very frequent visitor to these forums, but I was not aware of Links 2.01 at all, I only learned from it through your posting. Anyhow, thanks for your reply and your efforts, I am looking forward to your modification.

Thomas
http://www.japanreference.com
Quote Reply
Re: Verifying Links In reply to
I admit I haven't been frequenting the Links 2 forums of late, but the new version was certainly news to me, too. Maybe the product page could be updated to mention 2.1:

http://gossamer-threads.com/scripts/links/index.htm

Smile

Downloading the zipped files confirms that it is a new version. Were nph-verify.cgi and the admin security fix the only changes, or are there other things to watch for?

Dan

Quote Reply
Re: Verifying Links In reply to
From the readme.txt:

4. Revision History:
====================================================
July 9, 2000
o SECURITY FIX: Fixed admin security hole.
o BUGFIX: Removed old lwp::parallel based verifier, replaced with simple check.

So there-be the "new" version ...

John

Quote Reply
Re: Verifying Links In reply to
Hi John,

I looked at that before posting. In fact, that's the only mention I could find of the new version outside this forum... What I'm curious about is how many of the scripts are affected by the change? Just nph-verify.cgi, the admin screen, new verification scripts, anything else? The Revision History is pretty low on informational quantity on this one.

Dan

Quote Reply
Re: Verifying Links In reply to
Dan,

Your're right, of course. I haven't noticed anything new resulting from the new verifying script. I wouldn't think it would affect anything else, since it runs independtly from the other scripts (except, of course, from links.cfg etc.).

Quote Reply
Re: Verifying Links In reply to
Cool, thanks. It would make sense that the new verification script would run independently, as long as it's not being called by any version specific arguments.

I'll be updating someone else's Links 2 setup with the new verification (I use Links SQL now), so not using it as intimately as if it were my own installation, it's nice to know that there aren't interrelated aspects to the upgrade that could be easily overlooked.

Thanks,
Dan

Quote Reply
Re: Verifying Links In reply to
So does this mean that if we download the new version we can just install the new nph-verify script on its own, or do we have to change anyhting else?



Regards

MDJ1
http://www.isee-multimedia.co.uk
Quote Reply
Re: Verifying Links In reply to
Yes...all you do is use the new nph-verify.cgi.

Regards,

Eliot Lee

Quote Reply
Re: Verifying Links In reply to
Thanks eliot,

By the way im getting to grips with the database and writting perl. Sort of!!!



Regards

MDJ1
http://www.isee-multimedia.co.uk
Quote Reply
Re: Verifying Links In reply to
In Reply To:
You might also look at the setting you can adjust in nph-verify.cgi and see if you can overcome this problem.
Can you please elaborate on this?

I was very excited to see the new nph-verify.cgi, but unfortunately it still will not run for me. My DB is ~400kb with 1300 links. Verify now seems to stop on #120 via the browser and #12 via telnet...
When run via the browser, #120 reads
Checked <a href="http:/
and that is where it is cut off.



My problem with the old nph-verify.cgi was that:

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...
That specific IP's record was removed from the links.db, but my guess is that the new nph-verify is also having a similar problem.

Does anyone know more about $SIG{'ALRM'}?
Or, how would I go about using my host's core modules or is this even as relevant to the new nph-verify.cgi?

Thanks for any ideas.

Quote Reply
Re: Verifying Links In reply to
Has anyone been able to get this problem solved?

We are still having the same problem with 2.1

Rick