hare krsna,
yesterday night i went to bed after restarting our AWS2 server – ISKCONconnection, gbcspt – which had crashed, waking up some 4 hours later to AWS1 – chantnow & co – having crashed half an hour ago. but it came up again half an hour later, without me having done anything!
that hasn’t happened before. the server has an uptime of 4 days+, so it wasn’t somebody else restarting it. checking cron-jobs executed around this time, the only thing i find is an hourly automated MySQL command to check & repair the table chantnowdb.wp4y_posts, the ‘posts’ table of chantnow.com, which often gets corrupted.
i just want to make sure it wasn’t you @Pancharatna.das … you’re the only one i can think of who might have done anything to get the server running again – restart services or reboot the server…
it seems most likely that the hourly cron-job repairing the MySQL table got things working again. this isn’t the only reason the server goes down, there’s PHP and/or MySQL using up all available memory or the server running out of CPU cycles too that cause it to crash.
most of these things happen because of our present chantnow.com site being such a mess though. i want to move that up in my “urgency list” to make things more stable.
3 AM now and i’m seeing the same weird messages: