Samba problem. code=exited, status=255

Support
1

Briefly describe your issue below:
This is my first post, and i need some help. I recently updated my OS, and i started getting an error which is displayed below. I am not sure of the format to compile this in, but i am sure it will be sufficient enough to figure out what the problem is, and hopefully a soulution. Please feel free to ask any additional questions. please feel free.

Here is sudo systemctl status smbd.service :

● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-12-01 19:53:28 EST; 1min 56s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 21875 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=255)
Main PID: 21875 (code=exited, status=255)

Dec 01 19:53:28 parrot systemd[1]: Starting Samba SMB Daemon…
Dec 01 19:53:28 parrot systemd[1]: smbd.service: Main process exited, code=exited, status=255/n/a
Dec 01 19:53:28 parrot systemd[1]: smbd.service: Failed with result ‘exit-code’.
Dec 01 19:53:28 parrot systemd[1]: Failed to start Samba SMB Daemon.

AND HERE IS: journalctl -xe

Dec 01 20:05:01 parrot CRON[24048]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dec 01 20:05:01 parrot CRON[24047]: pam_unix(cron:session): session closed for user root
Dec 01 20:06:21 parrot sudo[24252]: d : TTY=pts/5 ; PWD=/home/d ; USER=root ; COMMAND=/usr/sbin/service smbd
Dec 01 20:06:21 parrot sudo[24252]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 01 20:06:23 parrot systemd[1]: Starting Samba SMB Daemon…
– Subject: Unit smbd.service has begun start-up
– Defined-By: systemd
– Support: https://www.debian.org/support

– Unit smbd.service has begun starting up.
Dec 01 20:06:23 parrot systemd[1]: smbd.service: Main process exited, code=exited, status=255/n/a
Dec 01 20:06:23 parrot systemd[1]: smbd.service: Failed with result ‘exit-code’.
Dec 01 20:06:23 parrot systemd[1]: Failed to start Samba SMB Daemon.
– Subject: Unit smbd.service has failed
– Defined-By: systemd
– Support: https://www.debian.org/support

– Unit smbd.service has failed.

– The result is RESULT.
Dec 01 20:06:23 parrot sudo[24252]: pam_unix(sudo:session): session closed for user root
lines 2044-2064/2064 (END)
Dec 01 20:05:01 parrot CRON[24048]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dec 01 20:05:01 parrot CRON[24047]: pam_unix(cron:session): session closed for user root
Dec 01 20:06:21 parrot sudo[24252]: d : TTY=pts/5 ; PWD=/home/d ; USER=root ; COMMAND=/usr/sbin/service smbd start
Dec 01 20:06:21 parrot sudo[24252]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 01 20:06:23 parrot systemd[1]: Starting Samba SMB Daemon…
– Subject: Unit smbd.service has begun start-up
– Defined-By: systemd
– Support: https://www.debian.org/support

– Unit smbd.service has begun starting up.
Dec 01 20:06:23 parrot systemd[1]: smbd.service: Main process exited, code=exited, status=255/n/a
Dec 01 20:06:23 parrot systemd[1]: smbd.service: Failed with result ‘exit-code’.
Dec 01 20:06:23 parrot systemd[1]: Failed to start Samba SMB Daemon.
– Subject: Unit smbd.service has failed
– Defined-By: systemd
– Support: https://www.debian.org/support

– Unit smbd.service has failed.

– The result is RESULT.
Dec 01 20:06:23 parrot sudo[24252]: pam_unix(sudo:session): session closed for user root

