This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!



I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!

No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

CIFS/SMB network sharing.
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

Windows 10 File Manager is no longer able to see the NAF4FREE server, nor is an Android phone that also uses CIFS/SMD. Both were working fine two days ago. I tried rebooting all three machines, and tried different CIFS/SMD settings. No luck. Then I tried an upgrade to 11.1.0.4.4994 and still no luck. I have no idea what happened. Below is my Diagnostics > Log starting from a recent Reboot. There are error messages, but I don't know were to begin. I would really appreciate any suggestions. I am technical but a noobie as far at Unix NAS4FREE is concerned. Thank you for any help you may be able to share!

Code: Select all

 Date & Time 	User 	Event
Dec 2 20:17:12	nas4free	smbd[2312]: smbd_cleanupd_unlock: Cleaning up brl and lock database after unclean shutdown
Dec 2 20:17:12	nas4free	smbd[2312]: [2017/12/02 20:17:12.920290, 1] ../source3/smbd/smbd_cleanupd.c:99(smbd_cleanupd_unlock)
Dec 2 20:17:10	nas4free	smbd[2879]: refusing to dump core
Dec 2 20:17:10	nas4free	smbd[2879]: unable to change to %N.core
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.957743, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:17:10	nas4free	smbd[2879]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:17:10	nas4free	smbd[2879]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:17:10	nas4free	smbd[2879]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: BACKTRACE: 7 stack frames:
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.957696, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:17:10	nas4free	smbd[2879]: PANIC (pid 2879): internal error
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.956896, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:17:10	nas4free	smbd[2879]: ===============================================================
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.956888, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:17:10	nas4free	smbd[2879]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:17:10	nas4free	smbd[2879]: INTERNAL ERROR: Signal 11 in pid 2879 (4.6.11)
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.956875, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:17:10	nas4free	smbd[2879]: ===============================================================
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.956847, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:17:06	nas4free	smbd[2878]: refusing to dump core
Dec 2 20:17:06	nas4free	smbd[2878]: unable to change to %N.core
Dec 2 20:17:06	nas4free	smbd[2878]: [2017/12/02 20:17:06.166241, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:17:06	nas4free	smbd[2878]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:17:06	nas4free	smbd[2878]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:17:06	nas4free	smbd[2878]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:06	nas4free	smbd[2878]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:06	nas4free	smbd[2878]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:06	nas4free	smbd[2878]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:06	nas4free	smbd[2878]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:06	nas4free	smbd[2878]: BACKTRACE: 7 stack frames:
Dec 2 20:17:06	nas4free	smbd[2878]: [2017/12/02 20:17:06.166196, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:17:06	nas4free	smbd[2878]: PANIC (pid 2878): internal error
Dec 2 20:17:06	nas4free	smbd[2878]: [2017/12/02 20:17:06.165434, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:17:06	nas4free	smbd[2878]: ===============================================================
Dec 2 20:17:06	nas4free	smbd[2878]: [2017/12/02 20:17:06.165426, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:17:06	nas4free	smbd[2878]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:17:06	nas4free	smbd[2878]: INTERNAL ERROR: Signal 11 in pid 2878 (4.6.11)
Dec 2 20:17:06	nas4free	smbd[2878]: [2017/12/02 20:17:06.165414, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:17:06	nas4free	smbd[2878]: ===============================================================
Dec 2 20:17:06	nas4free	smbd[2878]: [2017/12/02 20:17:06.165388, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:17:06	nas4free	smbd[2877]: refusing to dump core
Dec 2 20:17:06	nas4free	smbd[2877]: unable to change to %N.core
Dec 2 20:17:06	nas4free	smbd[2877]: [2017/12/02 20:17:06.156678, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:17:06	nas4free	smbd[2877]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:17:06	nas4free	smbd[2877]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:17:06	nas4free	smbd[2877]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:06	nas4free	smbd[2877]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:06	nas4free	smbd[2877]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:06	nas4free	smbd[2877]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:06	nas4free	smbd[2877]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:06	nas4free	smbd[2877]: BACKTRACE: 7 stack frames:
Dec 2 20:17:06	nas4free	smbd[2877]: [2017/12/02 20:17:06.156632, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:17:06	nas4free	smbd[2877]: PANIC (pid 2877): internal error
Dec 2 20:17:06	nas4free	smbd[2877]: [2017/12/02 20:17:06.155871, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:17:06	nas4free	smbd[2877]: ===============================================================
Dec 2 20:17:06	nas4free	smbd[2877]: [2017/12/02 20:17:06.155863, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:17:06	nas4free	smbd[2877]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:17:06	nas4free	smbd[2877]: INTERNAL ERROR: Signal 11 in pid 2877 (4.6.11)
Dec 2 20:17:06	nas4free	smbd[2877]: [2017/12/02 20:17:06.155851, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:17:06	nas4free	smbd[2877]: ===============================================================
Dec 2 20:17:06	nas4free	smbd[2877]: [2017/12/02 20:17:06.155826, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:17:06	nas4free	smbd[2876]: refusing to dump core
Dec 2 20:17:06	nas4free	smbd[2876]: unable to change to %N.core
Dec 2 20:17:06	nas4free	smbd[2876]: [2017/12/02 20:17:06.146949, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:17:06	nas4free	smbd[2876]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:17:06	nas4free	smbd[2876]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:17:06	nas4free	smbd[2876]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:06	nas4free	smbd[2876]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:06	nas4free	smbd[2876]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:06	nas4free	smbd[2876]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:06	nas4free	smbd[2876]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:06	nas4free	smbd[2876]: BACKTRACE: 7 stack frames:
Dec 2 20:17:06	nas4free	smbd[2876]: [2017/12/02 20:17:06.146903, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:17:06	nas4free	smbd[2876]: PANIC (pid 2876): internal error
Dec 2 20:17:06	nas4free	smbd[2876]: [2017/12/02 20:17:06.146129, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:17:06	nas4free	smbd[2876]: ===============================================================
Dec 2 20:17:06	nas4free	smbd[2876]: [2017/12/02 20:17:06.146121, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:17:06	nas4free	smbd[2876]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:17:06	nas4free	smbd[2876]: INTERNAL ERROR: Signal 11 in pid 2876 (4.6.11)
Dec 2 20:17:06	nas4free	smbd[2876]: [2017/12/02 20:17:06.146108, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:17:06	nas4free	smbd[2876]: ===============================================================
Dec 2 20:17:06	nas4free	smbd[2876]: [2017/12/02 20:17:06.146083, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:52	nas4free	smbd[2309]: Scheduled cleanup of brl and lock database after unclean shutdown
Dec 2 20:16:52	nas4free	smbd[2309]: [2017/12/02 20:16:52.865804, 1] ../source3/smbd/server.c:878(remove_child_pid)
Dec 2 20:16:52	nas4free	smbd[2874]: refusing to dump core
Dec 2 20:16:52	nas4free	smbd[2874]: unable to change to %N.core
Dec 2 20:16:52	nas4free	smbd[2874]: [2017/12/02 20:16:52.864124, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:52	nas4free	smbd[2874]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:52	nas4free	smbd[2874]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:52	nas4free	smbd[2874]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:52	nas4free	smbd[2874]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:52	nas4free	smbd[2874]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:52	nas4free	smbd[2874]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:52	nas4free	smbd[2874]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:52	nas4free	smbd[2874]: BACKTRACE: 7 stack frames:
Dec 2 20:16:52	nas4free	smbd[2874]: [2017/12/02 20:16:52.864077, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:52	nas4free	smbd[2874]: PANIC (pid 2874): internal error
Dec 2 20:16:52	nas4free	smbd[2874]: [2017/12/02 20:16:52.863275, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:52	nas4free	smbd[2874]: ===============================================================
Dec 2 20:16:52	nas4free	smbd[2874]: [2017/12/02 20:16:52.863267, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:52	nas4free	smbd[2874]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:52	nas4free	smbd[2874]: INTERNAL ERROR: Signal 11 in pid 2874 (4.6.11)
Dec 2 20:16:52	nas4free	smbd[2874]: [2017/12/02 20:16:52.863255, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:52	nas4free	smbd[2874]: ===============================================================
Dec 2 20:16:52	nas4free	smbd[2874]: [2017/12/02 20:16:52.863228, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:39	nas4free	proftpd[2873]: 192.168.1.10 (192.168.1.9[192.168.1.9]) - USER Anonymous: no such user found from 192.168.1.9 [192.168.1.9] to ::ffff:192.168.1.10:21
Dec 2 20:16:37	nas4free	proftpd[2872]: 192.168.1.10 (192.168.1.9[192.168.1.9]) - USER Anonymous: no such user found from 192.168.1.9 [192.168.1.9] to ::ffff:192.168.1.10:21
Dec 2 20:16:32	nas4free	smbd[2312]: smbd_cleanupd_unlock: Cleaning up brl and lock database after unclean shutdown
Dec 2 20:16:32	nas4free	smbd[2312]: [2017/12/02 20:16:32.457332, 1] ../source3/smbd/smbd_cleanupd.c:99(smbd_cleanupd_unlock)
Dec 2 20:16:17	nas4free	smbd[2871]: refusing to dump core
Dec 2 20:16:17	nas4free	smbd[2871]: unable to change to %N.core
Dec 2 20:16:17	nas4free	smbd[2871]: [2017/12/02 20:16:17.459994, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:17	nas4free	smbd[2871]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:17	nas4free	smbd[2871]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:17	nas4free	smbd[2871]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:17	nas4free	smbd[2871]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:17	nas4free	smbd[2871]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:17	nas4free	smbd[2871]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:17	nas4free	smbd[2871]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:17	nas4free	smbd[2871]: BACKTRACE: 7 stack frames:
Dec 2 20:16:17	nas4free	smbd[2871]: [2017/12/02 20:16:17.459948, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:17	nas4free	smbd[2871]: PANIC (pid 2871): internal error
Dec 2 20:16:17	nas4free	smbd[2871]: [2017/12/02 20:16:17.459202, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:17	nas4free	smbd[2871]: ===============================================================
Dec 2 20:16:17	nas4free	smbd[2871]: [2017/12/02 20:16:17.459194, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:17	nas4free	smbd[2871]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:17	nas4free	smbd[2871]: INTERNAL ERROR: Signal 11 in pid 2871 (4.6.11)
Dec 2 20:16:17	nas4free	smbd[2871]: [2017/12/02 20:16:17.459182, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:17	nas4free	smbd[2871]: ===============================================================
Dec 2 20:16:17	nas4free	smbd[2871]: [2017/12/02 20:16:17.459158, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:17	nas4free	smbd[2870]: refusing to dump core
Dec 2 20:16:17	nas4free	smbd[2870]: unable to change to %N.core
Dec 2 20:16:17	nas4free	smbd[2870]: [2017/12/02 20:16:17.450263, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:17	nas4free	smbd[2870]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:17	nas4free	smbd[2870]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:17	nas4free	smbd[2870]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:17	nas4free	smbd[2870]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:17	nas4free	smbd[2870]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:17	nas4free	smbd[2870]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:17	nas4free	smbd[2870]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:17	nas4free	smbd[2870]: BACKTRACE: 7 stack frames:
Dec 2 20:16:17	nas4free	smbd[2870]: [2017/12/02 20:16:17.450219, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:17	nas4free	smbd[2870]: PANIC (pid 2870): internal error
Dec 2 20:16:17	nas4free	smbd[2870]: [2017/12/02 20:16:17.449469, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:17	nas4free	smbd[2870]: ===============================================================
Dec 2 20:16:17	nas4free	smbd[2870]: [2017/12/02 20:16:17.449461, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:17	nas4free	smbd[2870]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:17	nas4free	smbd[2870]: INTERNAL ERROR: Signal 11 in pid 2870 (4.6.11)
Dec 2 20:16:17	nas4free	smbd[2870]: [2017/12/02 20:16:17.449449, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:17	nas4free	smbd[2870]: ===============================================================
Dec 2 20:16:17	nas4free	smbd[2870]: [2017/12/02 20:16:17.449425, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:16	nas4free	smbd[2869]: refusing to dump core
Dec 2 20:16:16	nas4free	smbd[2869]: unable to change to %N.core
Dec 2 20:16:16	nas4free	smbd[2869]: [2017/12/02 20:16:16.706252, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:16	nas4free	smbd[2869]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:16	nas4free	smbd[2869]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:16	nas4free	smbd[2869]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:16	nas4free	smbd[2869]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:16	nas4free	smbd[2869]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:16	nas4free	smbd[2869]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:16	nas4free	smbd[2869]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:16	nas4free	smbd[2869]: BACKTRACE: 7 stack frames:
Dec 2 20:16:16	nas4free	smbd[2869]: [2017/12/02 20:16:16.706208, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:16	nas4free	smbd[2869]: PANIC (pid 2869): internal error
Dec 2 20:16:16	nas4free	smbd[2869]: [2017/12/02 20:16:16.705458, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:16	nas4free	smbd[2869]: ===============================================================
Dec 2 20:16:16	nas4free	smbd[2869]: [2017/12/02 20:16:16.705450, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:16	nas4free	smbd[2869]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:16	nas4free	smbd[2869]: INTERNAL ERROR: Signal 11 in pid 2869 (4.6.11)
Dec 2 20:16:16	nas4free	smbd[2869]: [2017/12/02 20:16:16.705438, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:16	nas4free	smbd[2869]: ===============================================================
Dec 2 20:16:16	nas4free	smbd[2869]: [2017/12/02 20:16:16.705414, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:16	nas4free	smbd[2868]: refusing to dump core
Dec 2 20:16:16	nas4free	smbd[2868]: unable to change to %N.core
Dec 2 20:16:16	nas4free	smbd[2868]: [2017/12/02 20:16:16.696871, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:16	nas4free	smbd[2868]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:16	nas4free	smbd[2868]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:16	nas4free	smbd[2868]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:16	nas4free	smbd[2868]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:16	nas4free	smbd[2868]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:16	nas4free	smbd[2868]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:16	nas4free	smbd[2868]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:16	nas4free	smbd[2868]: BACKTRACE: 7 stack frames:
Dec 2 20:16:16	nas4free	smbd[2868]: [2017/12/02 20:16:16.696827, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:16	nas4free	smbd[2868]: PANIC (pid 2868): internal error
Dec 2 20:16:16	nas4free	smbd[2868]: [2017/12/02 20:16:16.696079, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:16	nas4free	smbd[2868]: ===============================================================
Dec 2 20:16:16	nas4free	smbd[2868]: [2017/12/02 20:16:16.696071, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:16	nas4free	smbd[2868]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:16	nas4free	smbd[2868]: INTERNAL ERROR: Signal 11 in pid 2868 (4.6.11)
Dec 2 20:16:16	nas4free	smbd[2868]: [2017/12/02 20:16:16.696058, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:16	nas4free	smbd[2868]: ===============================================================
Dec 2 20:16:16	nas4free	smbd[2868]: [2017/12/02 20:16:16.696034, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:15	nas4free	smbd[2867]: refusing to dump core
Dec 2 20:16:15	nas4free	smbd[2867]: unable to change to %N.core
Dec 2 20:16:15	nas4free	smbd[2867]: [2017/12/02 20:16:15.699755, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:15	nas4free	smbd[2867]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:15	nas4free	smbd[2867]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:15	nas4free	smbd[2867]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:15	nas4free	smbd[2867]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:15	nas4free	smbd[2867]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:15	nas4free	smbd[2867]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:15	nas4free	smbd[2867]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:15	nas4free	smbd[2867]: BACKTRACE: 7 stack frames:
Dec 2 20:16:15	nas4free	smbd[2867]: [2017/12/02 20:16:15.699709, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:15	nas4free	smbd[2867]: PANIC (pid 2867): internal error
Dec 2 20:16:15	nas4free	smbd[2867]: [2017/12/02 20:16:15.698962, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:15	nas4free	smbd[2867]: ===============================================================
Dec 2 20:16:15	nas4free	smbd[2867]: [2017/12/02 20:16:15.698953, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:15	nas4free	smbd[2867]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:15	nas4free	smbd[2867]: INTERNAL ERROR: Signal 11 in pid 2867 (4.6.11)
Dec 2 20:16:15	nas4free	smbd[2867]: [2017/12/02 20:16:15.698940, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:15	nas4free	smbd[2867]: ===============================================================
Dec 2 20:16:15	nas4free	smbd[2867]: [2017/12/02 20:16:15.698916, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:15	nas4free	smbd[2866]: refusing to dump core
Dec 2 20:16:15	nas4free	smbd[2866]: unable to change to %N.core
Dec 2 20:16:15	nas4free	smbd[2866]: [2017/12/02 20:16:15.689042, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:15	nas4free	smbd[2866]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:15	nas4free	smbd[2866]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:15	nas4free	smbd[2866]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:15	nas4free	smbd[2866]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:15	nas4free	smbd[2866]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:15	nas4free	smbd[2866]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:15	nas4free	smbd[2866]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:15	nas4free	smbd[2866]: BACKTRACE: 7 stack frames:
Dec 2 20:16:15	nas4free	smbd[2866]: [2017/12/02 20:16:15.688997, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:15	nas4free	smbd[2866]: PANIC (pid 2866): internal error
Dec 2 20:16:15	nas4free	smbd[2866]: [2017/12/02 20:16:15.688243, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:15	nas4free	smbd[2866]: ===============================================================
Dec 2 20:16:15	nas4free	smbd[2866]: [2017/12/02 20:16:15.688235, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:15	nas4free	smbd[2866]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:15	nas4free	smbd[2866]: INTERNAL ERROR: Signal 11 in pid 2866 (4.6.11)
Dec 2 20:16:15	nas4free	smbd[2866]: [2017/12/02 20:16:15.688223, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:15	nas4free	smbd[2866]: ===============================================================
Dec 2 20:16:15	nas4free	smbd[2866]: [2017/12/02 20:16:15.688198, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:14	nas4free	smbd[2865]: refusing to dump core
Dec 2 20:16:14	nas4free	smbd[2865]: unable to change to %N.core
Dec 2 20:16:14	nas4free	smbd[2865]: [2017/12/02 20:16:14.196864, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:14	nas4free	smbd[2865]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:14	nas4free	smbd[2865]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:14	nas4free	smbd[2865]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:14	nas4free	smbd[2865]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:14	nas4free	smbd[2865]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:14	nas4free	smbd[2865]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:14	nas4free	smbd[2865]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:14	nas4free	smbd[2865]: BACKTRACE: 7 stack frames:
Dec 2 20:16:14	nas4free	smbd[2865]: [2017/12/02 20:16:14.196816, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:14	nas4free	smbd[2865]: PANIC (pid 2865): internal error
Dec 2 20:16:14	nas4free	smbd[2865]: [2017/12/02 20:16:14.196061, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:14	nas4free	smbd[2865]: ===============================================================
Dec 2 20:16:14	nas4free	smbd[2865]: [2017/12/02 20:16:14.196052, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:14	nas4free	smbd[2865]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:14	nas4free	smbd[2865]: INTERNAL ERROR: Signal 11 in pid 2865 (4.6.11)
Dec 2 20:16:14	nas4free	smbd[2865]: [2017/12/02 20:16:14.196040, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:14	nas4free	smbd[2865]: ===============================================================
Dec 2 20:16:14	nas4free	smbd[2865]: [2017/12/02 20:16:14.196016, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:14	nas4free	smbd[2864]: refusing to dump core
Dec 2 20:16:14	nas4free	smbd[2864]: unable to change to %N.core
Dec 2 20:16:14	nas4free	smbd[2864]: [2017/12/02 20:16:14.185502, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:14	nas4free	smbd[2864]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:14	nas4free	smbd[2864]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:14	nas4free	smbd[2864]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:14	nas4free	smbd[2864]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:14	nas4free	smbd[2864]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:14	nas4free	smbd[2864]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:14	nas4free	smbd[2864]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:14	nas4free	smbd[2864]: BACKTRACE: 7 stack frames:
Dec 2 20:16:14	nas4free	smbd[2864]: [2017/12/02 20:16:14.185457, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:14	nas4free	smbd[2864]: PANIC (pid 2864): internal error
Dec 2 20:16:14	nas4free	smbd[2864]: [2017/12/02 20:16:14.184706, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:14	nas4free	smbd[2864]: ===============================================================
Dec 2 20:16:14	nas4free	smbd[2864]: [2017/12/02 20:16:14.184698, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:14	nas4free	smbd[2864]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:14	nas4free	smbd[2864]: INTERNAL ERROR: Signal 11 in pid 2864 (4.6.11)
Dec 2 20:16:14	nas4free	smbd[2864]: [2017/12/02 20:16:14.184686, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:14	nas4free	smbd[2864]: ===============================================================
Dec 2 20:16:14	nas4free	smbd[2864]: [2017/12/02 20:16:14.184662, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:12	nas4free	smbd[2863]: refusing to dump core
Dec 2 20:16:12	nas4free	smbd[2863]: unable to change to %N.core
Dec 2 20:16:12	nas4free	smbd[2863]: [2017/12/02 20:16:12.262420, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:12	nas4free	smbd[2863]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:12	nas4free	smbd[2863]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:12	nas4free	smbd[2863]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:12	nas4free	smbd[2863]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:12	nas4free	smbd[2863]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:12	nas4free	smbd[2863]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:12	nas4free	smbd[2863]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:12	nas4free	smbd[2863]: BACKTRACE: 7 stack frames:
Dec 2 20:16:12	nas4free	smbd[2863]: [2017/12/02 20:16:12.262374, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:12	nas4free	smbd[2863]: PANIC (pid 2863): internal error
Dec 2 20:16:12	nas4free	smbd[2863]: [2017/12/02 20:16:12.261620, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:12	nas4free	smbd[2863]: ===============================================================
Dec 2 20:16:12	nas4free	smbd[2863]: [2017/12/02 20:16:12.261612, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:12	nas4free	smbd[2863]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:12	nas4free	smbd[2863]: INTERNAL ERROR: Signal 11 in pid 2863 (4.6.11)
Dec 2 20:16:12	nas4free	smbd[2863]: [2017/12/02 20:16:12.261599, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:12	nas4free	smbd[2863]: ===============================================================
Dec 2 20:16:12	nas4free	smbd[2863]: [2017/12/02 20:16:12.261574, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:12	nas4free	smbd[2862]: refusing to dump core
Dec 2 20:16:12	nas4free	smbd[2862]: unable to change to %N.core
Dec 2 20:16:12	nas4free	smbd[2862]: [2017/12/02 20:16:12.251277, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:12	nas4free	smbd[2862]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:12	nas4free	smbd[2862]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:12	nas4free	smbd[2862]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:12	nas4free	smbd[2862]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:12	nas4free	smbd[2862]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:12	nas4free	smbd[2862]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:12	nas4free	smbd[2862]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:12	nas4free	smbd[2862]: BACKTRACE: 7 stack frames:
Dec 2 20:16:12	nas4free	smbd[2862]: [2017/12/02 20:16:12.251231, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:12	nas4free	smbd[2862]: PANIC (pid 2862): internal error
Dec 2 20:16:12	nas4free	smbd[2862]: [2017/12/02 20:16:12.250465, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:12	nas4free	smbd[2862]: ===============================================================
Dec 2 20:16:12	nas4free	smbd[2862]: [2017/12/02 20:16:12.250457, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:12	nas4free	smbd[2862]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:12	nas4free	smbd[2862]: INTERNAL ERROR: Signal 11 in pid 2862 (4.6.11)
Dec 2 20:16:12	nas4free	smbd[2862]: [2017/12/02 20:16:12.250445, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:12	nas4free	smbd[2862]: ===============================================================
Dec 2 20:16:12	nas4free	smbd[2862]: [2017/12/02 20:16:12.250420, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:16:12	nas4free	smbd[2309]: Scheduled cleanup of brl and lock database after unclean shutdown
Dec 2 20:16:12	nas4free	smbd[2309]: [2017/12/02 20:16:12.241229, 1] ../source3/smbd/server.c:878(remove_child_pid)
Dec 2 20:16:12	nas4free	smbd[2860]: refusing to dump core
Dec 2 20:16:12	nas4free	smbd[2860]: unable to change to %N.core
Dec 2 20:16:12	nas4free	smbd[2860]: [2017/12/02 20:16:12.238839, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:16:12	nas4free	smbd[2860]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:16:12	nas4free	smbd[2860]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:16:12	nas4free	smbd[2860]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:12	nas4free	smbd[2860]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:12	nas4free	smbd[2860]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:16:12	nas4free	smbd[2860]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:12	nas4free	smbd[2860]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:16:12	nas4free	smbd[2860]: BACKTRACE: 7 stack frames:
Dec 2 20:16:12	nas4free	smbd[2860]: [2017/12/02 20:16:12.238790, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:16:12	nas4free	smbd[2860]: PANIC (pid 2860): internal error
Dec 2 20:16:12	nas4free	smbd[2860]: [2017/12/02 20:16:12.237887, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:16:12	nas4free	smbd[2860]: ===============================================================
Dec 2 20:16:12	nas4free	smbd[2860]: [2017/12/02 20:16:12.237879, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:16:12	nas4free	smbd[2860]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:16:12	nas4free	smbd[2860]: INTERNAL ERROR: Signal 11 in pid 2860 (4.6.11)
Dec 2 20:16:12	nas4free	smbd[2860]: [2017/12/02 20:16:12.237866, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:12	nas4free	smbd[2860]: ===============================================================
Dec 2 20:16:12	nas4free	smbd[2860]: [2017/12/02 20:16:12.237837, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:15:27	nas4free	nmbd[2307]: *****
Dec 2 20:15:27	nas4free	nmbd[2307]:
Dec 2 20:15:27	nas4free	nmbd[2307]: Samba name server NAS4FREE is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.10
Dec 2 20:15:27	nas4free	nmbd[2307]:
Dec 2 20:15:27	nas4free	nmbd[2307]: *****
Dec 2 20:15:27	nas4free	nmbd[2307]: [2017/12/02 20:15:27.506299, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Dec 2 20:15:12	nas4free	nmbd[2307]: *****
Dec 2 20:15:12	nas4free	nmbd[2307]:
Dec 2 20:15:12	nas4free	nmbd[2307]: Samba server NAS4FREE is now a domain master browser for workgroup WORKGROUP on subnet 192.168.1.10
Dec 2 20:15:12	nas4free	nmbd[2307]:
Dec 2 20:15:12	nas4free	nmbd[2307]: *****
Dec 2 20:15:12	nas4free	nmbd[2307]: [2017/12/02 20:15:12.092355, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2)
Dec 2 20:15:04	nas4free	login: pam_winbind(login): PAM_REINITIALIZE_CRED not implemented
Dec 2 20:15:04	nas4free	login: pam_winbind(login): PAM_REINITIALIZE_CRED not implemented
Dec 2 20:15:04	nas4free	login: login on ttyv0 as root
Dec 2 20:15:04	nas4free	lighttpd[2634]: (server.c.1412) server started (lighttpd/1.4.48)
Dec 2 20:15:04	nas4free	winbindd[2314]: unable to initialize domain list
Dec 2 20:15:04	nas4free	winbindd[2314]: [2017/12/02 20:15:04.036437, 0] ../source3/winbindd/winbindd.c:1402(winbindd_register_handlers)
Dec 2 20:15:04	nas4free	winbindd[2314]: Could not fetch our SID - did we join?
Dec 2 20:15:04	nas4free	winbindd[2314]: [2017/12/02 20:15:04.036421, 0] ../source3/winbindd/winbindd_util.c:893(init_domain_list)
Dec 2 20:15:04	nas4free	winbindd[2314]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Dec 2 20:15:04	nas4free	winbindd[2314]: [2017/12/02 20:15:04.035405, 0] ../source3/winbindd/winbindd_cache.c:3171(initialize_winbindd_cache)
Dec 2 20:15:03	nas4free	smbd[2309]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Dec 2 20:15:03	nas4free	smbd[2309]: [2017/12/02 20:15:03.997515, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Dec 2 20:15:03	nas4free	smbd[2309]: file_init_global: Information only: requested 929709 open files, 59392 are available.
Dec 2 20:15:03	nas4free	smbd[2309]: [2017/12/02 20:15:03.994136, 1] ../source3/smbd/files.c:218(file_init_global)
Dec 2 20:15:03	nas4free	smbd[2308]: INFO: Profiling support unavailable in this build.
Dec 2 20:15:03	nas4free	smbd[2308]: [2017/12/02 20:15:03.983858, 1] ../source3/profile/profile_dummy.c:30(set_profile_level)
Dec 2 20:15:03	nas4free	nmbd[2307]: become_domain_master_browser_bcast: querying subnet 192.168.1.10 for domain master browser on workgroup WORKGROUP
Dec 2 20:15:03	nas4free	nmbd[2307]: [2017/12/02 20:15:03.924796, 0] ../source3/nmbd/nmbd_become_dmb.c:307(become_domain_master_browser_bcast)
Dec 2 20:15:03	nas4free	nmbd[2307]: Attempting to become domain master browser on workgroup WORKGROUP on subnet 192.168.1.10
Dec 2 20:15:03	nas4free	nmbd[2307]: become_domain_master_browser_bcast:
Dec 2 20:15:03	nas4free	nmbd[2307]: [2017/12/02 20:15:03.924777, 0] ../source3/nmbd/nmbd_become_dmb.c:294(become_domain_master_browser_bcast)
Dec 2 20:15:03	nas4free	nmbd[2307]: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Dec 2 20:15:03	nas4free	nmbd[2307]: [2017/12/02 20:15:03.924589, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Dec 2 20:15:00	nas4free	proftpd[2120]: 192.168.1.10 - ProFTPD 1.3.6 (stable) (built Fri Dec 1 2017 16:52:33 CET) standalone mode STARTUP
Dec 2 20:14:53	nas4free	kernel: igb0: link state changed to UP
Dec 2 20:14:53	nas4free	kernel: igb0: link state changed to DOWN
Dec 2 20:14:53	nas4free	kernel: igb0: link state changed to UP
Dec 2 20:14:53	nas4free	kernel: Trying to mount root from ufs:/dev/md0 []...
Dec 2 20:14:53	nas4free	kernel: random: unblocking device.
Dec 2 20:14:53	nas4free	kernel: ada5: 3815447MB (7814037168 512 byte sectors)
Dec 2 20:14:53	nas4free	kernel: ada5: Command Queueing enabled
Dec 2 20:14:53	nas4free	kernel: ada5: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Dec 2 20:14:53	nas4free	kernel: ada5: Serial Number WD-WCC131143154
Dec 2 20:14:53	nas4free	kernel: ada5: <WDC WD4000F9YZ-09N20L0 01.01A01> ATA8-ACS SATA 3.x device
Dec 2 20:14:53	nas4free	kernel: ada5 at ahcich8 bus 0 scbus8 target 0 lun 0
Dec 2 20:14:53	nas4free	kernel: ada4: 3815447MB (7814037168 512 byte sectors)
Dec 2 20:14:53	nas4free	kernel: ada4: Command Queueing enabled
Dec 2 20:14:53	nas4free	kernel: ada4: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Dec 2 20:14:53	nas4free	kernel: ada4: Serial Number WD-WCC131129868
Dec 2 20:14:53	nas4free	kernel: ada4: <WDC WD4000F9YZ-09N20L0 01.01A01> ATA8-ACS SATA 3.x device
Dec 2 20:14:53	nas4free	kernel: ada4 at ahcich7 bus 0 scbus7 target 0 lun 0
Dec 2 20:14:53	nas4free	kernel: ada3: 3815447MB (7814037168 512 byte sectors)
Dec 2 20:14:53	nas4free	kernel: ada3: Command Queueing enabled
Dec 2 20:14:53	nas4free	kernel: ada3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Dec 2 20:14:53	nas4free	kernel: ada3: Serial Number WD-WCC131124597
Dec 2 20:14:53	nas4free	kernel: ada3: <WDC WD4000F9YZ-09N20L0 01.01A01> ATA8-ACS SATA 3.x device
Dec 2 20:14:53	nas4free	kernel: ada3 at ahcich6 bus 0 scbus6 target 0 lun 0
Dec 2 20:14:53	nas4free	kernel: ada2: 3815447MB (7814037168 512 byte sectors)
Dec 2 20:14:53	nas4free	kernel: ada2: Command Queueing enabled
Dec 2 20:14:53	nas4free	kernel: ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Dec 2 20:14:53	nas4free	kernel: ada2: Serial Number WD-WCC131142430
Dec 2 20:14:53	nas4free	kernel: ada2: <WDC WD4000F9YZ-09N20L0 01.01A01> ATA8-ACS SATA 3.x device
Dec 2 20:14:53	nas4free	kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
Dec 2 20:14:53	nas4free	kernel: cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)
Dec 2 20:14:53	nas4free	kernel: cd0: Serial Number 3524602 278339509783
Dec 2 20:14:53	nas4free	kernel: cd0: <ATAPI iHAS124 W HL0F> Removable CD-ROM SCSI device
Dec 2 20:14:53	nas4free	kernel: ada2 at ahcich5 bus 0 scbus5 target 0 lun 0
Dec 2 20:14:53	nas4free	kernel: ada1: 3815447MB (7814037168 512 byte sectors)
Dec 2 20:14:53	nas4free	kernel: ada1: Command Queueing enabled
Dec 2 20:14:53	nas4free	kernel: ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Dec 2 20:14:53	nas4free	kernel: ada1: Serial Number WD-WCC131770050
Dec 2 20:14:53	nas4free	kernel: ada1: <WDC WD4000F9YZ-09N20L0 01.01A01> ATA8-ACS SATA 3.x device
Dec 2 20:14:53	nas4free	kernel: cd0 at ahcich1 bus 0 scbus1 target 0 lun 0
Dec 2 20:14:53	nas4free	kernel: ada1 at ahcich4 bus 0 scbus4 target 0 lun 0
Dec 2 20:14:53	nas4free	kernel: ada0: 30533MB (62533296 512 byte sectors)
Dec 2 20:14:53	nas4free	kernel: ada0: Command Queueing enabled
Dec 2 20:14:53	nas4free	kernel: ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
Dec 2 20:14:53	nas4free	kernel: ada0: Serial Number 133933400727
Dec 2 20:14:53	nas4free	kernel: ada0: <SanDisk SDSSDRC032G 3.0.0> ACS-2 ATA SATA 3.x device
Dec 2 20:14:53	nas4free	kernel: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
Dec 2 20:14:53	nas4free	kernel: ses0: SEMB SES Device
Dec 2 20:14:53	nas4free	kernel: ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
Dec 2 20:14:53	nas4free	kernel: ses0 at ahciem0 bus 0 scbus9 target 0 lun 0
Dec 2 20:14:53	nas4free	kernel: uhub2: 8 ports with 8 removable, self powered
Dec 2 20:14:53	nas4free	kernel: uhub3: 6 ports with 6 removable, self powered
Dec 2 20:14:53	nas4free	kernel: uhub3: <vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.04, addr 2> on usbus0
Dec 2 20:14:53	nas4free	kernel: uhub3 on uhub1
Dec 2 20:14:53	nas4free	kernel: ugen0.2: <vendor 0x8087 product 0x8008> at usbus0
Dec 2 20:14:53	nas4free	kernel: uhub2: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.04, addr 2> on usbus1
Dec 2 20:14:53	nas4free	kernel: uhub2 on uhub0
Dec 2 20:14:53	nas4free	kernel: ugen1.2: <vendor 0x8087 product 0x8000> at usbus1
Dec 2 20:14:53	nas4free	kernel: uhub1: 2 ports with 2 removable, self powered
Dec 2 20:14:53	nas4free	kernel: uhub0: 2 ports with 2 removable, self powered
Dec 2 20:14:53	nas4free	kernel: uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
Dec 2 20:14:53	nas4free	kernel: uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Dec 2 20:14:53	nas4free	kernel: ugen0.1: <Intel EHCI root HUB> at usbus0
Dec 2 20:14:53	nas4free	kernel: ugen1.1: <Intel EHCI root HUB> at usbus1
Dec 2 20:14:53	nas4free	kernel: pcm2: <Realtek ALC1150 (Rear Digital)> at nid 30 on hdaa0
Dec 2 20:14:53	nas4free	kernel: pcm1: <Realtek ALC1150 (Front Analog)> at nid 27 and 25 on hdaa0
Dec 2 20:14:53	nas4free	kernel: pcm0: <Realtek ALC1150 (Rear Analog 5.1/2.0)> at nid 20,22,21 and 24,26 on hdaa0
Dec 2 20:14:53	nas4free	kernel: hdaa0: <Realtek ALC1150 Audio Function Group> at nid 1 on hdacc0
Dec 2 20:14:53	nas4free	kernel: hdacc0: <Realtek ALC1150 HDA CODEC> at cad 0 on hdac0
Dec 2 20:14:53	nas4free	kernel: nvme cam probe device init
Dec 2 20:14:53	nas4free	kernel: iSCSI boot driver version 0.2.13
Dec 2 20:14:53	nas4free	kernel: Timecounters tick every 1.000 msec
Dec 2 20:14:53	nas4free	kernel: ZFS storage pool version: features support (5000)
Dec 2 20:14:53	nas4free	kernel: ZFS filesystem version: 5
Dec 2 20:14:53	nas4free	kernel: p4tcc3: <CPU Frequency Thermal Control> on cpu3
Dec 2 20:14:53	nas4free	kernel: est3: <Enhanced SpeedStep Frequency Control> on cpu3
Dec 2 20:14:53	nas4free	kernel: coretemp3: <CPU On-Die Thermal Sensors> on cpu3
Dec 2 20:14:53	nas4free	kernel: p4tcc2: <CPU Frequency Thermal Control> on cpu2
Dec 2 20:14:53	nas4free	kernel: est2: <Enhanced SpeedStep Frequency Control> on cpu2
Dec 2 20:14:53	nas4free	kernel: coretemp2: <CPU On-Die Thermal Sensors> on cpu2
Dec 2 20:14:53	nas4free	kernel: p4tcc1: <CPU Frequency Thermal Control> on cpu1
Dec 2 20:14:53	nas4free	kernel: est1: <Enhanced SpeedStep Frequency Control> on cpu1
Dec 2 20:14:53	nas4free	kernel: coretemp1: <CPU On-Die Thermal Sensors> on cpu1
Dec 2 20:14:53	nas4free	kernel: p4tcc0: <CPU Frequency Thermal Control> on cpu0
Dec 2 20:14:53	nas4free	kernel: est0: <Enhanced SpeedStep Frequency Control> on cpu0
Dec 2 20:14:53	nas4free	kernel: coretemp0: <CPU On-Die Thermal Sensors> on cpu0
Dec 2 20:14:53	nas4free	kernel: ppc0: cannot reserve I/O port range
Dec 2 20:14:53	nas4free	kernel: atkbd0: [GIANT-LOCKED]
Dec 2 20:14:53	nas4free	kernel: kbd0 at atkbd0
Dec 2 20:14:53	nas4free	kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Dec 2 20:14:53	nas4free	kernel: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
Dec 2 20:14:53	nas4free	kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Dec 2 20:14:53	nas4free	kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Dec 2 20:14:53	nas4free	kernel: sc0: <System console> at flags 0x100 on isa0
Dec 2 20:14:53	nas4free	kernel: orm0: <ISA Option ROMs> at iomem 0xc0000-0xccfff,0xcd000-0xcffff on isa0
Dec 2 20:14:53	nas4free	kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Dec 2 20:14:53	nas4free	kernel: acpi_button0: <Power Button> on acpi0
Dec 2 20:14:53	nas4free	kernel: ahciem0: <AHCI enclosure management bridge> on ahci2
Dec 2 20:14:53	nas4free	kernel: ahcich8: <AHCI channel> at channel 4 on ahci2
Dec 2 20:14:53	nas4free	kernel: ahcich7: <AHCI channel> at channel 3 on ahci2
Dec 2 20:14:53	nas4free	kernel: ahcich6: <AHCI channel> at channel 2 on ahci2
Dec 2 20:14:53	nas4free	kernel: ahcich5: <AHCI channel> at channel 1 on ahci2
Dec 2 20:14:53	nas4free	kernel: ahcich4: <AHCI channel> at channel 0 on ahci2
Dec 2 20:14:53	nas4free	kernel: ahci2: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
Dec 2 20:14:53	nas4free	kernel: ahci2: <Intel Lynx Point AHCI SATA controller> port 0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xf6706000-0xf67067ff irq 19 at device 31.2 on pci0
Dec 2 20:14:53	nas4free	kernel: isa0: <ISA bus> on isab0
Dec 2 20:14:53	nas4free	kernel: isab0: <PCI-ISA bridge> at device 31.0 on pci0
Dec 2 20:14:53	nas4free	kernel: usbus1: 480Mbps High Speed USB v2.0
Dec 2 20:14:53	nas4free	kernel: usbus1 on ehci1
Dec 2 20:14:53	nas4free	kernel: usbus1: EHCI version 1.0
Dec 2 20:14:53	nas4free	kernel: ehci1: <Intel Lynx Point USB 2.0 controller USB-A> mem 0xf6707000-0xf67073ff irq 23 at device 29.0 on pci0
Dec 2 20:14:53	nas4free	kernel: pci14: <ACPI PCI bus> on pcib14
Dec 2 20:14:53	nas4free	kernel: pcib14: <ACPI PCI-PCI bridge> irq 16 at device 9.0 on pci6
Dec 2 20:14:53	nas4free	kernel: pci13: <ACPI PCI bus> on pcib13
Dec 2 20:14:53	nas4free	kernel: pcib13: <ACPI PCI-PCI bridge> irq 19 at device 0.0 on pci12
Dec 2 20:14:53	nas4free	kernel: pci12: <ACPI PCI bus> on pcib12
Dec 2 20:14:53	nas4free	kernel: pcib12: <ACPI PCI-PCI bridge> irq 19 at device 8.0 on pci6
Dec 2 20:14:53	nas4free	kernel: pci11: <ACPI PCI bus> on pcib11
Dec 2 20:14:53	nas4free	kernel: pcib11: <ACPI PCI-PCI bridge> irq 18 at device 7.0 on pci6
Dec 2 20:14:53	nas4free	kernel: pci10: <ACPI PCI bus> on pcib10
Dec 2 20:14:53	nas4free	kernel: pcib10: <ACPI PCI-PCI bridge> irq 17 at device 6.0 on pci6
Dec 2 20:14:53	nas4free	kernel: pci9: <ACPI PCI bus> on pcib9
Dec 2 20:14:53	nas4free	kernel: pcib9: <ACPI PCI-PCI bridge> irq 16 at device 5.0 on pci6
Dec 2 20:14:53	nas4free	kernel: igb1: netmap queues/slots: TX 4/1024, RX 4/1024
Dec 2 20:14:53	nas4free	kernel: igb1: Bound queue 3 to cpu 3
Dec 2 20:14:53	nas4free	kernel: igb1: Bound queue 2 to cpu 2
Dec 2 20:14:53	nas4free	kernel: igb1: Bound queue 1 to cpu 1
Dec 2 20:14:53	nas4free	kernel: igb1: Bound queue 0 to cpu 0
Dec 2 20:14:53	nas4free	kernel: igb1: Ethernet address: bc:5f:f4:cb:2d:27
Dec 2 20:14:53	nas4free	kernel: igb1: Using MSIX interrupts with 5 vectors
Dec 2 20:14:53	nas4free	kernel: igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0x9000-0x901f mem 0xf6100000-0xf617ffff,0xf6180000-0xf6183fff irq 19 at device 0.0 on pci8
Dec 2 20:14:53	nas4free	kernel: pci8: <ACPI PCI bus> on pcib8
Dec 2 20:14:53	nas4free	kernel: pcib8: <ACPI PCI-PCI bridge> irq 19 at device 4.0 on pci6
Dec 2 20:14:53	nas4free	kernel: pci7: <serial bus, FireWire> at device 0.0 (no driver attached)
Dec 2 20:14:53	nas4free	kernel: pci7: <ACPI PCI bus> on pcib7
Dec 2 20:14:53	nas4free	kernel: pcib7: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci6
Dec 2 20:14:53	nas4free	kernel: pci6: <ACPI PCI bus> on pcib6
Dec 2 20:14:53	nas4free	kernel: pcib6: <ACPI PCI-PCI bridge> mem 0xf6300000-0xf631ffff irq 19 at device 0.0 on pci5
Dec 2 20:14:53	nas4free	kernel: pci5: <ACPI PCI bus> on pcib5
Dec 2 20:14:53	nas4free	kernel: pcib5: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
Dec 2 20:14:53	nas4free	kernel: igb0: netmap queues/slots: TX 4/1024, RX 4/1024
Dec 2 20:14:53	nas4free	kernel: igb0: Bound queue 3 to cpu 3
Dec 2 20:14:53	nas4free	kernel: igb0: Bound queue 2 to cpu 2
Dec 2 20:14:53	nas4free	kernel: igb0: Bound queue 1 to cpu 1
Dec 2 20:14:53	nas4free	kernel: igb0: Bound queue 0 to cpu 0
Dec 2 20:14:53	nas4free	kernel: igb0: Ethernet address: bc:5f:f4:cb:2d:25
Dec 2 20:14:53	nas4free	kernel: igb0: Using MSIX interrupts with 5 vectors
Dec 2 20:14:53	nas4free	kernel: igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb000-0xb01f mem 0xf6400000-0xf647ffff,0xf6480000-0xf6483fff irq 18 at device 0.0 on pci4
Dec 2 20:14:53	nas4free	kernel: pci4: <ACPI PCI bus> on pcib4
Dec 2 20:14:53	nas4free	kernel: pcib4: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
Dec 2 20:14:53	nas4free	kernel: ahcich3: <AHCI channel> at channel 1 on ahci1
Dec 2 20:14:53	nas4free	kernel: ahcich2: <AHCI channel> at channel 0 on ahci1
Dec 2 20:14:53	nas4free	kernel: ahci1: AHCI v1.00 with 2 6Gbps ports, Port Multiplier supported with FBS
Dec 2 20:14:53	nas4free	kernel: ahci1: <Marvell 88SE9172 AHCI SATA controller> port 0xc040-0xc047,0xc030-0xc033,0xc020-0xc027,0xc010-0xc013,0xc000-0xc00f mem 0xf6510000-0xf65101ff irq 17 at device 0.0 on pci3
Dec 2 20:14:53	nas4free	kernel: pci3: <ACPI PCI bus> on pcib3
Dec 2 20:14:53	nas4free	kernel: pcib3: <ACPI PCI-PCI bridge> irq 17 at device 28.1 on pci0
Dec 2 20:14:53	nas4free	kernel: ahcich1: <AHCI channel> at channel 1 on ahci0
Dec 2 20:14:53	nas4free	kernel: ahcich0: <AHCI channel> at channel 0 on ahci0
Dec 2 20:14:53	nas4free	kernel: ahci0: AHCI v1.00 with 2 6Gbps ports, Port Multiplier supported with FBS
Dec 2 20:14:53	nas4free	kernel: ahci0: <Marvell 88SE9172 AHCI SATA controller> port 0xd040-0xd047,0xd030-0xd033,0xd020-0xd027,0xd010-0xd013,0xd000-0xd00f mem 0xf6610000-0xf66101ff irq 16 at device 0.0 on pci2
Dec 2 20:14:53	nas4free	kernel: pci2: <ACPI PCI bus> on pcib2
Dec 2 20:14:53	nas4free	kernel: pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
Dec 2 20:14:53	nas4free	kernel: hdac0: <Intel Lynx Point HDA Controller> mem 0xf6700000-0xf6703fff irq 22 at device 27.0 on pci0
Dec 2 20:14:53	nas4free	kernel: usbus0: 480Mbps High Speed USB v2.0
Dec 2 20:14:53	nas4free	kernel: usbus0 on ehci0
Dec 2 20:14:53	nas4free	kernel: usbus0: EHCI version 1.0
Dec 2 20:14:53	nas4free	kernel: ehci0: <Intel Lynx Point USB 2.0 controller USB-B> mem 0xf6708000-0xf67083ff irq 16 at device 26.0 on pci0
Dec 2 20:14:53	nas4free	kernel: pci0: <simple comms> at device 22.0 (no driver attached)
Dec 2 20:14:53	nas4free	kernel: vgapci1: <VGA-compatible display> mem 0xf6020000-0xf602ffff at device 0.1 on pci1
Dec 2 20:14:53	nas4free	kernel: vgapci0: Boot video device
Dec 2 20:14:53	nas4free	kernel: vgapci0: <VGA-compatible display> port 0xe000-0xe0ff mem 0xf4000000-0xf5ffffff,0xf6030000-0xf603ffff irq 16 at device 0.0 on pci1
Dec 2 20:14:53	nas4free	kernel: pci1: <ACPI PCI bus> on pcib1
Dec 2 20:14:53	nas4free	kernel: pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
Dec 2 20:14:53	nas4free	kernel: pci0: <ACPI PCI bus> on pcib0
Dec 2 20:14:53	nas4free	kernel: pcib0: _OSC returned error 0x10
Dec 2 20:14:53	nas4free	kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Dec 2 20:14:53	nas4free	kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
Dec 2 20:14:53	nas4free	kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Dec 2 20:14:53	nas4free	kernel: Event timer "i8254" frequency 1193182 Hz quality 100
Dec 2 20:14:53	nas4free	kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Dec 2 20:14:53	nas4free	kernel: attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Dec 2 20:14:53	nas4free	kernel: Event timer "RTC" frequency 32768 Hz quality 0
Dec 2 20:14:53	nas4free	kernel: atrtc0: Warning: Couldn't map I/O.
Dec 2 20:14:53	nas4free	kernel: atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
Dec 2 20:14:53	nas4free	kernel: Event timer "HPET4" frequency 14318180 Hz quality 440
Dec 2 20:14:53	nas4free	kernel: Event timer "HPET3" frequency 14318180 Hz quality 440
Dec 2 20:14:53	nas4free	kernel: Event timer "HPET2" frequency 14318180 Hz quality 440
Dec 2 20:14:53	nas4free	kernel: Event timer "HPET1" frequency 14318180 Hz quality 440
Dec 2 20:14:53	nas4free	kernel: Event timer "HPET" frequency 14318180 Hz quality 550
Dec 2 20:14:53	nas4free	kernel: Timecounter "HPET" frequency 14318180 Hz quality 950
Dec 2 20:14:53	nas4free	kernel: hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Dec 2 20:14:53	nas4free	kernel: cpu3: <ACPI CPU> on acpi0
Dec 2 20:14:53	nas4free	kernel: cpu2: <ACPI CPU> on acpi0
Dec 2 20:14:53	nas4free	kernel: cpu1: <ACPI CPU> on acpi0
Dec 2 20:14:53	nas4free	kernel: cpu0: <ACPI CPU> on acpi0
Dec 2 20:14:53	nas4free	kernel: acpi0: Power Button (fixed)
Dec 2 20:14:53	nas4free	kernel: acpi0: <ALASKA A M I> on motherboard
Dec 2 20:14:53	nas4free	kernel: cryptosoft0: <software crypto> on motherboard
Dec 2 20:14:53	nas4free	kernel: nexus0
Dec 2 20:14:53	nas4free	kernel: random: fast provider: "Intel Secure Key RNG"
Dec 2 20:14:53	nas4free	kernel: random: registering fast source Intel Secure Key RNG
Dec 2 20:14:53	nas4free	kernel: netmap: loaded module
Dec 2 20:14:53	nas4free	kernel: kbd1 at kbdmux0
Dec 2 20:14:53	nas4free	kernel: md0: Preloaded image </mfsroot> 134217728 bytes at 0xffffffff82a90b78
Dec 2 20:14:53	nas4free	kernel: random: entropy device external interface
Dec 2 20:14:53	nas4free	kernel: Timecounter "TSC-low" frequency 1549581492 Hz quality 1000
Dec 2 20:14:53	nas4free	kernel: SMP: AP CPU #1 Launched!
Dec 2 20:14:53	nas4free	kernel: SMP: AP CPU #2 Launched!
Dec 2 20:14:53	nas4free	kernel: SMP: AP CPU #3 Launched!
Dec 2 20:14:53	nas4free	kernel: ioapic0 <Version 2.0> irqs 0-23 on motherboard
Dec 2 20:14:53	nas4free	kernel: WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Dec 2 20:14:53	nas4free	kernel: FreeBSD/SMP: 1 package(s) x 4 core(s)
Dec 2 20:14:53	nas4free	kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Dec 2 20:14:53	nas4free	kernel: ACPI APIC Table: <ALASKA A M I>
Dec 2 20:14:53	nas4free	kernel: Event timer "LAPIC" quality 600
Dec 2 20:14:53	nas4free	kernel: avail memory = 16380428288 (15621 MB)
Dec 2 20:14:53	nas4free	kernel: real memory = 17179869184 (16384 MB)
Dec 2 20:14:53	nas4free	kernel: TSC: P-state invariant, performance statistics
Dec 2 20:14:53	nas4free	kernel: VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
Dec 2 20:14:53	nas4free	kernel: XSAVE Features=0x1<XSAVEOPT>
Dec 2 20:14:53	nas4free	kernel: Structured Extended Features=0x2fbb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,NFPUSG>
Dec 2 20:14:53	nas4free	kernel: AMD Features2=0x21<LAHF,ABM>
Dec 2 20:14:53	nas4free	kernel: AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
Dec 2 20:14:53	nas4free	kernel: Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
Dec 2 20:14:53	nas4free	kernel: Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Dec 2 20:14:53	nas4free	kernel: Origin="GenuineIntel" Id=0x306c3 Family=0x6 Model=0x3c Stepping=3
Dec 2 20:14:53	nas4free	kernel: CPU: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz (3099.16-MHz K8-class CPU)
Dec 2 20:14:53	nas4free	kernel: FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0)
Dec 2 20:14:53	nas4free	kernel: root@dev.nas4free.org:/usr/obj/nas4free/usr/src/sys/NAS4FREE-amd64 amd64
Dec 2 20:14:53	nas4free	kernel: FreeBSD 11.1-RELEASE-p5 #0 r326430M: Fri Dec 1 15:33:13 CET 2017
Dec 2 20:14:53	nas4free	kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Dec 2 20:14:53	nas4free	kernel: The Regents of the University of California. All rights reserved.
Dec 2 20:14:53	nas4free	kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Dec 2 20:14:53	nas4free	kernel: Copyright (c) 1992-2017 The FreeBSD Project.
Dec 2 20:14:53	nas4free	kernel: Uptime: 1h13m10s
Dec 2 20:14:53	nas4free	kernel: All buffers synced.
Dec 2 20:14:53	nas4free	kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop... done
Dec 2 20:14:53	nas4free	kernel: Syncing disks, vnodes remaining... 5 1 1 0 0 0 done
Dec 2 20:14:53	nas4free	kernel: Waiting (max 60 seconds) for system process `syncer' to stop...
Dec 2 20:14:53	nas4free	kernel: Waiting (max 60 seconds) for system process `vnlru' to stop... done
Dec 2 20:14:53	nas4free	syslogd: kernel boot file is /boot/kernel/kernel

billgayler
Starter
Starter
Posts: 21
Joined: 06 Jun 2014 01:51
Location: London, UK
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by billgayler »

Not sure if this related but I am chasing a problems with my Sonos system that has lost the ability to connect to my music library since I switched to 11.1.0.4.4994. It seems to be able to see the NAS but access to the drives is denied.

It is probably the inverse yo your problems. I should explain that access to the NAS SMB folders still works fine on my win 10 network running Windows 10 Professional Edition build 15063 (64-bit).

I am aware that since SAMBA 4.5 NTLM 1 is switched off by default. There are articles on the Sonos forum suggesting adding the following text to the Additional Parameters section in the CIFS/SMB setup screen "ntlm auth = yes " to turn it back on.

It might be related to the problem you have spotted, it might not be, but it does seem odd that there are two of us reporting changed SMB behaviour since switching to 4994.

I am wondering if it might be a N4F bug.

Is anyone else having problems?
Version: 11.0.0.4 - Sayyadina (revision 3330)
Platform: x64-embedded on AMD Athlon(tm) II X3 455 Processor
System: ASUSTeK Computer INC. M4A78LT-M-LE
Mem: 4GB, Storage: ZFS (4.5TB - Rsync local - 4.5TB)

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

Thanks for your reply, billgayle.

My issue appeared prior to upgrading to 11.1.0.4.4994. It was appeared with the previous version that had been working properly. I upgraded to 11.1.0.4.4994 with the hope that a new install might solve the issue, but it did not.

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

SOLVED (sort of)

Although I had not changed my configuration, I restored from my saved copy and the problem persisted.

I then "upgraded" firmware back to version 11.1.0.4 - Atomics (revision 4528) and everything works great.

Despite my earlier note that the problem appeared prior to my upgrade to 11.1.0.4.4994, it may not have- I may have upgraded to 11.1.0.4.4994 and not noticed the issue.

There is a difference between version 11.1.0.4.4528 and 11.1.0.4.4994 that is causing CIFS/SMD in 4528 to work fine with my configuration, but 4994 not to work at all.

Hope that helps someone.

Alautre1
NewUser
NewUser
Posts: 12
Joined: 10 Jan 2015 11:08
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by Alautre1 »

Hi VJ8h8bwgHziT,

As I have the same issue with SONOs to access my Music library, I would be interested in having a copy of your 11.1.0.4.4528 release (Live CD - X64 version).
Thanks for your help.

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

Sorry I did not see your message sooner. I have file "NAS4Free-x64-embedded-11.1.0.4.4729.img.xz" and "NAS4Free-x64-embedded-11.1.0.4.4619.img.xz"

If that is the format you can use and you still would like it, how can I get it to you?

I do not use SONOs, so not sure this is the same issue you are having.

User avatar
lux
Advanced User
Advanced User
Posts: 193
Joined: 23 Jun 2012 11:37
Location: Bielefeld, Germany
Contact:
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by lux »

@ Alautre1

do you need Version ...4528 anymore? i could upload the .iso on my Webspace if neccesary 8-)
Home:11.3.x.7538/emb@32GB USB|1270v2@X9SCA-F|ECC32GB|i340-T4[lagg@GS108Tv2&smb-mch]|M1015@IT|9HDD~40TB@3xRaidZ1+1HDD+2SSD i335&i520+1xi800P@ZIL|~44W idle@SS-400FL2|Nanoxia Deep Silence 6B|24/7
Services: CIFS, FTP, TFTP, SSH, NFS, Rsync, Syncthing, Webserver, BitTorrent, VirtualBox | Extensions: OBI, TheBrig[certbot, Asterisk] | Extensions via vBox: Pi-hole, Jellyfin & zigbee2mqtt @DebianVM's
Test:12.x/emb@16GB USB|X3 420e@M4A88TD-V|16GB|i350-T2|M1015@IT|8xHDD+3xSSD[different Size&Brand]RaidZ1+2|for TESTing only

sleid
PowerUser
PowerUser
Posts: 774
Joined: 23 Jun 2012 07:36
Location: FRANCE LIMOUSIN CORREZE
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by sleid »

If you put in the file explorer of windows10 \\ ip of nas you arrive on your Nas, it is that you have problems with netbios on your windows.
12.1.0.4 - Ingva (revision 7852)
FreeBSD 12.1-RELEASE-p12 #0 r368465M: Tue Dec 8 23:25:11 CET 2020
X64-embedded sur Intel(R) Atom(TM) CPU C2750 @ 2.40GHz Boot UEFI
ASRock C2750D4I 2 X 8GB DDR3 ECC
Pool of 2 vdev Raidz1: 3 WDC WD40EFRX + 3 WDC WD40EFRX

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

Does anyone have any insight into this issue? I tried an upgrade to the newest version of NAS4FREE yesterday ( 11.1.0.4.5403) with the hope that it would fix my problem but it does not. I did post the issue and error messages under the INSTALLATION / UPGRADE topic yesterday. I am hoping someone has insight.

When that didn't work, I went back to 4528 which works great for both my Android and Windows 10 clients. Versions 4994 and 5403 work with neither even after I restore the working configuration.

I am technical but not so much with linux, and am really pulling my hair out over this one.

User avatar
Snufkin
Advanced User
Advanced User
Posts: 317
Joined: 01 Jul 2012 11:27
Location: Etc/GMT-3 (BSD style)
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by Snufkin »

VJ8h8bwgHziT wrote:
03 Dec 2017 02:32
Below is my Diagnostics > Log starting from a recent Reboot. There are error messages, but I don't know were to begin.

Code: Select all

 Date & Time 	User 	Event
...
Dec 2 20:17:10	nas4free	smbd[2879]: refusing to dump core
Dec 2 20:17:10	nas4free	smbd[2879]: unable to change to %N.core
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.957743, 0] ../source3/lib/dumpcore.c:310(dump_core)
Dec 2 20:17:10	nas4free	smbd[2879]: #6 0x801cd7ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Dec 2 20:17:10	nas4free	smbd[2879]: #5 0x801cd8926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Dec 2 20:17:10	nas4free	smbd[2879]: #4 0x80211d493 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: #3 0x80211da70 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: #2 0x80211d4c7 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: #1 0x8046bea58 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: #0 0x8046bec5e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Dec 2 20:17:10	nas4free	smbd[2879]: BACKTRACE: 7 stack frames:
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.957696, 0] ../source3/lib/util.c:902(log_stack_trace)
Dec 2 20:17:10	nas4free	smbd[2879]: PANIC (pid 2879): internal error
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.956896, 0] ../source3/lib/util.c:791(smb_panic_s3)
Dec 2 20:17:10	nas4free	smbd[2879]: ===============================================================
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.956888, 0] ../lib/util/fault.c:81(fault_report)
Dec 2 20:17:10	nas4free	smbd[2879]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 2 20:17:10	nas4free	smbd[2879]: INTERNAL ERROR: Signal 11 in pid 2879 (4.6.11)
Dec 2 20:17:10	nas4free	smbd[2879]: [2017/12/02 20:17:10.956875, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:17:10	nas4free	smbd[2879]: ===============================================================
There should be no above lines in your log, something is wrong.
Suggest following steps:
  1. backup your config
  2. shutdown your NAS and remove current USB stick with working N4F embedded (?) version
  3. mark SATA/SAS sockets/plugs then disconnect all HDD's with important info, leave just one for test purpose
  4. take different brand new USB stick and install on it latest N4F embedded
  5. boot your NAS on new USB stick, mount test disk, configure SAMBA and add share, leave default values in all fields where possible
  6. post here in code tags log content from http://<your_NAS_IP>/status.php page
XNAS 11.4.0.4 embedded, ASUS P5B-E, Intel DC E6600, 4 GB DDR2
ZFS 2 x HGST HDN726040ALE614, L2ARC PLEXTOR PX-128M5S

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

Thank you for those steps and for your help!

I don't actually use a USB stick, I am using an embedded in N4F on an internal SSD connected directly to the motherboard. I believe I can simply set the bios to boot from a USB stick rather than the internal SSD and have the same effect.

All the hard drives have important info and are part of ZFS. I could pull them all out and put in an old spare unused drive for testing.

Please confirm that the two adjustments to your suggested steps would be OK. I will probably not be able to do this project until the weekend so have time to plan.

THANK YOU!

EDIT: I am thinking I may not need to add a spare drive - Once I pull the ZHS drives the internal SSD (currently with the N4F) will remain. That can be my single data drive for this test when I install boot from and configure from a new USB stick. How is that for a plan? Anything need to be changed? Thanks again!

User avatar
Snufkin
Advanced User
Advanced User
Posts: 317
Joined: 01 Jul 2012 11:27
Location: Etc/GMT-3 (BSD style)
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by Snufkin »

VJ8h8bwgHziT wrote:
25 Apr 2018 13:35
Please confirm that the two adjustments to your suggested steps would be OK. I will probably not be able to do this project until the weekend so have time to plan.
Two adjustments are fine.

I'd even suggest pulling out your boot SSD, just to be on a safe side and not mess out your setup. And mount data partition (/dev/da0p4 on USB stick) created after default embedded installation.

The idea is to check for compatibility your hardware config and latest N4F embedded, especially Samba memory consumption (if it's your case).
XNAS 11.4.0.4 embedded, ASUS P5B-E, Intel DC E6600, 4 GB DDR2
ZFS 2 x HGST HDN726040ALE614, L2ARC PLEXTOR PX-128M5S

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

I had a dream about this last night and the idea popped into my head of comparing the log file of my working version (4528) to the version I posted above that does not work (5403).

When I look at the log file of my (4528) configuration, I see a recurring pattern of errors listed and they seem to be related to the issue. It might be a configuration setting causing these errors and preventing the upgrade to (5403).

Any insights or suggestions?

I really appreciate your help!



Apr 26 08:20:20 nas4free smbd[11274]: ads_find_dc: name resolution for realm 'NAS4FREEDNS' (domain 'WORKGROUP') failed: NT_STATUS_NO_LOGON_SERVERS
Apr 26 08:20:20 nas4free smbd[11274]: [2018/04/26 08:20:20.756953, 1] ../source3/libads/ldap.c:553(ads_find_dc)
Apr 26 08:20:19 nas4free smbd[11274]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR
Apr 26 08:20:19 nas4free smbd[11274]: [2018/04/26 08:20:19.653312, 1] ../auth/gensec/gensec_start.c:698(gensec_start_mech)
Apr 26 08:20:19 nas4free smbd[11274]: ../source3/librpc/crypto/gse_krb5.c:607: Error! Unable to set mem keytab - -1765328254
Apr 26 08:20:19 nas4free smbd[11274]: [2018/04/26 08:20:19.653178, 1] ../source3/librpc/crypto/gse_krb5.c:607(gse_krb5_get_server_keytab)
Apr 26 08:20:18 nas4free smbd[11271]: ads_find_dc: name resolution for realm 'NAS4FREEDNS' (domain 'WORKGROUP') failed: NT_STATUS_NO_LOGON_SERVERS
Apr 26 08:20:18 nas4free smbd[11271]: [2018/04/26 08:20:18.592550, 1] ../source3/libads/ldap.c:553(ads_find_dc)
Apr 26 08:20:17 nas4free smbd[11271]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR
Apr 26 08:20:17 nas4free smbd[11271]: [2018/04/26 08:20:17.513244, 1] ../auth/gensec/gensec_start.c:698(gensec_start_mech)
Apr 26 08:20:17 nas4free smbd[11271]: ../source3/librpc/crypto/gse_krb5.c:607: Error! Unable to set mem keytab - -1765328254
Apr 26 08:20:17 nas4free smbd[11271]: [2018/04/26 08:20:17.513114, 1] ../source3/librpc/crypto/gse_krb5.c:607(gse_krb5_get_server_keytab)
Apr 26 08:20:16 nas4free smbd[11270]: ads_find_dc: name resolution for realm 'NAS4FREEDNS' (domain 'WORKGROUP') failed: NT_STATUS_NO_LOGON_SERVERS
Apr 26 08:20:16 nas4free smbd[11270]: [2018/04/26 08:20:16.441340, 1] ../source3/libads/ldap.c:553(ads_find_dc)
Apr 26 08:20:15 nas4free smbd[11270]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR
Apr 26 08:20:15 nas4free smbd[11270]: [2018/04/26 08:20:15.384379, 1] ../auth/gensec/gensec_start.c:698(gensec_start_mech)
Apr 26 08:20:15 nas4free smbd[11270]: ../source3/librpc/crypto/gse_krb5.c:607: Error! Unable to set mem keytab - -1765328254
Apr 26 08:20:15 nas4free smbd[11270]: [2018/04/26 08:20:15.384246, 1] ../source3/librpc/crypto/gse_krb5.c:607(gse_krb5_get_server_keytab)

User avatar
Snufkin
Advanced User
Advanced User
Posts: 317
Joined: 01 Jul 2012 11:27
Location: Etc/GMT-3 (BSD style)
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by Snufkin »

Let us look at the logs.
As far as I understand you have Samba AD service active

Code: Select all

Dec 2 20:15:04	nas4free	winbindd[2314]: unable to initialize domain list
Dec 2 20:15:04	nas4free	winbindd[2314]: [2017/12/02 20:15:04.036437, 0] ../source3/winbindd/winbindd.c:1402(winbindd_register_handlers)
Dec 2 20:15:04	nas4free	winbindd[2314]: Could not fetch our SID - did we join?
Dec 2 20:15:04	nas4free	winbindd[2314]: [2017/12/02 20:15:04.036421, 0] ../source3/winbindd/winbindd_util.c:893(init_domain_list)
Dec 2 20:15:04	nas4free	winbindd[2314]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Dec 2 20:15:04	nas4free	winbindd[2314]: [2017/12/02 20:15:04.035405, 0] ../source3/winbindd/winbindd_cache.c:3171(initialize_winbindd_cache)
At the same time Master browser in your Samba service is active as well.
And Samba crashes immediately after the election of the local Master browser.

Code: Select all

Dec 2 20:16:12	nas4free	smbd[2860]: INTERNAL ERROR: Signal 11 in pid 2860 (4.6.11)
Dec 2 20:16:12	nas4free	smbd[2860]: [2017/12/02 20:16:12.237866, 0] ../lib/util/fault.c:79(fault_report)
Dec 2 20:16:12	nas4free	smbd[2860]: ===============================================================
Dec 2 20:16:12	nas4free	smbd[2860]: [2017/12/02 20:16:12.237837, 0] ../lib/util/fault.c:78(fault_report)
Dec 2 20:15:27	nas4free	nmbd[2307]: *****
Dec 2 20:15:27	nas4free	nmbd[2307]:
Dec 2 20:15:27	nas4free	nmbd[2307]: Samba name server NAS4FREE is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.10
Latest log confirms Samba AD is active but not prperly configured.

Code: Select all

Apr 26 08:20:16	nas4free	smbd[11270]: ads_find_dc: name resolution for realm 'NAS4FREEDNS' (domain 'WORKGROUP') failed: NT_STATUS_NO_LOGON_SERVERS
Apr 26 08:20:16	nas4free	smbd[11270]: [2018/04/26 08:20:16.441340, 1] ../source3/libads/ldap.c:553(ads_find_dc)
Apr 26 08:20:15	nas4free	smbd[11270]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR
Apr 26 08:20:15	nas4free	smbd[11270]: [2018/04/26 08:20:15.384379, 1] ../auth/gensec/gensec_start.c:698(gensec_start_mech)
Apr 26 08:20:15	nas4free	smbd[11270]: ../source3/librpc/crypto/gse_krb5.c:607: Error! Unable to set mem keytab - -1765328254
Apr 26 08:20:15	nas4free	smbd[11270]: [2018/04/26 08:20:15.384246, 1] ../source3/librpc/crypto/gse_krb5.c:607(gse_krb5_get_server_keytab)
Do you have some specific reason to have both features active?
XNAS 11.4.0.4 embedded, ASUS P5B-E, Intel DC E6600, 4 GB DDR2
ZFS 2 x HGST HDN726040ALE614, L2ARC PLEXTOR PX-128M5S

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

Thanks for your help!

I'm not certain of the configuration I had on Dec 2 when I posted that log. I had tried a number of configuration changes to get the upgrade working. What I posed on Apr 26 was immediately after restoring from the saved config file.

I did see that the "Local Master Browser" on the CIFS page had been set to YES but on the Services>Samba AD page it appears that that is not running. On the page there is a red triangle with a "!" and the warning "Cannot use DHCP for LAN interface". The "Enable" box in the upper right corner is unchecked.

At the top of the Services > CIFS/SMB > Settings page, for Authentication, I have selected "Active Directory". On the Access > Active Directory page, I have:
Domain Controller Name: NAS4FREEDC
Domain Name (DNS/Realm-Name): NAS4FREEDNS
Domain Name (NetBIOS-Name): WORKGROUP

I am not sure what is needed for the required field of "Domain Name (DNS/Realm-Name):" but that seems to the the first error.


I did turn off the "Local Master Browser" on the CIFS page by setting it to NO and rebooting. It works great. Seems to respond faster on my Android and Windows than with the Master set to YES. I still have errors in the Log file... still related to Active Directory:

Apr 27 13:36:29 nas4free smbd[2901]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR
Apr 27 13:36:29 nas4free smbd[2901]: [2018/04/27 13:36:29.229315, 1] ../auth/gensec/gensec_start.c:698(gensec_start_mech)
Apr 27 13:36:29 nas4free smbd[2901]: ../source3/librpc/crypto/gse_krb5.c:607: Error! Unable to set mem keytab - -1765328254
Apr 27 13:36:29 nas4free smbd[2901]: [2018/04/27 13:36:29.229185, 1] ../source3/librpc/crypto/gse_krb5.c:607(gse_krb5_get_server_keytab)
Apr 27 13:36:28 nas4free smbd[2900]: ads_find_dc: name resolution for realm 'NAS4FREEDNS' (domain 'WORKGROUP') failed: NT_STATUS_NO_LOGON_SERVERS
Apr 27 13:36:28 nas4free smbd[2900]: [2018/04/27 13:36:28.190807, 1] ../source3/libads/ldap.c:553(ads_find_dc)
Apr 27 13:36:27 nas4free smbd[2900]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR
Apr 27 13:36:27 nas4free smbd[2900]: [2018/04/27 13:36:27.132815, 1] ../auth/gensec/gensec_start.c:698(gensec_start_mech)
Apr 27 13:36:27 nas4free smbd[2900]: ../source3/librpc/crypto/gse_krb5.c:607: Error! Unable to set mem keytab - -1765328254
Apr 27 13:36:27 nas4free smbd[2900]: [2018/04/27 13:36:27.132683, 1] ../source3/librpc/crypto/gse_krb5.c:607(gse_krb5_get_server_keytab)
Apr 27 13:36:23 nas4free smbd[2899]: ads_find_dc: name resolution for realm 'NAS4FREEDNS' (domain 'WORKGROUP') failed: NT_STATUS_NO_LOGON_SERVERS
Apr 27 13:36:23 nas4free smbd[2899]: [2018/04/27 13:36:23.973258, 1] ../source3/libads/ldap.c:553(ads_find_dc)
Apr 27 13:36:22 nas4free smbd[2899]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR

I am saving this as a new configuration and my new baseline. Any insight on why I am not seeing the fields on the Samba AD page populated? .. or what to do about the Active Directory error?

Really do appreciate your help!!!! Thank you!

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

With the change above (turning Local Master Browser to NO), I again updated to (5403) to see what they Diagnostics > Log would say. Once I upgraded, Windows and Android could not no longer see the server. I captured the error log below for more clues before reverting back to (4528) so that I can access the server.

Apr 27 13:46:03 nas4free smbd[2981]: refusing to dump core
Apr 27 13:46:03 nas4free smbd[2981]: unable to change to %N.core
Apr 27 13:46:03 nas4free smbd[2981]: [2018/04/27 13:46:03.853910, 0] ../source3/lib/dumpcore.c:310(dump_core)
Apr 27 13:46:03 nas4free smbd[2981]: #6 0x801cd8ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Apr 27 13:46:03 nas4free smbd[2981]: #5 0x801cd9926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Apr 27 13:46:03 nas4free smbd[2981]: #4 0x80211f203 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Apr 27 13:46:03 nas4free smbd[2981]: #3 0x80211f7e0 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Apr 27 13:46:03 nas4free smbd[2981]: #2 0x80211f237 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Apr 27 13:46:03 nas4free smbd[2981]: #1 0x8046c22a8 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Apr 27 13:46:03 nas4free smbd[2981]: #0 0x8046c24ae <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Apr 27 13:46:03 nas4free smbd[2981]: BACKTRACE: 7 stack frames:
Apr 27 13:46:03 nas4free smbd[2981]: [2018/04/27 13:46:03.853860, 0] ../source3/lib/util.c:926(log_stack_trace)
Apr 27 13:46:03 nas4free smbd[2981]: PANIC (pid 2981): internal error
Apr 27 13:46:03 nas4free smbd[2981]: [2018/04/27 13:46:03.853041, 0] ../source3/lib/util.c:815(smb_panic_s3)
Apr 27 13:46:03 nas4free smbd[2981]: ===============================================================
Apr 27 13:46:03 nas4free smbd[2981]: [2018/04/27 13:46:03.853032, 0] ../lib/util/fault.c:81(fault_report)
Apr 27 13:46:03 nas4free smbd[2981]: Please read the Trouble-Shooting section of the Samba HOWTO
Apr 27 13:46:03 nas4free smbd[2981]: INTERNAL ERROR: Signal 11 in pid 2981 (4.7.6)
Apr 27 13:46:03 nas4free smbd[2981]: [2018/04/27 13:46:03.853018, 0] ../lib/util/fault.c:79(fault_report)
Apr 27 13:46:03 nas4free smbd[2981]: ===============================================================
Apr 27 13:46:03 nas4free smbd[2981]: [2018/04/27 13:46:03.852988, 0] ../lib/util/fault.c:78(fault_report)
Apr 27 13:46:03 nas4free smbd[2980]: refusing to dump core
Apr 27 13:46:03 nas4free smbd[2980]: unable to change to %N.core
Apr 27 13:46:03 nas4free smbd[2980]: [2018/04/27 13:46:03.830482, 0] ../source3/lib/dumpcore.c:310(dump_core)
Apr 27 13:46:03 nas4free smbd[2980]: #6 0x801cd8ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Apr 27 13:46:03 nas4free smbd[2980]: #5 0x801cd9926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Apr 27 13:46:03 nas4free smbd[2980]: #4 0x80211f203 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Apr 27 13:46:03 nas4free smbd[2980]: #3 0x80211f7e0 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Apr 27 13:46:03 nas4free smbd[2980]: #2 0x80211f237 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Apr 27 13:46:03 nas4free smbd[2980]: #1 0x8046c22a8 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Apr 27 13:46:03 nas4free smbd[2980]: #0 0x8046c24ae <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Apr 27 13:46:03 nas4free smbd[2980]: BACKTRACE: 7 stack frames:
Apr 27 13:46:03 nas4free smbd[2980]: [2018/04/27 13:46:03.830433, 0] ../source3/lib/util.c:926(log_stack_trace)
Apr 27 13:46:03 nas4free smbd[2980]: PANIC (pid 2980): internal error
Apr 27 13:46:03 nas4free smbd[2980]: [2018/04/27 13:46:03.829614, 0] ../source3/lib/util.c:815(smb_panic_s3)
Apr 27 13:46:03 nas4free smbd[2980]: ===============================================================
Apr 27 13:46:03 nas4free smbd[2980]: [2018/04/27 13:46:03.829605, 0] ../lib/util/fault.c:81(fault_report)
Apr 27 13:46:03 nas4free smbd[2980]: Please read the Trouble-Shooting section of the Samba HOWTO
Apr 27 13:46:03 nas4free smbd[2980]: INTERNAL ERROR: Signal 11 in pid 2980 (4.7.6)
Apr 27 13:46:03 nas4free smbd[2980]: [2018/04/27 13:46:03.829591, 0] ../lib/util/fault.c:79(fault_report)
Apr 27 13:46:03 nas4free smbd[2980]: ===============================================================
Apr 27 13:46:03 nas4free smbd[2980]: [2018/04/27 13:46:03.829561, 0] ../lib/util/fault.c:78(fault_report)

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

I found an issue where the name of the Access > Active Directory Domain Name (NetBIOS-Name) did not match the Services > CIFS/SMB > Settings NetBIOS Name. I have since set them both to NAS4FREENetBIOS.

The CIFS contines to work for me on (4528) but not (5403). I have attached the Diagnostic logs for each below.

I have no idea what to do next and really appreciate your help!


----------------------------------------------------------
version (4528) Diagnostic log (ABLE to connect from both Windows AND Android)
Apr 27 15:12:06 nas4free smbd[3139]: ads_find_dc: name resolution for realm 'NAS4FREEDNS' (domain 'WORKGROUP') failed: NT_STATUS_NO_LOGON_SERVERS
Apr 27 15:12:06 nas4free smbd[3139]: [2018/04/27 15:12:06.939784, 1] ../source3/libads/ldap.c:553(ads_find_dc)
Apr 27 15:12:05 nas4free smbd[3139]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR
Apr 27 15:12:05 nas4free smbd[3139]: [2018/04/27 15:12:05.879826, 1] ../auth/gensec/gensec_start.c:698(gensec_start_mech)
Apr 27 15:12:05 nas4free smbd[3139]: ../source3/librpc/crypto/gse_krb5.c:607: Error! Unable to set mem keytab - -1765328254
Apr 27 15:12:05 nas4free smbd[3139]: [2018/04/27 15:12:05.879696, 1] ../source3/librpc/crypto/gse_krb5.c:607(gse_krb5_get_server_keytab)
Apr 27 15:12:04 nas4free smbd[3138]: ads_find_dc: name resolution for realm 'NAS4FREEDNS' (domain 'WORKGROUP') failed: NT_STATUS_NO_LOGON_SERVERS
Apr 27 15:12:04 nas4free smbd[3138]: [2018/04/27 15:12:04.846732, 1] ../source3/libads/ldap.c:553(ads_find_dc)
Apr 27 15:12:03 nas4free smbd[3138]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR
Apr 27 15:12:03 nas4free smbd[3138]: [2018/04/27 15:12:03.780394, 1] ../auth/gensec/gensec_start.c:698(gensec_start_mech)
Apr 27 15:12:03 nas4free smbd[3138]: ../source3/librpc/crypto/gse_krb5.c:607: Error! Unable to set mem keytab - -1765328254
Apr 27 15:12:03 nas4free smbd[3138]: [2018/04/27 15:12:03.780263, 1] ../source3/librpc/crypto/gse_krb5.c:607(gse_krb5_get_server_keytab)
Apr 27 15:11:19 nas4free smbd[3137]: ads_find_dc: name resolution for realm 'NAS4FREEDNS' (domain 'WORKGROUP') failed: NT_STATUS_NO_LOGON_SERVERS
Apr 27 15:11:19 nas4free smbd[3137]: [2018/04/27 15:11:19.676525, 1] ../source3/libads/ldap.c:553(ads_find_dc)
Apr 27 15:11:18 nas4free smbd[3137]: Failed to start GENSEC server mech gse_krb5: NT_STATUS_INTERNAL_ERROR




----------------------------------------------------------
version (5403) Diagnostic log (unable to connect from both Windows and Android):
Apr 27 14:59:04 nas4free smbd[3400]: refusing to dump core
Apr 27 14:59:04 nas4free smbd[3400]: unable to change to %N.core
Apr 27 14:59:04 nas4free smbd[3400]: [2018/04/27 14:59:04.084968, 0] ../source3/lib/dumpcore.c:310(dump_core)
Apr 27 14:59:04 nas4free smbd[3400]: #6 0x801cd8ecf <pthread_getspecific+0xe5f> at /lib/libthr.so.3
Apr 27 14:59:04 nas4free smbd[3400]: #5 0x801cd9926 <pthread_sigmask+0x536> at /lib/libthr.so.3
Apr 27 14:59:04 nas4free smbd[3400]: #4 0x80211f203 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
Apr 27 14:59:04 nas4free smbd[3400]: #3 0x80211f7e0 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
Apr 27 14:59:04 nas4free smbd[3400]: #2 0x80211f237 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
Apr 27 14:59:04 nas4free smbd[3400]: #1 0x8046c22a8 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
Apr 27 14:59:04 nas4free smbd[3400]: #0 0x8046c24ae <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
Apr 27 14:59:04 nas4free smbd[3400]: BACKTRACE: 7 stack frames:
Apr 27 14:59:04 nas4free smbd[3400]: [2018/04/27 14:59:04.084914, 0] ../source3/lib/util.c:926(log_stack_trace)
Apr 27 14:59:04 nas4free smbd[3400]: PANIC (pid 3400): internal error
Apr 27 14:59:04 nas4free smbd[3400]: [2018/04/27 14:59:04.084073, 0] ../source3/lib/util.c:815(smb_panic_s3)
Apr 27 14:59:04 nas4free smbd[3400]: ===============================================================
Apr 27 14:59:04 nas4free smbd[3400]: [2018/04/27 14:59:04.084064, 0] ../lib/util/fault.c:81(fault_report)
Apr 27 14:59:04 nas4free smbd[3400]: Please read the Trouble-Shooting section of the Samba HOWTO
Apr 27 14:59:04 nas4free smbd[3400]: INTERNAL ERROR: Signal 11 in pid 3400 (4.7.6)
Apr 27 14:59:04 nas4free smbd[3400]: [2018/04/27 14:59:04.084050, 0] ../lib/util/fault.c:79(fault_report)
Apr 27 14:59:04 nas4free smbd[3400]: ===============================================================
Apr 27 14:59:04 nas4free smbd[3400]: [2018/04/27 14:59:04.084019, 0] ../lib/util/fault.c:78(fault_report)
Apr 27 14:59:04 nas4free smbd[3399]: refusing to dump core
Apr 27 14:59:04 nas4free smbd[3399]: unable to change to %N.core
Apr 27 14:59:04 nas4free smbd[3399]: [2018/04/27 14:59:04.066504, 0] ../source3/lib/dumpcore.c:310(dump_core)

User avatar
Snufkin
Advanced User
Advanced User
Posts: 317
Joined: 01 Jul 2012 11:27
Location: Etc/GMT-3 (BSD style)
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by Snufkin »

VJ8h8bwgHziT wrote:
27 Apr 2018 19:38
I still have errors in the Log file... still related to Active Directory:
Do you have MS Windows server running Active directory in your local network?
If not then set Authentication to Local user on this page
VJ8h8bwgHziT wrote:
27 Apr 2018 19:38
I did turn off the "Local Master Browser" on the CIFS page by setting it to NO and rebooting. It works great. Seems to respond faster on my Android and Windows than with the Master set to YES.
I'd recommend to leave default value Yes.
VJ8h8bwgHziT wrote:
27 Apr 2018 19:38
I captured the error log below for more clues...
This may be an error due to incorrect configuration, ie. Samba user authentication is set to Active directory when Active directory actually doesn't exist. And it may interfere with the upgrade procedure, which in turn leads to complete Samba crash in latest N4F release.
Last edited by Snufkin on 28 Apr 2018 06:46, edited 1 time in total.
XNAS 11.4.0.4 embedded, ASUS P5B-E, Intel DC E6600, 4 GB DDR2
ZFS 2 x HGST HDN726040ALE614, L2ARC PLEXTOR PX-128M5S

VJ8h8bwgHziT
Starter
Starter
Posts: 33
Joined: 20 Apr 2014 23:38
Status: Offline

Re: No longer able to see NAS4FEE v 11.1.0.4.4994 via CIFS/SMD (Windows 10 / Android)

Post by VJ8h8bwgHziT »

Snufkin - you nailed it. I was just logging back in to say am successfully on the new version and it is running fine! I remember experimenting with the AD features when they first came out and see that I left them rather than going back to Local user. Because I was able to read and write to the shares, I never went back to revisit it. I am sure previous upgrades accepted the flawed configuration. I do have one more question. The Diagnostic log looks good except for this:

Apr 27 18:36:47 nas4free smbd[2920]: pcap cache not loaded
Apr 27 18:36:47 nas4free smbd[2920]: [2018/04/27 18:36:47.683651, 1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
Apr 27 18:36:47 nas4free smbd[2920]: Failed to fetch record!
Apr 27 18:36:47 nas4free smbd[2920]: [2018/04/27 18:36:47.683626, 1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
Apr 27 18:36:42 nas4free smbd[2920]: pcap cache not loaded
Apr 27 18:36:42 nas4free smbd[2920]: [2018/04/27 18:36:42.977047, 1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
Apr 27 18:36:42 nas4free smbd[2920]: Failed to fetch record!
Apr 27 18:36:42 nas4free smbd[2920]: [2018/04/27 18:36:42.977016, 1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
Apr 27 18:24:55 nas4free smbd[2329]: inotify_rm_watch returned Invalid argument
Apr 27 18:24:55 nas4free smbd[2329]: [2018/04/27 18:24:55.168020, 1] ../source3/smbd/notify_inotify.c:369(watch_destructor)
Apr 27 18:24:55 nas4free smbd[2329]: inotify_rm_watch returned Invalid argument
Apr 27 18:24:55 nas4free smbd[2329]: [2018/04/27 18:24:55.157428, 1] ../source3/smbd/notify_inotify.c:369(watch_destructor)
Apr 27 18:24:54 nas4free smbd[2329]: inotify_rm_watch returned Invalid argument
Apr 27 18:24:54 nas4free smbd[2329]: [2018/04/27 18:24:54.966495, 1] ../source3/smbd/notify_inotify.c:369(watch_destructor)
Apr 27 18:22:39 nas4free smbd[2329]: inotify_rm_watch returned Invalid argument
Apr 27 18:22:39 nas4free smbd[2329]: [2018/04/27 18:22:39.367304, 1] ../source3/smbd/notify_inotify.c:369(watch_destructor)
Apr 27 18:21:32 nas4free smbd[2739]: pcap cache not loaded
Apr 27 18:21:32 nas4free smbd[2739]: [2018/04/27 18:21:32.851613, 1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
Apr 27 18:21:32 nas4free smbd[2739]: Failed to fetch record!
Apr 27 18:21:32 nas4free smbd[2739]: [2018/04/27 18:21:32.851588, 1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
Apr 27 18:21:22 nas4free smbd[2329]: inotify_rm_watch returned Invalid argument
Apr 27 18:21:22 nas4free smbd[2329]: [2018/04/27 18:21:22.251616, 1] ../source3/smbd/notify_inotify.c:369(watch_destructor)
Apr 27 18:21:22 nas4free smbd[2739]: pcap cache not loaded
Apr 27 18:21:22 nas4free smbd[2739]: [2018/04/27 18:21:22.239676, 1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
Apr 27 18:21:22 nas4free smbd[2739]: Failed to fetch record!
Apr 27 18:21:22 nas4free smbd[2739]: [2018/04/27 18:21:22.239647, 1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
Apr 27 18:19:27 nas4free nmbd[2262]: This response was from IP 192.168.1.6, reporting an IP address of 192.168.200.2.
Apr 27 18:19:27 nas4free nmbd[2262]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.10 for name WORKGROUP<1d>.
Apr 27 18:19:27 nas4free nmbd[2262]: [2018/04/27 18:19:27.057883, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Apr 27 18:09:22 nas4free smbd[2329]: inotify_rm_watch returned Invalid argument
Apr 27 18:09:22 nas4free smbd[2329]: [2018/04/27 18:09:22.290856, 1] ../source3/smbd/notify_inotify.c:369(watch_destructor)
Apr 27 18:09:20 nas4free smbd[2329]: inotify_rm_watch returned Invalid argument
Apr 27 18:09:20 nas4free smbd[2329]: [2018/04/27 18:09:20.662299, 1] ../source3/smbd/notify_inotify.c:369(watch_destructor)
Apr 27 18:09:06 nas4free login: login on ttyv0 as root
Apr 27 18:09:05 nas4free lighttpd[2568]: (server.c.1423) server started (lighttpd/1.4.49)
Apr 27 18:09:05 nas4free smbd[2266]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Apr 27 18:09:05 nas4free smbd[2266]: [2018/04/27 18:09:05.681742, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Apr 27 18:09:05 nas4free smbd[2266]: file_init_global: Information only: requested 929709 open files, 59392 are available.
Apr 27 18:09:05 nas4free smbd[2266]: [2018/04/27 18:09:05.676993, 1] ../source3/smbd/files.c:218(file_init_global)
Apr 27 18:09:05 nas4free smbd[2263]: INFO: Profiling turned OFF from pid 2263
Apr 27 18:09:05 nas4free smbd[2263]: [2018/04/27 18:09:05.494017, 1] ../source3/profile/profile.c:51(set_profile_level)
Apr 27 18:09:05 nas4free nmbd[2262]: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Apr 27 18:09:05 nas4free nmbd[2262]: [2018/04/27 18:09:05.430937, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Apr 27 18:09:04 nas4free proftpd[2093]: 192.168.1.10 - ProFTPD 1.3.6 (stable) (built Mon Apr 16 2018 23:51:52 CEST) standalone mode STARTUP

Post Reply

Return to “CIFS/SMB (Samba)”