Public bug reported:
[IMPACT]
* puppet setup with storeconfig activated
* On client run, master fail with stack level too deep error, and client do
no apply any of its manifests
* not all clients are affected, but if one client is failing it will fail
forever
* This issue is known and fixed on
Attached debdiff integrating upstream fix for trusty.
Issue is fixed in Utopic (puppet 3.5.1)
** Patch added: puppet_3.4.3-1ubuntu0.1.debdiff
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1313595/+attachment/4099292/+files/puppet_3.4.3-1ubuntu0.1.debdiff
** Changed in: puppet
*** This bug is a duplicate of bug 1023025 ***
https://bugs.launchpad.net/bugs/1023025
** This bug has been marked a duplicate of bug 1023025
search fail with get_ctrls : controls require LDAPv3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: openldap (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1023025
Title:
search fail with get_ctrls : controls require
Public bug reported:
Binary package hint: samba
In lucid upgraded from hardy, my nmbd daemon does not start (neither with
service nmbd start or calling /etc/init.d script). It seems that the upstart
job is doing the following test to ensure netbios is enabled:
testparm -s
If I can try to summarize the situation on this bug:
- This is a regression from hardy. This use to work on hardy.
- We document using tls for LDAP authentication in the server guide
The most annoying point IMHO, is that someone who has root access to his
server with a LDAP account with sudo,
Hi Andrew,
We do not include new package revisions in already released Ubuntu version. To
get 2.0.3 in intrepid (or in hardy), you should fill a bug report on
intrepid-backports. You can check the full process:
https://help.ubuntu.com/community/UbuntuBackports#How to request new packages
--
The fix in fail2ban 0.8.2-2ubuntu0.1 works for me. Thanks.
--
[SRU] fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
--
Ubuntu-server-bugs mailing list