What version of Parrot are you running? (uname -a:
Linux parrot 4.18.0-parrot10-amd64 #1 SMP Debian 4.18.10-1parrot10 (2018-10-06) x86_64 GNU/Linux)

What method did you use to install Parrot? (USB Flashed w/ Etcher x64)

Configured to multiboot with other systems? (yes, seperate Hard Drive on seperate SATA Port)

If there are any similar issues or solutions, link to them below: No

If there are any error messages or relevant logs, post them below: Name them.

2

If you dont need it, i wouldnt worry about it.

If you dont know if you need it: https://www.samba.org/samba/docs/current/man-html/smbd.8.html

Nevertheless i will have a look.

3

Well when i type: sudo service smbd start, it doesnt work… And i share files throughout the network.
Thank you.

4

When you start it manually does it spit out anything different?

Paste the output of testparam -s here, it will let us know if the configuration is ok.

Have you tried purging and re-installing?

5

Yes on the purging and installing. And i will as soon as I get in front of the machine. Thank you.

6

testparm -s

rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section “[homes]”
Processing section “[printers]”
Processing section “[print$]”
Processing section “[Media1]”
Processing section “[Shared]”
Loaded services file OK.
Server role: ROLE_STANDALONE

Global parameters

[global]
log file = /var/log/samba/log.%m
logging = file
map to guest = Bad User
max log size = 1000
obey pam restrictions = Yes
pam password change = Yes
panic action = /usr/share/samba/panic-action %d
passwd chat = Enter\snew\s\spassword:* %n\n Retype\snew\s\spassword:* %n\n password\supdated\ssuccessfully .
passwd program = /usr/bin/passwd %u
server role = standalone server
unix password sync = Yes
usershare allow guests = Yes
idmap config * : backend = tdb

[homes]
browseable = No
comment = Home Directories
create mask = 0700
directory mask = 0700
valid users = %S

[printers]
browseable = No
comment = All Printers
create mask = 0700
path = /var/spool/samba
printable = Yes

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers

[Media1]
guest ok = Yes
path = /home/d/Downloads
read only = No
valid users = d

[Shared]
guest ok = Yes
path = /home/d/Other/Shared/
read only = No
valid users = d

(yes the single letter username is correct)

when i start samba manually:

sudo service smbd start:
Job for smbd.service failed because the control process exited with error code.
See “systemctl status smbd.service” and “journalctl -xe” for details.
And those printeouts are above in the First post.
ALSO: Firejail has been purged, and smbd worked fine after i did that, (along with everything else) then a cuople months later it just stopped.
What is exit code 255?

7

Exit code 255 usually means the exit code was out of range (the max is 255) https://linux.die.net/abs-guide/exitcodes.html.

testparam didnt report any errors so the config should be fine.

These logs arnt giving us much to work with here, unless im blind. Check if nmbd service started ok service nmbd status.

I know logs are kept in /var/log/samba/ but i dont know if there will be any useful information in them. Might be worth having a look for obvious errors, if any.

8

It says bad user so maybe permissions problem? (I’d be mighty surprised if I saw something you didn’t lmfao but who knows I’m on my 4th espresso haha

9

nmbd.service - Samba NMB Daemon
Loaded: loaded (/lib/systemd/system/nmbd.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:nmbd(8)
man:samba(7)
man:smb.conf(5)

and the file system in /var/log/samba :
cores log.nmbd log.nmbd.5.gz log.smbd.2.gz log.wb-PARROT log.winbindd.4.gz
log. log.nmbd.1 log.owner-pc log.smbd.3.gz log.winbindd log.winbindd.5.gz
log.127.0.0.1 log.nmbd.2.gz log.parrot log.smbd.4.gz log.winbindd.1 log.winbindd.6.gz
log.192.168.128.100 log.nmbd.3.gz log.smbd log.smbd.5.gz log.winbindd.2.gz log.winbindd-idmap
log.%m log.nmbd.4.gz log.smbd.1 log.wb-BUILTIN log.winbindd.3.gz

which log would i look at? log.smbd, log.nmbd, or any of the varients?
Thank you

10

I havent tried to add another user yet, let me try that…

It wont let me add another user:

┌─[✗]─[root@parrot]─[/var/log/samba]
└──╼ #smbpasswd -a slipp
New SMB password:
Retype new SMB password:
Failed to add entry for user slipp.

11

Have a look in /var/log/samba/log.smbd

12

Here is what I got from log.smbd, (there are 6 different variations of it) I think Nico might be onto somthing about permissions problem… ???

[2018/12/02 00:28:37.582295, 0] …/source3/auth/auth_util.c:1382(make_new_session_info_guest)
create_local_token failed: NT_STATUS_ACCESS_DENIED
[2018/12/02 00:28:37.582712, 0] …/source3/smbd/server.c:2000(main)
ERROR: failed to setup guest info.
[2018/12/04 21:23:13.629747, 0] …/source3/auth/auth_util.c:1382(make_new_session_info_guest)
create_local_token failed: NT_STATUS_ACCESS_DENIED
[2018/12/04 21:23:13.630939, 0] …/source3/smbd/server.c:2000(main)
ERROR: failed to setup guest info.
[2018/12/05 11:34:28.553973, 0] …/source3/auth/auth_util.c:1382(make_new_session_info_guest)
create_local_token failed: NT_STATUS_ACCESS_DENIED
[2018/12/05 11:34:28.554933, 0] …/source3/smbd/server.c:2000(main)
ERROR: failed to setup guest info.
[2018/12/05 11:40:45.739672, 0] …/source3/auth/auth_util.c:1382(make_new_session_info_guest)
create_local_token failed: NT_STATUS_ACCESS_DENIED
[2018/12/05 11:40:45.739798, 0] …/source3/smbd/server.c:2000(main)
ERROR: failed to setup guest info.

Same thing on log.smbd.1,

Then in log.smbd.2 I got this in there:

[2018/11/20 01:54:16.673204, 0] …/lib/util/fault.c:79(fault_report)

[2018/11/20 01:54:16.673561, 0] …/lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 11 in pid 2222 (4.9.1-Debian)
Please read the Trouble-Shooting section of the Samba HOWTO
[2018/11/20 01:54:16.673604, 0] …/lib/util/fault.c:82(fault_report)

[2018/11/20 01:54:16.673637, 0] …/source3/lib/util.c:816(smb_panic_s3)
PANIC (pid 2222): internal error
[2018/11/20 01:54:16.675804, 0] …/lib/util/fault.c:261(log_stack_trace)
BACKTRACE: 12 stack frames:
#0 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(log_stack_trace+0x1f) [0x7fcb83b63cdf]
#1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fcb83420890]
#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7fcb83b63dbf]
#3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x19ff6) [0x7fcb83b63ff6]
#4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x128e0) [0x7fcb83bdb8e0]
#5 /lib/x86_64-linux-gnu/libc.so.6(+0xa11b4) [0x7fcb82cf41b4]
#6 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_memdup+0x31) [0x7fcb83b62971]
#7 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(load_interfaces+0x120) [0x7fcb83434ca0]
#8 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(reload_services+0x5e) [0x7fcb8390cc4e]
#9 /usr/sbin/smbd(main+0x579) [0x555c3027e569]
#10 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fcb82c75b17]
#11 /usr/sbin/smbd(_start+0x2a) [0x555c3027ff1a]
[2018/11/20 01:54:16.676060, 0] …/source3/lib/util.c:828(smb_panic_s3)
smb_panic(): calling panic action [/usr/share/samba/panic-action 2222]
[2018/11/20 01:54:16.682401, 0] …/source3/lib/util.c:836(smb_panic_s3)
smb_panic(): action returned status 0
[2018/11/20 01:54:16.682523, 0] …/source3/lib/dumpcore.c:315(dump_core)
dumping core in /var/log/samba/cores/smbd
[2018/11/21 10:25:56.115066, 0] …/lib/util/fault.c:79(fault_report)

[2018/11/21 10:25:56.115421, 0] …/lib/util/fault.c:80(fault_report)
INTERNAL ERROR: Signal 11 in pid 2683 (4.9.1-Debian)
Please read the Trouble-Shooting section of the Samba HOWTO
[2018/11/21 10:25:56.115465, 0] …/lib/util/fault.c:82(fault_report)

[2018/11/21 10:25:56.115497, 0] …/source3/lib/util.c:816(smb_panic_s3)
PANIC (pid 2683): internal error
[2018/11/21 10:25:56.117624, 0] …/lib/util/fault.c:261(log_stack_trace)
BACKTRACE: 12 stack frames:
#0 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(log_stack_trace+0x1f) [0x7f46c5089cdf]
#1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f46c4946890]
#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f46c5089dbf]
#3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x19ff6) [0x7f46c5089ff6]
#4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x128e0) [0x7f46c51018e0]
#5 /lib/x86_64-linux-gnu/libc.so.6(+0xa11b4) [0x7f46c421a1b4]
#6 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_memdup+0x31) [0x7f46c5088971]
#7 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(load_interfaces+0x120) [0x7f46c495aca0]
#8 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(reload_services+0x5e) [0x7f46c4e32c4e]
#9 /usr/sbin/smbd(main+0x579) [0x56077cef2569]
#10 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f46c419bb17]
#11 /usr/sbin/smbd(_start+0x2a) [0x56077cef3f1a]
[2018/11/21 10:25:56.117854, 0] …/source3/lib/util.c:828(smb_panic_s3)
smb_panic(): calling panic action [/usr/share/samba/panic-action 2683]
[2018/11/21 10:25:56.129325, 0] …/source3/lib/util.c:836(smb_panic_s3)
smb_panic(): action returned status 0
[2018/11/21 10:25:56.129505, 0] …/source3/lib/dumpcore.c:315(dump_core)
dumping core in /var/log/samba/cores/smbd
[2018/11/22 09:55:13.358496, 0] …/source3/auth/auth_util.c:1382(make_new_session_info_guest)
create_local_token failed: NT_STATUS_ACCESS_DENIED
[2018/11/22 09:55:13.360118, 0] …/source3/smbd/server.c:2000(main)
ERROR: failed to setup guest info.

THIS IS IN THERE A BIT FURTHER DOWN:

[2018/11/23 17:59:29.086993, 0] …/lib/param/loadparm.c:1016(lpcfg_service_ok)
WARNING: No path in service Shared - making it unavailable!

This is the only entry in log.smbd.3

[2018/11/15 21:51:52.076066, 0] …/lib/util/become_daemon.c:138(daemon_ready)
daemon_ready: STATUS=daemon ‘smbd’ finished starting up and ready to serve connections

and the same thing in 4 & 5 as was in 3

13

Right now we have something to work with. The ‘Bad User’ is default, but it is user/group related.

Have a look at these:
https://bugzilla.samba.org/show_bug.cgi?id=13697
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909465

I believe there are some workarounds for this issue.

14

I also vaugly remember installing zoneminder, but i couldnt get it to work, (thats when the problem started, i believe) and i am pretty sure it uses mysql. I just purged it, and the same problem occus. I’ll look at the workarounds.

Also this is what i get when i purge and re-install samba:

sudo apt-get install samba
Reading package lists… Done
Building dependency tree
Reading state information… Done
Suggested packages:
bind9 bind9utils ctdb ldb-tools ntp | chrony smbldap-tools ufw
The following NEW packages will be installed:
samba
0 upgraded, 1 newly installed, 0 to remove and 653 not upgraded.
Need to get 0 B/1,078 kB of archives.
After this operation, 16.3 MB of additional disk space will be used.
Selecting previously unselected package samba.
(Reading database … 368150 files and directories currently installed.)
Preparing to unpack …/samba_2%3a4.9.2+dfsg-1_amd64.deb …
Unpacking samba (2:4.9.2+dfsg-1) …
Processing triggers for libc-bin (2.27-6) …
Processing triggers for systemd (239-10) …
Processing triggers for man-db (2.8.4-2+b1) …
Setting up samba (2:4.9.2+dfsg-1) …
Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service
Please ignore the following error about deb-systemd-helper not finding those services.
(samba-ad-dc.service masked)
update-rc.d: smbd is in our deadpool blacklist! YOU SHALL NOT PASS!
insserv: warning: current start runlevel(s) (empty) of script smbd' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of scriptsmbd’ overrides LSB defaults (0 1 6).
update-rc.d: nmbd is in our deadpool blacklist! YOU SHALL NOT PASS!
insserv: warning: current start runlevel(s) (empty) of script nmbd' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of scriptnmbd’ overrides LSB defaults (0 1 6).
update-rc.d: We have no instructions for the samba-ad-dc init script.
update-rc.d: It looks like a network service! YOU SHALL NOT PASS!
insserv: warning: current start runlevel(s) (empty) of script samba-ad-dc' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of scriptsamba-ad-dc’ overrides LSB defaults (0 1 6).
Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → /lib/systemd/system/nmbd.service.
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service → /lib/systemd/system/smbd.service.
Processing triggers for libc-bin (2.27-6) …
Processing triggers for systemd (239-10) …
Configuring sandbox profiles…
Sandbox profiles updated!

15

Try removing Samba again through apt and install via pip after ensuring your user has permissions of samba printers etc is the next step id suggest after following what kidclown linked to
Edit actually try

firejail - - noprofile samba

16

I do not use firejail, i purged it as soon as i installed ParrotSec. It has caused me alot of problems in the past.

I looked around and found this page:
https://www.samba.org/samba/docs/current/man-html/samba-tool.8.html#idp5528432

And used this command to redo my logs so hopefully somthing will pop its head up:
“sudo samba-tool user list -d 10” and got this from terminal immediately:

sudo samba-tool user list -d 10
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
scavenger: 10
dns: 10
ldb: 10
tevent: 10
auth_audit: 10
auth_json_audit: 10
kerberos: 10
drs_repl: 10
smb2: 10
smb2_credits: 10
dsdb_audit: 10
dsdb_json_audit: 10
dsdb_password_audit: 10
dsdb_password_json_audit: 10
dsdb_transaction_audit: 10
dsdb_transaction_json_audit: 10
dsdb_group_audit: 10
dsdb_group_json_audit: 10
lpcfg_load: refreshing parameters from /etc/samba/smb.conf
Processing section “[global]”
Processing section “[homes]”
Processing section “[printers]”
Processing section “[print$]”
Processing section “[Media1]”
Processing section “[Shared]”
pm_process() returned Yes
ldb: ldb_trace_request: SEARCH
dn: @MODULES
scope: base
expr: (@LIST=*)
attr: @LIST
control:

ldb: ldb_trace_request: (tdb)->read_lock
ldb: ldb_trace_next_request: (tdb)->search
ldb: Added timed event “ltdb_callback”: 0x5585696838c0

ldb: Added timed event “ltdb_timeout”: 0x55856968cbe0

ldb: Running timer event 0x5585696838c0 “ltdb_callback”

ldb: ldb_trace_response: DONE
error: 0

ldb: ldb_trace_request: (tdb)->read_unlock
ldb: Destroying timer event 0x55856968cbe0 “ltdb_timeout”

ldb: Destroying timer event 0x5585696838c0 “ltdb_callback”

ldb: no modules required by the db
ldb: No modules specified for this database
ldb: ldb_trace_request: REGISTER_CONTROL
1.2.840.113556.1.4.1413
control:

ldb: ldb_asprintf/set_errstring: unable to find module or backend to handle operation: request
ldb: ldb_trace_request: SEARCH
dn:
scope: base
expr: (objectClass=*)
attr: rootDomainNamingContext
attr: configurationNamingContext
attr: schemaNamingContext
attr: defaultNamingContext
control:

ldb: ldb_trace_request: (tdb)->read_lock
ldb: ldb_trace_next_request: (tdb)->search
ldb: Added timed event “ltdb_callback”: 0x5585696838c0

ldb: Added timed event “ltdb_timeout”: 0x55856968cbe0

ldb: Running timer event 0x5585696838c0 “ltdb_callback”

ldb: ldb_asprintf/set_errstring: NULL Base DN invalid for a base search
ldb: ldb_trace_response: DONE
error: 34
msg: NULL Base DN invalid for a base search

ldb: ldb_trace_request: (tdb)->read_unlock
ldb: Destroying timer event 0x55856968cbe0 “ltdb_timeout”

ldb: Destroying timer event 0x5585696838c0 “ltdb_callback”

ldb_wrap open of secrets.ldb
ldb: ldb_trace_request: SEARCH
dn: cn=Primary Domains
scope: sub
expr: (&(flatname=WORKGROUP)(objectclass=primaryDomain))
attr:
control:

ldb: ldb_trace_request: (tdb)->read_lock
ldb: ldb_trace_next_request: (tdb)->search
ldb: Added timed event “ltdb_callback”: 0x55856968cbe0

ldb: Added timed event “ltdb_timeout”: 0x5585692d3a80

ldb: Running timer event 0x55856968cbe0 “ltdb_callback”

ldb: ldb_trace_response: DONE
error: 0

ldb: ldb_trace_request: (tdb)->read_unlock
ldb: Destroying timer event 0x5585692d3a80 “ltdb_timeout”

ldb: Destroying timer event 0x55856968cbe0 “ltdb_callback”

ldb: ldb_asprintf/set_errstring: dsdb_search at …/source4/dsdb/common/util.c:4702
Could not find machine account in secrets database: Failed to fetch machine account password for WORKGROUP from both secrets.ldb (Could not find entry to match filter: ‘(&(flatname=WORKGROUP)(objectclass=primaryDomain))’ base: ‘cn=Primary Domains’: No such object: dsdb_search at …/source4/dsdb/common/util.c:4702) and from /var/lib/samba/private/secrets.tdb: NT_STATUS_CANT_ACCESS_DOMAIN_INFO
Security token SIDs (1):
SID[ 0]: S-1-5-18
Privileges (0xFFFFFFFFFFFFFFFF):
Privilege[ 0]: SeMachineAccountPrivilege
Privilege[ 1]: SeTakeOwnershipPrivilege
Privilege[ 2]: SeBackupPrivilege
Privilege[ 3]: SeRestorePrivilege
Privilege[ 4]: SeRemoteShutdownPrivilege
Privilege[ 5]: SePrintOperatorPrivilege
Privilege[ 6]: SeAddUsersPrivilege
Privilege[ 7]: SeDiskOperatorPrivilege
Privilege[ 8]: SeSecurityPrivilege
Privilege[ 9]: SeSystemtimePrivilege
Privilege[ 10]: SeShutdownPrivilege
Privilege[ 11]: SeDebugPrivilege
Privilege[ 12]: SeSystemEnvironmentPrivilege
Privilege[ 13]: SeSystemProfilePrivilege
Privilege[ 14]: SeProfileSingleProcessPrivilege
Privilege[ 15]: SeIncreaseBasePriorityPrivilege
Privilege[ 16]: SeLoadDriverPrivilege
Privilege[ 17]: SeCreatePagefilePrivilege
Privilege[ 18]: SeIncreaseQuotaPrivilege
Privilege[ 19]: SeChangeNotifyPrivilege
Privilege[ 20]: SeUndockPrivilege
Privilege[ 21]: SeManageVolumePrivilege
Privilege[ 22]: SeImpersonatePrivilege
Privilege[ 23]: SeCreateGlobalPrivilege
Privilege[ 24]: SeEnableDelegationPrivilege
Rights (0x 0):
ltdb: tdb(/var/lib/samba/private/sam.ldb): tdb_open_ex: could not open file /var/lib/samba/private/sam.ldb: No such file or directory

Unable to open tdb ‘/var/lib/samba/private/sam.ldb’: No such file or directory
Failed to connect to ‘tdb:///var/lib/samba/private/sam.ldb’ with backend ‘tdb’: Unable to open tdb ‘/var/lib/samba/private/sam.ldb’: No such file or directory
ERROR(ldb): uncaught exception - Unable to open tdb ‘/var/lib/samba/private/sam.ldb’: No such file or directory
File “/usr/lib/python2.7/dist-packages/samba/netcmd/init.py”, line 177, in _run
return self.run(*args, **kwargs)
File “/usr/lib/python2.7/dist-packages/samba/netcmd/user.py”, line 485, in run
credentials=creds, lp=lp)
File “/usr/lib/python2.7/dist-packages/samba/samdb.py”, line 64, in init
options=options)
File “/usr/lib/python2.7/dist-packages/samba/init.py”, line 115, in init
self.connect(url, flags, options)
File “/usr/lib/python2.7/dist-packages/samba/samdb.py”, line 79, in connect
options=options)

