HTTP ERROR 503 Service Unavailable [Powered by Jetty:// 11.0.11]

Greetings everyone,

I'm facing this error (HTTP ERROR 503 Service Unavailable [Powered by Jetty:// 11.0.11]
when i tried to access JS7 interface

I'm newer on it could you please give some help and thanks in advance

Caused by: java.sql.SQLException: RSA public key is not available client side (option serverRsaPublicKeyFile not set)
at org.mariadb.jdbc.internal.com.send.authentication.CachingSha2PasswordPlugin.process(CachingSha2PasswordPlugin.java:189) ~[mariadb-java-client-2.7.2.jar:?]
at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.authenticationHandler(AbstractConnectProtocol.java:752) ~[mariadb-java-client-2.7.2.jar:?]
at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.createConnection(AbstractConnectProtocol.java:553) ~[mariadb-java-client-2.7.2.jar:?]
at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.connectWithoutProxy(AbstractConnectProtocol.java:1387) ~[mariadb-java-client-2.7.2.jar:?]
at org.mariadb.jdbc.internal.util.Utils.retrieveProxy(Utils.java:635) ~[mariadb-java-client-2.7.2.jar:?]
at org.mariadb.jdbc.MariaDbConnection.newConnection(MariaDbConnection.java:150) ~[mariadb-java-client-2.7.2.jar:?]
at org.mariadb.jdbc.Driver.connect(Driver.java:89) ~[mariadb-java-client-2.7.2.jar:?]
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:136) ~[HikariCP-3.2.0.jar:?]
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:369) ~[HikariCP-3.2.0.jar:?]
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:198) ~[HikariCP-3.2.0.jar:?]
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:467) ~[HikariCP-3.2.0.jar:?]
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:541) ~[HikariCP-3.2.0.jar:?]
at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:115) ~[HikariCP-3.2.0.jar:?]
at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:81) ~[HikariCP-3.2.0.jar:?]
at org.hibernate.hikaricp.internal.HikariCPConnectionProvider.configure(HikariCPConnectionProvider.java:59) ~[hibernate-hikaricp-5.5.4.Final.jar:5.5.4.Final]</init></init>

some otherlogs

root@yani-virtual-machine:/var/log/sos-berlin.com/js7/joc# docker logs 1aec64c9b7ae
copy /var/sos-berlin.com/js7/joc/resources/joc/start.d/console-capture.ini -> /var/sos-berlin.com/js7/joc/start.d/
copy /var/sos-berlin.com/js7/joc/resources/joc/start.d/deploy.ini -> /var/sos-berlin.com/js7/joc/start.d/
copy /var/sos-berlin.com/js7/joc/resources/joc/start.d/ext.ini -> /var/sos-berlin.com/js7/joc/start.d/
copy /var/sos-berlin.com/js7/joc/resources/joc/start.d/http.ini -> /var/sos-berlin.com/js7/joc/start.d/
copy /var/sos-berlin.com/js7/joc/resources/joc/start.d/https.ini -> /var/sos-berlin.com/js7/joc/start.d/
copy /var/sos-berlin.com/js7/joc/resources/joc/start.d/resources.ini -> /var/sos-berlin.com/js7/joc/start.d/
copy /var/sos-berlin.com/js7/joc/resources/joc/start.d/rewrite.ini -> /var/sos-berlin.com/js7/joc/start.d/
extract patch files if exist
JS7 entrypoint script switching ownership of image user id '1000' -> '0', group id '1000' -> '0'
usermod: UID '0' already exists
groupmod: GID '0' already exists
JS7 entrypoint script switching to user account 'jobscheduler' to run start script
JS7 entrypoint script starting JOC Cockpit: exec su-exec jobscheduler:0 /opt/sos-berlin.com/js7/joc/jetty/bin/jetty.sh start
Starting Jetty: 2023-02-11 22:39:50.125:INFO :oe.jetty:main: Console stderr/stdout captured to| /var/log/sos-berlin.com/js7/joc/jetty.log
tail: can't open '/var/sos-berlin.com/js7/joc/joc.state': No such file or directory
tail: no files
tail: can't open '/var/sos-berlin.com/js7/joc/joc.state': No such file or directory
tail: no files
tail: can't open '/var/sos-berlin.com/js7/joc/joc.state': No such file or directory
tail: no files
. . . . . . . . . . . . . . OK Sat Feb 11 22:40:49 UTC 2023

Did you ever find a solution here?

Hi Abdelmalek,
the issue is about establishing a secure connection to your MySQL database. Looking up the error message "RSA public key is not available client side" gives you a number of recommendations how to resolve this from the client (container) or from the databases side.

One of the recommendations includes to add to the query parameter allowPublicKeyRetrieval=true to the database URL.

In your hibernate.cfg.xml file that should be accessible from the mounted volume pointing to the /var/sos-berlin.com/js7/joc/resources/joc directory append the query parameter like this:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<hibernate-configuration>
 <session-factory>
...
     <property name="hibernate.connection.url">jdbc:mysql://mysql-5-7:3306/jobscheduler200&allowPublicKeyRetrieval=true</property>
...

Best regards
Andreas