** Changed in: samba (Ubuntu)
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/216358
Title:
Samba crashes repeatedly to assert_uid
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better. There have been many changes in Ubuntu since that time
you reported the bug and your problem may have been fixed with some of
the updates. It would help us a lot if you could test it on a currently
supported Ubuntu
** Changed in: samba
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
https://bugs.launchpad.net/bugs/216358
Title:
Samba crashes repeatedly to assert_uid
--
Ubuntu-server-bugs
Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the
report. Can anyone confirm whether this issue still exists in later versions
of Ubuntu?
** Changed in: glibc (Ubuntu Intrepid)
Status: New = Invalid
** Changed in: glibc (Ubuntu)
Status: New = Incomplete
--
Intrepid has reached EOL so im closing this SRU.
** Changed in: samba (Ubuntu Intrepid)
Status: Confirmed = Won't Fix
--
Samba crashes repeatedly to assert_uid
https://bugs.launchpad.net/bugs/216358
You received this bug notification because you are a member of Ubuntu
Server Team, which
I haven't seen this one happening in karmic/lucid, could anyone confirm
?
--
Samba crashes repeatedly to assert_uid
https://bugs.launchpad.net/bugs/216358
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
We are also randomly affected by this issue. I'm wondering if there is
any progress in fixing these problems in Hardy.
Nov 30 12:29:59 hm-server smbd[9133]: [2009/11/30 12:29:59, 0]
lib/util_sec.c:set_effective_uid(205)
Nov 30 12:29:59 hm-server smbd[9133]: setresuid failed with EAGAIN.
I've removed the patch flags from the previous attachments that were
flagged as patches since they didn't seem to fix the issue although they
are still patches. This will prevent the bug from showing up in the
patched bug workflow which seems most appropriate so no action is to be
taken with the
I haven't reverted to plain samba, but I get output that has the line
you mention in the logfile concerning my desktop computer (log.eos).
I've attached the log.
** Attachment added: Samba logfile
http://launchpadlibrarian.net/24397337/log.eos
--
Samba crashes repeatedly to assert_uid
Thierry Carrez wrote:
Please let me know if all reporters run SELinux, so that I can comment
on the upstream bug.
Installed but default config (which I interpret to means 'effectively
disabled'.
I haven't managed to try the patched version yet - been at the UKUUG
conference.
Keith
--
I've installed the files from https://launchpad.net/~ttx/+archive/ppa
and restarted the machine. It's running Hardy, and one of my shares are
completely inaccessible from my Ubuntu desktop running gnome. Are there
any other race conditions that should be avoided?
My trace seems a bit different
Thanks anders for that new piece of information.
Could you give the output of 'dpkg -l | grep samba' just to be sure that
you are running the patch version?
This seems to confirmed that the new version does fix Asynchronous I/O
result, but not the fact that setreSuid results in EAGAIN error.
Anders: thanks for testing !
Apparently my packages do not change anything :/
That might mean bug 341816 is not a duplicate of this one, I'll follow up on
that one separately.
The problem here is probably a similar one, but does not involve AIO code.
** Changed in: samba (Ubuntu)
Please let me know if all reporters run SELinux, so that I can comment
on the upstream bug.
--
Samba crashes repeatedly to assert_uid
https://bugs.launchpad.net/bugs/216358
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
I posted this output in my previous post, but it was lost inside the
Read more... link :)
~$ dpkg -l | grep samba
ii samba 3.0.28a-1ubuntu4.9~ppa1
ii samba-common 3.0.28a-1ubuntu4.9~ppa1
ii samba-dbg 3.0.28a-1ubuntu4.9~ppa1
I've looked through the emails i got with the samba panic/segfault
Thanks Anders, I should have seen this Read more... link.
For me, this helps to know if samba logs have the following line:
setresuid failed with EAGAIN.
But the latest ppa1 version probably won't do that, you'd have to revert
to plain samba first.
And the Samba log are many files by default
Proposed patch for Intrepid
Packages also available for testing in my PPA (2:3.2.3-1ubuntu3.6~ppa1)
at https://launchpad.net/~ttx/+archive/ppa
I can't really reproduce the issue in the first place, so I'd welcome
some testing to make sure this is indeed the right fix :)
** Attachment added:
Well, I don't really can test it either, so it would have to be tested
by others.
I don't really understand, how this race between AIO and setresuid would affect
the result of setresuid.
Seems it's fix the result of the (Asynchronous IO), not of setresuid.
But I have an even much bigger problem
Sigh. It is even a bit more complex than that:
In Unix-like systems, user-level activities are implemented by running
processes. Most Unix systems support a ``thread'' as a separate concept;
threads share memory inside a process, and the system scheduler actually
schedules threads. Linux does
Proposed patch for Hardy
That fix was included in 3.0.34, 3.2.4 and 3.3.0 so Jaunty would be
already fixed.
Please confirm that it really fixes the issue by testing the hardy samba
packages from my PPA (samba_3.0.28a-1ubuntu4.9~ppa1) at
https://launchpad.net/~ttx/+archive/ppa
** Attachment
** Bug watch added: Samba Bugzilla #5549
https://bugzilla.samba.org/show_bug.cgi?id=5549
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=5549
Importance: Unknown
Status: Unknown
--
Samba crashes repeatedly to assert_uid
** Changed in: samba (Ubuntu)
Assignee: (unassigned) = Thierry Carrez (ttx)
Status: Confirmed = In Progress
--
Samba crashes repeatedly to assert_uid
https://bugs.launchpad.net/bugs/216358
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: samba
Status: Unknown = Confirmed
--
Samba crashes repeatedly to assert_uid
https://bugs.launchpad.net/bugs/216358
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
** Changed in: samba (Ubuntu Intrepid)
Importance: Undecided = Medium
Assignee: (unassigned) = Thierry Carrez (ttx)
Status: New = Incomplete
** Changed in: samba (Ubuntu Intrepid)
Status: Incomplete = In Progress
** Changed in: samba (Ubuntu)
Status: In Progress =
Avoid a race condition in glibc between AIO and setresuid():
http://gitweb.samba.org/?p=samba.git;a=commit;h=c1ef3b8e28777f70086c8d2ee851e3a0b5b4ca4c
Become root for AIO operations:
http://gitweb.samba.org/?p=samba.git;a=commit;h=c60631879dbe6e87bc03c0412a4c8857b2f4339b
** Changed in: samba
Ok, I think this time I have found.
taken from 3.0.34 samba changelog (latest in 3.0):
http://www.samba.org/samba/history/samba-3.0.34.html
o Andrew Tridgell
* Avoid a race condition in glibc between AIO and setresuid().
* Become root for AIO operations.
This would explain why
In fact I believe it comes from that guy:
http://webui.sourcelabs.com/rhel/issues/459901
he seems to suggest that the real problem is with the kernel not exactly
implementing Posix correctly.
I still have a doubt because he speak of setresuid changing the value of AIO,
not changing the value
On Sat, Mar 14, 2009 at 02:39:53AM -, Paul Dufresne wrote:
I now tend to think this is caused by the -1 not being casted to appropriate
type in:
setresgid(-1,gid,-1);
and in:
assert_uid(-1, uid);
in lib/sec_util.c as I said in bug #314657 causing problems on 64 bits
machines.
Yeah, I began to realise I was wrong before reading you comment.
I have a new, I hope better hypothesis now.
It look a bit stupid, but maybe it is trying to become a deleted user.
For ZDS (original poster) it would have means he would have deleted the
nobody user (normally nobody have
id 65534
For Berni, I meant:
sudo cat /etc/group | grep 1001 of course.
--
Samba crashes repeatedly to assert_uid
https://bugs.launchpad.net/bugs/216358
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs
On Sun, Mar 15, 2009 at 03:01:40AM -, Paul Dufresne wrote:
It look a bit stupid, but maybe it is trying to become a deleted user.
For ZDS (original poster) it would have means he would have deleted the
nobody user (normally nobody have id 65534 in /etc/passwd, but I
remember a time where
I now tend to think this is caused by the -1 not being casted to appropriate
type in:
setresgid(-1,gid,-1);
and in:
assert_uid(-1, uid);
in lib/sec_util.c as I said in bug #314657 causing problems on 64 bits machines.
But I am unsure.
--
Samba crashes repeatedly to assert_uid
Bug #314657 and bug #229654 seems to be duplicates.
Well, I would make them duplicates of this one, but, as it was marked invalid...
hum, in fact looks more like Steve thinks his explanation for invaliding is
doubtful.
Guess I'll mark those duplicate of this one, and change to Incomplete.
**
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468296 suggests it
could be linked to roaming profiles.
--
Samba crashes repeatedly to assert_uid
https://bugs.launchpad.net/bugs/216358
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Steve,
this could not be normal - in /etc/security/limits.conf there is no limit
configured, and I dont know,
but could it be unlimited as default in Ubuntuty Hardy ?
Commenting out panic-action does not solve the problem, because it only
prevents the mail
and not the action. smbd still
So again here is the last panic action output, a little longer, but
still the NPROC limit error in the host logfile:
[2008/10/06 08:49:27, 0] lib/util_sec.c:set_effective_uid(205)
setresuid failed with EAGAIN. uid(1001) might be over its NPROC limit
[2008/10/06 08:49:27, 0]
I can confirm this kind of bug!
On a new installed Hardy, Samab crashes not everytime but often:
Log from the per Host logfile:
[2008/10/04 20:09:57, 0] lib/util_sec.c:set_effective_uid(205)
setresuid failed with EAGAIN. uid(1001) might be over its NPROC limit
[2008/10/04 20:09:57, 0]
berni123,
Thanks for providing this log. Now that I see the log, the crash makes
perfect sense. :)
But I have to say that it's not a samba bug. What we're looking at is a
failed assertion because the OS wouldn't let the process change UIDs; as
the log says, this may be because the user has
** Changed in: samba (Ubuntu)
Importance: Undecided = Low
Status: New = Incomplete
--
Samba crashes repeatedly to assert_uid
https://bugs.launchpad.net/bugs/216358
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Thank you for taking the time to report this issue and help to improve
Ubuntu.
Hitting this assertion error should also generate log entries. Could
you please check /var/log/samba/log.smbd (or the per-host logfile) for
entries of the form Failure to set uid privileges to [...]?
Does this
40 matches
Mail list logo
