Hi, I just got this issue after I upgrade to 3.1.0 few days back....
I had cron job setup & running from last 2 years now...
Cron /home/xxxxxx/public_html/search/admin/nph-verify.cgi --check-from 15

I get email results from it...
after upgrade I got something like this...


Checking 2009 links...

Wed Feb 15 03:00:02 2006 New child started
Wed Feb 15 03:00:02 2006 New child started
Wed Feb 15 03:00:02 2006 New child started
Wed Feb 15 03:00:02 2006 New child started
Wed Feb 15 03:00:02 2006 New child started
Wed Feb 15 03:00:02 2006 New child started
Wed Feb 15 03:00:02 2006 New child started
Wed Feb 15 03:00:02 2006 New child started
Wed Feb 15 03:00:03 2006 New child started
Wed Feb 15 03:00:03 2006 New child started
Finished launching children

451 http://www.xxx.com Success (200). Message: OK 200
180 http://www.yyy.com Success (200). Message: OK 200
741 http://www.zzz.com Success (200). Message: OK 200
....
about 200 links....
then...
820 http://www.ssss.com/ Request Failed (-4) Message: Could not
connect
Error fetching link (821): Failed to execute query: 'SELECT ID,URL FROM
lsql_Links WHERE ID = ?': MySQL server has gone away at
/home/xxxx/public_html/search/admin/Links/Tools.pm line 343.
Error fetching link (822): Failed to execute query: 'SELECT ID,URL FROM
lsql_Links WHERE ID = ?': MySQL server has gone away at
/home/xxxx/public_html/search/admin/Links/Tools.pm line 343.
Error fetching link (823): Failed to execute query: 'SELECT ID,URL FROM
lsql_Links WHERE ID = ?': MySQL server has gone away at
/home/xxx/public_html/search/admin/Links/Tools.pm line 343.
Error fetching link (824): Failed to execute query: 'SELECT ID,URL FROM
lsql_Links WHERE ID = ?': MySQL server has gone away at
/home/xxx/public_html/search/admin/Links/Tools.pm line 343.
Error fetching link (826): Failed to execute query: 'SELECT ID,URL FROM
lsql_Links WHERE ID = ?': MySQL server has gone away at
/home/xxx/public_html/search/admin/Links/Tools.pm line 343.
Error fetching link (828): Failed to execute query: 'SELECT ID,URL FROM
lsql_Links WHERE ID = ?': MySQL server has gone away at
/home/xxx/public_html/search/admin/Links/Tools.pm line 343.
nph-verify.cgi: error adding to Verify table (811): Failed to execute
query: 'INSERT INTO lsql_Verify (Status,Date_Checked,LinkID) VALUES
(?,?,?)': MySQL server has gone away at
/home/xxx/public_html/search/admin/nph-verify.cgi line 459.
nph-verify.cgi: error updating status (811): Failed to execute query:
'UPDATE lsql_Links SET Date_Checked = ? , Status = ? , Timestmp = NOW()
WHERE ID = ?': MySQL server has gone away at
/home/xxx/public_html/search/admin/nph-verify.cgi line 465.
nph-verify.cgi: error adding to Verify table (820): Failed to execute
query: 'INSERT INTO lsql_Verify (Status,Date_Checked,LinkID) VALUES
(?,?,?)': MySQL server has gone away at
/home/xxx/public_html/search/admin/nph-verify.cgi line 459.
nph-verify.cgi: error updating status (820): Failed to execute query:
'UPDATE lsql_Links SET Date_Checked = ? , Status = ? , Timestmp = NOW()
WHERE ID = ?': MySQL server has gone away at

(***** This goes on for several hunderd pages of error *****)

Total Run Time: 239 second(s)
Total Links checked: 253 [instead of 2009 that was mentioned above]
Total Links Bad: 27
Total Links Good: 226



what went wrong with new version?

What version are you upgrading from?

Adrian

I was not upgrading but updating from last fix that was released for LinkSQL, so basically 3.0.4 + all small fixes that were released after that to the lastest till LinkSQL 3.1.0 was released.

under "Update History" I have...


Older version update history: 3.0.0 3.0.1 3.0.2 3.0.3 3.0.4 3.1.0

----- CUT & PASTED FROM UPDATE HISTORY PAGE --------

Recommended update:
Search multiple terms paging fix
Show details
Installed: 2005-08-31 10:08:08
This update corrects the problem that paging is broken when searching for multiple terms.
Files contained in update:

File

Type

