Apache Problem

DCIM_Support · ‎2020-07-02

I upgraded to lastest DCO(7.4.5) and now my apache web server is failing to start and I am unable to connect to DCO. Below is the error I receive when it tries to start. I have already rebooted the system again to no avail. I have looked to see if there is anything else already has been bind to the port and there is not. I have already sent in a request to tech Support but thought I would post it here in case someone has already had this problem and fixed it. Thanks

Apache Error:

Starting web server: apache2(98)Address already in use: make_sock: could not bind to address [::]:6666

DCIM_Support · ‎2020-07-02

Hi Toby,

This has been solved offline.

Seems like root cause was some changes done to the Apache configuration on port 80 which again was reverted. However these changes caused the Apache module to have a state that then caused the upgrade to fail. It is not recommended to do any changes to the apache configuration and going forward we have made some changes to the server configuration making it harder to change the apache configuration.

Thanks for working with us on solving this issue.

See Answer In Context

DCIM_Support · ‎2020-07-02

Hi Toby,

Sounds like there might be something wrong in the upgrade process.

As I understand it you used the upgrade image and not a backup of the old system and the restoring the backup on fresh installed system? That is fine and should be working.

In order to fully understand the issue we need to have your log-files. Those can be download using the server configuration interface found at https://:10000 in the Struxuware Operation menu. (the log files can be attached to an answer in this community using the link functionality, otherwise please let me know and I will provide a folder to upload to)

Just to be sure there are no configuration changes done to the old DCO server installation?

DCIM_Support · ‎2020-07-02

Yes it was using the upgrade image. There were no config changes made to the old DCO server.

DCIM_Support · ‎2020-07-02

Thanks for clarifying and providing log-files. We will have a look. I removed the logs from your post since we have them now at our end.

DCIM_Support · ‎2020-07-02

Hi Toby,

This has been solved offline.

Seems like root cause was some changes done to the Apache configuration on port 80 which again was reverted. However these changes caused the Apache module to have a state that then caused the upgrade to fail. It is not recommended to do any changes to the apache configuration and going forward we have made some changes to the server configuration making it harder to change the apache configuration.

Thanks for working with us on solving this issue.

DCIM_Support · ‎2020-07-02

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.