samba - Jan 2008 - PANIC on 6 of my client servers .Please Help

Hi everybody
I have six samba servers working in various client locations all of which
exhibit the
same problem.

+++++++++++++++++++++++++++++++++++++++++++++++++
Jan 31 09:37:58 sos02sp smbd[1454]: [2008/01/31 09:37:58, 0]
lib/util_sec.c:assert_uid(101)
Jan 31 09:37:58 sos02sp smbd[1454]:   Failed to set uid privileges to (-1,533)
now set
to (0,0)
Jan 31 09:37:58 sos02sp smbd[1454]: [2008/01/31 09:37:58, 0]
lib/util.c:smb_panic(1621)
Jan 31 09:37:58 sos02sp smbd[1454]:   PANIC (pid 1454): failed to set uid
+++++++++++++++++++++++++++++++++++++++++++++++++

Followed by a backtrace dump. 

Some of these servers have been running for several years without any major
issues and
this problem seems to have after a version upgrade to 3.0.24. Having six servers
with
the same problem tends to indicate to myself that I have a common configuration
issue. I
have tried everything including complete fresh installs and don't seem to be
able to
resolve the issue.  Having done significant research on the Web, this panic
issue does
not appear to be endemic nor common.

To save space I has included all my logs and configurations at the following Web
address.


All logs and config information can be found at:-
http://www.secureoffice.com.au/samba/


 Any help (or constructive criticism) would be greatly appreciated


Regards
Brad Horrocks

--
Secure Office Services 
ABN 75 196 364 531
19 Burrendong Road
COOMBABAH QLD 4216
Ph. +61 7 5537 4955
Fx. +61 7 5537 4966
Mob.+61 (0)404142690
web: http://www.secureoffice.com.au

