Marc Dequènes wrote...
> On 2019-11-01 19:32, Christoph Biedl wrote:
>
> > Upstream uses "After=network.target" only, basically
> > https://sources.debian.org/src/inspircd/3.3.0-1/make/template/inspircd.service/
>
> Yes, but as referenced on this other bug systemd upstream recommends both
>
Quack,
On 2019-11-01 19:32, Christoph Biedl wrote:
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.
Yes, but I expect network availability
Control: found 939270 2.0.23-2
signature.asc
Description: PGP signature
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
Package: inspircd
Version: 2.0.27-1
Severity: important
Quack,
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
5 matches
Mail list logo
