Author Topic: [SOLVED] samba and squid module stopped after reboot...  (Read 10130 times)

julio

  • Guest
[SOLVED] samba and squid module stopped after reboot...
« on: June 19, 2014, 02:00:37 pm »
Hi, folks!

I'm try to testing the newest 3.5 daily build (19.06.2014).
If i set new share and add user or group access to share,
after server reboot, samba and squid module stopped.

zentyal.log:
Code: [Select]
Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: Connection refused, retrying. (1 attempts)
Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: Connection refused, retrying. (100 attempts)
Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: Connection refused, retrying. (200 attempts)
Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: Connection refused, retrying. (300 attempts)

I started bug tracker for this error, but no reaction from support:
https://tracker.zentyal.org/issues/1090

Has anyone successfully gotten working file sharing with ACLs on 3.5?
« Last Edit: June 27, 2014, 08:13:40 pm by julio »

The Knew Guy

  • Zen Apprentice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: samba and squid module stopped after reboot...
« Reply #1 on: June 20, 2014, 08:04:31 pm »
I'm having the same problem.  Samba database connection refused after setting up users, groups, shares and then rebooting the machine.  During Boot-up, a message appears on the screen that says something like "Zentyal is Setting up Core services"  After reboot, the Zentyal-samba module is broken and can only be fixed by purge/reinstall (which throws away all the configuration you just did)

Code: [Select]
some modules reported error when saving changes . More information on the logs in /var/log/zentyal/
FATAL: Could not connect to samba LDAP server: connect: Connection refused
FATAL: Could not connect to samba LDAP server: connect: Connection refused at
FATAL: Could not connect to samba LDAP server: connect: Connection refused at /usr/share/perl5/EBox/Ldap.pm line 219
EBox::Ldap::safeConnect('EBox::Ldap=HASH(0x9484be8)') called at /usr/share/perl5/EBox/Ldap.pm line 173
EBox::Ldap::connection('EBox::Ldap=HASH(0x9484be8)') called at /usr/share/perl5/EBox/LDAPBase.pm line 99
EBox::LDAPBase::search('EBox::Ldap=HASH(0x9484be8)', 'HASH(0x7928a28)') called at /usr/share/perl5/EBox/Samba.pm line 1856
EBox::Samba::securityGroups('EBox::Samba=HASH(0x7d0cdf0)') called at /usr/share/perl5/EBox/Samba.pm line 1636
EBox::Samba::realGroups('EBox::Samba=HASH(0x7d0cdf0)') called at /usr/share/perl5/EBox/Samba/Model/SambaSharePermissions.pm line 84
EBox::Samba::Model::SambaSharePermissions::populateGroup at /usr/share/perl5/EBox/Samba/Types/Select.pm line 50
EBox::Samba::Types::Select::options('EBox::Samba::Types::Select=HASH(0x9707b98)') called at /usr/share/perl5/EBox/Types/Select.pm line 179
EBox::Types::Select::printableValue('EBox::Samba::Types::Select=HASH(0x9707b98)') called at /usr/share/perl5/EBox/Types/Union.pm line 384
EBox::Types::Union::AUTOLOAD('EBox::Types::Union=HASH(0x9707958)') called at /usr/share/perl5/EBox/Types/Union.pm line 252
EBox::Types::Union::printableValue('EBox::Types::Union=HASH(0x9707958)') called at /usr/share/perl5/EBox/Model/Row.pm line 547
EBox::Model::Row::printableValueByName('EBox::Model::Row=HASH(0x9707a48)', 'user_group') called at /usr/share/perl5/EBox/Samba/Model/SambaSharePermissions.pm line 144
EBox::Samba::Model::SambaSharePermissions::syncRows('EBox::Samba::Model::SambaSharePermissions=HASH(0x9615400)', 'ARRAY(0x9687858)') called at /usr/share/perl5/EBox/Model/DataTable.pm line 1461
eval {...} at /usr/share/perl5/EBox/Model/DataTable.pm line 1457
EBox::Model::DataTable::ids('EBox::Samba::Model::SambaSharePermissions=HASH(0x9615400)') called at /usr/share/perl5/EBox/Samba.pm line 3462
EBox::Samba::shares('EBox::Samba=HASH(0x7d0cdf0)') called at /usr/share/perl5/EBox/Samba.pm line 3248
EBox::Samba::writeSambaConfig('EBox::Samba=HASH(0x7d0cdf0)') called at /usr/share/perl5/EBox/Samba.pm line 804
EBox::Samba::_setConfInternal('EBox::Samba=HASH(0x7d0cdf0)', undef) called at /usr/share/perl5/EBox/Samba.pm line 780
EBox::Samba::_setConf('EBox::Samba=HASH(0x7d0cdf0)') called at /usr/share/perl5/EBox/Module/Base.pm line 995
EBox::Module::Base::_regenConfig('EBox::Samba=HASH(0x7d0cdf0)') called at /usr/share/perl5/EBox/Module/Service.pm line 972
EBox::Module::Service::_regenConfig('EBox::Samba=HASH(0x7d0cdf0)') called at /usr/share/perl5/EBox/Samba.pm line 761
EBox::Samba::_regenConfig('EBox::Samba=HASH(0x7d0cdf0)') called at /usr/share/perl5/EBox/Module/Base.pm line 234
eval {...} at /usr/share/perl5/EBox/Module/Base.pm line 233
EBox::Module::Base::save('EBox::Samba=HASH(0x7d0cdf0)') called at /usr/share/perl5/EBox/GlobalImpl.pm line 651
eval {...} at /usr/share/perl5/EBox/GlobalImpl.pm line 650
EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x48ee178)', 'progress', 'EBox::ProgressIndicator=HASH(0x230b8f0)') called at /usr/share/perl5/EBox/Global.pm line 95
EBox::Global::AUTOLOAD('EBox::Global=HASH(0x48edba8)', 'progress', 'EBox::ProgressIndicator=HASH(0x230b8f0)') called at /usr/share/zentyal/global-action line 32 eval {...} at /usr/share/zentyal/global-action line 30
« Last Edit: June 20, 2014, 08:10:04 pm by tknew »

