kura
kura copied to clipboard
Server manager does not close properly
Describe the bug
The bundle org.eclipse.kura.http.server.manager
does not close properly. At least in case of error with the certificate. If you remove the certificate localhost
from the default Httpskeystore, the server goes into error and leave the endpoint on port 443 opened, preventing any further deployment of the web interface.
To Reproduce
Steps to reproduce the behavior (it is advisable to backup file /opt/eclipse/kura/user/security/httpskeystore.ks
before this as it will be emptied during the test):
beware the web portal will be lost after the test until you restore the keystore file and restart Kura
- Remove localhost certificate from HttpsKeystore
- Check opened ports on the system
- Port 443 is still in use
- The port remains used until Kura is stopped
Expected behavior The server should get an error and be closed but the port should not be present, allowing a restart of the service once everything is fine again or it is restarted from the platform (Kapua).
Target Environment (please complete the following information):
- Raspberry Pi 4B
- OS version: raspbian
- Kura version: 5.0.1
Additional context This test was found when the localhost certificate was being updated. At some time any user should do this and will find the issue it he does not want to restart Kura
There is a workaround possible by stopping the bundle prior to the critical operation and starting it again after it. Make sure you have remote access to the device via Kapua or similar, as the web interface will get down after the stop