Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - MaverickZA

Pages: [1]
1
Hi All,

I am having the following issue with a Zentyal server running as an additional DC, the other domain controllers are Zentyal as well.

The issue started happening after we lost power at one of our sites, now the entyal DC comes up, however the samba and DNS module in the dashboard refuse to start, this is the output of the log - /var/log/zentyal/zentyal.log;

Quote
2013/09/23 15:09:31 INFO> Service.pm:949 EBox::Module::Service::restartService - Restarting service for module: samba
2013/09/23 15:09:32 WARN> LDB.pm:193 EBox::LDB::safeConnect - Could not connect to samba LDAP server: connect: Connection refused, retrying. (1 attempts)
2013/09/23 15:09:34 INFO> SysvolSync.pm:204 EBox::Samba::SysvolSync::run - Samba sysvol synchronizer script started
2013/09/23 15:09:42 WARN> LDB.pm:193 EBox::LDB::safeConnect - Could not connect to samba LDAP server: connect: Connection refused, retrying. (100 attempts)
2013/09/23 15:09:52 WARN> LDB.pm:193 EBox::LDB::safeConnect - Could not connect to samba LDAP server: connect: Connection refused, retrying. (200 attempts)
2013/09/23 15:10:02 WARN> LDB.pm:193 EBox::LDB::safeConnect - Could not connect to samba LDAP server: connect: Connection refused, retrying. (300 attempts)
2013/09/23 15:10:02 DEBUG> LDB.pm:197 EBox::LDB::safeConnect - FATAL: Could not connect to samba LDAP server: connect: Connection refused
2013/09/23 15:10:02 ERROR> Service.pm:954 EBox::Module::Service::__ANON__ - Error restarting service: FATAL: Could not connect to samba LDAP server: connect: Connection refused
2013/09/23 15:10:07 INFO> Service.pm:949 EBox::Module::Service::restartService - Restarting service for module: samba
2013/09/23 15:10:08 WARN> LDB.pm:193 EBox::LDB::safeConnect - Could not connect to samba LDAP server: connect: Connection refused, retrying. (1 attempts)
2013/09/23 15:10:09 INFO> SysvolSync.pm:204 EBox::Samba::SysvolSync::run - Samba sysvol synchronizer script started
2013/09/23 15:10:18 WARN> LDB.pm:193 EBox::LDB::safeConnect - Could not connect to samba LDAP server: connect: Connection refused, retrying. (100 attempts)
2013/09/23 15:10:28 WARN> LDB.pm:193 EBox::LDB::safeConnect - Could not connect to samba LDAP server: connect: Connection refused, retrying. (200 attempts)
2013/09/23 15:10:38 WARN> LDB.pm:193 EBox::LDB::safeConnect - Could not connect to samba LDAP server: connect: Connection refused, retrying. (300 attempts)
2013/09/23 15:10:38 DEBUG> LDB.pm:197 EBox::LDB::safeConnect - FATAL: Could not connect to samba LDAP server: connect: Connection refused
2013/09/23 15:10:38 ERROR> Service.pm:954 EBox::Module::Service::__ANON__ - Error restarting service: FATAL: Could not connect to samba LDAP server: connect: Connection refused

I have tried to start the services manually within the CLI but with no luck.

Any suggestions on how I can get this back up and running?

Thanks

2
Installation and Upgrades / Samba4 Crash Zentyal
« on: October 20, 2012, 12:48:54 pm »
Hi Guys,

I am having an issue with running Zentyal 3 as a PDC using Samba4 RC2.

Right now I am in a testing phase - I have 2 workstations on this domain with a few user accounts created using RSAT.

The problem is that the Samba4 daemon seems to be crashing randomly. The symptom is that the workstations are no longer able to authenticate, it just keeps coming back saying that the Username and Password you have entered is incorrect (Windows 7 workstations). After a restart of the File and Sharing service in the dashboard the workstations are able to authenticate again. I have looked through the logs and nothing stands out. When this happens, I have also tried to run a kinit to get a kerberos ticket on the Zentyal PDC but it just comes back saying that no KDC could be contacted in the realm, once I restart the samba4 service it works again.

I was hoping someone could point me in the right direction on what the issue is? The only unique aspect of the environment is that there is already an existing domain on the network. Could they possibly be conflicting or something? Which I actually doubt because the other domain controller is a Samba4 Alpha16 and that is still running fine.

Thanks for any help.

3
Hi,

I would like to stop Zentyal from sourcing traffic out as it's eth1 address before it gets to my internet router (I have a specific reason I need to do this).

Is there an iptables command or something in the GUI that will allow me to disable this?

Thanks for any help.

Pages: [1]