jbahillo

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1444
  • Karma: +77/-2
    • View Profile
Re: samba and squid module stopped after reboot...
« Reply #2 on: June 20, 2014, 11:40:29 pm »
Is there any process listening on 389 port?

advice not sure if already checked. Stop samba module, make sure no samba process is running and try starting it again

julio

  • Guest
Re: samba and squid module stopped after reboot...
« Reply #3 on: June 21, 2014, 01:46:33 am »
Code: [Select]
netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode       PID/Program name
tcp        0      0 127.0.0.1:61443         0.0.0.0:*               LISTEN      0          20103       3211/nginx.conf
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      107        11800       1509/mysqld
tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      102        13416       1464/redis-server 1
tcp        0      0 0.0.0.0:5900            0.0.0.0:*               LISTEN      1000       13643       1724/x11vnc
tcp        0      0 127.0.0.1:6380          0.0.0.0:*               LISTEN      108        13557       1676/redis-server 1
tcp        0      0 0.0.0.0:2222            0.0.0.0:*               LISTEN      0          12786       1368/sshd
tcp        0      0 192.168.2.1:53          0.0.0.0:*               LISTEN      112        13944       2542/named
tcp        0      0 192.168.1.2:53          0.0.0.0:*               LISTEN      112        13942       2542/named
tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN      112        13940       2542/named
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      112        13938       2542/named
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      112        17463       2542/named
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      0          12101       2680/haproxy
tcp6       0      0 :::5900                 :::*                    LISTEN      1000       13644       1724/x11vnc
tcp6       0      0 :::2222                 :::*                    LISTEN      0          12788       1368/sshd
udp        0      0 0.0.0.0:49150           0.0.0.0:*                           0          13910       2434/dhcpd
udp        0      0 192.168.2.1:53          0.0.0.0:*                           112        13943       2542/named
udp        0      0 192.168.1.2:53          0.0.0.0:*                           112        13941       2542/named
udp        0      0 127.0.1.1:53            0.0.0.0:*                           112        13939       2542/named
udp        0      0 127.0.0.1:53            0.0.0.0:*                           112        13937       2542/named
udp        0      0 0.0.0.0:67              0.0.0.0:*                           0          13923       2434/dhcpd
udp        0      0 192.168.2.1:123         0.0.0.0:*                           0          19739       3031/ntpd
udp        0      0 192.168.1.2:123         0.0.0.0:*                           0          19738       3031/ntpd
udp        0      0 127.0.1.1:123           0.0.0.0:*                           0          19737       3031/ntpd
udp        0      0 127.0.0.1:123           0.0.0.0:*                           0          19736       3031/ntpd
udp        0      0 0.0.0.0:123             0.0.0.0:*                           0          19729       3031/ntpd
udp6       0      0 :::19272                :::*                                0          13911       2434/dhcpd
udp6       0      0 :::123                  :::*                                0          19730       3031/ntpd
« Last Edit: June 21, 2014, 01:50:55 am by julio »

julio

  • Guest
Re: samba and squid module stopped after reboot...
« Reply #4 on: June 21, 2014, 03:10:12 pm »
« Last Edit: June 21, 2014, 05:28:27 pm by julio »

