Start jobserver will always overwrite jobserver.conf

[domini...@conrad.de]

Dear schedulix masters,

we are using schedulix version 11.

After updating Java from 11 to 17 we encountered a problem with starting the jobserver.

We are filling the jobserver.conf file with our values, it looks like this:

#
# $Id: jobserver.conf.template,v 1.2 2006/02/11 00:40:46 bernhard Exp $
#
# Copyright (C) 2006 independIT Integrative Technologies GmbH
#

#
# The host to connect to
#
RepoHost=cdc-schedulix-preprod
#
# The port to connect to
#
RepoPort=2506
#
# User name to login with
#
RepoUser= "GLOBAL.'SERVER'.'cdc-schedulix-jobserver-01-preprod'"
#
# Password to login with
#
RepoPass=XXX

After we start our Jobserver we see this messages in our log and also the jobserver.conf file looks different.

WARNING [Jobserver] 20-08-2025 09:08:35 +0000 (04305101139) No line with USE_SSL found in /home/schedulix/etc/jobserver.conf
jobserver (server) 2.11 (1.1)
copyright (c) 2002-2023 independit integrative technologies gmbh
all rights reserved
WARNING [Jobserver] 20-08-2025 09:08:35 +0000 (04305101139) No line with TRUSTSTORE found in /home/schedulix/etc/jobserver.conf
WARNING [Jobserver] 20-08-2025 09:08:35 +0000 (04305101139) No line with KEYSTORE found in /home/schedulix/etc/jobserver.conf

jobserver.conf changed to this

#
# $Id: jobserver.conf.template,v 1.2 2006/02/11 00:40:46 bernhard Exp $
#
# Copyright (C) 2006 independIT Integrative Technologies GmbH
#

#
# The host to connect to
#
RepoHost=""
#
# The port to connect to
#
RepoPort=0
#
# User name to login with
#
RepoUser= "GLOBAL.'SERVER'.'cdc-schedulix-jobserver-01-preprod'"
#
# Password to login with
#
RepoPass=XXX

USE_SSL = "false"

TRUSTSTORE = ""

KEYSTORE = ""

Without the RepoHost and RepPort jobserver doesn't know where to connect to.

but when I change RepoHost and RepoPort back to my values, they will be overwritten again with starting the jobserver again.

Start script looks like this

$BICSUITEHOME/bin/jobserver-run $BICSUITECONFIG/jobserver.conf $BICSUITELOGDIR/jobserver.out

I am clueless why our jobserver.conf file will be overwritten when starting our jobserver.

Do you have any idea what is happening and how we can fix it?

Best regards

Dominik

[Ronald Jeninga]

Hi Dominik,

actually, it's a kind of feature....

Most important is that the values REPOHOST and REPOPORT are set in  the configuration of the Jobserver.

You can find its configuration on the config tab of the jobserver in the web GUI.

Most of the time it'll be sufficient to set those two values at GLOBAL level and have them inherited down the tree.

If you have a special network design where the host running the scheduling server has different names or IP addresses depending on the subnet from where you want to access it, you'll have to specify those values at lower level.

If a Jobserver connects, the scheduling server will send it its configuration.

Then, if the Jobserver detects that the REPOHOST and/or REPOPORT values (or any of the other values like USE_SSL, TRUSTSTORE, KEYSTORE and alike) differ from the value it finds in its configuration file,  the Jobserver will update its configuration file, disconnect and reconnect.

This comes in very handy if you want to move the scheduling server from one host to another, if you want to enable or disable SSL communication, or if you want to rename the Jobserver (e.g. redesigning the scope tree).

What I find odd is that you say this happens since you've updated Java.

So far I didn't receive any issue reports (well, apart from the garbage collector's configuration).

Hence, please check the config of the Jobserver and correct it if required.

If everything looks OK, we'll have to search deeper for the cause.

Best regards,

Ronald

[domini...@conrad.de]

Hello Ronald,

Thanks for your reply.

Adding the value to the GLOBAL section for the jobserver fixed the issue on our side.

The interesting part is that we only encountered this problem on our PrePROD environment (which uses Java 17), and not on our PROD environment (which uses Java 11). I don't recall ever having to set this in the UI before and have it inherit from the GLOBAL section.

But with that small change, it's now working perfectly.

Thanks a lot.

Best regards,
Dominik