What's left for 3.0.21 final release?

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

What's left for 3.0.21 final release?

Gerald Carter-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Waiting for feedback.....





cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDehGUIR7qMdg1EfYRAiGPAKCN6o/ZrZV8t/cR6Oxwct9L5mJ2OwCff7l+
N6ZWJUjy1h2HbCOgGJbfSEE=
=/NZj
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

Jeremy Allison
On Tue, Nov 15, 2005 at 10:49:24AM -0600, Gerald (Jerry) Carter wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Waiting for feedback.....

Looks like the FreeBSD fixes for storing OS/2 EA's broke
the storing of DOS attributes in EA's on FreeBSD (gotta love
those guys.... :-). Probably needs fixing for FreeBSD before
release.

Jeremy.
Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

John H Terpstra - Samba Team
In reply to this post by Gerald Carter-4
On Tuesday 15 November 2005 09:49, Gerald (Jerry) Carter wrote:
> Waiting for feedback.....

Many sites use the NT4 Domain User Manager to manage Samba-3. Given that fact,
and some minor glitches I have not yet eliminated in my test environments it
may be wise to alert users of potential issues.

Have you done a fresh (clean-slate) install of 3.0.21 and then tried using NT4
Domain User Manager with tdbsam and ldapsam backends?

I have observed the following only with NT4 Domain User Manager. Use of the
'net' command appears to function OK.

I do not have time to check this out further right now, and can appreciate
that you may not have the time either. The errors may well be configuration
errors on my part - I have not had time to pursue this. For all I know, the
patches over the past week may have already fixed these issues - if they were
real issues in the first place.

I know how much you dislike defective reports so will not file a bug report
until I have incontrovertable proof of a problem. The following is intended
purely in response to your request for feedback.

Last weeks errors:

        1. Managment of user rights

                Open the panel to manage user rights, then just commit without making
                any change. Error message said that removel of the local Administrator
                account is not permitted.

        2. Creation/change of local groups crashes smbd. Deletion of a local group
                works OK.

        3. Change of global group contents may result in a spurious error message.
                The change actually works fine.

        4. If only some of the Account controls are set in LDAP, an attempt to change
                Account lock-out settings may crash smbd. Each such crash requires a
                reboot of the Windows workstation before NT4 Domain User Manager
                could be used again. The sad thing is that not every attempt to set these
                parameters would crash smbd. I was not able to find a means to consistently
                reproduce the problem.

If you do not have time to delve into this, a note in the WHATSNEW.txt file
alerting people to a potential issue may be advisable. Perhaps we could say
something like: "There are reports that of the NT4 Domain User Manager may be
problematic with 3.0.21 - we want feedback if any difficulties are
experienced."

- John T.
Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

Jeremy Allison
On Tue, Nov 15, 2005 at 10:52:14AM -0700, John H Terpstra wrote:

>
> I know how much you dislike defective reports so will not file a bug report
> until I have incontrovertable proof of a problem. The following is intended
> purely in response to your request for feedback.
>
> Last weeks errors:
>
> 1. Managment of user rights
>
> Open the panel to manage user rights, then just commit without making
> any change. Error message said that removel of the local Administrator
> account is not permitted.
>
> 2. Creation/change of local groups crashes smbd. Deletion of a local group
> works OK.

ARRRRRRRGGGGGHHHHHH !!!!!!!!!!!!!!

THERE IS NO EXCUSE FOR NOT FILING A BUG REPORT ON THIS !!!!

*You* of all people MUST be running with "panic action = /bin/sleep 999999999"

NO SAMBA TEAM MEMBER SHOULD BE RUNNING WITHOUT THAT !!!!

That way *any* crash leaves a stuck process you can debug with gdb.

THERE IS NEVER AN EXCUSE FOR NOT REPORTING A CRASH BUG.

Jeremy.
Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

Thomas Bork-2
In reply to this post by Gerald Carter-4
Gerald (Jerry) Carter wrote:

> Waiting for feedback.....

A bugfix for

https://bugzilla.samba.org/show_bug.cgi?id=3124

would be nice ;)


der tom

Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

Jeremy Allison
On Tue, Nov 15, 2005 at 08:04:16PM +0100, Thomas Bork wrote:
> Gerald (Jerry) Carter wrote:
>
> >Waiting for feedback.....
>
> A bugfix for
>
> https://bugzilla.samba.org/show_bug.cgi?id=3124
>
> would be nice ;)

Isn't this a problem with timestamp granularity ? Isn't this
one we can't fix ?

Jeremy.
Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

Thomas Bork-2
Jeremy Allison wrote:

>>A bugfix for
>>https://bugzilla.samba.org/show_bug.cgi?id=3124
>>would be nice ;)
> Isn't this a problem with timestamp granularity ? Isn't this
> one we can't fix ?

I don't know the real reason for this bug but hope it is possible to fix
this.
A log with level 10 is attched to the bugzilla entry.

der tom
Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

Volker Lendecke
In reply to this post by Jeremy Allison
On Tue, Nov 15, 2005 at 09:55:52AM -0800, Jeremy Allison wrote:
> *You* of all people MUST be running with "panic action = /bin/sleep 999999999"

Serious question: What about

Index: param/loadparm.c
===================================================================
--- param/loadparm.c    (Revision 11734)
+++ param/loadparm.c    (Arbeitskopie)
@@ -1424,6 +1424,9 @@
        slprintf(s, sizeof(s) - 1, "%d.%d", DEFAULT_MAJOR_VERSION,
                 DEFAULT_MINOR_VERSION);
        string_set(&Globals.szAnnounceVersion, s);
+#ifdef DEVELOPER
+       string_set(&Globals.szPanicAction, "/bin/sleep 999999999");
+#endif
 
        pstrcpy(user_socket_options, DEFAULT_SOCKET_OPTIONS);
 
Volker

attachment0 (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

Gerald Carter-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Volker Lendecke wrote:

> On Tue, Nov 15, 2005 at 09:55:52AM -0800, Jeremy Allison wrote:
>> *You* of all people MUST be running with "panic action = /bin/sleep 999999999"
>
> Serious question: What about
>
> Index: param/loadparm.c
> ===================================================================
> --- param/loadparm.c    (Revision 11734)
> +++ param/loadparm.c    (Arbeitskopie)
> @@ -1424,6 +1424,9 @@
>         slprintf(s, sizeof(s) - 1, "%d.%d", DEFAULT_MAJOR_VERSION,
>                  DEFAULT_MINOR_VERSION);
>         string_set(&Globals.szAnnounceVersion, s);
> +#ifdef DEVELOPER
> +       string_set(&Globals.szPanicAction, "/bin/sleep 999999999");
> +#endif
>  
>         pstrcpy(user_socket_options, DEFAULT_SOCKET_OPTIONS);

Fine by me.





jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDekPtIR7qMdg1EfYRAuK6AKCrAkd5pa6CMioDcAEsQ1SrZtHcXgCfd1S4
vB1E4vJHPX8Hgu8Ai1NcNnk=
=mBHT
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

Jeremy Allison
In reply to this post by Volker Lendecke
On Tue, Nov 15, 2005 at 09:21:43PM +0100, Volker Lendecke wrote:

> On Tue, Nov 15, 2005 at 09:55:52AM -0800, Jeremy Allison wrote:
> > *You* of all people MUST be running with "panic action = /bin/sleep 999999999"
>
> Serious question: What about
>
> Index: param/loadparm.c
> ===================================================================
> --- param/loadparm.c    (Revision 11734)
> +++ param/loadparm.c    (Arbeitskopie)
> @@ -1424,6 +1424,9 @@
>         slprintf(s, sizeof(s) - 1, "%d.%d", DEFAULT_MAJOR_VERSION,
>                  DEFAULT_MINOR_VERSION);
>         string_set(&Globals.szAnnounceVersion, s);
> +#ifdef DEVELOPER
> +       string_set(&Globals.szPanicAction, "/bin/sleep 999999999");
> +#endif
>  
>         pstrcpy(user_socket_options, DEFAULT_SOCKET_OPTIONS);

Ship it ! :-).
Reply | Threaded
Open this post in threaded view
|

Re: What's left for 3.0.21 final release?

hideo takeuchi
In reply to this post by Gerald Carter-4
> Waiting for feedback.....

The problem is talking about a trusted AD domains on a Samba DC.
Use Samba Version: samba-3.0.21pre1、samba-3.0.21rc1

example:
  AD server name TAKEHIDE1
  AD Domain name TAKEADS
  Samba PDC name SMB-ML21


For samba-3.0.14a:
  # wbinfo -u
   TAKEADS\administrator
   TAKEADS\agrex
   TAKEADS\guest
   TAKEADS\krbtgt
   TAKEADS\takeuchi1

  # wbinfo -m
   TAKEADS

  # wbinfo -t
   checking the trust secret via RPC calls failed
   error code was NT_STATUS_CANT_ACCESS_DOMAIN_INFO (0xc00000da)
   Could not check secret

after updating to samba-3.0.20pre1 and samba-3.0.21rc1:
  # wbinfo -u
   Error looking up domain users

  # wbinfo -m
   TAKEADS

  # wbinfo -t
   checking the trust secret via RPC calls failed
   error code was NT_STATUS_CANT_ACCESS_DOMAIN_INFO (0xc00000da)
   Could not check secret

Then we got the log file that did not exist in samba-3.0.14a was made.

  # /var/log/samba/takehide1.log

    [2005/11/16 09:54:23, 0] libsmb/credentials.c:creds_server_check(159)
     creds_server_check: credentials check failed.
    [2005/11/16 09:54:23, 0]
     rpc_server/srv_netlog_nt.c:_net_sam_logon(638)
     _net_sam_logon: creds_server_step failed. Rejecting auth request
     from client TAKEHIDE1 machine account TAKEADS$
    [2005/11/16 09:54:23, 2] auth/auth.c:check_ntlm_password(317)
     check_ntlm_password:  Authentication for user [SMB-ML21$] ->
     [SMB-ML21$] FAILED with error NT_STATUS_NO_SUCH_USER


smb.conf:
[global]
         dos charset = CP932
         unix charset = EUCJP-MS
         display charset = EUCJP-MS
         workgroup = ML21TEST
         netbios name = SMB-ML21
         server string = %L : Samba %v on %h
         passdb backend = ldapsam
         guest account = Guest
         log file = /var/log/samba/%m.log
         log level = 0 auth:2
         max log size = 10000
         domain logons = Yes
         os level = 64
         preferred master = Yes
         domain master = Yes
         dns proxy = No
         local master = Yes
         wins support = Yes
         ldap suffix = dc=ml21,dc=com
         ldap machine suffix = ou=Computers
         ldap user suffix = ou=Users
         ldap group suffix = ou=Groups
         ldap admin dn = uid=Administrator,ou=Users,dc=ml21,dc=com
         ldap passwd sync = Yes
         admin users = Administrator
         printing = lprng
         dos filemode = Yes
         dos filetimes = Yes
         dos filetime resolution = Yes

         idmap uid = 10000-20000
         idmap gid = 20001-30000
         ldap idmap suffix = ou=Idmap
         idmap backend = ldap:ldap://localhost

         inherit acls = Yes
         logon path =
         logon home =

Best Regards,