Schedulix server not running due to no JDBC found

Yogeshwaran M

unread,

Feb 5, 2025, 7:27:05 AMFeb 5

to schedulix

This is my docker-compose file

version: '3.8'

services:
databaseserver:
image: postgres:14.1-alpine
restart: always
environment:
POSTGRES_USER: schedulix
POSTGRES_PASSWORD: schedulix
POSTGRES_DB: schedulixdb
ports:
- '54325:5432'
volumes:
- ./db:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -d schedulixdb -U schedulix"]
interval: 5s
timeout: 5s
retries: 5

schedulixserver:
build: .
tty: true
ports:
- '2506:2506'
depends_on:
databaseserver:
condition: service_healthy
environment:
JDBC_DRIVER: org.postgresql.Driver
JDBC_URL: jdbc:postgresql://databaseserver:5432/schedulixdb
JDBC_USERNAME: schedulix
JDBC_PASSWORD: schedulix
volumes:
- ./schedulix/server.conf:/opt/schedulix/etc/server.conf:ro

schedulixweb:
image: ennoenno/schedulix:schedulixfe-2.11.0-beta
ports:
- '8085:8001'
- '8095:8095'

volumes:
postgres_data:

Error Message
schedulix-schedulixserver-1 | INFO [main] 03 Feb 2025 16:59:20 GMT Exporting WORKDIR
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT No JDBC Driver Specified
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT ****************** Start Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:162)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.exception.FatalException.<init>(FatalException.java:50)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.Server.connectToDB(Server.java:412)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.RenewTicketThread.initRenewTicketThread(RenewTicketThread.java:97)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.Server.initRenewTicketThread(Server.java:118)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.Server.serverMain(Server.java:466)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.BICServer.main(BICServer.java:151)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT ****************** End Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT Error while unlocking repository (couldn't get database connection)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT ****************** Start Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:162)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.RenewTicketThread.initRenewTicketThread(RenewTicketThread.java:99)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.Server.initRenewTicketThread(Server.java:118)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.Server.serverMain(Server.java:466)
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.BICServer.main(BICServer.java:151)
schedulix-databaseserver-1 |
schedulix-databaseserver-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
schedulix-schedulixserver-1 | ERROR [main] 03 Feb 2025 16:59:20 GMT ****************** End Stacktrace *********************
schedulix-schedulixserver-1 | FATAL [main] 03 Feb 2025 16:59:20 GMT Fatal exception while loading Repository:
schedulix-schedulixserver-1 | No JDBC Driver Specified
schedulix-schedulixserver-1 | FATAL [main] 03 Feb 2025 16:59:20 GMT ****************** Start Stacktrace *********************
schedulix-schedulixserver-1 | FATAL [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:162)
schedulix-schedulixserver-1 | FATAL [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.Server.serverMain(Server.java:475)
schedulix-schedulixserver-1 | FATAL [main] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.BICServer.main(BICServer.java:151)
schedulix-schedulixserver-1 | FATAL [main] 03 Feb 2025 16:59:20 GMT ****************** End Stacktrace *********************
schedulix-schedulixserver-1 | INFO [Shutdown] 03 Feb 2025 16:59:20 GMT ***********************************************
schedulix-schedulixserver-1 | INFO [Shutdown] 03 Feb 2025 16:59:20 GMT ** **
schedulix-schedulixserver-1 | INFO [Shutdown] 03 Feb 2025 16:59:20 GMT ** U N G R A C E F U L S H U T D O W N ! ! **
schedulix-schedulixserver-1 | INFO [Shutdown] 03 Feb 2025 16:59:20 GMT ** **
schedulix-schedulixserver-1 | INFO [Shutdown] 03 Feb 2025 16:59:20 GMT ***********************************************
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT No JDBC Driver Specified
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT ****************** Start Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:162)
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.exception.FatalException.<init>(FatalException.java:50)
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.Server.connectToDB(Server.java:412)
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.ShutdownThread.SDMSrun(ShutdownThread.java:73)
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.util.SDMSThread.run(SDMSThread.java:219)
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT ****************** End Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT Error while unlocking repository (couldn't get database connection)
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT ****************** Start Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:162)
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.ShutdownThread.SDMSrun(ShutdownThread.java:75)
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT de.independit.scheduler.server.util.SDMSThread.run(SDMSThread.java:219)
schedulix-schedulixserver-1 | ERROR [Shutdown] 03 Feb 2025 16:59:20 GMT ****************** End Stacktrace *********************
schedulix-schedulixserver-1 | [scrolllog] Waiting for child (45) to terminate
schedulix-schedulixserver-1 | [scrolllog] Child exited with state 1
schedulix-schedulixserver-1 | [scrolllog] Try to restart child (child terminated with exit code <> 0)

Ronald Jeninga

unread,

Feb 5, 2025, 8:02:51 AMFeb 5

to schedulix

Hi,

please check the entries

DbUrl=jdbc:postgresql:schedulixdb

DbUser=schedulix

DbPasswd=schedulix
JdbcDriver=org.postgresql.Driver

in the $BICSUITECONFIG/server.conf file.

Furthermore the variable JDBCJAR in the $BICSUITECONFIG/java.conf file should point to the jar file containing the JDBC driver, like

JDBCJAR=/usr/share/java/postgresql.jar

That should fix your issue.

(And as soon as you have it running, changing the password to something more secure is definitely member of the set of good ideas ;)

Best regards,

Ronald

Yogeshwaran M

unread,

Feb 6, 2025, 1:51:25 AMFeb 6

to schedulix

After adding the server.conf file. Facing an error.

schedulix-schedulixserver-1 | INFO [main] 06 Feb 2025 06:43:22 GMT JDBC Driver used : PostgreSQL JDBC Driver
schedulix-schedulixserver-1 | INFO [main] 06 Feb 2025 06:43:22 GMT Acquire repository lock for 1738824201235
schedulix-schedulixserver-1 | INFO [main] 06 Feb 2025 06:43:22 GMT Some exception was raised while trying to insert a new ticket : org.postgresql.util.PSQLException: ERROR: relation "repository_lock" does not exist
schedulix-schedulixserver-1 | Position: 13
schedulix-schedulixserver-1 | INFO [main] 06 Feb 2025 06:43:22 GMT Lock Acquisition for 1738824201235 failed
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT Error while getting Ticket: ERROR: relation "repository_lock" does not exist
schedulix-schedulixserver-1 | Position: 8
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT ****************** Start Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:162)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.RenewTicketThread.getTicket(RenewTicketThread.java:256)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.Server.initRenewTicketThread(Server.java:119)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.Server.serverMain(Server.java:466)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.BICServer.main(BICServer.java:151)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT ****************** End Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT Error while getting Ticket
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT ****************** Start Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:162)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.exception.FatalException.<init>(FatalException.java:50)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.RenewTicketThread.getTicket(RenewTicketThread.java:257)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.Server.initRenewTicketThread(Server.java:119)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.Server.serverMain(Server.java:466)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.BICServer.main(BICServer.java:151)
schedulix-schedulixserver-1 | ERROR [main] 06 Feb 2025 06:43:22 GMT ****************** End Stacktrace *********************
schedulix-schedulixserver-1 | FATAL [main] 06 Feb 2025 06:43:22 GMT Fatal exception while loading Repository:
schedulix-schedulixserver-1 | Error while getting Ticket
schedulix-schedulixserver-1 | FATAL [main] 06 Feb 2025 06:43:22 GMT ****************** Start Stacktrace *********************
schedulix-schedulixserver-1 | FATAL [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:162)
schedulix-schedulixserver-1 | FATAL [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.Server.serverMain(Server.java:475)
schedulix-schedulixserver-1 | FATAL [main] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.BICServer.main(BICServer.java:151)
schedulix-schedulixserver-1 | FATAL [main] 06 Feb 2025 06:43:22 GMT ****************** End Stacktrace *********************
schedulix-schedulixserver-1 | INFO [Shutdown] 06 Feb 2025 06:43:22 GMT ***********************************************
schedulix-schedulixserver-1 | INFO [Shutdown] 06 Feb 2025 06:43:22 GMT ** **
schedulix-schedulixserver-1 | INFO [Shutdown] 06 Feb 2025 06:43:22 GMT ** U N G R A C E F U L S H U T D O W N ! ! **
schedulix-schedulixserver-1 | INFO [Shutdown] 06 Feb 2025 06:43:22 GMT ** **
schedulix-schedulixserver-1 | INFO [Shutdown] 06 Feb 2025 06:43:22 GMT ***********************************************
schedulix-schedulixserver-1 | INFO [Shutdown] 06 Feb 2025 06:43:22 GMT Release repository lock from 1738824201235
schedulix-schedulixserver-1 | ERROR [Shutdown] 06 Feb 2025 06:43:22 GMT Error while unlocking repository
schedulix-schedulixserver-1 | ERROR [Shutdown] 06 Feb 2025 06:43:22 GMT ****************** Start Stacktrace *********************
schedulix-schedulixserver-1 | ERROR [Shutdown] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:162)
schedulix-schedulixserver-1 | ERROR [Shutdown] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.ShutdownThread.SDMSrun(ShutdownThread.java:102)
schedulix-schedulixserver-1 | ERROR [Shutdown] 06 Feb 2025 06:43:22 GMT de.independit.scheduler.server.util.SDMSThread.run(SDMSThread.java:219)
schedulix-schedulixserver-1 | ERROR [Shutdown] 06 Feb 2025 06:43:22 GMT ****************** End Stacktrace *********************
schedulix-schedulixserver-1 | INFO [Shutdown] 06 Feb 2025 06:43:22 GMT Shutdown completed
schedulix-schedulixserver-1 | [scrolllog] Waiting for child (47) to terminate

