Unable to connect network drive SAMBA Share

Bug #306168 reported by Louis-Xavier Brusset
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: samba

Hello,
Since I migrated from Hardy to Intrepid I cannot connect with SAMBA to My freecom Network drive.
(uname -a => Linux Ubuntu-lx-dell 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 GNU/Linux)
I can use the embeded FTP server but it is not as functionnal.

I noticed that I can connect to a TRUE smb server (Igot a PC under Windows XP Pro) but it crashes with my FREECOM Network Drive.

I looked into Samba logs and I found this in /var/log/samba/log.winbindd-idmap :

[2008/12/02 19:13:40, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:13:40, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:13:40, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:13:40, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:14:23, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:14:23, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:14:23, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:14:23, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:14:23, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:14:23, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:14:23, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:14:23, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!

Revision history for this message
Thierry Carrez (ttx) wrote :

I'm not sure I understand...
You're trying to connect from an Intrepid client to a network share on a Freecom NAS.

The logs you're showing seem to come from a Samba/Winbind *server*. Are those logs from the Freecom NAS or from the Ubuntu client ? If the logs come from the Ubuntu client, why are you running a winbind server on it ?

Could you give me the output of the following command:
dpkg-query -W -f '${Status} ${Source} ${Package} ${Version}\n' | grep samba

If winbind appears installed and there is no reason why you run a winbind server on your client (if you don't know what it is, you probably don't need it), try "sudo apt-get remove winbind" and see if you still get these errors in your log. That doesn't mean your problem will be solved, but maybe we can remove the error message from the equation.

Thanks in advance

Changed in samba:
status: New → Incomplete
Revision history for this message
Louis-Xavier Brusset (lxbrusset) wrote :

hello,
The log comes from the client, one of my computers, I am not sure that I can get something from my NAS...

here is the result of the query :

install ok installed samba libpam-smbpass 2:3.2.3-1ubuntu3.3
install ok installed samba libsmbclient 2:3.2.3-1ubuntu3.3
install ok installed samba libwbclient0 2:3.2.3-1ubuntu3.3
install ok installed samba 2:3.2.3-1ubuntu3.3
install ok installed samba samba-common 2:3.2.3-1ubuntu3.3
install ok installed samba samba-tools 2:3.2.3-1ubuntu3.3
install ok installed samba smbclient 2:3.2.3-1ubuntu3.3
install ok installed samba smbfs 2:3.2.3-1ubuntu3.3
install ok installed system-config-samba 1.2.63-0ubuntu4
install ok installed samba winbind 2:3.2.3-1ubuntu3.3

I have removed windbind, it seams it does not resovled my problem, I reboot and I retry

Revision history for this message
Louis-Xavier Brusset (lxbrusset) wrote :

Hello I just rebooted without winbind, does not really change anything.
Can you give me commands to execute or logs to send you for helping comprehension ?

Revision history for this message
Thierry Carrez (ttx) wrote :

Once winbind is removed you should not get the idmap errors in your logs anymore. Those were related to a half-configured winbind server on your Ubuntu client. However your problem is not solved yet, we just removed noise.

What command or action are you doing to access your Samba share ? Are you using nautilus ? Using a cifs/smbfs mount command or /etc/fstab ? Using smbclient ? How does it "crash" ? Any error ?

Revision history for this message
Louis-Xavier Brusset (lxbrusset) wrote : Re: [Bug 306168] Re: Unable to connect network drive SAMBA Share

Hello,
Usually I use only Nautilus to connect to my NAS.
I did not try anything by command-line.
The symptoms are simple to explain :
I explore my smb shares with nautilus, open the icon of my NAS, select one
of the shares I created in my Freecom Web-based interface and after some
times Nautilus returns to my home directory.
I shouldn't be able to make experiments before 29th of december, as I am not
home. So if you have any idea to give me before I will register it and try
it ASAP.

Many Thanks,
LBT

2008/12/16 Thierry Carrez <email address hidden>

> Once winbind is removed you should not get the idmap errors in your logs
> anymore. Those were related to a half-configured winbind server on your
> Ubuntu client. However your problem is not solved yet, we just removed
> noise.
>
> What command or action are you doing to access your Samba share ? Are
> you using nautilus ? Using a cifs/smbfs mount command or /etc/fstab ?
> Using smbclient ? How does it "crash" ? Any error ?
>
> --
> Unable to connect network drive SAMBA Share
> https://bugs.launchpad.net/bugs/306168
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Cordialement,
Louis-Xavier BRUSSET

Revision history for this message
Louis-Xavier Brusset (lxbrusset) wrote :

hello,
as I was exploring my system I found this in /var/log/syslog :

Jan 5 10:30:48 Ubuntu-lx-dell kernel: [69195.916576] gvfsd-smb[7989]: segfault at 0 ip b7a082c3 sp b747bc9c error 4 in libc-2.8.90.so[b7991000+158000]
Jan 5 10:32:47 Ubuntu-lx-dell kernel: [69315.208694] gvfsd-smb[8032]: segfault at 0 ip b78b42c3 sp b7327c9c error 4 in libc-2.8.90.so[b783d000+158000]

I get the same in /var/log/messages :

Jan 5 10:30:48 Ubuntu-lx-dell kernel: [69195.916576] gvfsd-smb[7989]: segfault at 0 ip b7a082c3 sp b747bc9c error 4 in libc-2.8.90.so[b7991000+158000]
Jan 5 10:32:47 Ubuntu-lx-dell kernel: [69315.208694] gvfsd-smb[8032]: segfault at 0 ip b78b42c3 sp b7327c9c error 4 in libc-2.8.90.so[b783d000+158000]

and in /var/log/kern.log :

Jan 5 10:30:48 Ubuntu-lx-dell kernel: [69195.916576] gvfsd-smb[7989]: segfault at 0 ip b7a082c3 sp b747bc9c error 4 in libc-2.8.90.so[b7991000+158000]
Jan 5 10:32:47 Ubuntu-lx-dell kernel: [69315.208694] gvfsd-smb[8032]: segfault at 0 ip b78b42c3 sp b7327c9c error 4 in libc-2.8.90.so[b783d000+158000]

Revision history for this message
Thierry Carrez (ttx) wrote :

Let us know if purging winbind removed the idmap errors.
The rest of this bug looks a lot like bug 264943, could you try the PPA release posted there (see https://bugs.launchpad.net/ubuntu/+source/samba/+bug/264943/comments/89)

Revision history for this message
Louis-Xavier Brusset (lxbrusset) wrote :

Hello,
as the log file does not exist anymore we can see that purging winbind
removed the idmap errors.

For samba_3.2.3-1ubuntu3.5~ppa1 in your PPA, is there a procedure to install
this whithout uninstalling ubuntu-desktop ?
I tried to install your .deb files but as
samba-common_3.2.3-1ubuntu3.5~ppa1_i386 broke my dependencies I had to
reinstall the standard version.
I can't install samba_3.2.3-1ubuntu3.5~ppa1_i386 without installing your
version of samba-common.

I am blocked by my inexperiency of installing non standard versions ...

Regards,
LBT

Revision history for this message
Thierry Carrez (ttx) wrote :

The idea is to enable the PPA as a valid source of packages and run a regular upgrade.
I'd not recommend it if this is not a test environment. Better wait for the regular updated package in that case...

If you still accept to do it here is a quick recipe:
Add "deb http://ppa.launchpad.net/tcarrez/ubuntu intrepid main" at the end of your /etc/apt/sources.list
$ sudo apt-get update
$ sudo apt-get upgrade
This will upgrade all your samba packages to samba_3.2.3-1ubuntu3.5~ppa1 (including samba-common).
The PPA package will be replaced when the regular 3.2.3-1ubuntu3.5 is released.

Revision history for this message
Louis-Xavier Brusset (lxbrusset) wrote :

OK I «take the risk» for one of my computers, if it does not work I will
remove the line from my sources.

I will give you the result of this experiment.

2009/1/19 Thierry Carrez <email address hidden>

> The idea is to enable the PPA as a valid source of packages and run a
> regular upgrade.
> I'd not recommend it if this is not a test environment. Better wait for the
> regular updated package in that case...
>
> If you still accept to do it here is a quick recipe:
> Add "deb http://ppa.launchpad.net/tcarrez/ubuntu intrepid main" at the end
> of your /etc/apt/sources.list
> $ sudo apt-get update
> $ sudo apt-get upgrade
> This will upgrade all your samba packages to samba_3.2.3-1ubuntu3.5~ppa1
> (including samba-common).
> The PPA package will be replaced when the regular 3.2.3-1ubuntu3.5 is
> released.
>
> --
> Unable to connect network drive SAMBA Share
> https://bugs.launchpad.net/bugs/306168
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Cordialement,
Louis-Xavier BRUSSET

Revision history for this message
Louis-Xavier Brusset (lxbrusset) wrote :

I cross fingers, but it seems to work.

I will try this on my other computer to confirm the bug is corrected.

Revision history for this message
Dommo (u-carlot-u) wrote :

i was getting same error in intrepid x86

dmesg

 2305.421739] gvfsd-smb[8613]: segfault at 0 ip b79252c3 sp b739bc9c error 4 in libc-2.8.90.so[b78ae000+158000]
[ 2737.000075] CE: hpet increasing min_delta_ns to 15000 nsec
[ 3132.683629] gvfsd-smb[9220]: segfault at 0 ip b79a92c3 sp b741fc9c error 4 in libc-2.8.90.so[b7932000+158000]
[ 3135.466598] gvfsd-smb[9226]: segfault at 0 ip b79262c3 sp b739cc9c error 4 in libc-2.8.90.so[b78af000+158000]
[ 3137.079947] gvfsd-smb[9234]: segfault at 0 ip b79a72c3 sp b741dc9c error 4 in libc-2.8.90.so[b7930000+158000]
[ 3138.551219] gvfsd-smb[9240]: segfault at 0 ip b78a62c3 sp b731cc9c error 4 in libc-2.8.90.so[b782f000+158000]
[ 3139.963568] gvfsd-smb[9247]: segfault at 0 ip b789d2c3 sp b7313c9c error 4 in libc-2.8.90.so[b7826000+158000]
[ 3141.428323] gvfsd-smb[9251]: segfault at 0 ip b79932c3 sp b7409c9c error 4 in libc-2.8.90.so[b791c000+158000]
[ 3143.037154] gvfsd-smb[9261]: segfault at 0 ip b78a02c3 sp b7316c9c error 4 in libc-2.8.90.so[b7829000+158000]
[ 3190.498049] gvfsd-smb[9316]: segfault at 0 ip b790f2c3 sp b7385c9c error 4 in libc-2.8.90.so[b7898000+158000]
[ 3204.607946] gvfsd-smb[9345]: segfault at 0 ip b79a92c3 sp b741fc9c error 4 in libc-2.8.90.so[b7932000+158000]

then i added deb http://ppa.launchpad.net/tcarrez/ubuntu intrepid main as a source repo, updated....

dmesg still shows an error but i can connect to my nas just fine now.

here's the error:

[ 7348.824717] gvfsd-smb[14003]: segfault at 0 ip b792a2c3 sp b73a0c9c error 4 in libc-2.8.90.so[b78b3000+158000]
[ 7985.970395] gvfsd-smb[14606]: segfault at 0 ip b79d82c3 sp b744ec9c error 4 in libc-2.8.90.so[b7961000+158000]

thanks for the fix...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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