Re: PBW status
 

Nope. It's a software error. Can't get the database that runs the site working.

Anybody here know Tomcat and Mysql really well? If you do send me an email.

Geoschmo

Re: PBW status
 

can you send me the error message... I will see if I can help at all... I have to ghost 2 pc's for the plant floor and then set them up... but after that I could have a free hour to help with everyone working on the problem

Re: PBW status
 

Software error? As usual - undo the Last change that you did just before the error occured http://forum.shrapnelgames.com/images/icons/icon12.gif

Well I guess there have been no changes (? - never change a running system!!! http://forum.shrapnelgames.com/images/icons/icon12.gif ), so a software issue should not make PBW refuse to work after running for such a long time. Maybe the database is corrupt or needs a purge? Disk full? Capacity problem - memory? Faulty memory chip?

It might also help to upgrade to the latest Version, but I'm not up to date with Tomcat, known problems and bugfixes. I would probably make a backup of the database, delete it and create it new and fresh, and check if the problem persists. If not, copy the old tables one-by-one until it crashes and if, you have at least located the problem.

I have some time at hands, I can give you any help with mySQL if you need, but I'm no Tomcat expert.

Re: PBW status
 

Yes Roanon, no changes were made. The server froze up yesterday, and after rebooting we have what we have. I suspect you are right and it's some sort of database corruption. Tesco's gonna take a look at it. Hopefully he will be able to resolve it.

Re: PBW status
 

Is it possible that some outside source attempted to access your data base for mining purposes and in doing so caused the error?

I have read stories about this happening on other dedicated gaming sites and forums.

A company, or individual, will target gaming servers for access to emails and any other info on the players that use it. Often resulting in problems for the server.

This normally happens on forums, but it has happened on game servers like Earth 2025, and Utopia, as well as Planetarion.

Geoschmo the PBw server must seem like a gold mine to these SOB's. They get the IP and start hacking, the next thing you know, your data base is fried, PBW is down, and we all start getting spam in our email boxes. Oh ya, then your PayPal account suddenly is frozen and your bank account is drained.

I would be concerned.

Re: PBW status
 

Hacking is not THAT easy, I doubt it. Main reasons for intrusion are often easy-to-crack passwords, pissed off ex-mods/frieds with password knowledge, laughable simplistic password entering/checking routines, or yet another M$ bug (tm). Forum systems, especially those with open source, may be vulnerable to some annoying things, even reading of private data like email addys - as this info is usually available to common Users anyway and therefore less protected. But the database itself is normally safe from destructive intrusions. There are a lot of myths about "hacking", and it is too easy to blame some unknown hackers for any self-created problem with websites.

I think PBW is too small to be of interest, and the personal data too protected - should be easier and more rewarding to hack into the Shrapnell forum. http://forum.shrapnelgames.com/images/icons/icon12.gif

Re: PBW status
 

You have set my mind at ease my dear Roanon. http://forum.shrapnelgames.com/images/icons/icon7.gif Thank you.

So what could cause a Data Base to fail? Power surge, power failure, corrupt info?

I wish I knew more about how they worked, but I don't. Sorry Geo.

Re: PBW status
 

If the comp froze during a database write-access, I would not find it unusual that it got corrupted. Let's hope Tesco can find the time to fix the problem soon.

Re: PBW status
 

don't put high hopes in me i know little of tomcat and java....

Just learning.

Re: PBW status
 

Seems all is not stopped on the PBW site...

I've just received a "[SEIV PBW] Turn not yet received" message.
I Hope the turn will not be executed before the site is back...