Koozali.org: home of the SME Server

Samba Bug

simon101

Samba Bug
« on: August 18, 2004, 03:26:44 PM »
Hi there,

Does anybody know about this samba bug and is there a new RPM package with this samba release for SME 6.0?
Or can I just use the standard release for Redhat 7.3 ?
"http://us2.samba.org/samba/ftp/Binary_Packages/RedHat/RPMS/i386/7.3/samba-2.2.11-1.i386.rpm"


I've read this on "http://us1.samba.org/" .
________________________________________________________
Samba 2.2.11 addresses the following bug:

* Crashes in smbd triggered by a Windows XP SP2 client sending a FindNextPrintChangeNotify() request without previously issuing FindFirstPrintChangeNotify().
________________________________________________________

Where can I download this update when it gets released?
And how do I know when it is released?

Offline pisaacs

  • *
  • 15
  • +0/-0
    • http://www.millison.com.au
Samba Bug
« Reply #1 on: September 06, 2004, 06:17:58 AM »

simon101

Samba Bug
« Reply #2 on: September 06, 2004, 06:55:47 PM »
Hi there,

Thanks for the reply!
I have downloaded and installed the beta of samba 3.0 from:

http://mirror.contribs.org/smeserver/contribs/jprice/alpha/samba-3.0.0-3beta3/

And it allso seems to work fine..
What I was thinking, does nobody care at Contribs? Because it affects us all !
Everyone that is using samba before 2.2.11 is vunnerable for this bug...

Well, my problem is solved for now... but it is not for the best that I am using a beta package...

Still, I thak you for your time to post a reply.

Offline pisaacs

  • *
  • 15
  • +0/-0
    • http://www.millison.com.au
Samba Bug
« Reply #3 on: September 06, 2004, 11:46:59 PM »
Hi,

I know I am going to get flamed for this, but....

I believe that Mitel/SME is now a 'dead distro'. This is a real shame as the product was good and a great deal of effort has been put into the product and its support.

The Samba issue is only a symptom of the underlying problems of the current community model and it is olby a matter of time before the product becomes unusable.

We now have a system here the doesnt function correctly with Windows XP SP2, where there is a fix provided by Samba.

It is only a matter of time till some technical issue kills the distro for the average non technical user.

Not a happy state,

regards

Paul

Henk

Re: Samba Bug
« Reply #4 on: September 09, 2004, 10:45:41 PM »
Quote from: "pisaacs"
Hi,
Since no one more knowledgable has replied, here is what I have done -

wget http://us2.samba.org/samba/ftp/Binary_Packages/RedHat/RPMS/i386/7.3/samba-2.2.11-1.i386.rpm
wget http://mirror.contribs.org/smeserver/contribs/rvandenaker/beta/e-smith-cups/SME_6.0/cups-libs-1.1.19-8smea1.i386.rpm
wget http://mirror.contribs.org/smeserver/contribs/rvandenaker/beta/e-smith-cups/SME_6.0/libtiff-3.5.7-2.i386.rpm
rpm -Uvh *.rpm
/sbin/e-smith/expand-template /etc/smb.conf
service smb restart

It appears to be running fine.

regards

Paul


After a reboot of the server samba has to be restarted manual when updated the way you did.

guest22

Samba Bug
« Reply #5 on: September 10, 2004, 05:36:28 PM »
SME Server is _not_ dead. It just takes a lot of people and time to get things going and updated. So please subscribe yourself to 1 of the teams and make sure yourself that it's not 'dead'.

If you think you have found a bug and discussed it here then please report it to the bugtracker once it has been confirmed. That's the proper process. ONLY bugtracker entries will be addressed to in upcomming updates/releases. That's why this forum exists.

contribs.org does care....

Thanks,
RequestedDeletion

Henk

Samba Bug
« Reply #6 on: September 12, 2004, 11:59:09 PM »
I've reported this bug just a minute ago.

Maybe handy to know. I've tried the upgrade to the Samba 3.0 Beta contrib. Didn't work the right way. Within a couple of minutes the smb process took 95% processor time and the server became very slow.

With Samba 2 the server almost crashed and went out of memory.

Both only happens after a domain login with Windows XP Pro SP2. I don't have problems using shares with Win XP Home SP2

Quadrax

Samba Bug
« Reply #7 on: September 20, 2004, 08:53:27 PM »
Sorry, just a "signet" to follow/refound this subject easyly.

