I noticed 'www-servers/gatling' now crashes at boot. When I check with
netstat there is no listening port for connections. rc-service reports
gatling has crashed, there is a PID for it, but it is not listed under ps:
# rc-service gatling status
* status: crashed
# cat /run/gatling.pid
4021
# ps axfu | grep gatling
root 4165 0.0 0.0 6572 2224 pts/1 S+ 13:13 0:00
\_ grep --colour=auto gatling
If I try to start it I get a service already started complain. All I see in
the logs is:
* ip link set dev enp2s0 up
* Configuring enp2s0 for MAC address 00:AA:BB:CC:DD:FF ...
[ ok ]
* Starting ifplugd on enp2s0 ...
* start-stop-daemon: fopen `/run/ifplugd.enp2s0.pid': No such file or
directory
* Detaching to start `/usr/sbin/ifplugd' ...
[ ok ]
* Backgrounding ...
* WARNING: net.enp2s0 has started, but is inactive
* WARNING: gatling will start when net.enp2s0 has started
I think this problem started when I changed this PC's LAN network and it now
has IPv6 as well as IPv4, but this could be a coincidence. The init.d script
contains net as a startup dependency:
depend() {
need net
}
Could it be negotiating IP addresses now takes too long and gatling fails to
initialize and crashes for this reason? It is configured to only listen to an
IPv4 address, so I assume the addition of IPv6 should not really affect it.
Restarting it manually works and the service stays up, until the next reboot.
Any ideas what might be causing this?
