Franck Routier

Thanks for your help. There are indeed repeatint errors in service-history.log, saying: Caused by: org.postgresql.util.PSQLException: ERROR: null value in column "TIMEZONE" of relation "history_agents" violates not-null constraint with this stack: Détail : Failing row contains (1751557007085000, controller-test, test-agent, http://localhost:4445, null, 2025-07-03 15:36:47.085, null, null, null, null, 2025-07-03 15:36:47.085). at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2676)...

HI, I have a running JS7 instance for some time, and everything was working fine, but for wome time, I cannot access the Order Log of running orders anymore. I get an error message, for example: Couldn't find order log for #2025-07-13#T42020297532-root|sagcsl I looked into the different log files I was able to spot, but had not success... I don't find any specific error message that would enlighten me. Does anyone have an idea ? Thanks Franck

Hi, I am in the process of migrating from an older JS version to JS7. I have a running instance, with controller-id set to "controller-test". It's working great, and it is to be promoted as a production instance. So I now want to change the controller-id to controller-prod. I changed the config in var/config/controller.conf and restarted the service, but cintroller fails to start as it find references to previous id: 2023-11-05T10:13:16,210 info Rq8GCqou js7.data.event.SnapshotableStateBuilder -...

Hi, I need to update my JobScheduler from 1.13.2 to 1.13.8, as I think I'm hit by this bug https://change.sos-berlin.com/browse/JOC-1096?src=confmacro regarding DST in JOC. A patched war is available for 1.13.8. My problem is that I don't find the jobscheduler_linux_x64_update.1.13.8.tar.gz file, and download link in https://www.sos-berlin.com/en/jobscheduler-downloads says full install / update. So, can I use the "full install / update" file (reading jobscheduler_linux-x64.1.13.8.tar.gz) to update...

Thanks a lot for the elaborated answer. I appreciate that there is a paid support available, this is an option I might consider. That said, I found the culprit... it was loosely related to Jobscheduler, and definitely not to the database connections. In fact the IP address in /etc/hosts was wrong for the hostname. So, JOC Cockpit used the hostname to communicate with the Jobscheduler (REST API I guess), and the hostname was right, but it finally resolved to the other server IP. Otherwise, every setting...

Thanks Andreas, I appreciate your first guess, as it exorcized my fear of Jobscheduler doing black magic :-) Anyway, I started afresh a reinstalled all the stack from newly downloaded tar.gz. And... there is still some information somewhere that breaks things, as launching a task on JOC2 will: create a line in the Audit log tab. The schedulerid is right here. but nothing appears in the history tab... it will show in JOC1 !!! * and the job was executed on Jobscheduler1 as well !!!! Finally your first...

Hi, I have Jobscheduler installed as standalone master on a linux host, alongside a JOC. Both use a Postgresql database on same host. I have installed another instance of JobScheduler on another host on the same network, with another JOC. The scheduler ID I chossed is different. I also use a local Postgresql database, and the db name as well as the user password on the db are different as well. So I excpect the two Jobscheduler + JOC instances to be totally independant. BUT... the second JOC does...

Debug + target