schedulix-schedulixserver-1 | [scrolllog] Child exited with state 1
schedulix-schedulixserver-1 | [scrolllog] Try to restart child (child terminated with exit code <> 0)

Ronald Jeninga

unread,

Feb 6, 2025, 7:36:17 AMFeb 6

to schedulix

Hi,

well, we've eliminated the initial issue. That's good news.

As it seems you didn't install the schema for the system in the database.

You'll have to to something like:

cd $BICSUITEHOME/sql

psql -U schedulix -W schedulixdb < pg/install.sql

That will initialize the schema and it should be possible to start the server now.

(Naturally, the command line arguments should match your environment).

After the startup it is recommended to load the convenience package:

cd $BICSUITEHOME/install

sdmsh < convenience.sdms

Note that you'll have to create a $HOME/.sdmshrc file that looks like

User=SYSTEM

Password=G0H0ME

Host=localhost

Port=2506

As soon as all that works you should change the password of the SYSTEM user.

For normal users this can be done in the GUI, or by issuing a command like

ALTER USER RONALD WITH PASSWORD = 'Something Obscure';

in sdmsh.

In case of the user SYSTEM, you'll have to make that change in the server.conf file first.

Best regards,

Ronald

Yogeshwaran M

unread,

Feb 6, 2025, 10:48:31 AMFeb 6

