samba problem

Ask questions about Arch Linux ARM. Please search before making a new topic.

samba problem

Postby funnyman » Fri Aug 09, 2013 8:24 am

Hello, I Can't get samba running. Please help. Thank you

Logs:
$this->bbcode_second_pass_code('', '[1970/01/01 01:00:31, 0] ../source4/smbd/server.c:369(binary_smbd_main)
samba version 4.0.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2012
[1970/01/01 01:00:32, 0] ../source4/smbd/server.c:461(binary_smbd_main)
At this time the 'samba' binary should only be used for either:
'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the rpc proxy with 'dcerpc endpoint servers = remote'
You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks
[2013/08/09 10:17:44, 0] ../source4/smbd/server.c:369(binary_smbd_main)
samba version 4.0.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2012
[2013/08/09 10:17:45, 0] ../source4/smbd/server.c:461(binary_smbd_main)
At this time the 'samba' binary should only be used for either:
'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the rpc proxy with 'dcerpc endpoint servers = remote'
You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks
')
$this->bbcode_second_pass_code('', 'samba.service - Samba AD Daemon
Loaded: loaded (/usr/lib/systemd/system/samba.service; enabled)
Active: failed (Result: exit-code) since Thu 1970-01-01 01:00:32 CET; 43 years 7 months ago
Process: 342 ExecStart=/usr/bin/samba $SAMBAOPTIONS (code=exited, status=0/SUCCESS)
Main PID: 350 (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/samba.service

Jan 01 01:00:30 alarmpi systemd[1]: Starting Samba AD Daemon...
Jan 01 01:00:31 alarmpi systemd[1]: PID file /var/run/samba.pid not readable (yet?) after start.
Jan 01 01:00:31 alarmpi systemd[1]: Started Samba AD Daemon.
Jan 01 01:00:32 alarmpi systemd[1]: samba.service: main process exited, code=exited, status=1/FAILURE
Jan 01 01:00:32 alarmpi systemd[1]: Unit samba.service entered failed state.
')
$this->bbcode_second_pass_code('', '[global]
log file = /var/log/samba/%m.log
max log size = 50
load printers = No
dns proxy = No
idmap config * : backend = tdb

[homes]
comment = Home Directories
path = /mnt/data/homes/%S
valid users = %S
read only = No
create mask = 0700
directory mask = 0700
browseable = No
')
smbd and nmbd arent working if I start samba standalone, if I do systemctl start smbd and nmbd.service, it goes up like this:
$this->bbcode_second_pass_code('', 'smbd.service - Samba SMB/CIFS server
Loaded: loaded (/usr/lib/systemd/system/smbd.service; disabled)
Active: active (running) since Fri 2013-08-09 10:18:17 CEST; 25s ago
Process: 392 ExecStart=/usr/bin/smbd -D (code=exited, status=0/SUCCESS)
Main PID: 393 (smbd)
CGroup: name=systemd:/system/smbd.service
â^Ô^Üâ^Ô^Ŕ393 /usr/bin/smbd -D
â^Ô^Ôâ^Ô^Ŕ394 /usr/bin/smbd -D

Aug 09 10:18:17 alarmpi smbd[393]: [2013/08/09 10:18:17.827654, 0] ../source3/smbd/server.c:684(smbd_open_one_socket)
Aug 09 10:18:17 alarmpi smbd[393]: smbd_open_once_socket: open_socket_in: Address family not supported by protocol
Aug 09 10:18:17 alarmpi smbd[393]: [2013/08/09 10:18:17.847379, 0] ../source3/lib/util_sock.c:423(open_socket_in)
Aug 09 10:18:17 alarmpi smbd[393]: open_socket_in(): socket() call failed: Address family not supported by protocol
Aug 09 10:18:17 alarmpi smbd[393]: [2013/08/09 10:18:17.848896, 0] ../source3/smbd/server.c:684(smbd_open_one_socket)
Aug 09 10:18:17 alarmpi smbd[393]: smbd_open_once_socket: open_socket_in: Address family not supported by protocol
Aug 09 10:18:17 alarmpi smbd[398]: [2013/08/09 10:18:17.992913, 0] ../source3/printing/print_cups.c:151(cups_connect)
Aug 09 10:18:17 alarmpi smbd[398]: Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory
Aug 09 10:18:18 alarmpi smbd[394]: [2013/08/09 10:18:18.004437, 0] ../source3/printing/print_cups.c:528(cups_async_callback)
Aug 09 10:18:18 alarmpi smbd[394]: failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL
')
$this->bbcode_second_pass_code('', 'nmbd.service - Samba NetBIOS name server
Loaded: loaded (/usr/lib/systemd/system/nmbd.service; disabled)
Active: active (running) since Fri 2013-08-09 10:18:22 CEST; 14s ago
Process: 402 ExecStart=/usr/bin/nmbd -D (code=exited, status=0/SUCCESS)
Main PID: 403 (nmbd)
CGroup: name=systemd:/system/nmbd.service
â^Ô^Ôâ^Ô^Ŕ403 /usr/bin/nmbd -D

Aug 09 10:18:22 alarmpi systemd[1]: PID file /var/run/nmbd.pid not readable (yet?) after start.
Aug 09 10:18:22 alarmpi systemd[1]: Started Samba NetBIOS name server.
')
funnyman
 
Posts: 12
Joined: Thu May 30, 2013 1:11 pm

Re: samba problem

Postby funnyman » Fri Aug 09, 2013 10:19 am

I disabled starting "samba" and enabled only smbd.service and nmbd.service.
Now I can see Raspberry in my second computer, but I cant connect to it, it fails with "you have no permission to connect"
funnyman
 
Posts: 12
Joined: Thu May 30, 2013 1:11 pm


Return to User Questions

Who is online

Users browsing this forum: No registered users and 4 guests