samba4 default installation Connection failed (Error NT_STATUS_CONNECTION_REFUSED)

Bug #1055075 reported by Munzir Taha (منذر طه) on 2012-09-23
64
This bug affects 10 people
Affects Status Importance Assigned to Milestone
samba4 (Ubuntu)
Medium
Unassigned

Bug Description

I installed samba4, added a share /test to smb.conf and tried to access it and got
$ smbclient -L localhost -U%
Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED)

The log file /var/log/samba/log.%m (notice the buggy %m) contains
[2012/09/23 19:09:41, 0] ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler)
  /usr/sbin/smbd: Failed to exec child - No such file or directory
[2012/09/23 19:09:41, 0] ../file_server/file_server.c:98(file_server_smbd_done)
  file_server smbd daemon exited normally
[2012/09/23 19:09:41, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [ldap_server: no LDAP server required in standalone configuration]
[2012/09/23 19:09:41, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [cldap_server: no CLDAP server required in standalone configuration]
[2012/09/23 19:09:41, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [kdc: no KDC required in standalone configuration]
[2012/09/23 19:09:41, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [dreplsrv: no DSDB replication required in standalone configuration]
[2012/09/23 19:09:41, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [Cannot start Winbind (standalone configuration): Failed to find record for GT683R in /var/lib/samba/private/secrets.ldb: No such object: (null): Have you provisioned this server (GT683R) or changed it's name?]
[2012/09/23 19:09:41, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [kccsrv: no KCC required in standalone configuration]

$ sudo netstat -tunap |grep samba
tcp 0 0 0.0.0.0:1024 0.0.0.0:* LISTEN 5374/samba
tcp 0 0 0.0.0.0:135 0.0.0.0:* LISTEN 5374/samba
tcp6 0 0 :::1024 :::* LISTEN 5374/samba
tcp6 0 0 :::135 :::* LISTEN 5374/samba
udp 0 0 192.168.122.1:137 0.0.0.0:* 5376/samba
udp 0 0 192.168.122.255:137 0.0.0.0:* 5376/samba
udp 0 0 192.168.1.38:137 0.0.0.0:* 5376/samba
udp 0 0 192.168.1.255:137 0.0.0.0:* 5376/samba
udp 0 0 0.0.0.0:137 0.0.0.0:* 5376/samba
udp 0 0 192.168.122.1:138 0.0.0.0:* 5376/samba
udp 0 0 192.168.122.255:138 0.0.0.0:* 5376/samba
udp 0 0 192.168.1.38:138 0.0.0.0:* 5376/samba
udp 0 0 192.168.1.255:138 0.0.0.0:* 5376/samba
udp 0 0 0.0.0.0:138 0.0.0.0:* 5376/samba

I removed all iptables rules. Attached is my smb.conf
I also tried smbpasswd -a munzir followed by smbclient -L localhost -U munzir but got same result
---
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 12.10
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606)
NonfreeKernelModules: nvidia
Package: samba4 4.0.0~beta2+dfsg1-3
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Tags: quantal
Uname: Linux 3.5.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

tags: added: apport-collected
description: updated

apport information

Dave Gilbert (ubuntu-treblig) wrote :

Confirmed: I could recreate this
Medium: This is the universe version of samba not the main one; and also if this is just a default config problem then it's not a high; although I don't know enough Samba to know if it's really more serious.

I suspect there are multiple bugs here; the log.%m name suggests something is going wrong with the naming,
and the reference to /usr/sbin/smbd that doesn't exist suggests there is some larger scale package problem.

Dave

Changed in samba4 (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Dave Gilbert (ubuntu-treblig) wrote :

Observation; In the boot logs I see:

[ 11.335866] init: winbind main process (2135) terminated with status 127
[ 11.335884] init: winbind main process ended, respawning
[ 11.338729] init: winbind main process (2139) terminated with status 127
[ 11.338745] init: winbind main process ended, respawning
[ 11.340856] init: winbind main process (2141) terminated with status 127
[ 11.340871] init: winbind main process ended, respawning
[ 11.343190] init: winbind main process (2143) terminated with status 127
[ 11.343206] init: winbind main process ended, respawning
[ 11.345467] init: winbind main process (2145) terminated with status 127
[ 11.345483] init: winbind main process ended, respawning
[ 11.347586] init: winbind main process (2147) terminated with status 127
[ 11.347602] init: winbind main process ended, respawning
[ 11.349922] init: winbind main process (2149) terminated with status 127
[ 11.349938] init: winbind main process ended, respawning
[ 11.351959] init: winbind main process (2151) terminated with status 127
[ 11.351979] init: winbind main process ended, respawning
[ 11.354442] init: winbind main process (2153) terminated with status 127
[ 11.354457] init: winbind main process ended, respawning
[ 11.356271] init: winbind main process (2155) terminated with status 127
[ 11.356289] init: winbind main process ended, respawning
[ 11.358778] init: winbind main process (2157) terminated with status 127
[ 11.358793] init: winbind respawning too fast, stopped

Dave

Iain Buchanan (iainbuc) wrote :

I get the same issue. According to this:
https://wiki.samba.org/index.php/Samba4/Releases/4.0.0beta2
"smbd" is now the default, but "ntvfs" can be used.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694697
There was a similar bug reported here (guess this is what this package is based on?) Doesn't look like the change mentioned to make --use-ntvfs default has taken place yet, although specifying "--use-ntvfs" didn't work for me.

Jelmer Vernooij (jelmer) wrote :

Did you provision this server? It seems like it still has the old configuration.

You'll also need to enable the ntvfs file server.

Changed in samba4 (Ubuntu):
status: Confirmed → Incomplete
Michael Vogt (mvo) wrote :

Hi Jelmer, I ran into this issue as well, it appears that in the current 13.04 version the 11_force_ntvfs is in debian/patches but missing from debian/patches/series. Fix is trivial, I'm happy to attach it if that helps.

Dave Gilbert (ubuntu-treblig) wrote :

See comment #7 - apparent trivial package screwup

Changed in samba4 (Ubuntu):
status: Incomplete → Triaged

I used to solved the problem by adding the following, in the smb.conf

        server services = +smb -s3fs
        dcerpc endpoint servers = +winreg +srvsvc

thanks to Iain by pointing out https://wiki.samba.org/index.php/Samba4/Releases/4.0.0beta2

by the way I used to upgrade samba 3.3.10 to samba 3.4.17 previously encountered

#/usr/local/samba/bin/smbclient //localhost/netlogon -Uadministrator -->which displays
 Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSES)

and can't use windows remote administration tools in win7, but no problems encountered in winXp and also took 5-8 minutes to login but now seems all working fine, login instantly, able to use smbclient and the RSAT.

Attached is/are the previous logs encountered.

theghost (theghost) wrote :

On 13.10 my dmesg is still full of winbind output. Output of "dmesg | grep winbind":

[ 38.614222] init: winbind main process (1566) terminated with status 127
[ 38.614249] init: winbind main process ended, respawning
[ 38.637502] init: winbind main process (1569) terminated with status 127
[ 38.637528] init: winbind main process ended, respawning
[ 38.647683] init: winbind main process (1572) terminated with status 127
[ 38.647708] init: winbind main process ended, respawning
[ 38.655590] init: winbind main process (1576) terminated with status 127
[ 38.655614] init: winbind main process ended, respawning
[ 38.662234] init: winbind main process (1579) terminated with status 127
[ 38.662258] init: winbind main process ended, respawning
[ 38.669000] init: winbind main process (1582) terminated with status 127
[ 38.669026] init: winbind main process ended, respawning
[ 38.675483] init: winbind main process (1585) terminated with status 127
[ 38.675510] init: winbind main process ended, respawning
[ 38.681931] init: winbind main process (1588) terminated with status 127
[ 38.681958] init: winbind main process ended, respawning
[ 38.688364] init: winbind main process (1591) terminated with status 127
[ 38.688391] init: winbind main process ended, respawning
[ 38.694750] init: winbind main process (1594) terminated with status 127
[ 38.694777] init: winbind main process ended, respawning
[ 38.701585] init: winbind main process (1597) terminated with status 127
[ 38.701611] init: winbind respawning too fast, stopped

tags: added: saucy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.