Hi Andreas, I modified treatments which generated errors. I shut down the Scheduler, emptied the cache directory, then restarted. There is no more problem. The modified or added jobs are clearly visible in the cockpit interface. For your information, you have always an error : com.sos.scheduler.engine.plugins.newwebservice.routes.ApiRoute [WARN ] - java.lang.IllegalArgumentException: requirement failed: Invalid AgentAddress: ProcessClass are defined like this: serveur:port. I don't understand why...
Hi Andreas, I modified treatments which generated errors. I shut down the OJS, emptied the cache directory, then restarted. There is no more problem. The modified or added jobs are clearly visible in the cockpit interface. For your information, you have always an error : com.sos.scheduler.engine.plugins.newwebservice.routes.ApiRoute [WARN ] - java.lang.IllegalArgumentException: requirement failed: Invalid AgentAddress: ProcessClass are defined like this: serveur:port. I don't understand why this...
Hi Andreas and thank you again for your response. I noticed this exception, but I didn't think it was that important. We have this exception since the upgrade to 1.12.8. In reality, agents are not agent, but normal schedulers. We use ProcessClass instead of Agent. It's possible to update db to not consider Agent but real scheduler ? Or delete Agent from db ? Thanks again. Best regards Sebastien
Hi Andreas and thank you again for your response. I noticed this exception, but I didn't think it was that important. We have this exception since the upgrade to 1.12.8. In reality, agents are not agent, but normal schedulers. It's possible to update db to not consider Agent but real scheduler ? Thanks again. Best regards Sebastien
Hi Andreas, and thank you for your very quick response. Thank you again for precisions about reception of Informations by Cockpit. For plugin inventory: - in supervisor, i sent you attached-file (supervisor-inventory.log), data extracted with a grep command -A10 -B10 -r inventory scheduler.log - in Master, no trace of inventory plugin in scheduler.log. But there is a line for the inventory plugin in the configuration file. - in Cockpit, i sent you an attached-file (cockpit-inventory-50.log), data...
Hi Andreas, and thank you for your very quick response. Thank you again for precisions about reception of Informations by Cockpit. For plugin inventory: - in supervisor, i sent you attached-file (supervisor-inventory.log), data extracted with a grep command -A10 -B10 -r inventory scheduler.log - in Master, no trace of inventory plugin in scheduler.log - in Cockpit, i sent you an attached-file (cockpit-inventory-50.log), data extracted with a grep command -A50 -B50 -r inventory 2021_12_16.stderrout.log....
Hi Andreas, and thank you for your very quick response. Thank you agin for precisions about reception of Informations by Cockpit. For plugin inventory: - in supervisor, i sent you attached-file (supervisor-inventory.log), data extracted with a grep command -A10 -B10 -r inventory scheduler.log - in Master, no trace of inventory plugin in scheduler.log - in Cockpit, i sent you an attached-file (cockpit-inventory-50.log), data extracted with a grep command -A50 -B50 -r inventory 2021_12_16.stderrout.log....
JOC don't display new jobchain and modified jobchain
Hi Uwe, i've downloaded the patch, the plugin is now active every morning. Thank you. Regards, Sebastien
Hi Uwe, i've downloaded the patch, the plugin is active every morning. Thank you. Regards, Sebastien
Hi Uwe, i download the patch, the plugin is active every morning. Thank you. Regards, Sebastien
Hi Andreas, Thank you for your reply. Yes, update to 1.13.9 for both products, Master and Cockpit. I attach for you the scheduler log file. For moment, the JobStreams Plugin Logger Level is set to 'info' in the log4j2.xml file. Thank you in avance for your time. Best regards, Sebastien
JobStream Plugin is not active
Hi all, The latest version installed (1.12.8) is functional. I install scheduler only, no agent. I use Supervisor and multiple remote scheduler. We stayed on Cockpit for HMI. The job, jobchain, order, ..c., are created with the JOE editor on Windows and Linux. The execution of a job chain on a given server can be done by adjusting the scheduler.remote_scheduler variable in the order. I would like to use the same mechanism to execute a job chain on a ReturnCode of a node of another job chain. For...