What about the file itself (i.e., /mnt/galaxy/galaxy-app/main.log) - who
owns it? It could be that Galaxy was started manually during the build
phase by a user other than galaxy and so it can't rewrite that file now?
Either way, you can just delete that file and try it again.
As an image is built,
Hi,
I didn't do the cleanup, because I didn't change anything on the generated
instance/image.
I now created a new clean instance and get this error:
2015-06-22 22:35:37,190 DEBUG master:2482 Monitor done adding
service Galaxy (setting config_changed)
> 2015-06-22 22:35:37,190 DEBUG
Hi Alexander,
When you build the image, did you run the image cleanup step? RabbitMQ's
database needs to be cleaned up before building the image otherwise the
application won't start properly and the AMQP connection will never be
established.
You can also post the entire CloudMan's log somewhere a
Maybe connected. this error (happening multiple times):
> Exception happened during processing of request from ('127.0.0.1', 37201)
> Traceback (most recent call last):
> File
> "/home/ubuntu/.virtualenvs/CM/local/lib/python2.7/site-packages/paste/httpser
Hi,
I have the following problem:
First, the job scheduling didn't work.
I tried to upload a file, but the job was waiting.
Then I checked "squeue", which timed out.
The slurm service was running.
Then I restarted the cluster.
Now I even have problems access the cloudman admin page.
Meaning, the
