You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. python gal.py
2. After the below is printed.
gal: Unmonitored Process Launched (CMD: pypy wc_server.py )
gal: Unmonitored Process Launched (CMD: pypy report_gen.py )
3. 2minutes later:
4.
gal: Monitoring Processes...
gal: WATCHDOG: PID d565f24f2dd14591 EXPIRED
What is the expected output? What do you see instead?
Hours of:
gal: Monitored Process Launched (PID: 7cfb9aebc1e50c97 CMD: pypy gts.py 3 n
run_once get_config pid )
gal: WATCHDOG: PID 9174daae8983ff9a EXPIRED
gal: Monitored Process Launched (PID: b328a506303d5320 CMD: pypy gts.py all y
run_once get_config pid )
gal: WATCHDOG: PID 95d2f4a83582230d EXPIRED
gal: Monitored Process Launched (PID: e5cbb5a0d93b42a7 CMD: pypy gts.py 4 n
run_once get_config pid )
gal: WATCHDOG: PID e36e9203a3d7812f EXPIRED
gal: Monitored Process Launched (PID: 1c26a6b9a6b6a863 CMD: pypy gts.py all n
run_once pid )
What version of the product are you using? On what operating system?
0.3 ubuntu server 12.04 32bit
Please provide any additional information below.
Im not 100% of the expected output, or if in fact this is even an error/issue!
Original issue reported on code.google.com by bitnu...@gmail.com on 18 Apr 2013 at 12:26
The text was updated successfully, but these errors were encountered:
I took a look at this issue:
http://code.google.com/p/ga-bitbot/issues/detail?can=1&q=10&colspec=ID%20Type%20
Status%20Priority%20Milestone%20Owner%20Summary&id=10
I changed these values to match what you said in there but still same result!
"WATCHDOG_TIMEOUT" : 120,
"MONITORED_PROCESS_LAUNCH_TIMEOUT" : 120,
Original comment by bitnu...@gmail.com on 18 Apr 2013 at 12:48
thanks for the reply.
is this still part of the initial startup? do I need to leave this run, will it
output anything different? if left for say 12 hours there would be 100 if not
1000s of these warnings
Original comment by bitnu...@gmail.com on 19 Apr 2013 at 7:37
Original issue reported on code.google.com by
bitnu...@gmail.com
on 18 Apr 2013 at 12:26The text was updated successfully, but these errors were encountered: