[Samba] Upgrade 3.0.24-3.fc5 to 3.0.24-4.fc5 Anomaly

[Ken Smith]

As part of our deployment of FC updates we have upgraded our office 
server from 3.0.24-3 to 3.0.24.4. We got some strange results.

Shares that have the same name as the users home directory and/or the 
same name as their users id became inaccessible. For example, my user id 
is kens, my home directory is in /home/kens and there was a share of it 
called kens. There is also a common share accessed by ACL that became 
invisible. Win2K Explorer gave the message "Not accessible - path not 
found". WinXP gave similar results. There are other shares not related 
to user id's/directory names that appear to still work.

The SAMBA system is an NT4 style PDC and I was using local accounts with 
the right credentials on the Win boxes, which has always worked. The Win 
boxes are domain members.

To track this down I did the following

   1. Temporarily Changed permissions to 777 on my home directory &
      files - no difference
   2. Demoted the Samba machine to a member server to see if there was
      some home directory conflict and commented out the stanza in
      smb.conf that sets that up - no difference
   3. Disabled SELinux - no difference
   4. Created a share called "test" pointed to /home/test - it worked.
   5. Pointed the share called "test"  to my home directory - it worked
   6. Renamed the share called kens to kensxxx - that worked.
   7. On a separate FC6 machine, that has never run samba before, I set
      up a share called kens pointed to /home/kens. That worked
   8. Changed the share name of the ACL accessed common share. It worked
      too.

Conclusion - after an upgrade from 3.0.24-3 to 3.0.24.4, share names 
that previously were the same as the directory they pointed to can no 
longer have the same name.

THAT IS JUST PLAIN AWFUL!

I have renamed all the shares on the machine now and things are working 
again. But the number of things across the office network that relied on 
the share names beggars belief. Users E-mail profiles held on the server 
etc etc. A shambles.

The fact that a virgin installation of 3.0.24.4 does work (in the FC6 
test above) suggests that the history of the FC5 machine that has been 
upgraded from 3.0.24-3 has some significance in this situation.

It is interesting to note the following entries in the SAMBA part of 
logwatch from the FC5 machine the evening after this chaos. My guess of 
some of it comes from briefly running the machine as a member server.

--------------------- samba Begin ------------------------

 **Unmatched Entries**
 auth/auth_sam.c:check_sam_security(315)  Failed to modify entry. : 1 Time(s)
 nmbd/nmbd_browsesync.c:domain_master_node_status_fail(248)  domain_master_node_status_fail:  Doing a node status request to the domain master browser  for workgroup KENSNET at IP 172.16.0.4 failed.  Cannot sync browser lists. : 1 Time(s)
 nmbd/nmbd_incomingrequests.c:process_node_status_request(328)  process_node_status_request: status request for name KENSNET<1b> from IP 172.16.0.4 on subnet UNICAST_SUBNET - name not found. : 4 Time(s)
 param/loadparm.c:lp_do_parameter(3435)  WARNING: The "printer admin" option is deprecated : 21 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 7013 : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 7051 : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 719a : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 71f3 : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 725f : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 72bc : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 72cc : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 72d6 : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 731e : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 73be : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 75b9 : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 75d0 : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 760c : 1 Time(s)
 smbd/ipc.c:api_fd_reply(290)  api_fd_reply: INVALID PIPE HANDLE: 778c : 1 Time(s)
 smbd/service.c:make_connection_snum(849)  Can't become connected user! : 1 Time(s)
 
 ---------------------- samba End ------------------------- 


I know the formal procedure would be to run a test upgrade on another 
box. No all of us run such an environment and a 3.0.24-3 to -4 upgrade 
does suggest its pretty trivial. Not according to this experience.

If I can help with tracking this bug down please contact me

Ken












-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.