Your message dated Wed, 15 Sep 2010 22:47:07 +0000
with message-id <[email protected]>
and subject line Bug#592930: fixed in chrony 1.24-3
has caused the Debian Bug report #592930,
regarding invoke-rc.d: initscript chrony, action "start" failed.
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.)
--
592930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592930
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 1.24-2
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
After an upgrade, chrony *seems* to fail start so dpkg leaves it in an
unconfigured state.
,----
| crystalline:/home/niehaus# LC_ALL=en_GB.utf8 apt-get upgrade
| Reading package lists... Done
| Building dependency tree
| Reading state information... Done
| 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
| 2 not fully installed or removed.
| After this operation, 0B of additional disk space will be used.
| Do you want to continue [Y/n]?
| Setting up menu (2.1.43) ...
| Setting up chrony (1.24-2) ...
| /usr/sbin/chronyd already running.
| /usr/sbin/chronyd already running.
| invoke-rc.d: initscript chrony, action "start" failed.
| dpkg: error processing chrony (--configure):
| subprocess installed post-installation script returned error exit status 1
| Processing triggers for menu ...
| Errors were encountered while processing:
| chrony
| E: Sub-process /usr/bin/dpkg returned an error code (1)
| crystalline:/home/niehaus#
`----
However:
,----
| crystalline:/home/niehaus# /etc/init.d/chrony start
| Starting /usr/sbin/chronyd...
| /usr/sbin/chronyd failed to start.
There *seems* to be an failure on startup. But ...
| crystalline:/home/niehaus# ps aux | grep chrony
| root 30969 0.0 0.0 2136 1020 ? S 09:19 0:00
/usr/sbin/chronyd
| root 30971 0.0 0.0 5016 828 pts/1 S+ 09:19 0:00 grep chrony
... it appears in the process table. And ...
| crystalline:/home/niehaus# /etc/init.d/chrony stop
| Stopped /usr/sbin/chronyd (pid 30969).
| crystalline:/home/niehaus#
`----
... it can be stopped. Connecting to a running chrony with chronyc is
possible too.
Hm ... no idea ...
Thanks
Sebastian
- -- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages chrony depends on:
ii dpkg 1.15.7.2 Debian package management system
ii install-info 4.13a.dfsg.1-5 Manage installed documentation in
ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib
ii libncurses5 5.7+20100313-2 shared libraries for terminal hand
ii libreadline5 5.2-7 GNU readline and history libraries
ii timelimit 1.6-1 Simple utility to limit a process'
ii ucf 3.0025 Update Configuration File: preserv
Versions of packages chrony recommends:
ii udev 160-1 /dev/ and hotplug management daemo
chrony suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxmReAACgkQqVj5VlP9Od3+xwCcCyzrCfSgoDE6h8lJOhjt7f3J
MZEAnRWrkKRgLMhp9F1nSRtLj6QFyHBM
=j80u
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 1.24-3
We believe that the bug you reported is fixed in the latest version of
chrony, which is due to be installed in the Debian FTP archive:
chrony_1.24-3.diff.gz
to main/c/chrony/chrony_1.24-3.diff.gz
chrony_1.24-3.dsc
to main/c/chrony/chrony_1.24-3.dsc
chrony_1.24-3_amd64.deb
to main/c/chrony/chrony_1.24-3_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
John G. Hasler <[email protected]> (supplier of updated chrony package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 14 Sep 2010 10:06:47 -0500
Source: chrony
Binary: chrony
Architecture: source amd64
Version: 1.24-3
Distribution: unstable
Urgency: high
Maintainer: John G. Hasler <[email protected]>
Changed-By: John G. Hasler <[email protected]>
Description:
chrony - Sets your computer's clock from time servers on the Net
Closes: 552162 592930 593145
Changes:
chrony (1.24-3) unstable; urgency=high
.
* Applied (modifed) patch from Gregor Herrmann.
.
Closes: #593145: fails to configure on installation
Closes: #552162: chrony incorrectly thinks that it has failed to
(re)start
Closes: #592930: invoke-rc.d: initscript chrony, action "start" failed.
Checksums-Sha1:
d6594cc6741b7cb3a2d92ea0fc936e5b8f49dfec 1627 chrony_1.24-3.dsc
dc724e98a00f9172ee80bfb95cb85e2e868218f7 134038 chrony_1.24-3.diff.gz
bcac2e7a1008e3f9a6eb88d4e54726a836687725 361232 chrony_1.24-3_amd64.deb
Checksums-Sha256:
b34dcac99e0fa5b015a18c0f9b346593f5bc730e179789a4bf2fb0566bc8a588 1627
chrony_1.24-3.dsc
bd745c1408be35eed970f052f266846d25e14bc5713d8479070fdc971150b987 134038
chrony_1.24-3.diff.gz
02beba4096df7fa2cff54ba7d520c796af2371d1dbea623ae1f7115f4c115559 361232
chrony_1.24-3_amd64.deb
Files:
5d994e3b3b4d639748d1137acbf3de3b 1627 admin extra chrony_1.24-3.dsc
9177b06cc586d336ed8b64cc5c82982c 134038 admin extra chrony_1.24-3.diff.gz
2aa593f4094c0057c6bb94ce4552879a 361232 admin extra chrony_1.24-3_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJMkAu/AAoJEHNAHjW0+9ql1LcQALdKWlEFUlPfeyOIBw4hS6uI
GF5Y4DsRmtHi0NAXHE15GPd4LcB6KIHKcIzXCsOjy4yax+tuYt05uQ9zlXUT+BzC
TjBTU3iSZefyOTPto+K/0L2Z+TnmnP0P4i9wwXGJUPIFsidI4bDqQOvEelQZrBYV
ChpxRnf+RPJ8UxGekTAcl7l/gFlHdhHre9Ckq7mWbqQxzdpskwPa7PhBljP5HN+h
pCy/xcbYVra44/e6BLlUA66gPoSiYiL/AKbnEYlChDZD3qV5V/rZ0k+fTXJn/nxv
J+7bxS6GJLQXVPnzKqsOW3WamAMd1PLY9kFjp4zomoHzO3L0C5PB9CPZRT3JHNuM
DC+PQF3o+Zd6Cu8jezDraUIjgN+0UMf8QNSMQVpP3Dx6vJ5+odCHQyDok8gPkXYV
U7QexdOF/KG9rPq+Y4Yo+led2aU1usTnSbsgfeZG4PcdYyS0W5ljUOk3eVkAYCoz
crbiZvOc0+2vbQng6C0usmCQUp8PuiKEm4cOxST3rX+LhkYgjzHRENzTDYKllGj8
Wz7CPvV7meCkEN6tbz57q4zHiZbv3bEgrNCtrBd6Bz+V+T9oqe9AwHd1vDMO4zAk
Raogs+kIe2Zmq5es3JY2ZBvYkXm5yg5d/v4c68lJ/IztHB4isvOmLUU+Ozjz+Ibv
YasUra1fhvVtav7DqBqn
=XHQb
-----END PGP SIGNATURE-----
--- End Message ---