Offline gzartman

  • *
  • 306
  • +0/-0
    • LEI Engineering & Surveying
Re: Samba Bug
« Reply #8 on: September 28, 2004, 07:52:53 PM »
Quote from: "pisaacs"
Hi,
Since no one more knowledgable has replied, here is what I have done -

wget http://us2.samba.org/samba/ftp/Binary_Packages/RedHat/RPMS/i386/7.3/samba-2.2.11-1.i386.rpm
wget http://mirror.contribs.org/smeserver/contribs/rvandenaker/beta/e-smith-cups/SME_6.0/cups-libs-1.1.19-8smea1.i386.rpm
wget http://mirror.contribs.org/smeserver/contribs/rvandenaker/beta/e-smith-cups/SME_6.0/libtiff-3.5.7-2.i386.rpm
rpm -Uvh *.rpm
/sbin/e-smith/expand-template /etc/smb.conf
service smb restart
It appears to be running fine.
regards
Paul


I'd HIGHLY recommend against upgrading SME to this RPMS.  They are not "Redhat" builds of Samba, but Samba Team builds.  They will run on SME, don't get me wrong, but they are built much differently than the stock Redhat versions.  This could cause issues with future upgrades.  AFAIK, no one has yet to rebuilt 2.2.11 for SME 6.0.1.

Regards,

Greg Zartman
----
Greg J. Zartman
LEI Engineering & Surveying

SME user and community member since 2000.

harkete

Samba Bug
« Reply #9 on: October 01, 2004, 10:37:36 AM »
Hi,

(first post in this forum).

