radical-collaboration / extasy-grlsd

Repository to hold the input data and scripts for the ExTASY gromacs-lsdmap work
1 stars 1 forks source link

two extasy runs error #31

Closed euhruska closed 6 years ago

euhruska commented 6 years ago

I tried two extasy runs at the same time (with different setting), I got the below messages for both runs and nothing else happened:

2018-01-16 20:43:30,713: radical.entk.task_manager: MainProcess                     : MainThread     : WARNING : tmgr process already running, but attempted to restart!
2018-01-16 20:43:30,713: radical.entk.appmanager: MainProcess                     : MainThread     : INFO    : Restarting heartbeat thread from AppManager
2018-01-16 20:43:30,713: radical.entk.task_manager: MainProcess                     : MainThread     : WARNING : Heartbeat thread already running, but attempted to restart!
2018-01-16 20:43:30,713: radical.entk.appmanager: MainProcess                     : MainThread     : INFO    : Terminating heartbeat thread from AppManager
2018-01-16 20:43:30,713: radical.entk.task_manager: MainProcess                     : MainThread     : INFO    : Hearbeat thread terminated
2018-01-16 20:43:30,721: radical.entk.appmanager: MainProcess                     : MainThread     : INFO    : Restarting task manager process from AppManager
2018-01-16 20:43:30,721: radical.entk.task_manager: MainProcess                     : MainThread     : WARNING : tmgr process already running, but attempted to restart!

I sit possible to runn several extasy's at the same time?

vivek-bala commented 6 years ago

Yes, it is. But you will have to use two different docker RabbitMQ instances. Each of those will have different ports and you can assign the respective ports to the AppManager in the two extasy scripts.

The port assigned should be the port that maps to 5672. See http://radicalentk-06.readthedocs.io/en/arch-v0.6/install.html#installing-rabbitmq-using-docker

vivek-bala commented 6 years ago

Did you get a chance to try this out? Let me know if there are still any more issues.

euhruska commented 6 years ago

I don't currently use docker

euhruska commented 6 years ago

Still relevant, especially since bigger runs have a long wait time on bw. In that time can't run shorter simulations

euhruska commented 6 years ago

currently limited by this issue, can't put any more jobs into the bw queue

vivek-bala commented 6 years ago

Hey Eugen, you can use the same docker instance to run N number of EnTK scripts. The number of docker instances shouldn't be an issue any more.

vivek-bala commented 6 years ago

If you still face any issues, please attach the EnTK verbose logs (from the stdout+stderr). Thanks.

euhruska commented 6 years ago

will have to wait till the admin installs docker on my local system

vivek-bala commented 6 years ago

What is the docker instance that you use right now? For any experiment.

euhruska commented 6 years ago

I don't use docker, I install rabbitmq in conda

vivek-bala commented 6 years ago

Ah okay. You can use the same rabbitmq-server for two EnTK scripts. The latest release (>=0.7), each EnTK run uses unique id.

euhruska commented 6 years ago

works