Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: julio 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:
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?
-
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)
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
-
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
-
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
-
my temporarily solution:
https://tracker.zentyal.org/issues/1090#note-8
-
This is still broken as of today. Zentyal-samba 3.5~124
-
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?
-
Try with this:
https://tracker.zentyal.org/issues/1090#note-13 (https://tracker.zentyal.org/issues/1090#note-13)
sudo patch /usr/share/perl5/EBox/Ldap.pm < Ldap.pm.patch
-
Solved:
https://tracker.zentyal.org/issues/1090#note-14 (https://tracker.zentyal.org/issues/1090#note-14)
-
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.
-
I face the exact same issue after upgrading from 3.4 to 3.5: connections refused to samba
-
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.
-
@Laurent Dinclaux and @shoppc
please post your zentyal log file after following commands (without patch, after reboot):
sudo cp /var/log/zentyal/zentyal.log /var/log/zentyal/zentyal.log.bckp
sudo truncate -s0 /var/log/zentyal/zentyal.log
sudo reboot
-
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?
-
after the Commands, just copy up the Log here...
-
Here it is, attached
-
i need more Informations, please attach your "/var/log/zentyal/zentyal.log" and
"/var/log/syslog" Files after following Commands (after Reboot plase wait a little bit, aprox.: 5-10min):
sudo cp /var/log/zentyal/zentyal.log /var/log/zentyal/zentyal.log.bckp
sudo truncate -s0 /var/log/zentyal/zentyal.log
sudo cp /var/log/syslog /var/log/syslog.bckp
sudo truncate -s0 /var/log/syslog
sudo reboot
-
Attached
-
File "/var/lib/samba/private/secrets.ldb" exists?
ls -la /var/lib/samba/private/secrets.ldb
-
i have created a new BugTracker:
https://tracker.zentyal.org/issues/1499 (https://tracker.zentyal.org/issues/1499)
please follow this Tracker...
-
Thank you
-
manual samba "reprovision":
1. make full backup from your server with e.g.:clonezilla (the Devil doesn't sleep ;))
2. make zentyal backup (web interface): System->Import/Export Configuration->backup
3. purge samba and their dependencies:
sudo apt-get purge --auto-remove samba4. remove smb.conf if exist:
sudo rm /etc/samba/smb.conf5. install samba and squid and theirs dependencies back:
sudo apt-get install zentyal-samba zentyal-squid6. go to Users and Computers->Configure mode (web interface) and change LDAP DN to your Base DN:
dc=office,dc=gecka,dc=nc
press Change
7. go to Module Status (web interface) and enable "Users, Computers and File Sharing" and "HTTP Proxy" Modules, save with Save Changes button
8. revert your zentyal backup back (web interface): System->Import/Export Configuration->restore
9. save with Save Changes button
that's it! :D
-
Hello friends
I know this topic is quite old, but I am running into same problem with Samba, but I am using Zentyal 4.0.5...
Someone have this problem with Zentyal 4???
-
Yes, me having this problem too after upgrading to version 4.0.5
Gilberto; have you had any success solving this problem?
-
Hi I want to tell my case,
Once more Zentyal I was disappointed with their problems unresolved,...
Today suddenly stopped the samba service and I have 6 hours doing many tests but without any success, I have read all this post and also have made the solution of: https://tracker.zentyal.org/issues/1090 and: https://github.com/Zentyal/zentyal/commit/b2c81f37d531b8d62aa1864ccf54c850e484db29 ... none worked
Had Zentyal 3.5 when stopped samba and all users of the network were out of the "File Sharing" upgrade to version 4.0.5 (last with all updates) and there is no solution to my problem, samba stopped and fail.
Now I have to reinstall everything all back to create the users in the domain, and create folders shared :(this is too frustrating relying on this "solution" Zentyal and have these problems on the network of the company
Hopefully some day Zentyal has a truly stable version...
zentyal.log
2015/02/03 21:28:10 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Microsoft global catalog' (tcp)
2015/02/03 21:28:10 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Microsoft global catalog' (tcp)
2015/02/03 21:28:40 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Microsoft global catalog over SSL' (tcp)
2015/02/03 21:28:40 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Microsoft global catalog over SSL' (tcp)
2015/02/03 21:29:13 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Kerberos authentication' (tcp)
2015/02/03 21:29:14 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'NETBIOS session service' (tcp)
2015/02/03 21:29:43 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'DCE endpoint resolution' (tcp)
2015/02/03 21:29:44 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Lightweight Directory Access Protocol' (tcp)
2015/02/03 21:30:14 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'NETBIOS session service' (tcp)
2015/02/03 21:30:14 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Microsoft directory services' (tcp)
2015/02/03 21:30:44 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Lightweight Directory Access Protocol' (tcp)
2015/02/03 21:30:44 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Kerberos set/change password' (tcp)
2015/02/03 21:31:14 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Microsoft directory services' (tcp)
2015/02/03 21:31:14 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'LDAP over TLS/SSL' (tcp)
2015/02/03 21:31:44 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Kerberos set/change password' (tcp)
2015/02/03 21:31:44 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service '' (tcp)
2015/02/03 21:32:14 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'LDAP over TLS/SSL' (tcp)
2015/02/03 21:32:14 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Microsoft global catalog' (tcp)
2015/02/03 21:32:44 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service '' (tcp)
2015/02/03 21:32:45 WARN> Samba.pm:774 EBox::Samba::_waitService - Timeout reached while waiting for users service 'Microsoft global catalog over SSL' (tcp)
samba.log
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
[2015/02/03 21:28:43, 2] ../source4/dsdb/repl/drepl_partitions.c:116(dreplsrv_load_partitions)
[2015/02/03 21:28:43, 3] ../lib/ldb-samba/ldb_wrap.c:320(ldb_wrap_connect)
dreplsrv_partition[CN=Schema,CN=Configuration,DC=vringltda,DC=empresa] loaded
ldb_wrap open of secrets.ldb
[2015/02/03 21:28:43, 2] ../source4/dsdb/repl/drepl_partitions.c:116(dreplsrv_load_partitions)
dreplsrv_partition[DC=vringltda,DC=empresa] loaded
[2015/02/03 21:28:43, 2] ../source4/dsdb/repl/drepl_partitions.c:116(dreplsrv_load_partitions)
dreplsrv_partition[CN=Configuration,DC=vringltda,DC=empresa] loaded
[2015/02/03 21:28:43, 2] ../source4/dsdb/repl/drepl_partitions.c:116(dreplsrv_load_partitions)
dreplsrv_partition[DC=DomainDnsZones,DC=vringltda,DC=empresa] loaded
[2015/02/03 21:28:43, 2] ../source4/dsdb/repl/drepl_partitions.c:116(dreplsrv_load_partitions)
dreplsrv_partition[DC=ForestDnsZones,DC=vringltda,DC=empresa] loaded
[2015/02/03 21:28:43, 3] ../lib/ldb-samba/ldb_wrap.c:320(ldb_wrap_connect)
ldb_wrap open of idmap.ldb
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
[2015/02/03 21:28:43, 3] ../source4/smbd/service_stream.c:66(stream_terminate_connection)
Terminating connection - 'dcesrv: NT_STATUS_CONNECTION_DISCONNECTED'
[2015/02/03 21:28:43, 3] ../source4/smbd/process_single.c:114(single_terminate)
single_terminate: reason[dcesrv: NT_STATUS_CONNECTION_DISCONNECTED]
[2015/02/03 21:28:43, 3] ../source4/smbd/service_stream.c:66(stream_terminate_connection)
Terminating connection - 'kdc_tcp_call_loop: tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_DISCONNECTED'
[2015/02/03 21:28:43, 3] ../source4/smbd/process_single.c:114(single_terminate)
single_terminate: reason[kdc_tcp_call_loop: tstream_read_pdu_blob_recv() - NT_STATUS_CONNECTION_DISCONNECTED]
[2015/02/03 21:28:43, 0] ../lib/util/become_daemon.c:136(daemon_ready)
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
[2015/02/03 21:28:43, 2] ../source4/dsdb/kcc/kcc_service.c:127(kccsrv_load_partitions)
kccsrv_partition[CN=Schema,CN=Configuration,DC=vringltda,DC=empresa] loaded
[2015/02/03 21:28:43, 2] ../source4/dsdb/kcc/kcc_service.c:127(kccsrv_load_partitions)
kccsrv_partition[CN=Configuration,DC=vringltda,DC=empresa] loaded
[2015/02/03 21:28:43, 2] ../source4/dsdb/kcc/kcc_service.c:127(kccsrv_load_partitions)
kccsrv_partition[DC=vringltda,DC=empresa] loaded
[2015/02/03 21:28:43, 2] ../source4/dsdb/kcc/kcc_service.c:127(kccsrv_load_partitions)
kccsrv_partition[DC=DomainDnsZones,DC=vringltda,DC=empresa] loaded
[2015/02/03 21:28:43, 2] ../source4/dsdb/kcc/kcc_service.c:127(kccsrv_load_partitions)
kccsrv_partition[DC=ForestDnsZones,DC=vringltda,DC=empresa] loaded
[2015/02/03 21:28:43, 0] ../file_server/file_server.c:48(file_server_smbd_done)
file_server smbd daemon exited normally
[2015/02/03 21:28:43, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
task_server_terminate: [smbd child process exited]
[2015/02/03 21:28:43, 3] ../source4/dsdb/dns/dns_update.c:340(dnsupdate_check_names)
Calling DNS name update script
STATUS=daemon 'samba' finished starting up and ready to serve connectionssamba_terminate: smbd child process exited
[2015/02/03 21:28:43, 3] ../source4/dsdb/dns/dns_update.c:355(dnsupdate_check_names)
Calling SPN name update script