Probably same behavior.
After upgrading from Ubuntu 9 to Ubuntu 10.04 LTS - Lucid Lynx
vsftpd server failed to login users.
Problem was solved after libpam-smbpass was ununstalled.
From log files:
[auth-log]:
Oct 22 10:33:53 HP6720s1 vsftpd: pam_winbind(vsftpd:auth): pam_get_item
returned a
This is apparently avoided in Jaunty through the apparmor fix, no sightings so
far.
Closing as Fix Released, and nominating bug 357581 for Intrepid SRU.
** Changed in: samba (Ubuntu)
Status: Confirmed = Fix Released
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
Created bug 357581 to fix apparmor smbpass abstraction. I'm not sure it
will ultimately fix this problem, but it would surely explain why the
bug appeared in Samba 3.2 (LDB files weren't in use before) and why this
seems to be Ubuntu-specific (our cupsd/apparmor thing is Ubuntu-
specific). There
** Also affects: baltix
Importance: Undecided
Status: New
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Still struggling to reproduce this.
There seems to be something CUPS-related that results in secrets.tdb
corruption with Unable to open tdb '/var/lib/samba/group_mapping.ldb'
error messages. Once corrupted, this file seems to trigger libpam-
smbpass segfaults.
Following the error message lead,
I have just suffered this bug too, and it was after installing cups.
I removed libpam-smbpass, then I renamed secrets.tbd and installed
libpam-smbpass again.
Now I can login again, and I have Samba, but I don't have CUPS. Is there any
way to install cups and work this bug around?
--
segfault
Release: Jaunty
Since a recent upgrade (around the 16th of March), sudo has been broken.
Entering the correct password causes sudo to simply exit and not run the
command, it was found that this could be fixed by commenting/removing
the line
auth optional pam_smbpass.so migrate
in
** Changed in: samba (Ubuntu)
Assignee: Rafael Soares (rafaelsoaresbr) = (unassigned)
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
I found that the corrupted secrets.tdb prevented samba from starting:
[2009/03/27 12:16:44, 0] smbd/server.c:main(1213)
smbd version 3.2.3 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/03/27 12:16:44, 0] lib/util_tdb.c:tdb_wrap_log(886)
On Tue, Mar 24, 2009 at 12:58:40PM -, Thierry Carrez wrote:
Steve,
The smbpasswd-syslog.patch you submitted to Samba [1] as a fix to Debian
bug 434372 never made it to a Samba release. Since this sudo segfault
issue seems to only affect our build (and only since Intrepid) I was
wondering
In duplicate bug 346571, reporter is using the Jaunty version so we can
assume it's still present in jaunty.
Reporter confirms the secrets.tdb file contains text that should rather appear
in a log file:
Unable to open tdb '/var/lib/samba/group_mapping.ldb'
Failed to connect to
Steve,
The smbpasswd-syslog.patch you submitted to Samba [1] as a fix to Debian bug
434372 never made it to a Samba release. Since this sudo segfault issue seems
to only affect our build (and only since Intrepid) I was wondering if the patch
was not introducing an issue when run against the 3.2
This is probably a duplicate to bug 292791, though nobody there
explicitly reported secrets.tdb corruption.
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** Tags added: likely-dup
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
I was wondering if this wasn't Ubuntu-specific since I couldn't find any
report elsewhere of a similar problem. It's also introduced in 8.10, and
we didn't have any report of it persisting in 9.04 alpha (so far).
The tdb file corruption mentioned in comment 15 and comment 16 is
interesting. Since
Can we *please* get some triage on this bug? It has now made three
laptops where I work inoperable to those who do not know to disable the
pam_smpass module.
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Came across this issue just last night and found the cause to be less
than insidious.
Seems that after I finished editing smb.conf, the daemon reloaded the
new file automagically. This is when the trouble started.
As it turns out, my new config had a typo and was specifying a directory
that did
Correction, it wasn't a typo for the directory, it was a typo for the
line. Here is the line at issue:
path /data/apps
Which is missing the '=' operator. This is what caused samba to choke,
and pam to follow suit.
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You
And now I'm just muddying the water. Even with my corrected (and
testparm approved) smb.conf and samba daemons stopped, I get the pam
segfault because of pam_smbpass.so.
It should be noted that by returning to the default smb.conf, pam is
happy once more. I have attached the smb.conf that makes
Corrected the misspelling of 'tdbsam' on line 6 of the above posted
smb.conf. New config is working fine and pam hasn't segfaulted as of
yet.
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Server Team,
i had this issue, and resolved it by reinstalling libpam-smbpass.
now it came back.
i guess i'll have to remove that library. what are the ipacts on the
system in doing so?
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a
I encountered this bug today. For me, the problem was the
/var/lib/secrets.tdb file. It appears that a portion of the file was
clobbered by some log messages:
^...@^@^...@ltdb: tdb((null)): tdb_open_ex: could not open file
/var/lib/samba/group_mapping.ldb: Permission denied
Unable to open tdb
I see the same log messages in secrets.tdb on my affected machines as
well.
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs
Should this be merged with #302092?
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
I had the same problem on a fresh install of Ubuntu 8.10 amd64.
I followed the instructions given by Thierry Carrez above, and removed
samba and libpam-smbpass, deleted /var/lib/samba, created a new empty
directory to replace it, and reinstalled samba and libpam-smbpass.
Rebooted and all was
Could this error be related to this bug: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=478752, namely the last message, which lists CUPS
as the offender. I've recently uncommented the line listed in this
message and haven't seen any more errors, however it did take about 10
hours for it to
Is this a good idea to use gdb during a sudo command to check what
happen ?
( I just hear that gdb is a debugger... but I don't know how to use it
and how it work ! )
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member
zedtux:
OK, then we can try to cleanup by hand:
$ sudo rm -rf /var/lib/samba
$ sudo mkdir /var/lib/samba
pam_smbpass.so is known to segfault if the /var/lib/samba directory
doesn't exist, or if it is non-empty, filled by something it doesn't
like. I never saw it segfault when using an existing,
Thanks for your help !
I said, in my comment 4, that I have try to rm -rf /var/lib/samba and re-intall
package.
But, I have not try to uninstall every samba packages... :(
And now, as I need a working computer ( working on a project ), I have
re-install everything and now, no errors.
--
There was probably a problem with corrupted contents in
/var/lib/samba... this tends to occur a little too often in my taste and
pam_smbpass integration makes it fail quite badly. I'm not exactly sure
what we can do to avoid it though.
** Changed in: samba (Ubuntu)
Status: Incomplete = New
So, I have back in rescue mode and do all possible updates.
After that, I did an ls /var/lib/samba and saw many files.
So did the apt-get remove --purge libpam-sbmpass and then, execute again an ls
/var/lib/samba.
Files still there !
So, I did a rm -rf /var/lib/samba, and then apt-get install
Could you try the workaround in:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/302092/comments/4
Is it a 8.04 box that was upgraded to 8.10 ? Did sudo start to fail as
soon as you upgraded, or did it start to fail some time after ?
** Changed in: samba (Ubuntu)
Status: New =
About the workaround: could you confirm that /var/lib/samba is removed
after you purged libpam-smbpass and samba-common ?
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: samba (Ubuntu)
Sourcepackagename: linux = samba
--
segfault in pam_smbpass.so
https://bugs.launchpad.net/bugs/303458
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
34 matches
Mail list logo
