Arthur de Jong wrote:
> I just now noticed that I did not send the attached message to you but
> only to the bug report.
I did get it, somehow.
> If you can reasonably reliably reproduce this, can you add the following
> to /etc/init.d/nslcd (around line 120, right before
> # start nslcd).
IIRC
But from my logs it
seems that nslcd is now started before the network is available. Perhaps
systemd does not honour the LSB headers in the init script?
If you can include the debugging information that is described here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643948#61
that would be
I have the same issue.
It happens rarely but that's the bigger issue: NSS/LDAP is the most
critical service because without, all services and even login is
broken.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@l
On Thu, 2014-05-15 at 11:06 +1000, Trent W. Buck wrote:
> In the last couple of weeks, I switched from unencrypted ldap://ldap
> to encrypted ldaps://ldap, and now I'm seeing it on around 10% to 20%
> of boots (with a sample set of about ten boots).
If you can reasonably reliably reproduce this,
Arthur,
This datapoint is probably intuitive, but I'll point it out anyway.
I've been running 0.9.2-1wheezy1 (my own backport) on top of wheezy
for a while, and never saw this issue.
In the last couple of weeks, I switched from unencrypted ldap://ldap
to encrypted ldaps://ldap, and now I'm seein
Followup-For: Bug #643948
Package: libgcrypt11
Version: 1.5.3-2
On Thu, 2013-05-23 at 20:34 +0200, Arthur de Jong wrote:
> Today, for the first time I ran into this problem on my own system. From
> the logs:
Again a crash today, from syslog:
Nov 30 19:05:09 sorbet nslcd[2307]: version
On Thu, 2013-05-23 at 20:34 +0200, Arthur de Jong wrote:
> Today, for the first time I ran into this problem on my own system.
Forgot to mention, this is with the following versions:
ii libc6 2.17-3
ii libgcrypt111.5.0-5
ii libgnutls262.12.23-4
ii libgssapi-krb5-2
Today, for the first time I ran into this problem on my own system. From
the logs:
May 23 19:26:06 sorbet nslcd[2916]: accepting connections
May 23 19:26:06 sorbet nslcd[2916]: Libgcrypt notice: state transition Power-On
=> Fatal-Error
May 23 19:26:06 sorbet nslcd[2916]: Libgcrypt error: fatal er
Greetings,
We are probably observing the same issue. The following syslog fragment
shows that the failure seems to happend right after the initialization
of the network interface by NetworkManager. (The fragment has minor
replacements for privacy.)
Dec 27 07:51:18 carrefour nslcd[1451]: version
On Sun, 2 Oct 2011 17:24, adej...@debian.org said:
> Btw, it seems to be pretty bad for a library to abort the whole
> application when it's state is inconsistent.
This is a FIPS requirement. You are running your system in FIPS mode -
see the manual.
Shalom-Salam,
Werner
--
Die Gedanken
ivelo tina ; 643...@bugs.debian.org
Cc : libgcryp...@packages.debian.org
Envoyé le : Dimanche 2 Octobre 2011 17h24
Objet : Re: Bug#643948: nslcd: daemon hang during machine boot process
reassign 643948 libgcrypt11 1.5.0-3
thanks
On Sat, 2011-10-01 at 01:33 +0100, rakotoarivelo tina wrote:
> *** Ple
reassign 643948 libgcrypt11 1.5.0-3
thanks
On Sat, 2011-10-01 at 01:33 +0100, rakotoarivelo tina wrote:
> *** Please type your report below this line ***
> nslcd hang during machine boot process with the following errors:
>
> Sep 30 18:50:14 node-30 nslcd[1797]: version 0.7.13 starting
> Sep 30 1
Subject: nslcd daemon hang during machine boot process
Package: nslcd
Version: 0.7.13
Severity: important
*** Please type your report below this line ***
nslcd hang during machine boot process with the following errors:
Sep 30 18:50:14 node-30 nslcd[1797]: version 0.7.13 starting
Sep 30 18:50:14
13 matches
Mail list logo
