Any thoughts what can be?
On 18/01/22, 4:24 PM, "Ricardo Pertuz" <[email protected]> wrote:
Also seems to be configuration error when I tried to restart it manually
Jan 18 21:16:06 r-102-VM systemd[1]: Starting The Apache HTTP Server...
Jan 18 21:16:06 r-102-VM apachectl[20959]: AH00526: Syntax error on line
231 of /etc/apache2/sites-enabled/vhost-172.26.1.4.conf:
Jan 18 21:16:06 r-102-VM apachectl[20959]: Cannot define multiple Listeners
on the same IP:port
Jan 18 21:16:06 r-102-VM apachectl[20959]: Action 'start' failed.
Jan 18 21:16:06 r-102-VM apachectl[20959]: The Apache error log may have
more information.
Jan 18 21:16:06 r-102-VM systemd[1]: apache2.service: Control process
exited, code=exited, status=1/FAILURE
Jan 18 21:16:06 r-102-VM systemd[1]: apache2.service: Failed with result
'exit-code'.
When I run te configtest
root@r-102-VM:/var/log/apache2# apachectl configtest
AH00526: Syntax error on line 231 of
/etc/apache2/sites-enabled/vhost-172.26.1.4.conf:
Cannot define multiple Listeners on the same IP:port
Action 'configtest' failed.
This is la line 231
Listen 172.26.1.4:80
Listen 172.26.1.1:80
However the VR does not has the ip 172.26.1.4
31: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
link/ether 02:00:6b:b3:00:02 brd ff:ff:ff:ff:ff:ff
inet 172.26.1.12/24 brd 172.26.1.255 scope global eth3
valid_lft forever preferred_lft forever
inet 172.26.1.1/24 brd 172.26.1.255 scope global secondary eth3
valid_lft forever preferred_lft forever
Not sure why the system sends the 172.26.1.4 config to the VR
Regards,
Ricardo
From: Ricardo Pertuz <[email protected]>
Date: Tuesday, 18 January 2022, 4:15 PM
To: "[email protected]" <[email protected]>
Subject: apache2 on VR SIGTERM
Hi guys,
The Apache2 on some VRs is reporting offline, after seeing the error trace
I found this
[mpm_event:notice] [pid 2108:tid 140052633764992] AH00491: caught SIGTERM,
shutting down
I was thinking in increasing on the VR offering capacity as it has the
default one, but not sure it is the way to go. I haven’t get any kill command
on /var/log/messages
Regards,
