Heya, I was brought to this forum from a google search about
MNDS_AddPoolToNDS... I cannot for the life of me get this issue fixed.

http://tinyurl.com/26onur

I performed the nssAdminuser script, made sure the proxy user was in
eDirectory, and tried to reinstall nss through YaST. Nothing seems to
work.


Code:
--------------------

Jan 23 23:25:17 magnolia /etc/hotplug/block.agent[28764]: try 1 while waiting for /block/dm-3's bus_id
Jan 23 23:25:18 magnolia /etc/hotplug/block.agent[28780]: try 1 while waiting for /block/dm-4's bus_id
Jan 23 23:25:18 magnolia /etc/hotplug/block.agent[28782]: try 1 while waiting for /block/dm-5's bus_id
Jan 23 23:25:18 magnolia kernel: NSSLOG ==> [MSAP] /usr/src/packages/BUILD/kernel-smp-2.6.5/modules-2.6.5/nss/comn/comnLog.c[201]
Jan 23 23:25:18 magnolia kernel: Pool "SEATTLE_POOL" - MSAP block initialized.
Jan 23 23:25:18 magnolia kernel: NSSLOG ==> [MSAP] /usr/src/packages/BUILD/kernel-smp-2.6.5/modules-2.6.5/nss/comn/comnLog.c[201]
Jan 23 23:25:18 magnolia kernel: Pool "SEATTLE_POOL" - MSAP activate.
Jan 23 23:25:18 magnolia kernel: Server(d73f7cce-d90f-1000-9d-ba-003048844624) Cluster(00000000-0000-0000-00-00-000000000000)
Jan 23 23:25:18 magnolia kernel: NSSLOG ==> [MSAP] /usr/src/packages/BUILD/kernel-smp-2.6.5/modules-2.6.5/nss/comn/comnLog.c[201]
Jan 23 23:25:18 magnolia kernel: Pool "SEATTLE_POOL" - Watching pool.
Jan 23 23:25:18 magnolia kernel: NSSLOG ==> [MSAP] /usr/src/packages/BUILD/kernel-smp-2.6.5/modules-2.6.5/nss/comn/comnLog.c[201]
Jan 23 23:25:18 magnolia kernel: Pool "SEATTLE_POOL" - MSAP deactivate.
Jan 23 23:25:18 magnolia kernel: NSSLOG ==> [MSAP] /usr/src/packages/BUILD/kernel-smp-2.6.5/modules-2.6.5/nss/comn/comnLog.c[201]
Jan 23 23:25:18 magnolia kernel: Pool "SEATTLE_POOL" - MSAP activate.
Jan 23 23:25:18 magnolia kernel: Server(d73f7cce-d90f-1000-9d-ba-003048844624) Cluster(00000000-0000-0000-00-00-000000000000)
Jan 23 23:25:18 magnolia kernel: NSSLOG ==> [MSAP] /usr/src/packages/BUILD/kernel-smp-2.6.5/modules-2.6.5/nss/comn/comnLog.c[201]
Jan 23 23:25:18 magnolia kernel: Pool "SEATTLE_POOL" - Watching pool.
Jan 23 23:25:18 magnolia adminfs daemon[28756]: MNDS_AddPoolToNDS: Error -604 from DDCCreateEntry(magnolia_SEATTLE_POOL_POOL)
Jan 23 23:25:18 magnolia /etc/hotplug/block.agent[28764]: try 2 while waiting for /block/dm-3's bus_id
Jan 23 23:25:19 magnolia /etc/hotplug/block.agent[28780]: try 2 while waiting for /block/dm-4's bus_id
Jan 23 23:25:19 magnolia /etc/hotplug/block.agent[28782]: try 2 while waiting for /block/dm-5's bus_id
Jan 23 23:25:19 magnolia /etc/hotplug/block.agent[28764]: try 3 while waiting for /block/dm-3's bus_id
Jan 23 23:25:20 magnolia /etc/hotplug/block.agent[28780]: try 3 while waiting for /block/dm-4's bus_id
Jan 23 23:25:20 magnolia /etc/hotplug/block.agent[28782]: try 3 while waiting for /block/dm-5's bus_id
Jan 23 23:25:20 magnolia /etc/hotplug/block.agent[28764]: try 4 while waiting for /block/dm-3's bus_id
Jan 23 23:25:21 magnolia /etc/hotplug/block.agent[28780]: try 4 while waiting for /block/dm-4's bus_id
Jan 23 23:25:21 magnolia /etc/hotplug/block.agent[28782]: try 4 while waiting for /block/dm-5's bus_id
Jan 23 23:25:21 magnolia /etc/hotplug/block.agent[28764]: try 5 while waiting for /block/dm-3's bus_id
Jan 23 23:25:22 magnolia /etc/hotplug/block.agent[28780]: try 5 while waiting for /block/dm-4's bus_id
Jan 23 23:25:22 magnolia /etc/hotplug/block.agent[28782]: try 5 while waiting for /block/dm-5's bus_id
Jan 23 23:25:23 magnolia /etc/hotplug/block.agent[28764]: new block device /block/dm-3
Jan 23 23:25:23 magnolia /etc/hotplug/block.agent[28780]: new block device /block/dm-4
Jan 23 23:25:23 magnolia /etc/hotplug/block.agent[28782]: new block device /block/dm-5

--------------------


Which looks very close to that other thread. If I reconfigure NSS from
YaST without removing the proxy user, it will give me error -606 and
exit. However, if I delete the proxy user, then reconfigure via yast,
it sits there for a second, then exits, returning no errors.

Either way, I still get the error above. I'd love to hear any advice,
or articles that can help me out.

Note. I have EVMS installed and configured I believe right:


Code:
--------------------
fstab:
/dev/evms/sda5 / reiserfs acl,user_xattr 1 1
/dev/evms/sda1 /boot ext2 acl,user_xattr 1 2
/dev/sdb5 /data1 auto noauto,user 0 0
/dev/sdb1 /data2 auto noauto,user 0 0
/dev/sdb6 /data3 auto noauto,user 0 0
/dev/evms/sda6 swap swap defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=ut f8 0 0
/dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0

--------------------


The only other thing that looks suspicious in the logs is when namcd is
shutdown, it cannot see the ldap server:


Code:
--------------------

Jan 23 23:36:30 magnolia /usr/sbin/namcd[31826]: Starting namcd..
Jan 23 23:36:30 magnolia /usr/sbin/namcd[31826]: namcd populating the user hash tables
Jan 23 23:36:30 magnolia /usr/sbin/namcd[31826]: namcd populating group hash tables
Jan 23 23:36:30 magnolia /usr/sbin/namcd[31826]: namcd Populated hash tables
Jan 23 23:36:30 magnolia /usr/sbin/namcd[31826]: Created all the threads
Jan 23 23:41:35 magnolia /usr/sbin/namcd[31826]: deinitialized the worker threads
Jan 23 23:41:35 magnolia /usr/sbin/namcd[31826]: deinitialized the cache refresh thread
Jan 23 23:41:35 magnolia /usr/sbin/namcd[31826]: monitorChangesInLDAP: ldap_result: Can't contact LDAP server
Jan 23 23:41:38 magnolia /usr/sbin/namcd[31826]: deinitialized the LDAP watcher thread
Jan 23 23:41:40 magnolia /usr/sbin/namcd[31826]: Deleted hash tables and flushed data into local files
Jan 23 23:41:40 magnolia /usr/sbin/namcd[31826]: Deinitialized threads

--------------------


any of this related?


--
japerry