I've installed the rpm's as mentioned here. (http://us2.samba.org/samba/ftp/Binary_Packages/RedHat/RPMS/i386/7.3/samba-2.2.11-1.i386.rpm and others.)

Everything seemed to work fine at first. Domain logons working etc... But suddenly both the smbd and nmbd processes stopped working (as they're both running under supervise they're restarting constantly ... producing enormous logfiles.).

I've checked my logfiles and this is what is see:

(in var/log/samba/log.nmbd):

----------------------------------------------------
[2004/10/01 10:29:08, 0] nmbd/nmbd.c:main(784)
  Incorrect program usage - is the command line correct?
----------------------------------------------------

(in var/log/smbd/currect):

----------------------------------------------------
@40000000415d15892d8b3bac /usr/sbin/smbd: invalid option -- F
@40000000415d15892d8fa0ac Usage: /usr/sbin/smbd [-DaioPh?V] [-d debuglevel] [-l log basename] [-p port]
@40000000415d15892d8fac64        [-O socket options] [-s services file]
@40000000415d15892d8fb434       -D                    Become a daemon (default)
@40000000415d15892d8fb81c       -a                    Append to log file (default)
@40000000415d15892d8fbfec       -i                    Run interactive (not a daemon)
@40000000415d15892d8fc7bc       -o                    Overwrite log file, don't append
@40000000415d15892d8fcba4       -h                    Print usage
@40000000415d15892d902194       -?                    Print usage
@40000000415d15892d902964       -V                    Print version
@40000000415d15892d902d4c       -d debuglevel         Set the debuglevel
@40000000415d15892d90351c       -l log basename.      Basename for log/debug files
@40000000415d15892d903904       -p port               Listen on the specified port
@40000000415d15892d9040d4       -O socket options     Socket options
@40000000415d15892d9044bc       -s services file.     Filename of services file
--------------------------------------------------

(in var/log/nmbd/current):

--------------------------------------------------
@40000000415d127516f5673c /usr/sbin/nmbd: invalid option -- F
@40000000415d127516f572f4 Usage: /usr/sbin/nmbd [-DaiohV] [-H lmhosts file] [-d debuglevel] [-l log basename]
@40000000415d127516f57ac4        [-n name] [-p port] [-s configuration file]
@40000000415d127516f58294       -D                    Become a daemon (default)
@40000000415d127516f5867c       -a                    Append to log file (default)
@40000000415d127516f58e4c       -i                    Run interactive (not a daemon)
@40000000415d127516f5961c       -o                    Overwrite log file, don't append
@40000000415d127516f5eff4       -h                    Print usage
@40000000415d127516f5fbac       -V                    Print version
@40000000415d127516f5ff94       -H hosts file         Load a netbios hosts file
@40000000415d127516f60764       -d debuglevel         Set the debuglevel
@40000000415d127516f60b4c       -l log basename.      Basename for log/debug files
@40000000415d127516f6131c       -n netbiosname.       Primary netbios name
@40000000415d127516f61704       -p port               Listen on the specified port
@40000000415d127516f63644       -s configuration file Configuration file name
@40000000415d127516f63e14
--------------------------------------------------


So apparently - atleast for someone with litte experience - someone is trying to start the both the processes with a parameter "-F" which is not supported (anymore?).

Could anyone here please give a hint on how to get rid of this annoying problem? Is it possible to rollback the samba-2.2.11 release? I installed it due to the fact that WinXPSP2 clients could not log in, but later found out that it was due to the SignOrSeal registry stuff.

I would be enormously grateful for some help!

Tia
/Erik Janouch

Some further investigation showed the following:

Apparently the samba-2.2.11 relasse for Redhat 7.3 doesn't include the patch (patch-2.2.11-2.2.12.diffs.gz) needed for nmbd/smbd running under supervise. That's why the parameters "-S -F" fail when supervise want's to start nmbd/smbd.

I do not know how to compile a rpm with the diff-patch included (and I assume it is impossible on sme-server because it's lacking libtool... etc). Is there anyone out there able to provide a compiled rpm including this patch?

Or did I get everything wrong somehow?

Still looking for help!!!

Tia
/Erik Janouch

Offline gregswallow

  • *
  • 651
  • +1/-0
Samba Bug
« Reply #10 on: October 01, 2004, 11:27:50 PM »
http://us1.samba.org/samba/ftp/Binary_Packages/RedHat/RPMS/i386/7.3/samba-2.2.12-1_rh73.i386.rpm

who will be the first to try it...If you have any success, post your comments here.

Greg

harkete

Samba Bug
« Reply #11 on: October 02, 2004, 01:06:35 AM »
Quote from: "gregswallow"
http://us1.samba.org/samba/ftp/Binary_Packages/RedHat/RPMS/i386/7.3/samba-2.2.12-1_rh73.i386.rpm

who will be the first to try it...If you have any success, post your comments here.

Greg


That's essentially what I did. Without success (with samba-2.2.11). It worked fine until I restarted the box. Then it broke in the way describe in my previous post. Due to the fact (I think) that it lacks the support of "nmbd/smbd -F -S" parameters (to be able to run in supervise mode).

/Erik

Offline gregswallow

  • *
  • 651
  • +1/-0
Samba Bug
« Reply #12 on: October 02, 2004, 01:40:44 AM »
I assumed when you wrote...
Quote from: "harkete"

Apparently the samba-2.2.11 relasse for Redhat 7.3 doesn't include the patch (patch-2.2.11-2.2.12.diffs.gz) needed for nmbd/smbd running under supervise. That's why the parameters "-S -F" fail when supervise want's to start nmbd/smbd.

...that the 2.2.12 realease fixed the problem.  

Greg

harkete

Samba Bug
« Reply #13 on: October 02, 2004, 11:09:00 AM »
Quote from: "gregswallow"
I assumed when you wrote...
Quote from: "harkete"

Apparently the samba-2.2.11 relasse for Redhat 7.3 doesn't include the patch (patch-2.2.11-2.2.12.diffs.gz) needed for nmbd/smbd running under supervise. That's why the parameters "-S -F" fail when supervise want's to start nmbd/smbd.

...that the 2.2.12 realease fixed the problem.  I will try it on a test box when I have time anyways.

Greg


I've just installed the release samba-2.2.12-1_rh7.i386.rpm. Just after installation and the necessary expand-template and smb restart everything works fine. But after reboot, something goes wrong. I haven't quite figured out who's to blame - and I certainly hope someone here can give me a clue - but I atleast know how to temporarily fix the problem.

I do:

service smnb stop
service nmbd stop
service smb stop

Then I kill all the nmbd/smnb processes still running. Normally I have like 20 or so.

Then

service smb start

And now everything is working fine again [as far as I can understand.]. So it seems that somewhere in the 7.d runlevel scripts there's some kind of conflict as to whom is to run the smnb and nmbd processes. It can't be so hard to fix. Just a matter of finding out where.

Gratefully waiting for clarifications.

Tia
/Erik