Bug #7996
closedScheduler fails with exception
0%
Description
File "/home/debian/klever-work/../klever/scheduler/bin/../schedulers/__init__.py", line 175, in launch
server_state = self.server.exchange(scheduler_state)
File "/home/debian/klever-work/../klever/scheduler/bin/../server/bridge.py", line 50, in exchange
ret = self.session.json_exchange("service/get_jobs_and_tasks/", data)
File "/home/debian/klever-work/../klever/scheduler/bin/../utils/bridge.py", line 99, in json_exchange
response = self.__request(endpoint, 'POST', json_data)
File "/home/debian/klever-work/../klever/scheduler/bin/../utils/bridge.py", line 77, in __request
method, url))
OSError: Got unexpected status code "504" when send "POST" request to "http://localhost:8998/service/get_jobs_and_tasks/"
Updated by Evgeny Novikov about 7 years ago
For me it is pretty fine if schedulers and all other components fail immediately when they receive such the errors from Bridge. This means that the whole system crashed unrecoverably. Sometimes restarts can help but generally one need to contact administrators/developers for considering and fixing issues in the semi manual way. The most trivial way is to recreate everything from scratch. Other thoughts?
Updated by Evgeny Novikov almost 7 years ago
This issue was likely fixed by providing means for automatic restarts, wasn't it?
Updated by Ilja Zakharov almost 7 years ago
- Status changed from New to Closed
Yes, it restarts from scratch in production mode.