LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Problem with Samba (https://www.linuxquestions.org/questions/linux-newbie-8/problem-with-samba-4175658324/)

PingAn 07-31-2019 04:11 AM

Problem with Samba
 
Dear all,
I installed Samba in CentOS 7 and there is error (with Samba) when shutting down the machine. Where to find out the error?

dc.901 07-31-2019 06:09 AM

Quote:

Originally Posted by PingAn (Post 6020064)
Dear all,
I installed Samba in CentOS 7 and there is error (with Samba) when shutting down the machine. Where to find out the error?

Where/how do you see the error if you do not know where to find it? How do you know it is error with samba?

If you use systemctl to stop samba service, do you get any error?

PingAn 07-31-2019 08:33 AM

1 Attachment(s)
Please see error attached to this. Thanks.

michaelk 07-31-2019 04:39 PM

The problem is actually happening when samba starts but you only see it at shutdown.

The errors indicate that some directives in your smb.conf file are not correct or the smb.conf file itself is corrupted some how. Did you edit the file and if so how?

Please post your /etc/samba/smb.conf file but please remove all the comments i.e files that start with a ; or # characters.

PingAn 07-31-2019 10:03 PM

Thanks. Here is the file (there is actual IP or domain instead of ?)
[global]
workgroup = SAMBA
security = user

passdb backend = tdbsam

printing = cups
printcap name = cups
load printers = yes
cups options = raw
workgroup = ???.??
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
unix charset = UTF-8
dos charset = CP932
hosts allow = ?.?.?.?
security = smb01
passdb backend = ????
map to guest = Bad User
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775
[Share]
path = /home/share# shared directory
writable = yes# writable
guest ok = yes# guest allowed
guest only = yes# guest only
create mode = 0777# fully accessed file
directory mode = 0777# fully accessed directory

michaelk 08-01-2019 07:51 AM

There are directives specific to the [global] section and ones specific to the [share] section and you can use the testparm utility to verify the syntax of your smb.conf file.

Quote:

inherit acls = Yes
unix charset = UTF-8
dos charset = CP932
hosts allow = ?.?.?.?
passdb backend = ????
map to guest = Bad User
These directives belong in the [global] section and the reason for the error messages above. In addition security = smb01 is not correct. I'm not exactly sure what you are trying to accomplish but the directive should be in the [global] section. If you want to enable SMB version 1 which is not recommended, the correct syntax should be:

min procotol = SMB1

For more information see the samba guide.
https://www.samba.org/samba/docs/cur...mb.conf.5.html

PingAn 08-01-2019 11:19 PM

1 Attachment(s)
Here is current file

[global]
workgroup = SAMBA
security = user
passdb backend = tdbsam
printing = cups
printcap name = cups
load printers = yes
cups options = raw
min procotol = SMB1
# security = smb01
workgroup = ?.?
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
unix charset = UTF-8
dos charset = CP932
hosts allow = ?.?.?.?
passdb backend = ??
map to guest = Bad User
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775
[Share]# any name you like
path = /home/share# shared directory
writable = yes# writable
guest ok = yes# guest allowed
guest only = yes# guest only
create mode = 0777# fully accessed file
directory mode = 0777# fully accessed directory

but I still get attached error.

pan64 08-02-2019 01:10 AM

you did not fix the problem mentioned by michaelk (and stated in the error message you posted)

PingAn 08-02-2019 01:49 AM

1 Attachment(s)
Here is file

[global]
workgroup = SAMBA
security = user
passdb backend = tdbsam
printing = cups
printcap name = cups
load printers = yes
cups options = raw
min procotol = SMB1
# security = smb01
workgroup = ?.?
inherit acls = Yes
unix charset = UTF-8
dos charset = CP932
hosts allow = ?.?.?.*
passdb backend = ??
map to guest = Bad User
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775
[Share]# any name you like
path = /home/share# shared directory
writable = yes# writable
guest ok = yes# guest allowed
guest only = yes# guest only
create mode = 0777# fully accessed file
directory mode = 0777# fully accessed directory

and I still have got attached error below.

pan64 08-02-2019 02:59 AM

you might want to check testparm: https://www.samba.org/samba/docs/cur...estparm.1.html

michaelk 08-02-2019 07:11 AM

Once you modify the smb.conf file to manually restart samba run the command as root
systemctl start nmb
systemctl start smb


Quote:

passdb backend = ??
workgroup = ?.?
I realize your trying to hide information but there are only three available backends. tdbsam, smbpasswd or ldapsam. The default is tdbsam and is already at the top of your smb.conf file. You also already have workgroup directive and just replace SAMBA with your actual workgroup name. See below.

Quote:

workgroup = SAMBA
passdb backend = tdbsam

PingAn 08-03-2019 12:17 AM

1 Attachment(s)
Many thanks Michael.

Quote:

systemctl start nmb
systemctl start smb
Below is current smb.conf. I did change file and start it.

Quote:

[global]
workgroup = SAMBA
security = user
passdb backend = tdbsam
printing = cups
printcap name = cups
load printers = yes
cups options = raw
min procotol = SMB1
# security = smb01
inherit acls = Yes
unix charset = UTF-8
dos charset = CP932
hosts allow = ?.?.?.?
map to guest = Bad User
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775
[Share]# any name you like
path = /home/share# shared directory
writable = yes# writable
guest ok = yes# guest allowed
guest only = yes# guest only
create mode = 0777# fully accessed file
directory mode = 0777# fully accessed directory

But I still get attached error.

michaelk 08-03-2019 06:13 AM

Can not see the actual error message

systemctl -l restart smb

Or look at the log

journalctl -u smb

PingAn 08-03-2019 08:53 AM

1 Attachment(s)
Quote:

systemctl -l restart smb

Or look at the log

journalctl -u smb
Thanks. I did restart smb and please see details attached below.

michaelk 08-03-2019 09:01 AM

My fault, I misspelled protocol.

Try:
min protocol = SMB1

PingAn 08-03-2019 10:29 AM

1 Attachment(s)
Quote:

min protocol = SMB1
Thanks a lot. I did change and restarted smb. Can you see error below please?

michaelk 08-03-2019 11:25 AM

I am not sure what the status code means.

Look at /var/log/samba log files and the output of journalctl -xe

PingAn 08-04-2019 07:25 AM

Thanks.

Here are the errors

Quote:

[root@?-?-?-?-on-nets smb01]# systemctl status smb.service
● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2019-08-04 19:43:18 HKT; 34min ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 1367 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 1367 (code=exited, status=1/FAILURE)

Aug 04 19:43:16 ?-?-?-?-on-nets.com systemd[1]: Starting Samba SMB Daemon...
Aug 04 19:43:17 ?-?-?-?-on-nets.com systemd[1]: smb.service: main process exited, code=exited, sta...URE
Aug 04 19:43:18 ?-?-?-?-on-nets.com systemd[1]: Failed to start Samba SMB Daemon.
Aug 04 19:43:18 ?-?-?-?-on-nets.com systemd[1]: Unit smb.service entered failed state.
Aug 04 19:43:18 ?-?-?-?-on-nets.com systemd[1]: smb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@?-?-?-?-on-nets smb01]# systemctl -l restart smb
Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details.
[root@?-?-?-?-on-nets smb01]# journalctl -xe
Aug 04 20:12:54 ?-?-?-?-on-nets.com sshd[3702]: pam_unix(sshd:auth): authentication failure; logname= ui
Aug 04 20:12:56 ?-?-?-?-on-nets.com sshd[3702]: Failed password for invalid user earl from 219.143.153.2
Aug 04 20:12:56 ?-?-?-?-on-nets.com sshd[3702]: Received disconnect from 219.143.153.229 port 58590:11:
Aug 04 20:12:56 ?-?-?-?-on-nets.com sshd[3702]: Disconnected from 219.143.153.229 port 58590 [preauth]
Aug 04 20:17:02 ?-?-?-?-on-nets.com dbus[774]: [system] Activating service name='org.freedesktop.problem
Aug 04 20:17:02 ?-?-?-?-on-nets.com dbus[774]: [system] Successfully activated service 'org.freedesktop.
Aug 04 20:17:06 ?-?-?-?-on-nets.com gnome-shell[2653]: JS ERROR: Exception in callback for signal: posit
getCurrentRect@resource:///org/gnome/shell/ui/key
wrapper@resource:///org/gnome/gjs/modules/_legacy
_onFocusPositionChanged@resource:///org/gnome/she
wrapper@resource:///org/gnome/gjs/modules/_legacy
_emit@resource:///org/gnome/gjs/modules/signals.j
_setCurrentWindow/this._currentWindowPositionId<@
Aug 04 20:17:16 ?-?-?-?-on-nets.com su[3819]: (to root) smb01 on pts/1
Aug 04 20:17:16 ?-?-?-?-on-nets.com su[3819]: pam_unix(su:session): session opened for user root by smb0
Aug 04 20:18:37 ?-?-?-?-on-nets.com polkitd[788]: Registered Authentication Agent for unix-process:3899:
Aug 04 20:18:37 ?-?-?-?-on-nets.com systemd[1]: Starting Samba SMB Daemon...
-- Subject: Unit smb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit smb.service has begun starting up.
Aug 04 20:18:37 ?-?-?-?-on-nets.com systemd[1]: smb.service: main process exited, code=exited, status=1/
Aug 04 20:18:37 ?-?-?-?-on-nets.com systemd[1]: Failed to start Samba SMB Daemon.
-- Subject: Unit smb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit smb.service has failed.
--
-- The result is failed.
Aug 04 20:18:37 ?-?-?-?-on-nets.com systemd[1]: Unit smb.service entered failed state.
Aug 04 20:18:37 ?-?-?-?-on-nets.com systemd[1]: smb.service failed.
Aug 04 20:18:37 ?-?-?-?-on-nets.com polkitd[788]: Unregistered Authentication Agent for unix-process:389
lines 2848-2881/2881 (END)

