- Joined
- May 19, 2006
- Messages
- 156,720
- Reaction score
- 53,497
- Gender
- Male
- Political Leaning
- Undisclosed
For what? Re-posting them?
Just in case the server crashes and also if I have to reference them in the future.
For what? Re-posting them?
Just in case the server crashes and also if I have to reference them in the future.
I used to do that when I posted via dial-up...the chance of some glitch during the posting was much higher, so I needed to ensure I could repost if necessary.Just in case the server crashes and also if I have to reference them in the future.
Short version: The ISP was painting their datacenter and the painter accidentally 'elbowed' the emergency power off switch. Databases do not like instant power off. It needed to be repaired. We lost the posts while the server was confused.
Long technical version: The above statement, plus... During the data recovery the server had mixed tokens and session ID's in the system after reboot. That enabled a few to be able to log in and possibly post. However, I was unable to turn off the forum software as the switch is in the database. We were also unable to view/update via phpmyadmin. During this time, the troubleshooters attempted repair from daily and weekly backups and were unsuccessful (due to the errors stated previously). Command line on the system appeared great resulting in the technicians having quick judgments to the current status. When attempting to contact the ports for the db via 80, it would go nuts. The errors (5 of them) combined with our multiple cache system made it even more of a challenge to find the root cause.
Results: The database was eventually recovered from the latest daily backup successfully. Posts after 2:30am Saturday are lost.
Please accept our apology and thank you for your patience during the last two days.
I did! The thing is the OP does not states or even hints that Apacherat posted NSA sensitive information that caused it to appear that DP had somehow "accidentally" switched the power off button! It is a conspiracy!
Hence now all his posts together with our posts (lateral damage) were removed from Saturday!
Short version: The ISP was painting their datacenter and the painter accidentally 'elbowed' the emergency power off switch. Databases do not like instant power off. It needed to be repaired. We lost the posts while the server was confused.
Long technical version: The above statement, plus... During the data recovery the server had mixed tokens and session ID's in the system after reboot. That enabled a few to be able to log in and possibly post. However, I was unable to turn off the forum software as the switch is in the database. We were also unable to view/update via phpmyadmin. During this time, the troubleshooters attempted repair from daily and weekly backups and were unsuccessful (due to the errors stated previously). Command line on the system appeared great resulting in the technicians having quick judgments to the current status. When attempting to contact the ports for the db via 80, it would go nuts. The errors (5 of them) combined with our multiple cache system made it even more of a challenge to find the root cause.
Results: The database was eventually recovered from the latest daily backup successfully. Posts after 2:30am Saturday are lost.
Please accept our apology and thank you for your patience during the last two days.
Posts after 2:30am Saturday are lost.
I have wondered who to thank for this little playground.
Thank you. This is a wonderful place to play and meet people.
Short version: The ISP was painting their datacenter and the painter accidentally 'elbowed' the emergency power off switch. Databases do not like instant power off. It needed to be repaired. We lost the posts while the server was confused.
Long technical version: The above statement, plus... During the data recovery the server had mixed tokens and session ID's in the system after reboot. That enabled a few to be able to log in and possibly post. However, I was unable to turn off the forum software as the switch is in the database. We were also unable to view/update via phpmyadmin. During this time, the troubleshooters attempted repair from daily and weekly backups and were unsuccessful (due to the errors stated previously). Command line on the system appeared great resulting in the technicians having quick judgments to the current status. When attempting to contact the ports for the db via 80, it would go nuts. The errors (5 of them) combined with our multiple cache system made it even more of a challenge to find the root cause.
Results: The database was eventually recovered from the latest daily backup successfully. Posts after 2:30am Saturday are lost.
Please accept our apology and thank you for your patience during the last two days.
There's an emergency power-off switch or 3 around the edges of the datacenter I work at....not sure they're connected though.
They're orange, surrounded by alternating black/yellow slashes and have clear plastic covers to prevent accidents.
And another hickup. Good thing Vauge does not need sleep.
And another hickup. Good thing Vauge does not need sleep.
I am working on a letter delicately written to reflect how we all feel. I just need to count to 10 first.
I am working on a letter delicately written to reflect how we all feel. I just need to count to 10 first.
No biggie. For straight American males who love football like I do, we lost nothing.
Post on DP...or watch LSU and Georgia. Hmmm...
*levels hands up and down*
Posts after 2:30am Saturday are lost.
.