Originally posted by Undave
It happens every night at 10:30pm (BST) and lasts for about 5 or 6 minutes. Would that mean it\'s something to do with the server or with loads of people logging in at the same time or what?
Either way it happens regular as clockwork so just leave the site for a few minutes and try again later.
i can only hypothesize as i do not have access to the server records. i know there is some kind of script that handles broken images. i am sure we have all seen them. there is probably a script that cleans up deleted images also. if these do not run immediately when occured, it may be timed to do so on a schedule, or at least to check to make sure they were done, or some other sever daily function like getting a new list of ads, or something...
a daily occurence could easily cause the database to be unavailable. it coudl also be as you said many people trying to get on at once, or maybe some DDOS type thing where some bot is trying to connect but cannot. some databases have a limit set to the number of users connecting at a time. the acutal time it takes for PHP to conenct to the database depends, but usually isnt very long. like when you make a post it takes only a part of a second to interact with the database and you are done. so odds of too many people are few and far between, but can be possible if the limit is reached when a bunch of people try to do something at once.
not sure how the random image script works ont he voting side, but people viewing images coudl easily reach some database limit if MANY people try to hit the site up at once.
otherwise PHP could have stalled. not knowing the version used on the site i couldnt diagnose any problem that may be relevant. PHP does have an option to the maximum amount of time for a script to run before it locks up and is cancelled.
say the PHP script to record a broken image got stuck because the page doesn\'t load or cannot find the image. maybe it alreayd made a conenction to the database and did not close the conenction yet. this would mean one less user to connect to the database as the broken image script may is stuck using it until its (30 seconds by default) maximum execution time.
this is all just saying CMoN has its own dedicated server. if the server is shared with other sites, then maybe one of them having a problem connecting to their database could be slowing down the database software, or could have some daily script running on the server itself to backup the database that means it cannot be connected to by the CMoN scripts.
if that error comes at the same time each day it is surely not user error, but server doings. maybe not error, but its doing something, whether it is supposed to or not.
that is just my guess.
i would check if i new the UTC of your BST time given. +1 UTC?
either way it is the PHP trying to conenct to the database using the password and username hidden within the PHP script (not connected to any user account) that normally causes a \"nobody@localhost using password:no\" error.
something in dbconnect.php or whatever script just didn\'t run right.
that is my best guess.