-
hermes webadmin stopped working. I get the login page but then a 502 gateway error after auth. Was working fine before and not sure what changed, havent ran any updates or anything Im aware of. Running in vmware. Seeing the below in tomcat logs, not sure if thats related. Any assistance would be much appreciated. `14-May-2025 09:51:52.252 INFO [Thread-5] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["https-jsse-nio-8443"] 14-May-2025 09:53:11.438 WARNING [main] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of deployment descriptor [/etc/tomcat9/Catalina/localhost/ciphermail.xml] with an external docBase means the directory [/var/lib/tomcat9/webapps/ciphermail] in the appBase will be ignored 14-May-2025 09:53:16.375 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 14-May-2025 09:53:18.949 WARNING [main] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of deployment descriptor [/etc/tomcat9/Catalina/localhost/web.xml] with an external docBase means the directory [/var/lib/tomcat9/webapps/web] in the appBase will be ignored 14-May-2025 09:53:22.583 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. |
Beta Was this translation helpful? Give feedback.
Replies: 22 comments
-
Hi, this looks like an error for the ciphermail Web GUI. Have you tried restarting ciphermail back end:
and then ciphermail front end:
|
Beta Was this translation helpful? Give feedback.
-
Ive rebooted the whole vm but ill give that a shot as well and let you know |
Beta Was this translation helpful? Give feedback.
-
no change |
Beta Was this translation helpful? Give feedback.
-
thanks for trying. Looking at it a little closer, the error log output you sent does not seem to indicate a problem. Can you check to ensure that your /etc/hosts has the following entry in it? 127.0.0.1 securemail.prosites.com Thanks |
Beta Was this translation helpful? Give feedback.
-
did you change the URL of your Hermes server recently? |
Beta Was this translation helpful? Give feedback.
-
no, we havent made any change recently, the url has remained the same since deployment (go live maybe a year ago). Also, I can get into ciphermail webui fine, just the hermes web admin is the issue. Ill check the hostfile thing |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Okay that looks good. ok that looks good. Can you check the hermesseg service:
and maybe the following:
|
Beta Was this translation helpful? Give feedback.
-
The reason I asked about ciphermail was because the logs you sent looked like Tomcat logs from ciphermail. |
Beta Was this translation helpful? Give feedback.
-
ya, I just put that there because I found it and wasnt sure if it was related. It looked like it might be an issue specifically around the app "main". Didnt know and was trying to provide as much detail as possible. Looking into the other service now |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
looks like its in a looping start failure. Now we are getting somewhere. Im not really seeing a reason though |
Beta Was this translation helpful? Give feedback.
-
Can you post the contents of the following file:
Thanks |
Beta Was this translation helpful? Give feedback.
-
Also, please the following command in the cli as root:
if you are asked to apply an update do NOT! Once in the Commandbox prompt type the following and send me the output:
Thanks |
Beta Was this translation helpful? Give feedback.
-
{ |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
okay I think I see the issue. In the Commandbox prompt, enter the following and send me the output please:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
The server's location should not be in root but rather in /opt/CommandBox/web-contexts/wwwroot-hermesseg. Not sure how that changed, but please try the following: Stop the hermesseg service:
Go into the Commandbox prompt:
In the Commandbox prompt type the following and it will show you a list of servers in the stopped status:
Next type the following command to forget the server and ensure you respond "Y" to confirm:
Next exit the Commandbox prompt:
Next start the hermesseg service:
Let me know how that works. |
Beta Was this translation helpful? Give feedback.
-
Ill give that a shot today and let you know |
Beta Was this translation helpful? Give feedback.
-
That looks like it worked. The web admin is back up now. |
Beta Was this translation helpful? Give feedback.
-
Glad you got it working. |
Beta Was this translation helpful? Give feedback.
The server's location should not be in root but rather in /opt/CommandBox/web-contexts/wwwroot-hermesseg. Not sure how that changed, but please try the following:
Stop the hermesseg service:
# systemctl stop hermesseg
Go into the Commandbox prompt:
# box
In the Commandbox prompt type the following and it will show you a list of servers in the stopped status:
Next type the following command to forget the server and ensure you respond "Y" to confirm: