It's getting stupidly annoying that i can't change a servers ip address, without having the most strange behaviors.
- Webmin does accept the ip change without any problem, only Apache2 won't?
It is just running (somewhere) but won't return any answers/requests. Not remotely nor locally!
Also not after a reboot of the whole machine .. Apache is running, but does not answer anywhere.
If i change back ip-address & vSwitch settings, it runs fine.
How the F&ck do i change apache's ip ???
Apache logs: (before and after ip change)
Code: Select all
[Thu Oct 27 21:45:52.448268 2016] [core:warn] [pid 2341] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
[Thu Oct 27 21:45:52.450785 2016] [mpm_prefork:notice] [pid 2341] AH00163: Apache/2.4.10 (Debian) configured -- resuming normal operations
[Thu Oct 27 21:45:52.450811 2016] [core:notice] [pid 2341] AH00094: Command line: '/usr/sbin/apache2'
[Thu Oct 27 21:58:07.635603 2016] [mpm_prefork:notice] [pid 2341] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
[Thu Oct 27 21:58:08.493807 2016] [mpm_prefork:notice] [pid 2341] AH00163: Apache/2.4.10 (Debian) configured -- resuming normal operations
[Thu Oct 27 21:58:08.493853 2016] [core:notice] [pid 2341] AH00094: Command line: '/usr/sbin/apache2'
[Thu Oct 27 21:58:12.418428 2016] [mpm_prefork:notice] [pid 2341] AH00169: caught SIGTERM, shutting down
[Thu Oct 27 22:19:15.619321 2016] [mpm_prefork:notice] [pid 4825] AH00163: Apache/2.4.10 (Debian) configured -- resuming normal operations
[Thu Oct 27 22:19:15.619361 2016] [core:notice] [pid 4825] AH00094: Command line: '/usr/sbin/apache2'
[Thu Oct 27 22:32:05.474694 2016] [mpm_prefork:notice] [pid 4825] AH00169: caught SIGTERM, shutting down
[Thu Oct 27 22:32:06.784754 2016] [mpm_prefork:notice] [pid 8370] AH00163: Apache/2.4.10 (Debian) configured -- resuming normal operations
[Thu Oct 27 22:32:06.784797 2016] [core:notice] [pid 8370] AH00094: Command line: '/usr/sbin/apache2'
[Fri Oct 28 00:23:43.601031 2016] [mpm_prefork:notice] [pid 8370] AH00169: caught SIGTERM, shutting down
[Fri Oct 28 00:23:49.326707 2016] [mpm_prefork:notice] [pid 10396] AH00163: Apache/2.4.10 (Debian) configured -- resuming normal operations
[Fri Oct 28 00:23:49.326765 2016] [core:notice] [pid 10396] AH00094: Command line: '/usr/sbin/apache2'
[Fri Oct 28 00:30:18.446487 2016] [mpm_prefork:notice] [pid 10396] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
[Fri Oct 28 00:30:18.549413 2016] [mpm_prefork:notice] [pid 10396] AH00163: Apache/2.4.10 (Debian) configured -- resuming normal operations
[Fri Oct 28 00:30:18.549443 2016] [core:notice] [pid 10396] AH00094: Command line: '/usr/sbin/apache2'
DMESG logs:
Code: Select all
[ 2743.944254] vmxnet3 0000:03:00.0 eth0: NIC Link is Down
[ 2744.034577] vmxnet3 0000:03:00.0 eth0: NIC Link is Up 10000 Mbps
[ 9677.921257] vmxnet3 0000:03:00.0 eth0: NIC Link is Down
[ 9678.196309] vmxnet3 0000:03:00.0 eth0: NIC Link is Up 10000 Mbps
[ 9678.196325] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 9678.219988] vmxnet3 0000:03:00.0 eth0: NIC Link is Down
[ 9678.233954] vmxnet3 0000:03:00.0 eth0: NIC Link is Up 10000 Mbps
After the ADDRCONF(NETDEV_CHANGE) Apache wont work on the new ip address, although it starts and runs, there's NO return on whatsoever request, remotely or locally.
Webmin (using another http-based webserver, internally) DOES accept these ip changes without any problems!
What am i doing wrong... as the 1st machine is already on new network -for a week-, only this active web-server won't ... grrrrr
....
DG.