I performed a do-release-upgrade through SSH to upgrade a server from 8.04 to 10.04.
I have followed the on-screen infos through the upgrade and everything seemed to go well. However, after the upgrade and the final reboot, the server never started again. Or at least was unreachable (Apache, SSH, mail... Nothing!).
Fortunately the hosting company provides a recovery system which allows me to reach the server with a live Linux, to mount the partitions and access them.
So my question is: now that I'm in recovery mode, where should I look to find out where the problem comes from? I'm looking in the system logs but don't find anything.
I need to have this server up and running again by 8 tomorrow morning (2am now), so your help would be very much appreciated...
I found this in the logs:
Mar 31 22:43:14 wpc2617 exiting on signal 15 Mar 31 22:55:37 wpc2617 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="14695" x-info="http://www.rsyslog.com"] (re)start Mar 31 22:55:37 wpc2617 rsyslogd: rsyslogd's groupid changed to 103 Mar 31 22:55:37 wpc2617 rsyslogd: rsyslogd's userid changed to 102
And I wonder if a userid change couldn't explain the whole issue. Is it possible that a/ it happens during an upgrade b/ it has such consequences?