search

radical-collaboration / extasy-grlsd

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

Unable to distinguish several entk runs #73

Open euhruska opened 6 years ago

euhruska commented 6 years ago

Currently, I have multiple runs and each log looks identical, shown below. My issue is I have to kill one of them because of a bug, but don't remember which tmux run was which. I can't scroll up since the log is too long. Is there a way to distinguish the log immediately? At the same time, it seems to me that each log repeats radical.entk.task_manager.0000, which isn't terribly informative. Maybe periodically write the rp session name or the associated bluewaters job id.

2018-08-20 19:53:01,085: radical.entk.task_manager.0000: MainProcess                     : heartbeat      : INFO    : Received heartbeat response
2018-08-20 19:53:01,086: radical.entk.task_manager.0000: MainProcess                     : heartbeat      : INFO    : Sent heartbeat request
2018-08-20 19:53:01,463: radical.entk.task_manager.0000: task-manager                    : MainThread     : INFO    : Received heartbeat request                                                                    2018-08-20 19:53:01,464: radical.entk.task_manager.0000: task-manager                    : MainThread     : INFO    : Sent heartbeat response
2018-08-20 19:53:31,234: radical.entk.task_manager.0000: MainProcess                     : heartbeat      : INFO    : Received heartbeat response                                                                   2018-08-20 19:53:31,234: radical.entk.task_manager.0000: MainProcess                     : heartbeat      : INFO    : Sent heartbeat request
vivek-bala commented 6 years ago

The logs are printed to stdout so you would have to either rename your tmux sessions or capture stdout to a file (see here) with a name that you prefer. Note that although the log messages are printed to stdout, the profiles are created in a folder with unique id of the format re.session.*

Hope that helps!

euhruska commented 6 years ago

Is there in the log somewhere the rp session name/id or the associated bluewaters job ID? I can't find it. I capture the stdout to a file, so that helps, but finding out while log belongs to which rp session is the problem.

vivek-bala commented 6 years ago

I see. Right now there isn't, unfortunately. We have been discussing putting the rp.session. folder inside the re.session. on each run so that the association is automatic. I will try to include it the next release.

euhruska commented 6 years ago

Is the re.Session name/id somewhere in the log?