I have Debian 4 installed and it seemed to be working fairly smoothly. Then we had power outage due to a storm and it ended up killing the power supply and motherboard of another PC, upon reboot of Debian it checked the disks and seemed to be fine, but now I am noticing three problems. I don't see any errors on the screen when I boot but if I need to stop and start mysql I get the following error when I start it

I have run the following command to no avail
I have also logged into phpMyAdmin selected the database checked all tables in the database and selected Repair table at the bottom and repeated for all databases no errors on any database. I even went as far as removing all databases stopping mysql and removing mysql and then installing it and running the mysql_install_db and I get the same error when I start mysql. I have no idea what I can do to fix this error.

I also noticed since this that cron jobs haven't been run when I check cron is not started I manually start it and seems to be fine until I reboot then I have to go back and manually start cron.

Last error I get is the following
There is errors in the log about this, the position changes from position 0 to 4.

The only thing that has changed is instead of the Debian PC only being used remotely that now someone is using it at the terminal until we can replace the motherboard and power supply of the PC that lost them in the storm. The only thing it is being used for is view web pages, watch movies, instant message with pigeon and play an online game (uses wine to do this) I believe the game is Nitto.

Any help on these issues would be greatly appreciated.

I've seen a couple of places that say this isn't an error, but simply the way it works. I have to confess that it looks more like a notice than an error to me.

From: http://ubuntuforums.org/archive/index.php/t-598657.html

Up to this point I have not seen it, but I have not been using Debian long switched from Slackware. But if it is not an error there no need to worry about it just the other two problems, well the one I think only one I need to look at is the cron error from what I can tell the other problem is not an error.

Can you give some context to the gconf error? i.e. some lines above that and below? Also, have you tried running:

I did the apt-get update/upgrade most were due to openoffice but did notice a libxml in with it. Required a reboot when I did it because it did my kernel as well. There were no new entries for this so I went back to this morning as you can see from the timestamp of the logs.

Are you saying it's working OK and cron is fine after the reboot?

cron had to be manually started. I just can't figure out what has changed other then instead of someone using it remotely using either ssh or vnc someone is at the terminal using it until their PC gets replaced/rebuilt

Have you tried reinstalling cron?

I am trying that now, waiting for system to come back up to see if it starts cron at boot. Nope here is what I did after a reboot.

As you can see it is not started after a reboot. Below I stop it knowing I going to get an error because it is not running.

Below I start cron and run a ps aux | grep cron

FINALLY solved this along with what you have suggested I did the following and it fixed it

Then rebooted did a ps aux | grep cron and it is running and here is what it did

I haven't used these yet, and I keep forgetting they exist. I wonder if that was all you needed? In any case, it's fixed, so it doesn't matter. Have fun!

Main thing is it is working again. Thank you for all your help.