Overview
After upgrading the Exinda's firmware, the user may find that the web UI is inaccessible, showing the browser's generic error message:
'This page can't be displayed'
Checking the Exinda's logs will show the following errors:
- mgmtd[2281]: [mgmtd.ERR]: md_web_reconfig_httpd(), /home/build/jenkins/workspace/exos_nightly/samara/tree/customer/exinda/src/include/../bin/mgmtd/modules/md_web.inc.c:406, build 1: Error code 14014 (generic IO error) returned
- mgmtd[2281]: [mgmtd.ERR]: md_web_commit_apply(), md_web.c:2485, build 1: Error code 14014 (generic IO error) returned
- mgmtd[2281]: [mgmtd.ERR]: Error 14014 (generic IO error) returned from apply function for module: web
- mgmtd[2281]: [mgmtd.WARNING]: Apply error without explicit commit return code for module web
- pm[2586]: [pm.NOTICE]: Restarting process httpd (HTTP Server Daemon) after crash or unexpected exit of process httpd (HTTP Server Daemon)
- pm[2586]: [pm.NOTICE]: Launched httpd (HTTP Server Daemon) with pid 4105
httpd[4105]: Syntax error on line 175 of /var/opt/tms/output/httpd.conf:
httpd[4105]: SSLCertificateKeyFile: file '/var/opt/tms/output/web/conf/server.key' does not exist or is empty
- pm[2586]: [pm.NOTICE]: Process httpd (HTTP Server Daemon) (pid 4105) exited with code 1
- pm[2586]: [pm.NOTICE]: Process httpd (HTTP Server Daemon) terminated unexpectedly, but left nothing that we recognized as a core file
Root Cause
This error is caused when importing a config file which contains the command:
crypto syscertificate name system-self-signed public-cert pem #12.
Resolution
- If the Exinda is already on the new firmware and the web UI is inaccessible, please run the following command from the CLI:
en
conf t
crypto syscertificate system-self-signed regenerate
- Now restart the system, you can use the command:
reload
- The aforementioned can be avoided in the future, by removing the following command from the config file before importing it:
crypto syscertificate name system-self-signed public-cert pem #12