Problem connecting to AD server pam_windbind.so not in /etc/pam.d/logi

Status
Not open for further replies.

Abel408

Dabbler
Joined
Oct 15, 2012
Messages
32
Hello everyone,

I have two freenas servers. One connects to AD fine and one doesn't. The one that doesn't seems to list all the correct information for wbinfo, but it only lists local users for getent passwd and local groups for getent group. winbind is listed correctly in nsswitch.conf. The only difference I see between the two is the /etc/pam.d/login file. The one that works looks like this:

Code:
#
# $FreeBSD: src/etc/pam.d/login,v 1.17 2007/06/10 18:57:20 yar Exp $
#
# PAM configuration for the "login" service
#
 
# auth
auth            sufficient      pam_self.so            no_warn
auth            sufficient      /usr/local/lib/pam_winbind.so silent try_first_pass krb5_auth krb5_ccache_type=FILE
auth            include        system
 
# account
account        requisite      pam_securetty.so
account        required        pam_nologin.so
account        sufficient      /usr/local/lib/pam_winbind.so krb5_auth krb5_ccache_type=FILE
account        include        system
 
# session
session        include        system
 
# password
password        include        system


and the one that does not work looks like this:

Code:
#
# $FreeBSD: src/etc/pam.d/login,v 1.17 2007/06/10 18:57:20 yar Exp $
#
# PAM configuration for the "login" service
#
 
# auth
auth            sufficient      pam_self.so            no_warn
auth            include        system
 
# account
account        requisite      pam_securetty.so
account        required        pam_nologin.so
account        include        system
 
# session
session        include        system
 
# password
password        include        system


I also do not have a /etc/pam.d/samba file on the server that does not work.

I believe that is where my problem is. I tried adding those lines to that file, but it just reverts back after a reboot.

The freenas version I am using is FreeNAS-8.0-RELEASE-i386. I know it's old.. I have been unable to upgrade via the web and unable to physically get to the server.

Any help is greatly appreciated. This problem is driving me nuts :(

EDIT: I was also getting a bunch of these in my log.windbind.idmap

Code:
[2014/01/21 16:14:06.468424,  3] winbindd/idmap.c:302(idmap_init_domain)
  idmap backend rid not found
[2014/01/21 16:14:06.468449,  3] lib/module.c:48(do_smb_load_module)
  Error loading module '/usr/local/lib/samba/idmap/rid.so': Cannot open "/usr/local/lib/samba/idmap/rid.so"
[2014/01/21 16:14:06.468458,  3] winbindd/idmap.c:307(idmap_init_domain)
  Could not probe idmap module rid
[2014/01/21 16:14:06.470931,  3] winbindd/idmap.c:302(idmap_init_domain)
  idmap backend rid not found
[2014/01/21 16:14:06.470955,  3] lib/module.c:48(do_smb_load_module)
  Error loading module '/usr/local/lib/samba/idmap/rid.so': Cannot open "/usr/local/lib/samba/idmap/rid.so"
[2014/01/21 16:14:06.470968,  3] winbindd/idmap.c:307(idmap_init_domain)
  Could not probe idmap module rid
[2014/01/21 16:14:06.473559,  3] winbindd/idmap.c:302(idmap_init_domain)
  idmap backend rid not found
[2014/01/21 16:14:06.473584,  3] lib/module.c:48(do_smb_load_module)
  Error loading module '/usr/local/lib/samba/idmap/rid.so': Cannot open "/usr/local/lib/samba/idmap/rid.so"
[2014/01/21 16:14:06.473593,  3] winbindd/idmap.c:307(idmap_init_domain)
  Could not probe idmap module rid


-Chris
 

Abel408

Dabbler
Joined
Oct 15, 2012
Messages
32
It looks like my build is missing the /usr/local/lib/samba/idmap directory. Probably the same issue as this: https://bugs.freenas.org/issues/362

I tried syncing the idmap directory from my server that works, but that is a x64 server and it didn't work on my i386 server. This download link is also dead:http://download.freenas.org/idmap.tar.bz2


I tried upgrading with the gui with no success. I also tried upgrading from CLI and received this: xzcat /mnt/Vo1/FreeNAS-9.1.1-RELEASE-x64.8_0_x_LEGACY_GUI_Upgrade.xz | sh -x /root/update
+ set -e
+ . /etc/nanobsd.conf
+ NANO_DRIVE=ufs/FreeNAS
+ mount
+ grep ufs/FreeNASs1
+ exec sh /root/updatep2
dd: /dev/da5s2: short write on character device
dd: /dev/da5s2: end of device
953600+0 records in
3724+1 records out
488194560 bytes transferred in 177.554077 secs (2749554 bytes/sec)

Rebooted and was still on the same build… I'm stuck. The only option seems to be to upgrade using a CD, but who knows if that will work. I seem to be hitting every single problem.
 
D

dlavigne

Guest
I'm not surprised that a GUI upgrade from so old a version didn't work. Make sure you have a copy of your config (from the GUI) and either dd an image file to the same (or another) stick or do a new CD install. Once you have the new version, restore your config.
 
Status
Not open for further replies.
Top