Cannot get to Cloudera Manager after server reboot

[#1]

Hi, I have a fresh install of Cloudera Manager and it was running fine until I rebooted the server. The only thing I changed was the hosts file, but I don't think that has anything to do with it (I even changed the hosts file back).

The cloudera-scm-server service is running, but am getting a couple errors when I check the status.

cloudera-scm-server.service - Cloudera CM Server Service
Loaded: loaded (/usr/lib/systemd/system/cloudera-scm-server.service; enabled; preset: disabled)
Active: active (running) since Tue 2025-07-01 17:46:47 CDT; 23s ago
Process: 5922 ExecStartPre=/opt/cloudera/cm/bin/cm-server-pre (code=exited, status=0/SUCCESS)
Main PID: 5924 (java)
Tasks: 87 (limit: 819655)
Memory: 986.0M
CPU: 40.080s
CGroup: /system.slice/cloudera-scm-server.service
└─5924 /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.432.b06-2.el9.x86_64/bin/java -cp ".:/usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/java/postgresql-connector-java.jar:lib/*" -server -Dlog4j.configuration=file:/etc/cloudera-scm-server/log4j.properties -Dfil>

Jul 01 17:46:47 dmidlkprdls01.svr.luc.edu systemd[1]: Starting Cloudera CM Server Service...
Jul 01 17:46:47 dmidlkprdls01.svr.luc.edu systemd[1]: Started Cloudera CM Server Service.
Jul 01 17:46:47 dmidlkprdls01.svr.luc.edu cm-server[5924]: BIG=
Jul 01 17:46:47 dmidlkprdls01.svr.luc.edu cm-server[5924]: JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.432.b06-2.el9.x86_64
Jul 01 17:46:50 dmidlkprdls01.svr.luc.edu cm-server[5924]: ERROR StatusLogger Reconfiguration failed: No configuration found for '764c12b6' at 'null' in 'null'
Jul 01 17:46:52 dmidlkprdls01.svr.luc.edu cm-server[5924]: Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.

The /var/log/cloudera-scm-server logs just keep going too. So not sure I can get an accurate, but here is what I have.

2025-07-01 17:16:25,216 WARN C3P0PooledConnectionPoolManager[identityToken->2sl8jibb1jicthn92yvkg|1f0b3cfe]-HelperThread-#0:com.mchange.v2.resourcepool.BasicResourcePool: Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@4beaf6bd is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2025-07-01 17:16:25,216 WARN C3P0PooledConnectionPoolManager[identityToken->2sl8jibb1jicthn92yvkg|1f0b3cfe]-HelperThread-#1:com.mchange.v2.resourcepool.BasicResourcePool: com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@45dde636 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (5). Last acquisition attempt exception:
java.sql.SQLException: The server time zone value 'CDT' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the 'serverTimezone' configuration property) to use a more specific time zone value if you want to utilize time zone support.
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:76)
at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:836)
at com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:456)
at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:246)
at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:198)
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:175)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:220)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:206)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:203)
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1176)
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPendingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1163)
at com.mchange.v2.resourcepool.BasicResourcePool.access$700(BasicResourcePool.java:44)
at com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.run(BasicResourcePool.java:1908)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)
Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException: The server time zone value 'CDT' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the 'serverTimezone' configuration property) to use a more specific time zone value if you want to utilize time zone support.
at sun.reflect.GeneratedConstructorAccessor38.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:61)
at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:85)
at com.mysql.cj.util.TimeUtil.getCanonicalTimezone(TimeUtil.java:134)
at com.mysql.cj.protocol.a.NativeProtocol.configureTimezone(NativeProtocol.java:2186)
at com.mysql.cj.protocol.a.NativeProtocol.initServerSession(NativeProtocol.java:2209)
at com.mysql.cj.jdbc.ConnectionImpl.initializePropsFromServer(ConnectionImpl.java:1318)
at com.mysql.cj.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:967)
at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:826)
... 12 more

The time zone and everything is correct.

Cloudera Version: 7.13.1

MariaDB Version: 10.5.22

Java Version: 1.8.0_432

Any ideas?

[#2]

@jkoral Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our Cloudera Manager experts @soychago @paras @upadhyayk04  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.

[#3 · Accepted solution]

Thank you very much for your response. I may have just fixed the issue. I did go by the default instructions when setting up the JDBC driver and decided to update it to the latest one instead, which seemed to work. 

For anyone that runs into this issue and you want to install the latest JDBC driver, go to https://dev.mysql.com/downloads/connector/j/5.1.html and change the select Operating System to Platform Independent and that's where you will find the tar.gz file. Not sure how this worked with version 8.0.22 at first, but it didn't after the reboot. But I tested another reboot with version 9.3.0 and it worked just fine.

[#4]

@jkoral although the troubleshooting makes sense, we generally see the "Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException: The server time zone value 'CDT' is unrecognized or represents more than one time zone" when there's a timezone conflict between the Cloudera Manager Server host and the MySQL server (not the host, but the MySQL timezone in /etc/my.cnf), is set to the CDT timezone, causing the conflict.

To resolve it, we generally ensure both the CM server and the MySQL server have the same timezone. Here's some suggested troubleshooting:

1. Check the timezone setting of the MySQL server in the /etc/my.cnf file.
2. Ensure the MySQL server's timezone matches the server's timezone setting.
3. Modify the timezone setting in the configuration file if it does not match.
4. Restart the MySQL server to apply the changes.
5. Restart the Cloudera Manager Server and verify that it starts up without issues.
6. A product improvement task will be created to update the JDBC driver to use the server's timezone setting when establishing a connection.

Now, on the other hand, here's our documentation concerning the JDBC drivers along with the supported versions:

https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/upgrade-hdp/topics/amb-install-mysql-jdbc... 

You can choose the operating system version, JDBC Driver and cluster version from the dropdowns.

[#5]

Thank you very much. I have setup the timezone in my.cnf.