Your message dated Mon, 20 Nov 2017 19:33:31 +0100
with message-id <[email protected]>
and subject line Re: Bug#882231: rsyslog: On boot no UDP socket could be
successfully be initialized
has caused the Debian Bug report #882231,
regarding rsyslog: On boot no UDP socket could be successfully be initialized
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
882231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882231
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsyslog
Version: 8.29.0-2~bpo9+1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
On boot of the system, rsyslog is started up, and is mentioned to be active and
running correctly.
It is however not listening on UPD socket. systemctl shows following on the
status request:
Nov 20 13:05:43 sv-1 systemd[1]: Starting System Logging Service...
Nov 20 13:05:44 sv-1 rsyslogd[2113]: bound address XXX.XXX.XXX.XXX IP free
[v8.29.0 try http://www.rsyslog.com/e/2186 ]
Nov 20 13:05:44 sv-1 rsyslogd[2113]: No UDP socket could successfully be
initialized, some functionality may be disabled. [v8.29.0]
After restarting rsyslog, it is accepting information on UDP socket, and
working further correctly.
This was noticed by by looking for information of one of the other servers,
which didn't end up in the /var/log/syslog file.
After restart of the rsyslog server the information of the other servers did
end up on the log file.
Upgrading rsyslog from the default version in debian stretch (8.24.0-1 to the
backport version 8.29.0-2) didn't fix the problem.
Rsyslog is configured to accept UDP traffic from other servers, to have one
central syslog server.
To be able to have this working reliable, it should be start up correctly on
boot, without the need of restarting manual after boot.
-- System Information:
Debian Release: 9.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/20 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages rsyslog depends on:
ii init-system-helpers 1.48
ii libc6 2.24-11+deb9u1
ii libestr0 0.1.10-2
ii libfastjson4 0.99.4-1
ii liblogging-stdlog0 1.0.5-2+b2
ii liblognorm5 2.0.3-1~bpo9+1
ii libsystemd0 232-25+deb9u1
ii libuuid1 2.29.2-1
ii lsb-base 9.20161125
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages rsyslog recommends:
ii logrotate 3.11.0-0.1
Versions of packages rsyslog suggests:
pn rsyslog-doc <none>
pn rsyslog-gnutls <none>
pn rsyslog-gssapi <none>
pn rsyslog-mongodb <none>
pn rsyslog-mysql | rsyslog-pgsql <none>
pn rsyslog-relp <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Walter
Am 20.11.2017 um 16:11 schrieb Walter den Besten:
> Michael,
>
>
> Adding the suggested Unit lines as suggested.
>
> [Unit]
> After=network-online.target
> Wants=network-online.target
>
> This solves most of the issue detected, as it doesn’t fix the binding
> for the defined IP6 address.
>
> Was expecting this to be included in the standard startup settings of
> the service, which was obviously wrong.
> Thanks for the quick response.
Well, binding to specific IPv4/IPv6 addresses is not the
default/standard setup of rsyslog.
If I included Wants/After=network-online.target it would unnecessarily
delay the startup for the majority of users who use a default rsyslog
config.
I thus think it's not a good idea to include this by default and thus
close this bug report.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
