View Single Post
  #3  
Old 12-02-2018, 11:29 AM
edwardcoast is offline
Guest
 
Join Date: Jan 2014
Posts: 1,143
Quote:
Originally Posted by Melbourne View Post
Don't assume that it is a permission problem just because the computer tells you so.

Computer systems are given only a limited number of ways that they can report failure, and frequently the reporting layer doesn't actually know the cause of the functional error.

In your case, the directory move operation failed: all the interface knows is that it failed: it gives you a chance to try again as a different user.

I don't know what is causing the problem, but since you suggest that it is inconsistent, possibilities to consider are (a) the MAC is making the folder the 'active' folder before trying to change it, (b) you are having trouble creating the hidden files used by the Mac (c) you are connecting with a protocol other than the one you think you are (ftp, nfs afp).
I'm not assuming anything at this point. I know from experience with Samba things like this relate to permissions and authentication for logins. But whatever those problems were, it was usually it worked or not. This doesn't seem to follow a real pattern. Some folders in a directory won't let you rename them, while others do. One thing is constant, when this does occur, it stays that way even if I restart Samba. The only work around has been to login through the shell and do things there.

For now, I have placed this in the smb.conf file:
Quote:
#log level = 3 auth_audit:3 auth_json_audit:3
Note that it is commented. This generates a lot of data for the log files. So next time this unexplained behavior occurs I'm going to uncomment this line, restart Samba and repeat the action. Then examine the logs to see if I can get more clues as to what is going on. Even if it were an error message or warning that said something like "Can't establish foobaz on myfile" I would at least have something to research further.

The protocol is SMB. I have even removed the Mac's hidden files in the directory/folder and that doesn't stop this odd behavior. I would describe this Samba share environment as simple. I do know that adding the
Quote:
ntlm auth = yes
to the smb.conf was needed for support an older Windows 7 system. But my research has not turned up that the Mac cares about ntlm.

It could be the "active" directory issue you describe, but what is causing the events to behave abnormally is the mystery.

I've never really had to dig into the higher level Samba logs before, so this will be a learning experience.