The Knew Guy

  • Zen Apprentice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: samba and squid module stopped after reboot...
« Reply #5 on: June 25, 2014, 08:21:41 pm »
This is still broken as of today.  Zentyal-samba 3.5~124

The Knew Guy

  • Zen Apprentice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: samba and squid module stopped after reboot...
« Reply #6 on: June 25, 2014, 09:26:58 pm »
Still breaks on reboot, I tried to manually start the processes with service zentyal samba start and it fails.  I manually started samba from the command line by simply typing samba and it started fine.  "zentyal samba" is still considered "stopped" (both from the dashboard, and from service zentyal samba status command, but I am able to access the "Manage" link on users and groups despite the service being stopped. 

Perhaps Samba isn't broken, just the initialization of it is?

julio

  • Guest
samba and squid module stopped after reboot...
« Reply #7 on: June 26, 2014, 07:32:29 pm »
Try with this:
https://tracker.zentyal.org/issues/1090#note-13

Code: [Select]
sudo patch /usr/share/perl5/EBox/Ldap.pm < Ldap.pm.patch
« Last Edit: June 27, 2014, 08:13:49 pm by julio »

julio

  • Guest

shoppc

  • Zen Apprentice
  • *
  • Posts: 9
  • Karma: +2/-0
    • View Profile
Re: [SOLVED] samba and squid module stopped after reboot...
« Reply #9 on: July 29, 2014, 09:40:56 pm »
Hi,

I Have Community edition 3.5.2 setup and running.  Today console desktop screen just stayed BLACK. When I went to use the console remotely through WebAdmin all was looking fine, so figured it was my VMware workstation playing up.  Anyway, restarted the server and found two issues:

1 - the Internal & External Interfaces were swapped, proved by changing the vnet setting on each interface in my virtual environment until pings could be made on each LAN segment.  Bit odd, but not sure if this is a bug with Zentyal on startup. 

But most important/relevant....

2 - Half of the services had not started, checked zentyal.log and sure enough I had the Samba LDAP error as found in this report (bug report 1090).  I followed the advice here and restarted the services from command line - all good and all working.  However, I would say that the bug is not solved!  The issue has been identified, but not permanently resolved (otherwise I wouldn't have experienced it after updates). 

Hopefully someone can pull/fix whatever causes this, since it took me a day to find the issue (being new to Zentyal and all that).  Otherwise, good system!  Regarding (1), the interfaces - will monitor and report an issue if it occurs again.

Laurent Dinclaux

  • Zen Monk
  • **
  • Posts: 83
  • Karma: +5/-0
    • View Profile
    • Gecka
Re: [SOLVED] samba and squid module stopped after reboot...
« Reply #10 on: August 04, 2014, 10:39:58 pm »
I face the exact same issue after upgrading from 3.4 to 3.5: connections refused to samba
Laurent

shoppc

  • Zen Apprentice
  • *
  • Posts: 9
  • Karma: +2/-0
    • View Profile
Re: [SOLVED] samba and squid module stopped after reboot...
« Reply #11 on: August 05, 2014, 03:20:00 pm »
Applied the 'patch', as per the instructions found in bug 1090 report.  All working again except OpenChange module. So scrapping my install to start again. Will monitor the install/update process and report finding here if there is anything of help. I understand the roadmap speaks if a new release point soon (sept) I think, maybe will wait till then.

julio

  • Guest
Re: [SOLVED] samba and squid module stopped after reboot...
« Reply #12 on: August 06, 2014, 09:44:29 am »
@Laurent Dinclaux and @shoppc
please post your zentyal log file after following commands (without patch, after reboot):

Code: [Select]
sudo cp /var/log/zentyal/zentyal.log /var/log/zentyal/zentyal.log.bckp
sudo truncate -s0 /var/log/zentyal/zentyal.log
sudo reboot
« Last Edit: August 06, 2014, 09:48:16 am by julio »

shoppc

  • Zen Apprentice
  • *
  • Posts: 9
  • Karma: +2/-0
    • View Profile
Re: [SOLVED] samba and squid module stopped after reboot...
« Reply #13 on: August 06, 2014, 03:48:55 pm »
Ok, I have scrapped my VM for Zentyal, but will rebuild later (may take a week or two), as I'm away on holiday.  Once re-installed v3.5 & updated, do you want me to copy up the Log here?  Or, do you want a fresh install with NO updates and then the logs?

julio

  • Guest
Re: [SOLVED] samba and squid module stopped after reboot...
« Reply #14 on: August 06, 2014, 06:20:48 pm »
after the Commands, just copy up the Log here...