PingAn 08-07-2019 02:49 AM

Dear all,
Any other help?

pan64 08-07-2019 02:53 AM

Dear PingAn, see post #17. Your daemon could not be started and the reason was most probably written into the log.

PingAn 08-12-2019 04:18 AM

Can you advise regarding the file below (from /var/log/samba/old)?

Quote:

[2019/08/02 07:30:27.694922, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter unix charset found in service section!
[2019/08/02 07:30:27.700453, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter dos charset found in service section!
[2019/08/02 07:30:27.700604, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter security found in service section!
[2019/08/02 07:30:27.700697, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter passdb backend found in service section!
[2019/08/02 07:30:27.703602, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter map to guest found in service section!
[2019/08/02 07:30:27.727358, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/02 17:31:15.235783, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/02 17:31:15.246022, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/02 17:31:15.257405, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 11:13:16.423808, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 11:13:16.442694, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 11:13:16.451769, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 11:19:43.333441, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 11:19:43.333791, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 11:19:43.334826, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 11:50:06.980245, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 11:50:06.990647, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 11:50:06.992345, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 12:32:18.895433, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 12:32:18.895719, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 12:32:18.896629, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 12:38:29.590202, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 12:38:29.590484, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 12:38:29.591303, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 17:40:27.320513, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 17:40:27.333378, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 17:40:27.340462, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 21:35:07.710413, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 21:35:07.728954, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 21:35:07.729806, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 21:39:12.284287, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 21:39:12.284538, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 21:39:12.285390, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 21:39:42.954037, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 21:39:42.954329, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 21:39:42.960804, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 23:13:53.674957, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 23:13:53.683312, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 23:13:53.684928, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!

PingAn 08-21-2019 08:52 PM

Dear all,
Any other help?

michaelk 08-21-2019 09:42 PM

You never fixed my spelling error

min procotol = SMB1

should be

min protocol = SMB1

Quote:

[Share]# any name you like
path = /home/share# shared directory
writable = yes# writable
guest ok = yes# guest allowed
guest only = yes# guest only
create mode = 0777# fully accessed file
directory mode = 0777# fully accessed directory
Remove the comments on each line (#...)

PingAn 08-22-2019 04:26 AM

Where did you see the wrong spelling (in which file)?

Here is my smb.conf

Quote:

[global]
workgroup = SAMBA
security = user
passdb backend = tdbsam
printing = cups
printcap name = cups
load printers = yes
cups options = raw
min protocol = SMB1
# security = smb01
inherit acls = Yes
unix charset = UTF-8
dos charset = CP932
hosts allow = ?.?.?.?
map to guest = Bad User
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775
[Share]# any name you like
path = /home/share# shared directory
writable = yes# writable
guest ok = yes# guest allowed
guest only = yes# guest only
create mode = 0777# fully accessed file
directory mode = 0777# fully accessed directory


michaelk 08-22-2019 04:55 AM

Ok that error was fixed. Now remove the comments as indicated in my previous post.

PingAn 08-22-2019 09:20 PM

I've removed all comments within smb.conf file but I've still got the following

Quote:

[root@?-?-?-?-on-nets smb01]# systemctl start smb
Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details.
[root@?-?-?-?-on-nets smb01]# systemctl status smb.service
● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2019-08-23 10:16:11 HKT; 23s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 4345 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 4345 (code=exited, status=1/FAILURE)

Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: Starting Samba SMB Daemon...
Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: smb.service: main process exited, code=exited, stat...URE
Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: Failed to start Samba SMB Daemon.
Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: Unit smb.service entered failed state.
Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: smb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@?-?-?-?-on-nets smb01]# journalctl -xe
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit nmb.service has begun starting up.
Aug 23 10:16:06 ?-?-?-?-on-nets.com systemd[1]: nmb.service: main process exited, code=exited, status=1/F
Aug 23 10:16:06 ?-?-?-?-on-nets.com systemd[1]: Failed to start Samba NMB Daemon.
-- Subject: Unit nmb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit nmb.service has failed.
--
-- The result is failed.
Aug 23 10:16:06 ?-?-?-?-on-nets.com systemd[1]: Unit nmb.service entered failed state.
Aug 23 10:16:06 ?-?-?-?-on-nets.com systemd[1]: nmb.service failed.
Aug 23 10:16:06 ?-?-?-?-on-nets.com polkitd[796]: Unregistered Authentication Agent for unix-process:4317
Aug 23 10:16:11 ?-?-?-?-on-nets.com polkitd[796]: Registered Authentication Agent for unix-process:4339:3
Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: Starting Samba SMB Daemon...
-- Subject: Unit smb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit smb.service has begun starting up.
Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: smb.service: main process exited, code=exited, status=1/F
Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: Failed to start Samba SMB Daemon.
-- Subject: Unit smb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit smb.service has failed.
--
-- The result is failed.
Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: Unit smb.service entered failed state.
Aug 23 10:16:11 ?-?-?-?-on-nets.com systemd[1]: smb.service failed.
Aug 23 10:16:11 ?-?-?-?-on-nets.com polkitd[796]: Unregistered Authentication Agent for unix-process:4339
lines 2904-2937/2937 (END)

michaelk 08-22-2019 10:12 PM

Check the logs.

PingAn 08-24-2019 08:17 AM

Sorry, which log file do you mean?

michaelk 08-24-2019 08:55 AM

/var/log/samba

PingAn 08-24-2019 10:02 AM

Sorry to that log file is empty.
Quote:

[root@?-?-?-?-on-nets samba]# ls -l
total 0
drwx------. 4 root root 30 Jul 10 14:14 cores
-rw-r--r--. 1 root root 0 Aug 12 10:25 log.nmbd
-rw-r--r--. 1 root root 0 Aug 12 10:25 log.smbd
drwx------. 2 root root 156 Aug 12 17:33 old

michaelk 08-24-2019 10:06 AM

Check the files in the old directory.

PingAn 08-24-2019 08:42 PM

Here is log.smbd-20190812

Quote:

[2019/08/02 07:30:27.694922, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter unix charset found in service section!
[2019/08/02 07:30:27.700453, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter dos charset found in service section!
[2019/08/02 07:30:27.700604, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter security found in service section!
[2019/08/02 07:30:27.700697, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter passdb backend found in service section!
[2019/08/02 07:30:27.703602, 0] ../lib/param/loadparm.c:1862(lpcfg_do_service_parameter)
Global parameter map to guest found in service section!
[2019/08/02 07:30:27.727358, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/02 17:31:15.235783, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/02 17:31:15.246022, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/02 17:31:15.257405, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 11:13:16.423808, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 11:13:16.442694, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 11:13:16.451769, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 11:19:43.333441, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 11:19:43.333791, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 11:19:43.334826, 0] ../lib/param/loadparm.c:1621(set_variable_helper)
set_variable_helper(yes# writable): value is not boolean!
[2019/08/03 11:50:06.980245, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 11:50:06.990647, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
Here is part of log.nmbd-20190812
Quote:

...
[2019/08/03 19:22:18.824364, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 172.217.218.28
[2019/08/03 19:27:20.278377, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 192.168.122.1
[2019/08/03 19:27:20.279029, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 172.217.218.28
[2019/08/03 19:27:23.107760, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2019/08/03 21:35:06.592433, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 21:35:06.604508, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 21:35:06.667359, 0] ../lib/util/become_daemon.c:138(daemon_ready)
daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/08/03 21:35:39.754912, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server LOCALHOST is now a local master browser for workgroup SAMBA on subnet 172.217.218.28

*****
[2019/08/03 21:40:59.138502, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server LOCALHOST is now a local master browser for workgroup SAMBA on subnet 192.168.122.1

*****
[2019/08/03 21:54:20.550045, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2019/08/03 23:13:52.693673, 0] ../lib/param/loadparm.c:784(lpcfg_map_parameter)
Unknown parameter encountered: "min procotol"
[2019/08/03 23:13:52.706609, 0] ../lib/param/loadparm.c:1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "min procotol"
[2019/08/03 23:13:52.780269, 0] ../lib/util/become_daemon.c:138(daemon_ready)
daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/08/03 23:14:17.297266, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 172.217.218.28
[2019/08/03 23:19:26.731197, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 192.168.122.1
[2019/08/03 23:19:26.733495, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 172.217.218.28
[2019/08/03 23:24:30.006783, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 192.168.122.1
[2019/08/03 23:24:30.007704, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 172.217.218.28
[2019/08/03 23:29:36.768487, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 192.168.122.1
[2019/08/03 23:29:36.770296, 0] ../source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
become_local_master_browser: Error - cannot find server 28-218-217-172-ON-NETS in workgroup SAMBA on subnet 172.217.218.28
[2019/08/03 23:34:24.371033, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...

michaelk 08-25-2019 07:30 PM

Nothing in the logs since 2019/08/03 and from the provided information it looked like it started ok.

Nothing to really indicate the cause of the problem. Could be permissions. What have you changed in addition to the smb.conf file?

PingAn 08-26-2019 12:43 AM

I did no change other than the adjustment against smb.conf.

John03 08-26-2019 01:35 AM

Samba issue
 
I was facing error in Samba while installing in my Centos OS. Can you please help me out.

PingAn 08-26-2019 02:24 AM

John,
Can you raise one other ticket and not to annoy this issue?

PingAn 08-29-2019 09:20 PM

Any other help to the original problem?

michaelk 09-01-2019 10:41 AM

Try starting smbd in interactive from a terminal window instead of using systemd. That might show errors that are not seen by systemd or written to the log files. As root:

smbd -i


All times are GMT -5. The time now is 07:37 PM.