Your message dated Sat, 8 Sep 2018 00:05:51 +0200
with message-id <[email protected]>
and subject line Closing old bugs
has caused the Debian Bug report #803963,
regarding error: unable to bind to wildcard address 0.0.0.0 - another process
may be running - EXITING
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.)
--
803963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803963
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ntpd
Version: ntp
Severity: normal
Dear Maintainer,
I noticed this inside my logs:
nov 03 17:22:04 debian ntpd[29294]: restrict: ignoring line 37, mask '::'
unusable.
and now, when I try to manually run the service it doesn't work:
ntpd -g -q
3 Nov 17:49:44 ntpd[30876]: ntpd [email protected] Tue Nov 3 02:26:54 UTC 2015
(1): Starting
3 Nov 17:49:44 ntpd[30876]: Command line: ntpd -g -q
3 Nov 17:49:44 ntpd[30876]: proto: precision = 0.628 usec (-21)
3 Nov 17:49:44 ntpd[30876]: Listen and drop on 0 v6wildcard [::]:123
3 Nov 17:49:44 ntpd[30876]: unable to bind to wildcard address 0.0.0.0 -
another process may be running - EXITING
or with
ntpd -qgd
3 Nov 18:02:05 ntpd[31239]: ntpd [email protected] Tue Nov 3 02:26:54 UTC 2015
(1): Starting
3 Nov 18:02:05 ntpd[31239]: Command line: ntpd -qgd
3 Nov 18:02:05 ntpd[31239]: proto: precision = 1.117 usec (-20)
3 Nov 18:02:05 ntpd[31239]: Listen and drop on 0 v6wildcard [::]:123
3 Nov 18:02:05 ntpd[31239]: unable to bind to wildcard address 0.0.0.0 -
another process may be running - EXITING
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
driftfile /var/lib/ntp/ntp.drift
# Enable this if you want statistics to be logged.
#statsdir /var/log/ntpstats/
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example
# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
# pick a different set every time it starts up. Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
#pool 0.debian.pool.ntp.org iburst
#pool 1.debian.pool.ntp.org iburst
#pool 2.debian.pool.ntp.org iburst
#pool 3.debian.pool.ntp.org iburst
server 0.europe.pool.ntp.org iburst
server 1.europe.pool.ntp.org iburst
server 2.europe.pool.ntp.org iburst
server 3.europe.pool.ntp.org iburst
# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details. The web page
<http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.
# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited
# Local users may interrogate the ntp server more closely.
restrict default noquery nopeer
restrict 127.0.0.1
restrict ::1
# Needed for adding pool entries
restrict source notrap nomodify noquery
# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
restrict 192.168.1.0 mask 255.255.255.0 notrust
# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255
# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines. Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient
--- End Message ---
--- Begin Message ---
Hello,
thank you for spending your time helping to make Debian better with
this bug report. Unfortunately your bug report could not be (completely)
dealt with in an appropriate time.
The version you have filed this bug report against is for a release that
is not supported anymore. Unfortunately we do not have the manpower to
reproduce bugs that old. It is possibly already fixed with the current
version.
Therefor I'm closing this bug. If you can still reproduce this issue on
a supported release (Debian 9 aka stretch, preferably also in sid) feel
free to reopen the bug report.
Thanks,
Bernhard
--- End Message ---
