I attempted to upgrade a JunOS SPACE instance from 15.2R1 to 15.2R2. It would sit at “upgrade process has not started” and 0%. If I changed the URI to the base, I’d be back in the SPACE GUI as if nothing had happened and I had never entered maintenance mode.
This was caused by a failed upgrade months earlier which left a msg.<date> file behind in /var/jmp_upgrade/master/msg . Deleting that file allowed me to successfully upgrade the unit.
After a successful upgrade, the msg/ directory will be empty in both the master and slave directories.
In the process, I learned about a few more files that SPACE looks for. If these exist from a failed upgrade, they can keep a new upgrade from starting. Delete these if they exist:
/var/log/activeUpgradeStatus.log
/var/jmp_upgrade/slave/log/upgradeMetaData.txt
You can find a clue as to why your upgrade is not proceeding in these two directories:
/var/jmp_upgrade/slave/log/
/var/jmp_upgrade/master/log/
Look for log files named after the current and target SPACE version.
Also monitor this file for any issues with maintenance mode:
/tmp/maintenance.log
Thorsten on (mostly) Tech 