Directory Users could not be retrieved

Status
Not open for further replies.

Pandamonium

Dabbler
Joined
Nov 2, 2016
Messages
47
Hi All,

Recently upgraded to Freenas 11 and I now have an issue whenever I try to amend the permissions on a share. I get this error...

Directory Users could not be retrieved: (-30973, 'BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery -- BDB0060 PANIC: fatal region error detected; run recovery')

and then...

Directory Groups could not be retrieved: (-30973, 'BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery -- BDB0060 PANIC: fatal region error detected; run recovery')

Once I receive this error, all my shares become inaccessible from Windows until I reboot the Freenas server.

Any idea how I can fix this please?

Many Thanks
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
That looks pretty bad.

Are you running this virtualized?

If not, what's your hardware and so on? Might need to file a bug report on this, seems SMB related...assume you're using Samba.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
hardware specs? Setup? AD? come on man provide some good info here.
 

Pandamonium

Dabbler
Joined
Nov 2, 2016
Messages
47
Server is physical...

Supermicro X11SSL Motherboard, 32GB Ram, Intel Xeon E3-1230 v5 @ 3.40GHz


Joined to AD, several SMB shares, several plugins (syncthing, plex, owncloud etc) all installed through GUI in jails. System was running fine for several months on Freenas 9 update frequently. Updated to 11 a few days ago.

Now also seeing the following errors without doing anything to shares...

aggregation plugin: Unable to read the current rate of "domain/cpu-x/cpu-user" (where x is 0,2,3 or 5 so far).
utils-vl-lookup: The user object callback failed with status 2.
 

Pandamonium

Dabbler
Joined
Nov 2, 2016
Messages
47
Reinstalled freenas 11 from scratch and restored config. Now seems to be working OK.
 

JayG30

Contributor
Joined
Jun 26, 2013
Messages
158
Ran into the same error on one of my freenas boxes that I just recently upgraded to 11. But by reloading the GUI and waiting I can enable it though. Haven't tried a fresh install of 11 at this point.

Off topc, but what led me to this issue was another crazy issue I'm having that I feel I have to share.

Basically all I have to do is run an xcopy on a windows server to copy a file to a mapped SMB share on freenas and the freenas box will lose AD connection immediately. This started right after upgraded to freenas 11.

I have a script that maps an SMB drive, then uses xcopy to copy the file to the mapped SMB share. This had worked fine for the past few years and then I noticed the file stopped updating. I manually tried to run it and found that every time I ran the xcopy command it reported it couldn't find the network location (which I know is correct) and subsequently all access to SMB shares for everyone stopped working. Go into freenas and save the AD configuration again and it comes back.

I tried the same script/commands again a different mapped SMB share and it worked fine...which is even more confusing. And yes permissions are identical on the shares, the user performing xcopy is a domain admin with full access to the folders/files.
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
Ran into the same error on one of my freenas boxes that I just recently upgraded to 11. But by reloading the GUI and waiting I can enable it though. Haven't tried a fresh install of 11 at this point.

Off topc, but what led me to this issue was another crazy issue I'm having that I feel I have to share.

Basically all I have to do is run an xcopy on a windows server to copy a file to a mapped SMB share on freenas and the freenas box will lose AD connection immediately. This started right after upgraded to freenas 11.

I have a script that maps an SMB drive, then uses xcopy to copy the file to the mapped SMB share. This had worked fine for the past few years and then I noticed the file stopped updating. I manually tried to run it and found that every time I ran the xcopy command it reported it couldn't find the network location (which I know is correct) and subsequently all access to SMB shares for everyone stopped working. Go into freenas and save the AD configuration again and it comes back.

I tried the same script/commands again a different mapped SMB share and it worked fine...which is even more confusing. And yes permissions are identical on the shares, the user performing xcopy is a domain admin with full access to the folders/files.
You've piqued my curiosity. Do you mind increasing samba logging to debug, reproducing the problem, then sending me the debug file via PM? I'll take a look at it and also try to reproduce on my systems.
 
  • Like
Reactions: BaT

LawrenceSystems

