Control: tag 939270 confirmed moreinfo Control: found 939270 2.0.27-1 Control: notfound 939270 3.3.0-1
Marc Dequènes wrote... > Similarly as #910368 for Apache the systemd service file lacks proper > settings to wait for network to be available. > I got these logs: > Aug 17 12:47:08 Jinta inspircd[401]: WARNING: Not all your client ports > could be bound -- > Aug 17 12:47:08 Jinta inspircd[401]: starting anyway with 0 of 8 client > ports bound. > Aug 17 12:47:08 Jinta inspircd[401]: The following port(s) failed to bind: > Aug 17 12:47:08 Jinta inspircd[401]: 1. Address: 193.200.43.27:6667 > Reason: Cannot assign requested address Let me rephrase: If inspircd is configured to bind to specific addresses, this binding does not happen if the configuration hasn't happened (yet). This can be healed by re-ordering the execution order. Plus: > To make matter worse the daemon decides to go on even when all ports fail to > bind, which results in systemd status to be all green and, unless you > monitor the port too, you can miss the failure. Can you confirm this does not happen in unstable (3.3.0-1)? I failed to reproduce the issue there, also the service file unterwent some changes, it's now taken from upstream. > Same suggestion: > After=network-online.target > Wants=network-online.target Upstream uses "After=network.target" only, basically https://sources.debian.org/src/inspircd/3.3.0-1/make/template/inspircd.service/ Christoph
signature.asc
Description: PGP signature
