All server admin URLs are returning an http error 500.
Any ideas on why this would happen? Nothing in the server configuration has changed in at least a month. The server was restarted two weeks ago, but has been running since without problem.
I checked the system this morning and all was fine. I was making another routine check when I started getting the error.
The application itself seems to be working fine, as I can connect with a client as normal. I simply have no admin access to the system. I believe I have remote clients connected now as well, but don’t know who they are and cant message them through the system.
So here’s the questions–
Is there a way to just kill-restart the webserver portion of servoy server on it’s own without effecting a running solution?
–or–
Is there another way to message my clients, so I can get them offline in order to safely kill and restart the entire Servoy Server?
And, no, I do not have server logs–Unfortunately, I followed the directions in the Server documentation manual (page 130) for sending logs to text files and it apparently didn’t work, so those files are empty. (Someone might want to take a look at that.)
IT2Be:
I don’t think it will help you much and I assume you already found it but to be sure, this is what I found:
Internal Error 500
The server encountered an unexpected condition which prevented it from fulfilling the request.
Thanks for the response. I just don’t know the specific cause of the issue or how I might avoid it in future, since the error seemed to come out of nowhere. (I’ve made no changes through the admin screen in quite a while.)
IT2Be:
Well, the message is not specific! But I googled for it so maybe there is more info available.
I don’t think this really comes from Servoy but more from you server.
No, it’s Servoy. The message is coming from the Tomcat web server which is part of Servoy Server. This is the server which serves jsp pages for the headless and web clients (which I’m not using) as well as the online admin pages.
I think I found the problem, although I’m not exactly sure how one directly caused the other.
I found a seemingly unrelated issue in MySQL, which has existed since November–a minor problem involving a mis-formatted timestamp field. When I fixed this problem, the 500 errors simply went away. I expexted to at least have to restart the server, but no. It just started working again.
No idea what the specific trigger was, since the server had been working with the MySQL issue for two months without incident.