Не стартует самба и винбинд

По второй статье вроде сервер зашел в домене. Но теперь у меня не стартует samba.

Вот что выводит по команде testparm:

Про rlimit_max прочитал. Сделал. Все равно пишет про него. Да и наверное есть другие ошибки. Просто помогите разобраться как ввести машину в домен правильно и чтобы шары могли работать. Давайте придерживаться первой статьи, т.к. про sssd совсем ничего не знаю.

В лог самба что пишет?

Про rlimit_max прочитал. Сделал. Все равно пишет про него.

Что прочитали/сделали? Если у вас systemd, то надо редактировать /etc/systemd/system.conf, а не /etc/security/limits.conf.

В лог вот что пишет, сейчас запустил.

Про rlimit_max делал именно в /etc/security/limits.conf. Можно на время командой ulimit -n 16384.

create_local_token failed: NT_STATUS_NO_MEMORY
ERROR: failed to setup guest info.

Такая ошибка бывает, если запустить самбу до winbind. Если у тебя в конфиге есть security = ADS, то запуск winbind обязателен.

Парадоксально, вывел из домена и все заработало. (((

Наверное нужно что то прописать в самбе для домена конкретное.

Может есть у кого готовая своя конфигурация самбы под домен?

Советуйте что нибудь, буду проверять и тыкаться. ))

Testparm: «rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)»

Classic

List

Threaded

Testparm: «rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)»

I just installed samba on a new server, 3.4.5-42, 64 bit version from
Sernet, over CentOS 5.4.

When running testparm, I get the following warning:

rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)

I searched Google for some answer but I couldn’t find a satisfactory
one. What should I do to solve this?
Can someone from the Samba team enlighten me on this?

—
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba

Re: Testparm: «rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)»

Hi, I am not from the samba team but I stepped into the same situation:

you have to set the ulimit -n to the windows limit
» ulimit -n 16384 »
(Max open files)

That is valid for the console you are in

regards
—
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba

Re: Testparm: «rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)»

It’s a warning, you can safely ignore it. Windows 7 clients need to
have exactly the same number of open handles available as Windows
servers, else it fails in some file copy situations with a «out of
handles» message. Samba has taken care of it for you, but it’s just
letting you know your fd limit is set a bit low.

Jeremy
—
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba

Re: Testparm: «rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)» — SOLVED

> I just installed samba on a new server, 3.4.5-42, 64 bit version from
> Sernet, over CentOS 5.4.
>
> When running testparm, I get the following warning:
>
> rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)
>

In order to make the necessary change permanent, I entered the following
line in «/etc/security/limits.conf»:

The warning previously given by «testparm» is now gone.

From «limits.conf»‘s header:

— the wildcard *, for default entry
— nofile — max number of open files

Thanks to those who answered my question.

—
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba

Re: Testparm: «rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)»

Jeremy Allison wrote:
> On Mon, Jan 25, 2010 at 11:44:03AM +0000, Miguel Medalha wrote:

>> rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)
>>
>> I searched Google for some answer but I couldn’t find a satisfactory
>> one. What should I do to solve this?
[. ]
> It’s a warning, you can safely ignore it. Windows 7 clients need to
> have exactly the same number of open handles available as Windows
> servers, else it fails in some file copy situations with a «out of
> handles» message. Samba has taken care of it for you, but it’s just
> letting you know your fd limit is set a bit low.

Uninformed reaction: is it useful to let the user know? Does setting
the fd limit higher result in better behavior, or does the automatic
increase have results that would be counterintuitive if not mentioned?

If the former, maybe the default rlimit_max should be increased
(on Debian squeeze it seems to be 1024 fwiw). If the latter, I think
the message should say

rlimit_max: rlimit_max (8192) increased to minimum Windows limit (16384)

to be more informative and sound less like a warning. Like this,
maybe (untested).

— 8
Signed-off-by: Jonathan Nieder
—
source3/param/loadparm.c | 4 ++—
1 files changed, 2 insertions(+), 2 deletions(-)

diff —git a/source3/param/loadparm.c b/source3/param/loadparm.c
index 2f68f00..bda20d8 100644
— a/source3/param/loadparm.c
+++ b/source3/param/loadparm.c
@@ -4898,7 +4898,7 @@ static int max_open_files(void)
#endif

Samba rlimit max windows

Anyone getting that error when running testparm on their samba.conf file?

How can it be resolved?

to your /etc/security/limits.conf file
and reboot.

It worked for me.

On my freshly installed 10.04 (Linux samba 2.6.32-22-server #33-Ubuntu SMP) with minimal packages,
adding «* — nofile 16384» to /etc/security/limits.conf
doesn’t change the testparm output after a reboot.

# testparm still returns: «rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)»

Even tried enabling/adding «session required pam_limits.so» to /etc/pam.d/su and reboot
Result of testparm is identical: «rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)»

Any suggestions how to correctly remove the rlimit_max warning?

to your /etc/security/limits.conf file
and reboot.

It worked for me.

It worked for me too! Thank you! 😛

I found this reference: http://lists.samba.org/archive/samba/2010-January/153331.html

On Mon, Jan 25, 2010 at 11:44:03AM +0000, Miguel Medalha wrote:
>
> I just installed samba on a new server, 3.4.5-42, 64 bit version from
> Sernet, over CentOS 5.4.
>
> When running testparm, I get the following warning:
>
> rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)
>
> I searched Google for some answer but I couldn’t find a satisfactory
> one. What should I do to solve this?
> Can someone from the Samba team enlighten me on this?