Dabbler
Joined
Jun 14, 2017
Messages
14
I just had the same thing happen to me, FreeNAS-11.0-U2 and if I delete/add a volume the SMB service stops working. I can restart the service but it keeps dying off. I reboot the server, works fine as long as I am not deleting/adding volumes. I don't know if it makes a difference, but the volumes I was deleting and adding were both encrypted and had a password.

Here is the log.smbd from it crashing, me starting the service and it crashing again. As I said, once I rebooted the system seems fine and until this issue is resolved I will just plan on rebooting the server if I need to make any make any changes to the drives.

Code:
[2017/07/29 11:16:31.176338,  0] ../lib/util/fault.c:79(fault_report)
  INTERNAL ERROR: Signal 11 in pid 48316 (4.6.4-GIT-5fe3bc2)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2017/07/29 11:16:31.176373,  0] ../lib/util/fault.c:81(fault_report)
  ===============================================================
[2017/07/29 11:16:31.176400,  0] ../source3/lib/util.c:791(smb_panic_s3)
  PANIC (pid 48316): internal error
[2017/07/29 11:16:31.188545,  0] ../source3/lib/util.c:902(log_stack_trace)
  BACKTRACE: 7 stack frames:
   #0 0x803262d1e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
   #1 0x803262b18 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
   #2 0x800c9a597 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
   #3 0x800c9ab40 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
   #4 0x800c9a563 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
   #5 0x8008488b6 <pthread_sigmask+0x4f6> at /lib/libthr.so.3
   #6 0x800847e9f <pthread_getspecific+0xe5f> at /lib/libthr.so.3
[2017/07/29 11:16:31.188666,  0] ../source3/lib/util.c:803(smb_panic_s3)
  smb_panic(): calling panic action [/usr/local/libexec/samba/samba-backtrace]
ptrace: Device busy.
ptrace: Device busy.
ptrace: Device busy.
[2017/07/29 12:26:47.961599,  1] ../source3/profile/profile_dummy.c:30(set_profile_level)
  INFO: Profiling support unavailable in this build.
[2017/07/29 12:26:48.120849,  1] ../source3/smbd/files.c:218(file_init_global)
  file_init_global: Information only: requested 439562 open files, 59392 are available.
