Hola, is it only me who is discovering that since we ported to the new server the website is quite often offline? It seems that there is something like a wakeonlan-mode? Cause after about one minute the server is up again! About highnoon (gmt+1) there is most of the times a database-error (might be coincidence).
For me that is no problem! Actually I spend much too much time in the forum during worktime 
so for me it is even ok! 
But it doesn't make a good impression to the outer world if the first contact to jME would be a "server is not responsing"-error.
Just wanted to mention it. Nevertheless keep on with the good work.
ToM
I get sent here http://guide.opendns.com/?url=jmonkeyengine.com&servfail quite often, when I come on, this my home page too, firefox isn't set to start up on the homepage though but thats not the issue is it. when click home again sometimes more than once the site will finally load.
i can second that database error. I've seen it a few times around noon at GMT +1 … e.g. yesterday
Edit: It's happening when the server backs up the important website data at 0600 EST, otherwise known as noon by you guys…
I can just repeat it. Is it possible to turn off that "wake on lan"-option for the jME-web-server? I explain again the scenario:
- browsing to jmonkeyengine.com => error
- about one minute later the website is online.
What is that? Looks for me like a wake-on-lan or green-pc or whatever!
ttrocha said:
I can just repeat it. Is it possible to turn off that "wake on lan"-option for the jME-web-server? I explain again the scenario:
- browsing to jmonkeyengine.com => error
- about one minute later the website is online.
What is that? Looks for me like a wake-on-lan or green-pc or whatever!
There's nothing of that sort running... on the hardware or software side. Is this still happening at the GMT+1 time?
No that has nothing to do with the database-backups! That comes from time to time! Seems to me that in this case noone used the site for a while! As I said, it is down, and half a minute later it is up… quite strange…
Anyone else recognized that behavior or found the database offline (beside the gmt+1-issue)?
So for you(sbook) the webiste is always online when you try to access it!??
Actually for me that is no problem! I know that it is accessable after that short period! I think of what first users might think…
I find the site down quite often and usually it does come back online after a minute or so.
Yes I've had these very short down-times as well now that you mention it. I couldn't tell whether it was a problem on my end or the server because it was so brief.
ttrocha said:
No that has nothing to do with the database-backups! That comes from time to time! Seems to me that in this case noone used the site for a while! As I said, it is down, and half a minute later it is up.... quite strange...
Anyone else recognized that behavior or found the database offline (beside the gmt+1-issue)?
So for you(sbook) the webiste is always online when you try to access it!??
Actually for me that is no problem! I know that it is accessable after that short period! I think of what first users might think...
That's very strange, I can honestly say that I've never encountered that... The google analytics reports lower usage in the time's you're reporting but has never seems to hit 0, the lowest it goes is about 10-12 users per hour..
I absolutely understand your [very real] concern though, I'll have a more discerning look into this
sbook,
just so you know (and can check or test or whatever). The website was down for hours now, starting pretty much at 12AM GMT+1 until i guess 3PM or so. :|
cheers
EDIT: thats the error message i get:
Connection Problems
Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later
dhdd said:
sbook,
just so you know (and can check or test or whatever). The website was down for hours now, starting pretty much at 12AM GMT+1 until i guess 3PM or so. :|
cheers
EDIT: thats the error message i get:
Connection Problems
Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later
Thank you, we caught it and are looking in to it