Permission

/home/xxx/public_html/search/admin/Links/Utils.pm *
file
0644

uninstall
Recommended update:
User-side files cannot be deleted fix
Show details
Installed: 2005-12-29 18:12:36
Gossamer Links 3.0.4 contains a bug that can prevent files from being deletable from the user-side (file column upload and deletion requires template modifications). This update fixes the problem as well as cleaning up a few other minor file column issues.
Files contained in update:

File

Type

Permission

/home/xxx/public_html/search/admin/GT/CGI.pm *
file
0644
/home/xxx/public_html/search/admin/GT/SQL/Admin.pm *
file
0644
/home/xxx/public_html/search/admin/GT/SQL/Display/HTML.pm *
file
0644
/home/xxx/public_html/search/admin/GT/SQL/File.pm *
file
0644
/home/xxx/public_html/search/admin/Links/User/Modify.pm *
file
0644

uninstall
Optional update:
Windows updater fix
Show details
Installed: 2005-07-15 16:07:48
When on a Windows server, the Gossamer Update system may incorrectly download the install.dat file when attempting a version upgrade. This update fixes the problem and allows version upgrades to work successfully.
Files contained in update:

File

Type

Permission

/home/xxx/public_html/search/admin/GT/Update.pm *
file
0644

uninstall
Optional update:
Missing tags in detailed page
Show details
Installed: 2005-09-16 06:09:25
This update adds in the isPaidLink/isFreeLink template tags that are missing in the detailed page.
Files contained in update:

File

Type

Permission

/home/xxx/public_html/search/admin/Links/SiteHTML.pm *
file
0644

uninstall
Optional update:
sendmail compatibility fix
Show details
Installed: 2005-11-17 11:11:25
The default sendmail arguments that GT::Mail uses (-t -oi -oeq) may be incompatible with the sendmail binary on your server. This update allows you to override the arguments with ones which are compatible. These overriding arguments are passed in by specifying them after the sendmail path in db_mail_path option.
Files contained in update:

File

Type

Permission

/home/xxx/public_html/search/admin/Links.pm *
file
0644

uninstall
Optional update:
Bookmarks paging fix
Show details
Installed: 2006-01-07 09:01:28
After performing certain actions on bookmarks paging was broken - this update corrects this issue.
Files contained in update:

File

Type

Permission

/home/xxx/public_html/search/admin/Links/Bookmark.pm *
file
0644

uninstall
Optional update:
Link validate Add Date option
Show details

I looked at the error again and it looks like your MySQL server's configuration can't handle the concurrency of the children the nph-verify spawns. If you edit nph-verify.cgi and change the line near the top:
to:
It should help lower the load on your MySQL server.

PS: the verify code hasn't changed since 3.0, so it wouldn't be the 3.1.0 update that caused this issue for you.

Adrian

Thanks Adrian!

It did not error it tonight & I have not changed anything & the only this that is different is that the links that needed to be checked were 2000+ links & when It failed & only checked few hundred & it keep on piling as it ran every-night. so when I verified it manually from web running with same settings as 15 days. It ran & checked for few hundred & then script quit & showed links it verified & good/bad result. Which makes me wonder is why when cron times-out like this, it does not gracefully end, instead start showing errors & continues till all links are executed. even thought at end will only show results for links actually verified which is good

Server info:-
Kernel version 2.4.21-37.ELsmp
Apache version 1.3.34 (Unix)
PERL version 5.8.4
MySQL version 4.1.14-standard

Thanks!

here is my new findings....

I changed verify-nph file to child max 1
still got same error... only starts when their are over 1000 links to verify.
as said before that my server's mySQL may be didn't allowed multiple connections (childs) I should reduce it from 10 to 5.
I notice on average the server CPU load is less than 1 on Quad CPU server.(which is good)

so I changed cron job time & that also didn't help...

last thing was, I changed child 1 to 29 to see what will happened... same error

Finally, I run verify from web using 29.... it went through w/o problem & checked all 1000+ links using same condition.
Now the links that need to verify are less than 100 & cron job works fine....

So to sum up, I think it is 100% LinkSQL code that does create problem when running in cron jobs regardless of how many childs used & only of links over 1000.

Any feedback as to what may be causing this?

Could you send me ssh and admin panel access and the what exactly has to be done to make the problem occur?

Adrian

Hi Jasy007,

did you get any further with this, I have posted a few times but no luck, I have exaclty the same porblems running LSQL verify.

cheers
Kev

Cheers
KevM