This problem can be solved by deregistering the jobserver after shutdown with the sdmsh command:
deregister <jobserver name>
Example shutdown and deregister of a jobserver using sdmsh or web gui shell:
When a jobserver is started and connects to schedulix it becomes registered automatically, telling the system he is ready to process jobs.
A shutdown of a jobserver or just being disconnected for a while
like offline jobservers will still allow jobs to be assigned to
Think about jobs which can be processed by one jobserver only. Not allowing to still assign those jobs to the disconnect the jobserver will put all of those jobs in ERROR because of resource shortage.
This is not what we want if we want to just shutdown a jobserver temporarily for maintenance like changing environment variables.
Deregistering a jobserver will tell schedulix to not assign jobs to this jobserver any longer which may result in jobs in ERROR because of resource shortage if this is the only jobserver possible for those jobs.
Note that schedulix also puts all jobs still active on the deregistered jobserver into a BROKEN_FINISHED state to allow rerunning them on an other available jobserver after restart.
Does this answer your question?