after last oes updates poa start failed

Hello,

I just updated my oes11 server with the last patches. After restart I
noticed, that the poa and the domain failed to start.

In /var/log/messages I found this lines:
startproc: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
startproc: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
startproc: exit status of parent of
/opt/novell/groupwise/agents/bin/gwmta: 9
startproc: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0

Other servers with same constellation (oes11, gw 2014.sp1) restarted w/o
probs.

Problem with Lum? The po and domain files residing on NSS-volumes

Gotthard

--
Gotthard Anger
Anwenderbetreuung Netzwerkadministration
Landeskirchenamt der EKM
gotthardanger@no-mx.forums.novell.com
http://forums.novell.com/member.php?u=35038
  • Hello,

    Just for the records:

    Lum was the right idea. I reconfigured the LUM-option in yast and
    rebooted the server.
    No all runs fine.

    Gotthard


    Am 28.03.2015 um 10:36 schrieb Gotthard Anger:
    > Hello,
    >
    > I just updated my oes11 server with the last patches. After restart I
    > noticed, that the poa and the domain failed to start.


    >
    > In /var/log/messages I found this lines:
    > startproc: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
    > startproc: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
    > startproc: exit status of parent of
    > /opt/novell/groupwise/agents/bin/gwmta: 9
    > startproc: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
    >
    > Other servers with same constellation (oes11, gw 2014.sp1) restarted w/o
    > probs.
    >
    > Problem with Lum? The po and domain files residing on NSS-volumes
    >
    > Gotthard
    >



    --
    Gotthard Anger
    Anwenderbetreuung Netzwerkadministration
    Landeskirchenamt der EKM
    gotthardanger@no-mx.forums.novell.com
    http://forums.novell.com/member.php?u=35038