Res, 
(I use openwebmail, I'll use the CR for you).

I'm using FC6 and the servers have all been upgraded from FC2 and FC4. 
The upgrade was completed before I took them over so I don't know what samba
version
 was in use with those versions of Fedora.

The idea was to standardise on a particular version to simplify maintenance and
it
seems to have caused more problems than it cured.

I didn't do the original upgrade to read the history, however... 
I have completely removed samba and all associated files (tdb's et) from 
one of  the servers and then tried to re-install using fresh Fedora RPM's. 

The same problem persists..

Regards
Brad Horrocks

--
Secure Office Services 
ABN 75 196 364 531
19 Burrendong Road
COOMBABAH QLD 4216
Ph. +61 7 5537 4955
Fx. +61 7 5537 4966
Mob.+61 (0)404142690
web: http://www.secureoffice.com.au

---------- Original Message -----------
From: Res <res@ausics.net>
To: "Brad Horrocks [Secure Office Services]"
<bradhorrocks@secureoffice.com.au>
Cc: samba@lists.samba.org
Sent: Thu, 31 Jan 2008 17:08:01 +1000 (EST)
Subject: Re: [Samba] PANIC on 6 of my client servers .Please Help
> *Top Posting*" I dont know what client you used, but the format
exceeds 75
> chars per line in Pine so my comments will be out of wack if I reply 
> inline...
> 
> You have said 3.0.24, have you tried 3.0.28 which current?
> The version you moved "to" 3.0.24 is a year old.
> What version did you upgrade from?
> Have you read the history changes for subsequent releases from your old to 
> current?
> What OS/version are at least one of these on?
> 
> Res
> 
> On Thu, 31 Jan 2008, Brad Horrocks [Secure Office Services] wrote:
> 
> > Hi everybody
> > I have six samba servers working in various client locations all of
which exhibit the
> > same problem.
> >
> > +++++++++++++++++++++++++++++++++++++++++++++++++
> > Jan 31 09:37:58 sos02sp smbd[1454]: [2008/01/31 09:37:58, 0]
lib/util_sec.c:assert_uid(101)
> > Jan 31 09:37:58 sos02sp smbd[1454]:   Failed to set uid privileges to
(-1,533) now set
> > to (0,0)
> > Jan 31 09:37:58 sos02sp smbd[1454]: [2008/01/31 09:37:58, 0]
lib/util.c:smb_panic(1621)
> > Jan 31 09:37:58 sos02sp smbd[1454]:   PANIC (pid 1454): failed to set
uid
> > +++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Followed by a backtrace dump.
> >
> > Some of these servers have been running for several years without any
major issues and
> > this problem seems to have after a version upgrade to 3.0.24. Having
six servers with
> > the same problem tends to indicate to myself that I have a common
configuration issue. I
> > have tried everything including complete fresh installs and don't
seem to be able to
> > resolve the issue.  Having done significant research on the Web, this
panic issue does
> > not appear to be endemic nor common.
> >
> > To save space I has included all my logs and configurations at the
following Web
address.
> >
> >
> > All logs and config information can be found at:-
> > http://www.secureoffice.com.au/samba/
> >
> >
> > Any help (or constructive criticism) would be greatly appreciated
> >
> >
> > Regards
> > Brad Horrocks
> >
> > --
> > Secure Office Services
> > ABN 75 196 364 531
> > 19 Burrendong Road
> > COOMBABAH QLD 4216
> > Ph. +61 7 5537 4955
> > Fx. +61 7 5537 4966
> > Mob.+61 (0)404142690
> > web: http://www.secureoffice.com.au
> >
> >
> 
> -- 
> Cheers
> Res
> 
> mysql> update auth set Framed-IP-Address='127.0.0.127' where
user= 'troll';
------- End of Original Message -------

Res wrote:
> Hi Brad,
>
> On Thu, 31 Jan 2008, Scott Lovenberg wrote:
>
>>> I'm using FC6 and the servers have all been upgraded from FC2
and
>>> FC4. The upgrade was completed before I took them over so I
don't
>>> know what samba version
>>>  was in use with those versions of Fedora.
>
> Using Fedora as a server is dangerous at the best of times, even now 
> Fedora dont support FC6, and will soon enough not even support FC7, I 
> suggest,
> if you can, upgrade the entire OS, to, I'd recommend Slackware 12, 
> security updates are available for more than 5 years, and as Slackware 
> is well known for not modifying packages it has far far far less 
> problems then the stuff that RH/Debian and so on release.
>
> But, if upgrading OS is not an option (it really needs to be) I'd 
> really not use any RPM for it either, what you can do, is grab the 
> 3.0.28 source and compile it, if you use the following in your 
> 'configure' its close to what RH use (extracted from a source.rpm)
>
> ./configure --prefix=/usr --localstatedir=/var 
> --with-configdir=/etc/samba --with-privatedir=/etc/samba --with-fhs 
> --with-quotas --with-smbmount --with-pam --with-pam_smbpass 
> --with-syslog --with-utmp --with-swatdir=/usr/share/swat 
> --with-shared-modules=idmap_rid --with-libsmbclient 
> --with-sendfile-support --with-acl-support --with-winbind
>
>
> If you move to Slackware and want to configure your own, just remove 
> the two pam options.
>
>>>
>>> The idea was to standardise on a particular version to simplify 
>>> maintenance and it
>>> seems to have caused more problems than it cured.
>
> It can :)
>
>>>
>>> I didn't do the original upgrade to read the history,
however... I
>>> have completely removed samba and all associated files (tdb's
et)
>>> from one of the servers and then tried to re-install using fresh 
>>> Fedora RPM's. The same problem persists..
>
> Are you using the same smb.conf ? or are you re writting a brand new one
>
>
I concur; Slackware-10.2 was my first distro (I've learned so much using 
it), and it's the only distro I use for my own servers (Had to use 
CentOS at work... it's RHEL, you know...).  I'm running a Slackware-12 
and BlueWhite64-12 for my PDC and iSCSI SAN, respectively.  If you're of 
the 64 bit persuasion, I'd recommend BlueWhite64 which is a 64 bit port 
of Slack proper, and I've heard that Slamd64 is pretty good as well.  
Also, you can get PAM as a tgz package if you'd like to use it for 
password synchronization... although, it does increase your attack 
vectors surface area a great deal as compared to Slack with only two or 
three services running.  Lastly, I really like the BSD init over Sys V 
init for management.  Anyways, a bit OT, but I thought I'd second the 
notion of staying away from Fedora in production.

On Feb 1, 2008 5:35 PM, Res <res@ausics.net> wrote:
> On Sat, 2 Feb 2008, Brad Horrocks [Secure Office Services] wrote:
>
> > Thanks guys,
> > You've pretty well confirmed I was beating a dead horse (so to
speak).
> >
> > I've downloaded slackware12 and am about to install it into a
> development server.
> >
> > Again much appreciated
> >
>
>
> Best of luck, BTW I seem to have missed the reply to this, not sure why,
> perhaps  SpamAssassinn ate it *shrug* :)
>
>
> --
> Cheers
> Res
>
> mysql> update auth set Framed-IP-Address='127.0.0.127' where
user> 'troll';
>
Ironically, after posting this, I spent the day fighting with Fedora8 in
vmware as a test... Well, it went out the window and will be replaced by
Slackware next time around.  Anyways, if you should have any questions about
Slackware, the guys over at Slackware -
LinuxQuestions.org<http://www.linuxquestions.org/questions/slackware-14/>are
very helpful and knowledgeable.  Best of luck!

-- 
Peace and Blessings,
-Scott.

"Of course, that's just my opinion; I could be wrong"
-Dennis Miller