This has been working fine until a couple of days ago and now I receive the following e-mail after a build --all cron:

I have 2 sites and it's only happening on one of them. Any ideas?

Please enable "debug" in Setup > Misc Options, and try again.

What does the error message show (it will be a MySQL query error)

Cheers

Andy (mod)
andy@ultranerds.co.uk

---

Want to give me something back for my help? Please see my Amazon Wish List
GLinks ULTRA Package | GLinks ULTRA Package PRO
Links SQL Plugins | Website Design and SEO | UltraNerds | ULTRAGLobals Plugin | Pre-Made Template Sets | FREE GLinks Plugins!

That's strange. When I enable debigging and run the cron it sends the comlete e-mail with "All Done" time at the bottom. With debugging off it doesn't report past the Build Cool page.

I have noticed that when I changed the cron on the server there is a message: "/usr/bin/crontab permissions are wrong (6755). Please set to 4755."

Don't know if this has anything to do with it.

MMm - odd - not sure :/

Cheers

Andy (mod)
andy@ultranerds.co.uk

---

Want to give me something back for my help? Please see my Amazon Wish List
GLinks ULTRA Package | GLinks ULTRA Package PRO
Links SQL Plugins | Website Design and SEO | UltraNerds | ULTRAGLobals Plugin | Pre-Made Template Sets | FREE GLinks Plugins!

OK, it ran again during the night but returned errors this time. I don't know what to report back here but the general error is as follows:

A fatal error has occured:

Can't call method "fetchall_list" on an undefined value at Links::Build::build_category line 737.
Please enable debugging in setup for more details.

Stack Trace
======================================
Links (3140): Links::environment called at /home/mysite/public_html/cgi-bin/links/admin/Links.pm line 786 with no arguments.
Links (3140): Links::fatal called at Links::Build::build_category line 737 with arguments
(Can't call method "fetchall_list" on an undefined value at Links::Build::build_category line 737.).
Links (3140): Links::Build::build_category called at /home/mysite/public_html/cgi-bin/links/admin/GT/Plugins.pm line 133 with arguments
(HASH(0x17b76e0)).
Links (3140): GT::Plugins::dispatch called at /home/mysite/public_html/cgi-bin/links/admin/Links/Build.pm line 30 with arguments
(GT::Plugins=HASH(0xa5b420), build_category, CODE(0x1051ca0), HASH(0x17b76e0)).
Links (3140): Links::Build::build called at /home/mysite/public_html/cgi-bin/links/admin/nph-build.cgi line 628 with arguments
(category, HASH(0x17b76e0)).
Links (3140): main::_build_category called at /home/mysite/public_html/cgi-bin/links/admin/GT/Plugins.pm line 133 with arguments
(HASH(0xa5f580)).
Links (3140): GT::Plugins::dispatch called at /home/mysite/public_html/cgi-bin/links/admin/nph-build.cgi line 106 with arguments
(GT::Plugins=HASH(0xa5b420), create_category, CODE(0xa16a20), HASH(0xa5f580)).
Links (3140): main::build_all called at /home/mysite/public_html/cgi-bin/links/admin/nph-build.cgi line 65 with no arguments.
Links (3140): main::main called at /home/mysite/public_html/cgi-bin/links/admin/nph-build.cgi line 42 with no arguments.

GT::SQL::error = Failed to execute query: 'SELECT ID FROM mysite_Category WHERE FatherID = ?': MySQL server has gone away $!: Connection reset by peer

Can't call method "fetchall_list" on an undefined value at Links::Build::build_category line 737.

Your MySQL server is dying or disconnecting for some reason.

Adrian

I'm going to change the time of the cron. Yesterday I altered it from 00:00 and it built OK.

Right, I've just had it run again a minute ago and it built OK.

I have 2 cron jobs set to run at 00:00 (nph-build.cgi --all and expiry_notify.pl) so maybe they were conflicting. I've now set nph-build.cgi --all to run 10 minutes after expiry_notify.pl.

We'll see if it changes anything. If not I'll move them both away from 00:00.

Well it looks like splitting the cron job times did the trick. They both ran last night without a hitch.

Strange how they had been working fine for so long and then suddenly started to error. I can only think that it might be something that's changed recently like a software upgrade on the server.

Hi,

on my installation this error occures because the MySQL server didn't allow so many connections at the same time.