SOLVED: Local Samba shares: cifs_mount failed

[aboshan]

Hi guys,

I've just migrated from F14 to F19, on a fresh install. I'm in the process of getting everything set up again like it was with Amahi 6.

Everything worked fine, until I hit a bump at the "mount_shares_locally" script integration.
Whatever I did, my /mnt/samba/ shares stayed empty.

dmesg gave:
"CIFS VFS: cifs_mount failed w/return code = -13"
PERMISSION DENIED

I checked all my permissions, as this was my first thought. I ended up throwing all security overboard for the sake of testing and set shares and samba mounts to

Code: Select all

chown -R aboshan:users /var/hda/files/* chmod -R 777 /var/hda/files/*

but no avail.

My attention then went to cifs-utils, as this was the function within mount_shares_locally which didn't succeed. I tried executing it manually:

Code: Select all

sudo mount.cifs //hda/Pictures /home/aboshan/pictures -o credentials=/home/aboshan/.smb_credentials

gives

Code: Select all

CIFS VFS: cifs_mount failed w/return code = -13

I tried mounting it directly through fstab:

Code: Select all

//127.0.0.1/Pictures /mnt/samba/Pictures cifs username=aboshan,password=XXXXX,rw,iocharset=utf8,uid=1000,gid=1000,sec=ntlm 0 0

But still got the

Code: Select all

mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

error...

Next step, what's wrong with samba?

smb.conf seems fine:

Code: Select all

# This file is automatically generated for WORKGROUP setup. # Any manual changes MAY BE OVERWRITTEN # Amahi configuration, generated on 2014-08-20 12:44:46 +0200 [global] workgroup = jahn server string = jahn.com netbios name = hda printing = cups printcap name = cups load printers = yes cups options = raw log file = /var/log/samba/%m.log log level = 0 max log size = 150 preferred master = yes os level = 60 time server = yes unix extensions = no wide links = yes security = user username map script = /usr/share/hda-platform/hda-usermap large readwrite = yes encrypt passwords = yes dos charset = CP850 unix charset = UTF8 guest account = nobody map to guest = Bad User wins support = yes [homes] comment = Home Directories valid users = %S browseable = no writable = yes create mask = 0644 directory mask = 0755 [print$] path = /var/lib/samba/drivers read only = yes force group = root write list = @ntadmin root force group = root create mask = 0664 directory mask = 0775 guest ok = yes [printers] path = /var/spool/samba writeable = yes browseable = yes printable = yes public = yes [Books] comment = Books path = /var/hda/files/books writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Docs] comment = Docs path = /var/hda/files/docs writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Dropbox] comment = Dropbox path = /var/hda/files/dropbox writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Games] comment = Games path = /var/hda/files/games writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Movies] comment = Movies path = /var/hda/files/movies writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Music] comment = Music path = /var/hda/files/music writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Pictures] comment = Pictures path = /var/hda/files/pictures writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Public] comment = Public path = /var/hda/files/public writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Series] comment = Series path = /var/hda/files/series writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Stuff] comment = Stuff path = /var/hda/files/stuff writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Torrents] comment = Torrents path = /var/hda/files/torrents writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole [Videos] comment = Videos path = /var/hda/files/videos writeable = yes browseable = yes create mask = 0775 force create mode = 0664 directory mask = 0775 force directory mode = 0775 dfree command = /usr/bin/greyhole-dfree vfs objects = greyhole

however, /var/log/samba/smbd.log is giving me lots of errors:

Code: Select all

[2014/08/20 15:22:54.420269, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2014/08/20 15:22:54.420870, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2014/08/20 15:26:35.505848, 0] ../lib/util/pidfile.c:153(pidfile_unlink) Failed to delete pidfile /run/smbd.pid. Error was No such file or directory [2014/08/20 15:27:31.180085, 0] ../source3/smbd/server.c:1286(main) standard input is not a socket, assuming -D option DBI connect('database=hda_production;host=localhost','amahihda',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at /usr/share/hda-platform/hda-usermap line 68. [2014/08/20 15:27:36.713303, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2014/08/20 15:27:41.899952, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2014/08/20 15:40:37.282637, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2014/08/20 15:40:37.283280, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2014/08/20 15:53:37.848810, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2014/08/20 15:53:37.850574, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2014/08/20 16:06:38.498155, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected

Which seems quite the same issue as in next thread: viewtopic.php?f=14&t=5483

It's true Amahi didn't reboot automatically after I installed it, so maybe the culprit is to be found there.

I'll try a new install this evening, and let you guys know how it went.

If anybody has another idea, especially about the error message figuring in the samba log, you are more than welcome to share!

[aboshan]

Hi all again!

Success!!

A reinstall fixed it. This time I waited patiently when the login prompt appeared after the first reboot, that the hda rebooted for a second time.
My samba shares were directly available, as well as the locally mounted ones after implementation of the mount_shares_locally script.

Hours of troubleshooting because of being too eager to try out the new setup.

In my defence, it is not stated clearly enough in the wiki that you have to wait for a second reboot.
Make it bold, put some exclamation marks around it, things like that, as this seems to be a possible dealbreaker for your Amahi install.

I hope this will help future Amahi-fanatics!