to schedulix

Thansk Ronald.

Installed nessary Schema's using this command
psql -U schedulix -W schedulixdb < pg/install.sql.

Now the server is up and running.

Regarding this where I have to run this on the schedulix server or Postgres?

cd $BICSUITEHOME/install

sdmsh < convenience.sdms

Note that you'll have to create a $HOME/.sdmshrc file that looks like

User=SYSTEM

Password=G0H0ME

Host=localhost

Port=2506

I have tried on both facing an error that "sdmsh command is not found".

Could you assist me to fix this?

Thanks & Regards,
Yogeshwaran M

Ronald Jeninga

unread,

Feb 10, 2025, 5:28:13 AMFeb 10

to schedulix

Hi Yogeshwaran,

sorry for the somewhat late reply, but it was extremely busy last week.

If you log in to the machine that runs the schedulix server as user schedulix, you should be able to run sdmsh without issues.

The sole purpose of the schedulix user is maintenance of the scheduling system.

Hence at least this user should set his PATH and a few other variables that are needed to work with the system.

Typically the variables to set are found in the /opt/schedulix/etc/SETTINGS file and it'll be a good idea to source that from your .bashrc.

Just in case you don't have this SETTINGS file, mine looks like

schedulix:~/etc$ cat SETTINGS
BICSUITEHOME=/opt/schedulix/bicsuite
PATH=$BICSUITEHOME/bin:$PATH
LD_LIBRARY_PATH=$BICSUITEHOME/lib:$LD_LIBRARY_PATH
BICSUITECONFIG=/opt/schedulix/etc
BICSUITELOGDIR=/opt/schedulix/log
export BICSUITEHOME BICSUITECONFIG BICSUITELOGDIR PATH LD_LIBRARY_PATH

As you can see, no higher magic. Depending on your installation, you might have to tweak the values a little.

Now, with the correct PATH and BICSUITECONFIG variable in place, you should be able to run sdmsh.