[ SOLVED ] Re: Samba failure message...

[Gilberto Ferreira]

Hi

I have Zentyal 4.0.5 work as Domain Controller and Proxy HTTP/HTTPS.
Everything goes fine, how ever, from time to time, Samba crash with the following message:


2015/01/12 08:30:13 DEBUG> Ldap.pm:219 EBox::Ldap::safeConnect - FATAL: Could not connect to the server: connect: Connection refused at FATAL: Could not connect to the server LDAP do samba: connect: Connection refused at /usr/share/perl5/EBox/Ldap.pm line 219
EBox::Ldap::safeConnect('EBox::Ldap=HASH(0x64c5ad0)') called at /usr/share/perl5/EBox/Ldap.pm line 173
EBox::Ldap::connection('EBox::Ldap=HASH(0x64c5ad0)') called at /usr/share/perl5/EBox/Ldap.pm line 507
EBox::Ldap::rootDse('EBox::Ldap=HASH(0x64c5ad0)') called at /usr/share/perl5/EBox/Samba/SetUidGidNumbers.pm line 39
EBox::Samba::SetUidGidNumbers::new('EBox::Samba::SetUidGidNumbers') called at /usr/share/perl5/EBox/Samba/SetUidGidNumbers.pm line 211
2015/01/12 01:55:57 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: Connection refused, retrying. (1 attempts)



Somebody experience similar problem?

I'll appreciate any kind of help... I do not know what can I do anymore...

Thanks

[jbahillo]

Hello: When such error happens check if samba is listening on por 389. If it is  not, then checking why it has stopped doing so is your next step

[Gilberto Ferreira]

We swap the hardware for a better one and this solve the problem!

Thanks

[Gilberto Ferreira]

Hi all...

I think the problem was solved by change the hardware, but no way!

I still get the error from Samba!


2015/01/12 08:30:13 DEBUG> Ldap.pm:219 EBox::Ldap::safeConnect - FATAL: Could not connect to the server: connect: Connection refused at FATAL: Could not connect to the server LDAP do samba: connect: Connection refused at /usr/share/perl5/EBox/Ldap.pm line 219
EBox::Ldap::safeConnect('EBox::Ldap=HASH(0x64c5ad0)') called at /usr/share/perl5/EBox/Ldap.pm line 173
EBox::Ldap::connection('EBox::Ldap=HASH(0x64c5ad0)') called at /usr/share/perl5/EBox/Ldap.pm line 507
EBox::Ldap::rootDse('EBox::Ldap=HASH(0x64c5ad0)') called at /usr/share/perl5/EBox/Samba/SetUidGidNumbers.pm line 39
EBox::Samba::SetUidGidNumbers::new('EBox::Samba::SetUidGidNumbers') called at /usr/share/perl5/EBox/Samba/SetUidGidNumbers.pm line 211
2015/01/12 01:55:57 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: Connection refused, retrying. (1 attempts)

Any help??

[jbahillo]

Hello Gilberto:

Have you tried, what I asked before?

[Gilberto Ferreira]

Hello Gilberto:

Have you tried, what I asked before?

Hello jbahilo

Sorry... I didn't that...

I will do in next time...

But do you have some glue why this happen???

I ran Zentyal in a VM and this VM I make backup every night... I thought backup is make VM stop in someway, so I disable the backup process... Even so, I get the error...

This is very bad, 'cause I need squid running here all the time...

Thanks for any kind of help...

Cheers

[jbahillo]

Hello:

As said, it looks like samba is not listening to 389 port (samba LDAP is not running) Nevertheless you should firstc onfirm this. Once confirmed, finding why this is happening should be the next step


Best regards

[Gilberto Ferreira]

Hi again

Doin' some debug in syslog, I get this error, in same time error on zentyal.log appears...

