Our Knime server has been running on an AWS EC2 for years.
I just rebooted our Knime server and suddenly no user can log in anymore. We get a “Cannot be authenticated, probably the password is wrong” on Knime AP, or simply “Login failed. Please try again.” on the Web Portal.
We were all logged in before the reboot.
I can still access the server using SSH ( and the webportal… at least the login page )
I don’t see anything in the logs.
Thanks in advance.
It looks like the action of rebooting actually corrupted the userconf.mv.db file.
I have restored it from a backup and everything works now.
Next time I’ll gracefully stop the server before rebooting the VM
Hi @sebversailles ,
Welcome to KNIME Community.
Glad to know that issue is resolved, H2 databases has lots of issues around DB corruption. As mentioned by you, One of the reason for the corruption would be about the open connections to the DB during the reboot.
spring boot - H2 database corruption on a regular basis - Stack Overflow
- If classloader with H2 can be forcibly unloaded (on some application servers, for example) or application is going to be terminated in some abnormal way, you need to close all connections before it or execute the
SHUTDOWN command and wait for its completion.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.