[Samba] More Random Behaviour
Okay, I'm starting to face professional ridicule at work over this. A Samba install should take a couple of days, I've been at it... far to long now. When this started I chased the problem in all the wrong directions. I thought it was this environment. Now I don't think so. I have Samba 3.0.14a installed on an AIX 5.2 server. I had it running (not the way I wanted, but running). Then, for no reason, and with NO changes made, it started to deny me access to my home directory. FOR NO REASON. I had not changed anything. I've been fighting just that kind of random failures for the past couple of weeks. The logs are pretty much usless. Even at log level 10, it only shows that it denied access, and gives idiot reasons like user not found or some such. I'm now down-reving to 3.0.12 . I've installed that version in other places with good result, I'm hoping it will correct the issues here. I can't go up-rev to 3.0.20 because the build fails (unless someone has a solution for THAT problem...). Maybe it will also magically correct the other authentication issues that I shouldn't be having too.. -Ric -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
On Thu, Sep 29, 2005 at 08:47:34AM -0600, Ric Tibbetts wrote: Okay, I'm starting to face professional ridicule at work over this. A Samba install should take a couple of days, I've been at it... far to long now. When this started I chased the problem in all the wrong directions. I thought it was this environment. Now I don't think so. I have Samba 3.0.14a installed on an AIX 5.2 server. I had it running (not the way I wanted, but running). Then, for no reason, and with NO changes made, it started to deny me access to my home directory. FOR NO REASON. I had not changed anything. There is *nover* NO REASON. Something changed. You just don't know what. I've been fighting just that kind of random failures for the past couple of weeks. The logs are pretty much usless. Even at log level 10, it only shows that it denied access, and gives idiot reasons like user not found or some such. If you're ignoring messages like this, then you will fail. You need to take a long hard look at your system administration practices in order to be successful in this. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
At 10:16 AM 9/29/2005, Jeremy Allison wrote: On Thu, Sep 29, 2005 at 08:47:34AM -0600, Ric Tibbetts wrote: Okay, I'm starting to face professional ridicule at work over this. A Samba install should take a couple of days, I've been at it... far to long now. When this started I chased the problem in all the wrong directions. I thought it was this environment. Now I don't think so. I have Samba 3.0.14a installed on an AIX 5.2 server. I had it running (not the way I wanted, but running). Then, for no reason, and with NO changes made, it started to deny me access to my home directory. FOR NO REASON. I had not changed anything. There is *nover* NO REASON. Something changed. You just don't know what. Okay, I'll phrase that another way: I would agree with you, however: I changed nothing in the Samba setup, or configuration. No one else was logged into the server. Hence: There were no changes to the Samba server. It simply, sporadically, stopped allowing me access to my home directory. You can draw your own conclusions from that. I've been fighting just that kind of random failures for the past couple of weeks. The logs are pretty much usless. Even at log level 10, it only shows that it denied access, and gives idiot reasons like user not found or some such. If you're ignoring messages like this, then you will fail. You need to take a long hard look at your system administration practices in order to be successful in this. Once again. It was allowing me access, and then, suddenly, it stopped, and would report a variety of causes, ranging from: No NT servers available User not found bad passwords etc. These events have been random, and there seems to be no direct cause. If the user exists in both the Unix passwd scheme, AND as an smbpasswd entry, there's no reason Samba should suddenly not be able to find it. I've just down-reved form 3.0.14a to 3.0.12, and so far, it's running fine (except for a problem with smbpasswd, but I'll address that seperately). -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
On Thu, Sep 29, 2005 at 10:29:26AM -0600, Ric Tibbetts wrote: These events have been random, and there seems to be no direct cause. If the user exists in both the Unix passwd scheme, AND as an smbpasswd entry, there's no reason Samba should suddenly not be able to find it. Indeed, and that's why you need to look for other sources of instability on the system. The code doesn't just randomly fail. You need to understand what is going on. Blindly down-revving is a receipe for disaster. The format of many internal tdb databases are changed when up-reving. Unless you saved them off and restored them you're likely to run into more trouble. You need to understand your system a *lot* better than you currently do. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
- Original Message - From: Ric Tibbetts [EMAIL PROTECTED] To: Jeremy Allison [EMAIL PROTECTED] Cc: samba@lists.samba.org Sent: Thursday, September 29, 2005 12:29 PM Subject: Re: [Samba] More Random Behaviour At 10:16 AM 9/29/2005, Jeremy Allison wrote: On Thu, Sep 29, 2005 at 08:47:34AM -0600, Ric Tibbetts wrote: Okay, I'm starting to face professional ridicule at work over this. A Samba install should take a couple of days, I've been at it... far to long now. When this started I chased the problem in all the wrong directions. I thought it was this environment. Now I don't think so. I have Samba 3.0.14a installed on an AIX 5.2 server. I had it running (not the way I wanted, but running). Then, for no reason, and with NO changes made, it started to deny me access to my home directory. FOR NO REASON. I had not changed anything. There is *nover* NO REASON. Something changed. You just don't know what. Okay, I'll phrase that another way: I would agree with you, however: I changed nothing in the Samba setup, or configuration. No one else was logged into the server. Hence: There were no changes to the Samba server. It simply, sporadically, stopped allowing me access to my home directory. You can draw your own conclusions from that. Can you tell me some info about your AIX box? model/cpu's/memory oslevel -r lslpp -l bos.net.* no -a ioo -a vmo -a do you run NFS and/or dhcpsd on this box? other network services? have you had to reboot ther server or restart samba to get the problem to go away? does errpt show SYSVMM out of network resources ? And I agree with Jeremy; software doesn't just stop working without a darn good reason...and it's usually the OS if you've truly changed nothing. Can you give load and timeframe information? Do you use local user (/etc/passwd) files or LDAP? We need LOTS of info for an issue like this Cheers, Bill I've been fighting just that kind of random failures for the past couple of weeks. The logs are pretty much usless. Even at log level 10, it only shows that it denied access, and gives idiot reasons like user not found or some such. If you're ignoring messages like this, then you will fail. You need to take a long hard look at your system administration practices in order to be successful in this. Once again. It was allowing me access, and then, suddenly, it stopped, and would report a variety of causes, ranging from: No NT servers available User not found bad passwords etc. These events have been random, and there seems to be no direct cause. If the user exists in both the Unix passwd scheme, AND as an smbpasswd entry, there's no reason Samba should suddenly not be able to find it. I've just down-reved form 3.0.14a to 3.0.12, and so far, it's running fine (except for a problem with smbpasswd, but I'll address that seperately). -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
At 10:32 AM 9/29/2005, Jeremy Allison wrote: On Thu, Sep 29, 2005 at 10:29:26AM -0600, Ric Tibbetts wrote: These events have been random, and there seems to be no direct cause. If the user exists in both the Unix passwd scheme, AND as an smbpasswd entry, there's no reason Samba should suddenly not be able to find it. Indeed, and that's why you need to look for other sources of instability on the system. The code doesn't just randomly fail. You need to understand what is going on. Blindly down-revving is a receipe for disaster. The format of many internal tdb databases are changed when up-reving. Unless you saved them off and restored them you're likely to run into more trouble. You need to understand your system a *lot* better than you currently do. Yes, I moved the tdb databases first. I didn't blindly down-rev anything, I actually am trying to it right, and make it work. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
A few random possible causes for no reason failures: - a config file was changed some time ago but someone failed to test it by restarting the daemon or rebooting the server, until now -some server is having network connectivity or load issues, and the backup or secondary doesn't have the same information -some third party changed permissions somewhere that wasn't immediately apparent -your server is having connectivity or load or file system space issues (don't forget to check the space where the error log goes) -your config file has cruft in it from many versions ago that no longer applies to this particular version (that bit me yesterday on my AV scanner!) Seriously, turn your log level down to something sane and make sure that you understand any error that you see. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
At 12:29 PM 9/29/2005, Elizabeth Schwartz wrote: A few random possible causes for no reason failures: - a config file was changed some time ago but someone failed to test it by restarting the daemon or rebooting the server, until now -some server is having network connectivity or load issues, and the backup or secondary doesn't have the same information -some third party changed permissions somewhere that wasn't immediately apparent -your server is having connectivity or load or file system space issues (don't forget to check the space where the error log goes) -your config file has cruft in it from many versions ago that no longer applies to this particular version (that bit me yesterday on my AV scanner!) Seriously, turn your log level down to something sane and make sure that you understand any error that you see. Thank you for the pointers. A couple of them have serious validity in this environment. For the moment, I've down-reved to 3.0.12, and the stability issue seems to have subsided. There could be many reasons for that, but for the moment I'm taking advantage of the calm, and using the time to work the authentication issue. Once that is resolved, or at least better understood by me, I'll look at moving the version back up if necessary. -Ric -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
On Friday 30 September 2005 00:16, Jeremy Allison wrote: On Thu, Sep 29, 2005 at 08:47:34AM -0600, Ric Tibbetts wrote: Then, for no reason, and with NO changes made, it started to deny me access to my home directory. FOR NO REASON. I had not changed anything. There is *nover* NO REASON. Something changed. You just don't know what. Have to agree. The on-going problem I face with one client's slow application happens to revolve around a switch from IPX to IP protocol for the fileshares, but they didn't mention that little detail for the first *three*days* I turned up on site. It appers that Win32 applications treat their native protocols differently, and botch it (small packets, no cacheing). Cheers; Leon -- http://cyberknights.com.au/ Modern tools; traditional dedication http://plug.linux.org.au/ Member, Perth Linux User Group http://slpwa.asn.au/Member, Linux Professionals WA http://osia.net.au/ Member, Open Source Industry Australia http://linux.org.au/Member, Linux Australia -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
On Friday 30 September 2005 00:29, Ric Tibbetts wrote: I changed nothing in the Samba setup, or configuration. No one else was logged into the server. Hence: There were no changes to the Samba server. What security software does the server run? Is there anything like Mandrake's MSec running regularly, which might correct the permissions on various things? Cheers; Leon -- http://cyberknights.com.au/ Modern tools; traditional dedication http://plug.linux.org.au/ Member, Perth Linux User Group http://slpwa.asn.au/Member, Linux Professionals WA http://osia.net.au/ Member, Open Source Industry Australia http://linux.org.au/Member, Linux Australia -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