Jan 17 13:55:18 managerserver kernel: [365562.235093] init: zentyal.set-uid-gid-numbers main process (9615) killed by PIPE signal
Jan 17 13:55:18 managerserver kernel: [365562.235100] init: zentyal.set-uid-gid-numbers main process ended, respawning
Jan 17 13:55:49 managerserver kernel: [365593.090185] init: zentyal.set-uid-gid-numbers main process (12582) terminated with status 111
Jan 17 13:55:49 managerserver kernel: [365593.090192] init: zentyal.set-uid-gid-numbers main process ended, respawning
Jan 17 13:56:19 managerserver kernel: [365623.799002] init: zentyal.set-uid-gid-numbers main process (12877) terminated with status 111
Jan 17 13:56:19 managerserver kernel: [365623.799009] init: zentyal.set-uid-gid-numbers main process ended, respawning
Jan 17 13:56:50 managerserver kernel: [365654.517366] init: zentyal.set-uid-gid-numbers main process (13168) terminated with status 111
Jan 17 13:56:50 managerserver kernel: [365654.517373] init: zentyal.set-uid-gid-numbers main process ended, respawning
Jan 17 13:57:21 managerserver kernel: [365685.259877] init: zentyal.set-uid-gid-numbers main process (13465) terminated with status 111
Jan 17 13:57:21 managerserver kernel: [365685.259885] init: zentyal.set-uid-gid-numbers main process ended, respawning
Jan 17 13:57:52 managerserver kernel: [365716.034154] init: zentyal.set-uid-gid-numbers main process (13746) terminated with status 111
Jan 17 13:57:52 managerserver kernel: [365716.034161] init: zentyal.set-uid-gid-numbers main process ended, respawning



Is there something to do with samba error?? I meant, both error are related???

[jbahillo]

Hi:

This process is the reponsible of adding  rfc2307 attributes (uid, gid) to samba AD LDAP. I think that it might be related to this.

[Gilberto Ferreira]

Hi:

This process is the reponsible of adding  rfc2307 attributes (uid, gid) to samba AD LDAP. I think that it might be related to this.

Fine!.. So, perhaps this is the main problem, or, at least, related to... Am I right?
How can we work together to fix this??

Thanks a lot

[jbahillo]

Hello:

What about submiting a  bug on bugs.zentyal.org ?

[Gilberto Ferreira]

Hello:

What about submiting a  bug on bugs.zentyal.org ?

Done couple weeks ago:

 Bug #2849: Zentyal 4 + Samba issues

https://tracker.zentyal.org/issues/2849

[Gilberto Ferreira]

Hello

I saw an update to zentyal samba today...

Am I right to think that is something to do with this topic???

[jbahillo]

Hello Gilberto:

It looks like that  some of the fixed introduce here might affect you, yes:

https://github.com/Zentyal/zentyal/blob/master/main/samba/ChangeLog#L4-L14:

4.0.6
+ Remove deprecated sids-to-hide file and associated methods
+ Fixed sort order of EBox::Samba::users method
+ Adapted migration code from 3.2 to 4.0
+ Added waitForLDAPObject to EBox::Module::LDAP
+ Allow to manage Schema Admins group
+ Add 'drs:max object sync' parameter to avoid replication error
after loading schemas
+ Override smbd and nmbd daemons when migrating from 3.2
+ Increased default max log size to 100 MB
+ Backup and restore module's kerberos service password file

[Gilberto Ferreira]

Hello Gilberto:

It looks like that  some of the fixed introduce here might affect you, yes:

https://github.com/Zentyal/zentyal/blob/master/main/samba/ChangeLog#L4-L14:

4.0.6
+ Remove deprecated sids-to-hide file and associated methods
+ Fixed sort order of EBox::Samba::users method
+ Adapted migration code from 3.2 to 4.0
+ Added waitForLDAPObject to EBox::Module::LDAP
+ Allow to manage Schema Admins group
+ Add 'drs:max object sync' parameter to avoid replication error
after loading schemas
+ Override smbd and nmbd daemons when migrating from 3.2
+ Increased default max log size to 100 MB
+ Backup and restore module's kerberos service password file

Hello jbahillo

Nice to hear that...
I already apply the update... I'll see if no more trouble again... =)

Thanks a lot