[2017/07/29 12:26:48.158205,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/07/29 12:26:50.390784,  1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
  Failed to fetch record!
[2017/07/29 12:26:50.390837,  1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
  pcap cache not loaded
[2017/07/29 12:26:50.397850,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x3ef) on IPC$.
[2017/07/29 12:26:50.398059,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x105) on IPC$.
[2017/07/29 12:27:00.360853,  1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
  Failed to fetch record!
[2017/07/29 12:27:00.360925,  1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
  pcap cache not loaded
[2017/07/29 12:27:00.361581,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x3ef) on IPC$.
[2017/07/29 12:27:00.361796,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x105) on IPC$.
[2017/07/29 12:27:10.366310,  1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
  Failed to fetch record!
[2017/07/29 12:27:10.366375,  1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
  pcap cache not loaded
[2017/07/29 12:27:10.366882,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x3ef) on IPC$.
[2017/07/29 12:27:10.367047,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x105) on IPC$.
[2017/07/29 12:27:13.899933,  0] ../lib/util/fault.c:78(fault_report)
  ===============================================================
[2017/07/29 12:27:13.900017,  0] ../lib/util/fault.c:79(fault_report)
  INTERNAL ERROR: Signal 11 in pid 96675 (4.6.4-GIT-5fe3bc2)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2017/07/29 12:27:13.900045,  0] ../lib/util/fault.c:81(fault_report)
  ===============================================================
[2017/07/29 12:27:13.900064,  0] ../source3/lib/util.c:791(smb_panic_s3)
  PANIC (pid 96675): internal error
[2017/07/29 12:27:13.900792,  0] ../source3/lib/util.c:902(log_stack_trace)
  BACKTRACE: 7 stack frames:
   #0 0x803262d1e <log_stack_trace+0x1e> at /usr/local/lib/libsmbconf.so.0
   #1 0x803262b18 <smb_panic_s3+0x98> at /usr/local/lib/libsmbconf.so.0
   #2 0x800c9a597 <smb_panic+0x27> at /usr/local/lib/libsamba-util.so.0
   #3 0x800c9ab40 <string_sub_once> at /usr/local/lib/libsamba-util.so.0
   #4 0x800c9a563 <fault_setup+0x73> at /usr/local/lib/libsamba-util.so.0
   #5 0x8008488b6 <pthread_sigmask+0x4f6> at /lib/libthr.so.3
   #6 0x800847e9f <pthread_getspecific+0xe5f> at /lib/libthr.so.3
[2017/07/29 12:27:13.900893,  0] ../source3/lib/util.c:803(smb_panic_s3)
  smb_panic(): calling panic action [/usr/local/libexec/samba/samba-backtrace]
ptrace: Device busy.
ptrace: Device busy.
ptrace: Device busy.
[2017/07/29 13:11:05.332882,  1] ../source3/profile/profile_dummy.c:30(set_profile_level)
  INFO: Profiling support unavailable in this build.
[2017/07/29 13:11:05.532997,  1] ../source3/smbd/files.c:218(file_init_global)
  file_init_global: Information only: requested 439562 open files, 59392 are available.
[2017/07/29 13:11:05.626845,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/07/29 13:12:44.709504,  1] ../source3/profile/profile_dummy.c:30(set_profile_level)
  INFO: Profiling support unavailable in this build.
[2017/07/29 13:12:44.721011,  1] ../source3/smbd/files.c:218(file_init_global)
  file_init_global: Information only: requested 439562 open files, 59392 are available.
[2017/07/29 13:12:44.724106,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/07/29 13:13:08.151334,  1] ../source3/profile/profile_dummy.c:30(set_profile_level)
  INFO: Profiling support unavailable in this build.
[2017/07/29 13:13:08.162858,  1] ../source3/smbd/files.c:218(file_init_global)
  file_init_global: Information only: requested 439562 open files, 59392 are available.
[2017/07/29 13:13:08.165893,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/07/29 13:32:35.060653,  1] ../source3/profile/profile_dummy.c:30(set_profile_level)
  INFO: Profiling support unavailable in this build.
[2017/07/29 13:32:35.190572,  1] ../source3/smbd/files.c:218(file_init_global)
  file_init_global: Information only: requested 439562 open files, 59392 are available.
[2017/07/29 13:32:35.308460,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/07/29 13:37:13.271865,  1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
[2017/07/29 13:37:13.271872,  1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
  Failed to fetch record!
  Failed to fetch record!
[2017/07/29 13:37:13.272057,  1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
[2017/07/29 13:37:13.272064,  1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
  pcap cache not loaded
  pcap cache not loaded
[2017/07/29 13:37:13.291926,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x3ef) on IPC$.
[2017/07/29 13:37:13.299017,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x105) on IPC$.
[2017/07/29 13:37:22.347405,  1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
  Failed to fetch record!
[2017/07/29 13:37:22.347559,  1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
  pcap cache not loaded
[2017/07/29 13:37:22.348119,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x3ef) on IPC$.
[2017/07/29 13:37:22.348309,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x105) on IPC$.
[2017/07/29 13:37:32.364491,  1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
  Failed to fetch record!
[2017/07/29 13:37:32.364711,  1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
  pcap cache not loaded
[2017/07/29 13:37:32.371821,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x3ef) on IPC$.
[2017/07/29 13:37:32.372039,  0] ../source3/smbd/trans2.c:3422(smbd_do_qfsinfo)
  smbd_do_qfsinfo: not an allowed info level (0x105) on IPC$.
[2017/07/29 13:52:10.188574,  1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
  Failed to fetch record!
[2017/07/29 13:52:10.188733,  1] ../source3/smbd/server_reload.c:69(delete_and_reload_printers)
  pcap cache not loaded
[2017/07/29 13:52:10.312217,  1] ../source3/smbd/service.c:502(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2017/07/29 13:52:10.317498,  1] ../source3/smbd/service.c:502(make_connection_snum)

 

JayG30

Contributor
Joined
Jun 26, 2013
Messages
158
You've piqued my curiosity. Do you mind increasing samba logging to debug, reproducing the problem, then sending me the debug file via PM? I'll take a look at it and also try to reproduce on my systems.

I actually ended up fixing the issue. I simple deleted the SMB share and recreated it. Issue disappeared. :confused:
 
Status
Not open for further replies.
Top