NSS Volumes periodically disconnecting

On Aug 18, we patched our SLES10SP4\OES2SP3 (64-bit) servers with the latest patches from Novell. Since then, 3 of our servers are periodically disconnecting the NSS volumes. Only way to get them back is to reboot the servers. We thought we figured out the issue this morning, but one the servers just lost it's volumes again and when I brought it back up, I'm now seeing the following error in the /var/log/messages. I'm watching the CIFS.log to see if I can capture anything else that shows up.

CIFS [8256]: ERROR: ENTRY: Loading of NCSSDK library failed, error: libncssdk.so: cannot open shared object file: No such file or directory
CIFS [8256]: WARNING: ENTRY: Interface lo is skipped from populating for name resolution

I've check the CIFS Proxy account and it's not locked out and is in the CIFS Default Password Policy
  • On 22/08/2013 14:36, hfr63 wrote:

    > On Aug 18, we patched our SLES10SP4\OES2SP3 (64-bit) servers with the
    > latest patches from Novell. Since then, 3 of our servers are
    > periodically disconnecting the NSS volumes. Only way to get them back
    > is to reboot the servers. We thought we figured out the issue this
    > morning, but one the servers just lost it's volumes again and when I
    > brought it back up, I'm now seeing the following error in the
    > /var/log/messages. I'm watching the CIFS.log to see if I can capture
    > anything else that shows up.
    >
    > CIFS [8256]: ERROR: ENTRY: Loading of NCSSDK library failed, error:
    > libncssdk.so: cannot open shared object file: No such file or
    > directory
    > CIFS [8256]: WARNING: ENTRY: Interface lo is skipped from populating
    > for name resolution
    >
    > I've check the CIFS Proxy account and it's not locked out and is in the
    > CIFS Default Password Policy


    By "latest patches" did that include eDirectory 8.8 SP7 Patch 4
    (8.8.7.4)? What does "rpm -qa | grep edirectory" output?

    I'm wondering if your problem is related to TID 7013072.

    HTH.

    [1] http://www.novell.com/support/kb/doc.php?id=7013072
    --
    Simon
    Novell Knowledge Partner

    ------------------------------------------------------------------------
    Do you work with Novell technologies at a university, college or school?
    If so, your campus could benefit from joining the Technology Transfer
    Partner (TTP) program. See novell.com/ttp for more details.
    ------------------------------------------------------------------------
  • Well, it's not hourly in fact it was DAYS before the initial crash AND what gets me it's not all the servers. But how do you do a back trace? Like to see if it is this or something else.
  • This morning (8/23) one of the problem servers had it's volumes dismounted again. Found the following error in the cifs.log file.

    volmnd[7976]: Pinging EFLs
    syslog-ng[3583]: STATS: dropped 0
    kernel: ndsd[2115]: segfault at 0000000000000000 rip 00002af433d7149a rsp 0000000049e6db80 error 4
    syslog-ng[3583]: STATS: dropped 0
    /usr/sbin/namcd[5824]: param_errmsg: Unknown error returned reading configuration parameter: alternative-ldap-server-list

    I hard booted the server this time instead of just a regular reboot.
  • hfr63;2278965 wrote:
    This morning (8/23) one of the problem servers had it's volumes dismounted again. Found the following error in the cifs.log file.

    volmnd[7976]: Pinging EFLs
    syslog-ng[3583]: STATS: dropped 0
    kernel: ndsd[2115]: segfault at 0000000000000000 rip 00002af433d7149a rsp 0000000049e6db80 error 4
    syslog-ng[3583]: STATS: dropped 0
    /usr/sbin/namcd[5824]: param_errmsg: Unknown error returned reading configuration parameter: alternative-ldap-server-list

    I hard booted the server this time instead of just a regular reboot.


    Did you see Simon's comment that this might be a possible issue that's described in TID 7013072?

    If that matches your situation (patchlevel), best to open a SR with Novell to get hold of the FTF patch.

    -Willem
  • Yeah well, I opened an SR and they told me SLES10SP4\OES2SP3 is end of life as of 31 July and no longer supported...... Got them to open a ticket anyway because I haven't had this issue before I deployed the patches. Still waiting for a support engineer to call me even though it was escalated as a down system......
  • Yeah well, I opened an SR and they told me SLES10SP4\OES2SP3 is end of life as of 31 July and no longer supported...... Got them to open a ticket anyway because I haven't had this issue before I deployed the patches. Still waiting for a support engineer to call me even though it was escalated as a down system......
  • Yeah well, I opened an SR and they told me SLES10SP4\OES2SP3 is end of life as of 31 July and no longer supported...... Got them to open a ticket anyway because I haven't had this issue before I deployed the patches. Still waiting for a support engineer to call me even though it was escalated as a down system......
  • novell-edirectory-ldap-exensions-32bit-8.8.7.4-0.7
    novell-edirectory-ldap-extensions-8.8.7.4-0.7
    yast2-novell-edirectory-2.14.10-195
    novell-edirectory-tsands-8.8.7.4-0.10
    novell-edirectory-tsands-32bit-8.8.7.4-0.10
    novell-edirectory-passstore-1.0.1-0.11
    novell-edirectory-jclnt-8.8.7.4.0.10
    novell-migration-edirectory-0.1.0-64.3
  • On 23/08/2013 14:56, hfr63 wrote:

    > Yeah well, I opened an SR and they told me SLES10SP4\OES2SP3 is end of
    > life as of 31 July and no longer supported


    Whilst OES2 SP3 is now end of life it's not true to say it's no longer
    supported - General Support ended on 31 July but it's now in Extended
    Support (ends 01 Jan 2015) and if you have maintenance for OES11 (the
    current version) you can purchase Extended Support Service Request
    Package. See http://support.novell.com/lifecycle/faq.jsp

    The alternative, of course, is to upgrade or migrate to OES11 SP1 (on
    SLES11 SP2).

    HTH.
    --
    Simon
    Novell Knowledge Partner

    ------------------------------------------------------------------------
    Do you work with Novell technologies at a university, college or school?
    If so, your campus could benefit from joining the Technology Transfer
    Partner (TTP) program. See novell.com/ttp for more details.
    ------------------------------------------------------------------------
  • hfr63;2279025 wrote:
    Yeah well, I opened an SR and they told me SLES10SP4\OES2SP3 is end of life as of 31 July and no longer supported...... Got them to open a ticket anyway because I haven't had this issue before I deployed the patches. Still waiting for a support engineer to call me even though it was escalated as a down system......


    You are running the latest patches/levels