It does. This may be related to a known upstream problem with some
motherboards. Please try commenting out the rtcfile directive in
/etc/chrony/chrony.conf.
After commenting out rtcfile upgrading the package again works, so that
might at least be a work around. Still I think that this
I had problems with /dev/rtc before, sometimes related to HPET which in
combination with chrony even froze my system. This kernel bug has been fixed
recently. Also I had problems when using the wrong module. Are you sure you
use
the right one? Does hwclock work for you?
I don't really know
Helmut writes:
Exactly: or is hung. An hung is a bug.
Yes, of course it is. However, it is important to know whether Chronyd is
failing to start, starting and then crashing, or getting hung up.
--
John Hasler
[EMAIL PROTECTED]
Elmwood, WI USA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Helmut writes:
I also tried to strace chronyd directly. It hangs in a read from
filedescriptor 6 which happens to be /dev/rtc according to lsof, so
indeed chronyd *is* hung. Hope this helps.
It does. This may be related to a known upstream problem with some
motherboards. Please try
On Fri, Oct 31, 2008 at 10:22:40PM +0100, Helmut Grohne wrote:
I also tried to strace chronyd directly. It hangs in a read from
filedescriptor 6 which happens to be /dev/rtc according to lsof, so
indeed chronyd *is* hung. Hope this helps.
I had problems with /dev/rtc before, sometimes related
severity 504000 important
thanks
Given that the whole setup works like a charm for me I think the severity is
too high, thus I downgraded it. From looking at /etc/ppp/ip-up.d/chrony I'd
guess that $PASSWORD is empty for you. Could you please verify?
Michael
--
Michael Meskes
Michael at
If you want to get an answer I urge you to also contact the submitter
(me) by either by ccing me directly or by ccing [EMAIL PROTECTED]
Otherwise it is very unlikely that I eventually catch your comment. See
#351856.
Given that the whole setup works like a charm for me I think the severity is
On Fri, Oct 31, 2008 at 01:33:48PM +0100, Helmut Grohne wrote:
If you want to get an answer I urge you to also contact the submitter
(me) by either by ccing me directly or by ccing [EMAIL PROTECTED]
Argh, sorry, just forgot it.
I had to downgrade, because chrony also broke suspend2disk[1], so
Hallo Michael,
Sorry, I don't buy into this argument, but it's nitpicking anyway. The bug has
to be fixed.
ACK
It is not empty. And if it was empty, downgrading would not solve the
issue.
No, that's not necessarily true. There may be a problem in the shell script
for
example or in
Helmut writes:
I had to downgrade, because chrony also broke suspend2disk[1]...
Is this a different bug? If so it should be reported seperately.
...so I could as well have tagged it critical because it affects other
applications as well.
I can find no package named anything like
Helmut writes:
When I manually start chronyc and then type a command (sourcestats for
instance) it keeps waiting forever.
This almost certainly means that chronyd is not running (or is hung).
--
John Hasler
[EMAIL PROTECTED]
Elmwood, WI USA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
On Fri, Oct 31, 2008 at 02:49:04PM +0100, Helmut Grohne wrote:
Thanks for you effort. If you have any ideas for debugging, please tell
me.
Have you ever tried using the default config?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at
On Fri, Oct 31, 2008 at 09:45:45AM -0500, John Hasler wrote:
...so I could as well have tagged it critical because it affects other
applications as well.
I can find no package named anything like suspend2disk. As I have no
laptop I am not familiar with the various hibernation and
Hallo Michael,
Have you ever tried using the default config?
Yes, no change.
I also tried to strace chronyd directly. It hangs in a read from
filedescriptor 6 which happens to be /dev/rtc according to lsof, so
indeed chronyd *is* hung. Hope this helps.
Helmut
--
To UNSUBSCRIBE, email to
Hello John,
I had to downgrade, because chrony also broke suspend2disk[1]...
Is this a different bug? If so it should be reported seperately.
I explained why this affected ...
...so I could as well have tagged it critical because it affects other
applications as well.
I can find no
Hi John,
When I manually start chronyc and then type a command (sourcestats for
instance) it keeps waiting forever.
This almost certainly means that chronyd is not running (or is hung).
Exactly: or is hung. An hung is a bug.
Helmut
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
16 matches
Mail list logo
