Christophe Wolfhugel wrote:
> Kurt Roeckx wrote:
> > Do you use the default ntp.conf as shipped in the latest package?
> > If not can you either try that or add "rlimit memlock 0" at the
> > top of ntp.conf?
>
> Good hit Kurt.
>
> No I do not use the stock ntp.conf ...
Same here. I have the exac
On Thu, Jul 30, 2015 at 08:26:43AM +0100, Christophe Wolfhugel wrote:
>
> I would conclude that "something somewhere" makes the getpw*
> call fail when "rlimit memlock 0" is not used.
As I understand, the default should change in one of the next
upstream versions. It causes all kind of weird beh
Based on the conversations upstream, I'd say that rlimit memlock 0
should be the default in debian, not something that needs to be added to
working configs. (It appears that beyond the startup issue, it's fairly
common for running ntpd's to crash with out-of-memory errors when using
memlock. Th
On 28/07/15 15:28, Kurt Roeckx wrote:
> Do you use the default ntp.conf as shipped in the latest package?
> If not can you either try that or add "rlimit memlock 0" at the
> top of ntp.conf?
Good hit Kurt.
No I do not use the stock ntp.conf (I have an autokey config),
and indeed "rlimit memlock 0
On Tue, Jul 28, 2015 at 02:41:12PM +0200, Christophe Wolfhugel wrote:
> I do agree there must be something else which broke the
> getpw call or the libc somehow. On another machine I also
> have compat for nsswitch.conf and it worked.
Do you use the default ntp.conf as shipped in the latest packag
On 2015-07-28 14:41:12 +0200, Christophe Wolfhugel wrote:
> I do agree there must be something else which broke the
> getpw call or the libc somehow. On another machine I also
> have compat for nsswitch.conf and it worked.
>
> Also on my setup the Perl "getpwuid/getpwnam" functions
> were still wo
I do agree there must be something else which broke the
getpw call or the libc somehow. On another machine I also
have compat for nsswitch.conf and it worked.
Also on my setup the Perl "getpwuid/getpwnam" functions
were still working correctly despite the ntpd's call failing.
I do not have a clea
On 2015-07-27 18:50:34 +0200, Christophe Wolfhugel wrote:
> I observed the same issue with the recent update from testing, although
> I narrowed this down to a possible change or bug in other packages.
>
> On my system /etc/nsswitch.conf was set to compat for passwd/group/shadow
I also have:
pas
On 2015-07-26 19:34:10 -0600, Bob Proulx wrote:
> After today's update ntp no longer starts on my Sid system. After
> being gone on travel for ten days I return and update Sid and now ntp
> isn't running.
>
> The log message reports:
[...]
This problem doesn't occur on my up-to-date sid machine
On Sun, Jul 26, 2015 at 07:34:10PM -0600, Bob Proulx wrote:
> Jul 26 19:23:54 hysteria ntpd[15301]: Cannot find user ID 109
>
> $ grep 109 /etc/passwd
> ntp:x:109:116::/home/ntp:/bin/false
>
> $ grep 116 /etc/group
> ntp:x:116:
The call to getpwuid() failed. So I think there is someth
Package: ntp
Version: 1:4.2.8p3+dfsg-1
Followup-For: Bug #793745
I observed the same issue with the recent update from testing, although
I narrowed this down to a possible change or bug in other packages.
On my system /etc/nsswitch.conf was set to compat for passwd/group/shadow
and I did set it (
Package: ntp
Version: 1:4.2.8p3+dfsg-1
Severity: serious
After today's update ntp no longer starts on my Sid system. After
being gone on travel for ten days I return and update Sid and now ntp
isn't running.
The log message reports:
Jul 26 19:23:54 hysteria ntpd[15300]: ntpd 4.2.8p3@1.3265-o
12 matches
Mail list logo
