[Samba] Not enough storage space error
raghav at exzatechconsulting.com
Fri Aug 4 04:03:06 UTC 2017
Thanks for quick response.
We will monitor the memory usage and intimate you accordingly.
However, I doubt using the 4.7rc in this case. Also, creating a test
environment with 4.7rc, simulating the current process (Adding new
domain member PCs and users, reorganizing the Groups and OU) is very
difficult. Will definitely give it a try.
Thanks & Regards,
Do not print this e-mail unless required. Save Paper & trees.
On 04/08/17 8:44 AM, Andrew Bartlett wrote:
> On Fri, 2017-08-04 at 06:34 +0530, Anantha Raghava wrote:
>> Hello Andrew,
>> From the day one, we set the log level to 3. Log size is really huge.
>> However, I did not see some thing very interesting and related to
>> this error. It is all to do with user login, information, etc. Should
>> I have to increase the log level to get more info?
>> One thing we noticed. When we restart the samba-ad-dc service, it
>> allows us to add new users, add new computers to domain, and even
>> move the user from one OU to another. However, from last two days, at
>> around evening (around 4:45 PM), samba all of a sudden cuts off all
>> users from domain and even fails to list the domain controllers in
>> RSAT. If we restart samba-ad-dc, it starts working properly.
>> Now we need to see, what is that event that is causing this cut off
>> all of a sudden? Is it a shear coincidence? Or is it something to do
>> with the large number of PCs are now getting added from different
>> places? Incidentally, we use the same domain admin account (limited
>> administrator) to add PCs to domain. Is this causing some problem?
> Can you track the memory use of samba over time?
> You say elsewhere that there is plenty of RAM free, but is that still
> the case just before it blows up?
> Can you try Samba 4.7rc, where we made LDAP multi-process? That would
> keep any memory leak more isolated, which might help us find it.
> You can also look for some clues in the output of:
> smbcontrol $PID pool-usage
> It is very verbose, but careful analysis over time might give a clue
> where the memory is.
> Andrew Bartlett
>> Thanks & Regards,
>> Anantha Raghava
>> Do not print this e-mail unless required. Save Paper & trees.
>> On 03/08/17 8:09 AM, Andrew Bartlett wrote:
>>> On Wed, 2017-08-02 at 21:09 +0530, Anantha Raghava via samba wrote:
>>>> We are using Samba AD DC (Version 4.6.5) on CentOS 7.3. We have
>>>> servers with BIND9 DNS and all are working just fine.
>>>> Today, when we attempted to move couple of users from one OU to
>>>> Windows RSAT reported /*"Windows cannot move object. Ther*//*e
>>>> not enough storage space*//*"*/.
>>> I wouldn't take the error string literally. There are too many
>>> of mapping going on. LDAP does not contain such an error, so think
>>> it as a bad translation.
>>>> Our servers have 300 GB Storage more
>>>> that 270GB is free on the storage. At the moment we have added
>>>> 1000 users and about 450 computers into domain. Overall, we will
>>>> about 7500 users and equal no of computers to domain. I also
>>>> that RSAT lost the connection to domain all of a sudden. However,
>>>> when I
>>>> restarted the samba-ad-dc service, it reconnected. I am able to
>>>> computers and new users into domain. But moving the user from one
>>>> another is throwing above error.
>>>> I believe the DB is a 32 bit one and should support upto 4 GB.
>>>> checked in /usr/local/samba/private folder the size of smb.ldb
>>>> about 4.1 MB and rest of the ldb and tdb files are around 1 MB in
>>>> Now, how do I correctly check the current DB size? Is the above
>>>> strange behaviour? How do we fix the above error?
>>> Turn up the logging on the AD DC and see what the real error and
>>> string is.
>>> Andrew Bartlett
More information about the samba