Notes |
|
(0013093)
|
psarobe
|
2009-02-03 18:02
(edited on: 2009-02-03 18:18) |
|
Juanpa,
After restarting manually the console then you see correctly the version 240. To me it's clear that for some reason the Rollback process doesn't reboot the system and that's the reason why the tomcat service is down and the console doesn't work properly
Unfortunately after the rollback the console does not work properly because of:
1. If you go to System information it doesn't tell you the installed software. SEE ATTACH error_rollback_3.png
2. If you go to System Updates and press "Check for Updates" it doesn't do anything. SEE ATTACH error_rollback_4.png
|
|
|
|
Once the rollback is done it performs a backup restore. That is why Tomcat is down. Did the restore finish? Once that is done the system is rebooted. |
|
|
|
1. The rollback finished and a message is shown saying that.
2. And for sure it doesn't reboot the system otherwise:
2.1 The tomcat would be up
2.2 I wouldn't have to restart the console |
|
|
|
Apart from that take into account my first note. Do you want me reboot the system manually and see if everything works fine? |
|
|
|
I reboot the system manually and still the same problems. I'm not able to check for updates and the system information doesn't tell you the installed software |
|
|
|
Did the update to MP2 do a backup before updating?
Did you see if it started a restore after the rollback? |
|
|
|
There are 2 issue here:
1) The rollback fails because of a typo in /etc/init.d/raa-restore
2) The console fails because of issue 0007220.
Once the typo in 1) is fixed I'll close this issue because the problem comes from 0007220. |
|
|
|
To be fixed in the upcoming 2.40MP4 release. |
|