Author Topic: Updates are bad  (Read 1378 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
Updates are bad
« on: February 04, 2023, 08:07:09 AM »
OK. I bought this for 12$ and after every update, either nginx or apache2 are not working. CWP PRO is waste of money.

Kind regards.

Pissed off customer.

Marijan.
Speak friend and enter :)

Offline
*
Re: Updates are bad
« Reply #1 on: February 04, 2023, 08:11:17 AM »
I don't get it if you can't make a decent update, DON'T do it.
Speak friend and enter :)

Offline
*
Re: Updates are bad
« Reply #2 on: February 04, 2023, 08:16:39 AM »
From working server after your UPDATES this is what i end up with. Every time. Either Apache or Nginx.
Quote
-- Unit httpd.service has begun starting up.
Feb 04 09:14:03 srv.mellon-dev.com httpd[15735]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Feb 04 09:14:03 srv.mellon-dev.com httpd[15735]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Feb 04 09:14:03 srv.mellon-dev.com httpd[15735]: no listening sockets available, shutting down
Feb 04 09:14:03 srv.mellon-dev.com httpd[15735]: AH00015: Unable to open logs
Feb 04 09:14:03 srv.mellon-dev.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Speak friend and enter :)

Offline
****
Re: Updates are bad
« Reply #3 on: February 04, 2023, 02:55:02 PM »
I think I've seen this one time before. Probably a non-clean exit on httpd. Clear the PID file manually and then try starting your http service (Apache/Nginx).

Offline
*
Re: Updates are bad
« Reply #4 on: December 03, 2023, 05:44:37 PM »
If like me, after an update from CWP pro your Apache services or Nginx services wonít start and you look at the logs to find that port 80 canít be bound to and you get any of the following errors:

nginx/httpd problem (98)Address already in use, bind to :80/443 failed


yum remove httpd* cwp-httpd -y
yum install cwp-httpd -y

after that rebuild webserver config.