Start a Conversation

Unsolved

A

5 Posts

894

August 29th, 2022 04:00

Something very strange happened to WMS.....

Windows server 2019

WMS version 3.6.1.23

Only had 3 terminals as this is dev.

Production is working no issues, did take a snapshot when noticed the below. 

We noticed that our WMS dev environment, was not working.  we have not used in some time. we thought no big deal we can reboot and all will be well.  but the rabbit hole just kept going of very strange things. 

After the reboot we noticed Dell WMS: Tomcat Service was not running when we try to start it we get. Error 1068: The Dependency service or group failed to start.  Oh no big deal let go look at the tom cat logs....

C:\Program Files\DELL\WMS\Tomcat-9\logs

 

 

 

2022-08-01 09:23:13 Apache Commons Daemon procrun stderr initialized.
Handler error
java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:590)
	at org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:526)
	at org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:325)
	at java.logging/java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:445)
	at java.logging/java.util.logging.LogManager$2.run(LogManager.java:394)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.logging/java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:382)
	at java.logging/java.util.logging.LogManager.getLogManager(LogManager.java:430)
	at java.logging/java.util.logging.Logger.demandLogger(Logger.java:648)
	at java.logging/java.util.logging.Logger.getLogger(Logger.java:717)
	at java.logging/java.util.logging.Logger.getLogger(Logger.java:701)
	at org.apache.juli.logging.DirectJDKLog.(DirectJDKLog.java:61)
	at org.apache.juli.logging.DirectJDKLog.getInstance(DirectJDKLog.java:181)
	at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:133)
	at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)
	at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)
	at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)
Caused by: java.lang.Error: java.io.FileNotFoundException: C:\Program Files\DELL\WMS\OpenJDK-11.0.13\lib\tzdb.dat (The system cannot find the file specified)

 

 

 

OK that's strange tzdb.dat is missing lets go to C:\Program Files\DELL\WMS\OpenJDK-11.0.13\

ok wow all of OpenJDK is gone.... the only two folders that are there is lib, bin Release. Lib only contains a file called modules, and Bin contains the java binary and some dlls. So it appears that JDK is missing alot of files.

From looking over the tomcat logs the last time it appears to have ran was 6/27/2022... but has been generating the above error in the logs to 8/1/2022.

at this point we started comparing other directories to our production server and found more missing files. 

C:\Program Files\DELL\WMS\MariaDB\ is missing files like pretty much everything. the only thing there is mysqld and server.dll.  And that is just one more example.....

So the reason it wont start is because their are a number of missing files for WMS.

I checked logs no one has accessed the server other than me and the other horizon admin. 

if you want more logs or more information let me know, and ill post it. 

Has anyone every had this happen before?

 

 

 

2 Posts

December 7th, 2022 02:00

Same thing happened to our WMS server, after upgrading from version 3.1 to 3.3.
I did not notice it at first, because during/after the update everything keeps running perfectly fine. 

Until I restarted the server..

I solved this by doing a fresh install of 3.3 on a temp VM and copying over the MariaDB/MongoDB/Tomcat folders without overriding any existing files.

The openJDK folder was intact on my system.

1 Rookie

 • 

681 Posts

December 8th, 2022 07:00

This was observed under some old upgrades, and the resolution above was appropriate.  It has not occurred in recent builds so I believe it has been identified and mitigated.

No Events found!

Top