Then i did this:
“sudo service smbd restart” i got this in the log.smbd

same thing in the logs… I dont know… yet… but i will.
I’m gonna check out the links that he provided me.

17

I apologize, you did say that in an earlier post. I actually have not seen very many instances (honestly any that i believe dont have any problems truly) Where the user has benefited or even not suffered inconveniences of a different kind from purging firejail instead of configuring it properly. We have made a lfew pretty substantial changes to its interaction and the balance of convenience and usability while not compromising system security as much.when was the last time you used it? Would you be open to trying it again possibly? Did you check apparmor logs yet? The you shall not pass is one of the messag s from update-rc.d, so check that and init-system-helpers. These are multipl things/places to check but id be really bamboozled if its not in one of the places @KidKlown or I have listed, simply because im, pretty sure we’ve covered everything that would do it minus the server youre using. Actually thats a good question if you dont make any progress down any of those paths; what kind of server do you use (you said you use it for files right?)?

18

If i re-install firejail, will it affect any of the programs that i have currently installed?

I am not sure what apparmor logs are. I seen the “You shall not pass” instance.

To answer your server question, just my computer that i d/l videos and I share some folders and pull video from the shared directory to vlc on FireTV Stick… (simple. :slight_smile:) or my phone, or w/e that uses samba.

I have a third machine that has ParrotSec on it and i didnt try to install ZoneMinder on, and i can serve file via Samba no problem, but my other laptop and desktop i did, and since I have had this problem. My main PC, i can re-install the OS again, and get it back to where i like it and be ok about it, but the laptop, i cant for an undisclosed reason, and i would like to get the samba working. I have since uninstalled ZoneMinder, but experiencing the same problem.

19

I would not advise going through the headache of getting fire jail all set up again and then what if it wasn’t firejail, that’s one of the reasons I like to advise clean installs to clear the possibilities a little of things that tend to rear their ugly heads bigger and badder sometime in the future. Plus I always used to make it a game of how each one was more effecient and had less errors (sometimes it took a few times to reach that metric) and it helped me understand my actual needs as well.

20

I will post this link again: :point_down:
:point_right: https://bugzilla.samba.org/show_bug.cgi?id=13697 :point_left:

2 Likes