It’s a warning, you can safely ignore it. Windows 7 clients need to
have exactly the same number of open handles available as Windows
servers, else it fails in some file copy situations with a «out of
handles» message. Samba has taken care of it for you, but it’s just
letting you know your fd limit is set a bit low.

i have tried this and it did not work for me

It does not work for me either.
It is not ubuntu specific though, you can have the error on Centos 5:

and solaris as well:

Hi! I tried this issue but the problem is still present:

rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)

Please see post #13.

It’s not a problem that needs to be fixed.

This did not work for me either (new lucid install). I noticed that the * domain specification does not apply to root (according to the files). Basically, this worked for me:

* — nofile 16384
root — nofile 16384

to your /etc/security/limits.conf file
and reboot.

I really only needed the root line but include the * to be complete in providing a true *. Hope this helps,

The line
root — nofile 16384
worked for me, but I guess it’s because it was a server that I never log in to as an ordinary user — just root.
Otherwise, you may need the «* — nofile 16384» line, or more exactly, replace the «*» with the user running samba.

I did not have to reboot though, just logout and in again, then the warning was gone.
I have not yet tried to reboot the server, so I don’t know if this setting will survive a reboot — but it would be strange if not..

might not want to just blindly start changing config files, in general.

For this particular item, not sure if this has been addressed yet, but here’s a security reason for that setting of 1024

I found a solution in this site:

I have a slightly different, but probably related problem. testparn includes the output

rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)

I have not been able to get the command

testparm -s /etc/samba/smb.conf.master > /etc/samba/smb.conf

to update the smb.conf, however, I get permission denied, or some such. I think I would have to log in as root to make this work, so I just updated smb.conf with sudo gedit instead. That would have prevented the change from being done.

Anyone know how I can get testparm to output the new file, i.e. how i get teh permission to work.

In the meantime I’ll try your fix. Thanks.

I have a slightly different, but probably related problem. testparn includes the output

rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)

I have not been able to get the command

testparm -s /etc/samba/smb.conf.master > /etc/samba/smb.conf

to update the smb.conf, however, I get permission denied, or some such. I think I would have to log in as root to make this work, so I just updated smb.conf with sudo gedit instead. That would have prevented the change from being done.

Anyone know how I can get testparm to output the new file, i.e. how i get teh permission to work.

In the meantime I’ll try your fix. Thanks.

There is no *fix* — There is no error. This has been mentioned several times in this thread. The answer is: Leave it alone. This is meant as a notification only.

Yes, but the problem is that I get the same symptoms. I can’t see any other computers, Windows or Ubuntu, and they can’t see me. Without Samba I can at least see the windows machines.

The symptoms you are referring to are not related in any way to the subject of: rlimit_max (1024) below minimum Windows limit (16384). They are best resolved in the other thread you started.

It worked for me too! Thank you! 😛

I found this reference: http://lists.samba.org/archive/samba/2010-January/153331.html

Samba version: samba3x-3.5.4-0.70.el5_6.1

This thread simply will not die.

There is no *fix* — There is no error. This has been mentioned several times in this thread. The answer is: Leave it alone. This is meant as a notification only.

There is no *fix* — There is no error. This has been mentioned several times in this thread. The answer is: Leave it alone. This is meant as a notification only.

Sort of. The message per se is not an error, but can lead to one. I manage a small network with 100+ users, and once in a while I hit the limit and some clients gets errors when trying to connect to a service.

Or, in other words, you will get an error when samba hit the limit.

copypast from:
http://how-it.ru/public/root/110-samba__preduprezhdenie__rlimit_max__rlimit_max__10 24__below_minimum_windows_limit__16384__.html

to your /etc/security/limits.conf file
and reboot.

Didn’t work for me as well
My installation is fresh Ubuntu 12.04 with samba 3.6.3

On Mon, Jan 25, 2010 at 11:44:03AM +0000, Miguel Medalha wrote:

>
> I just installed samba on a new server, 3.4.5-42, 64 bit version from
> Sernet, over CentOS 5.4.
>
> When running testparm, I get the following warning:
>
> rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)
>
> I searched Google for some answer but I couldn’t find a satisfactory
> one. What should I do to solve this?
> Can someone from the Samba team enlighten me on this?

It’s a warning, you can safely ignore it. Windows 7 clients need to
have exactly the same number of open handles available as Windows
servers, else it fails in some file copy situations with a «out of
handles» message. Samba has taken care of it for you, but it’s just
letting you know your fd limit is set a bit low.

Jeremy
It’s not an issue that needs to be fixed.

to your /etc/security/limits.conf file
and reboot.

It worked for me.

This worked for me as well thank you!

Note: the reboot isn’t necessary, just log out and log back in.

to your /etc/security/limits.conf file
and reboot.

It worked for me.

Also worked for me — thanks for the fix!

Still hasen’t changed from 4 years ago.

On Mon, Jan 25, 2010 at 11:44:03AM +0000, Miguel Medalha wrote:

>
> I just installed samba on a new server, 3.4.5-42, 64 bit version from
> Sernet, over CentOS 5.4.
>
> When running testparm, I get the following warning:
>
> rlimit_max: rlimit_max (8192) below minimum Windows limit (16384)
>
> I searched Google for some answer but I couldn’t find a satisfactory
> one. What should I do to solve this?
> Can someone from the Samba team enlighten me on this?

It’s a warning, you can safely ignore it. Windows 7 clients need to
have exactly the same number of open handles available as Windows
servers, else it fails in some file copy situations with a «out of
handles» message. Samba has taken care of it for you, but it’s just
letting you know your fd limit is set a bit low.

Jeremy is Jeremy Allison, one of the developers of Samba so you’d think his comments would carry some weight. I mean if he doesn’t know how it works then we should all start using NFS.