How to recreate:

1.) octopus up-stable o1
2.) abort upgrade (n)
3.) change some setting of o1.octopus.cnf
4.) octopus up-stable o1

Fails with:

This Aegir Instance is already up to date By default only one upgrade daily is allowed If you wish to run upgrade for /data/disk/o1 again, remove its control file /data/disk/o1/log/up-120519

5.) rm data/disk/o1/log/up-120519
6.) octopus up-stable o1

Another BOA installer is running probably - /var/run/boa_run.pid exists

7.) it exists!
8.) getting terrified and post to the issue queue... .

Comments

muschpusch’s picture

muschpusch commented
Issue summary: View changes

remove name

muschpusch’s picture

muschpusch commented
Title: upgading octopus 2.0.3 » upgading to octopus 2.0.3 from 2.0.2 fails

[just changing title]

omega8cc’s picture

omega8cc commented
Title: upgading to octopus 2.0.3 from 2.0.2 fails » There are pid files preventing running many installers at once - by design
Component: Code » Miscellaneous
Category: bug » support
Status: Active » Closed (works as designed)

This is normal and expected. If you have aborted the script you must delete the two pid files it complains about before it will allow you to run it again - it will also stop cron for tasks until the pid files get removed automatically when the script completes its work.

muschpusch’s picture

muschpusch commented

thank you!!!

muschpusch’s picture

muschpusch commented
Issue summary: View changes

add step