iPrint cluster resource loads in comatose state

  • 7013452
  • 14-Oct-2013
  • 14-Oct-2013

Environment

Novell iPrint for Linux
Novell Cluster Services

Situation

If an OES11 SP1 cluster node has ever received the "July 2013 Scheduled Maintenance for OES11SP1" update, the iPrint cluster resource will load to comatose state when attempting to load to that node.  Upgrading to newer code will not get past the problem.

Resolution

1. Within the cluster load script, comment the following 3 lines
;ignore_error mv /media/nss/<iPrintVolName>/var/opt/novell/iprint/iprintgw.lpr /media/nss/<iPrintVolName>/var/opt/novell/iprint/iprintgw.lpr.bak
;exit_on_error rcnovell-idsd start
;exit_on_error rcnovell-ipsmd start
2. Load the cluster resource to the non-working node.
3. Run the iprint_nss_relocate script
Syntax:
/opt/novell/iprint/bin/iprint_nss_relocate -a <admin dn> -n <NSS path> -l cluster
Example:
/opt/novell/iprint/bin/iprint_nss_relocate -a cn=admin,o=novell -n /media/nss/MyiPrintVolName -l cluster
  • Replace MyiPrintVolName with the name of the cluster volume
  • Do not have '/' after the /media/nss/MyiPrintVolName
4. Remove the 3 comment marks from the cluster load script.
5. Offline and online the cluster to the problem node to confirm the problem is resolved.

Cause

The "July 2013 Scheduled Maintenance for OES11SP1" update incorrectly sets some of the Novell iPrint symbolic links necessary for an iPrint cluster configuration.  The incorrect sym links are:

/var/opt/novell/iprint -> /media/nss/<iPrintVolName>/var/opt/novell/log/iprint/
/var/opt/novell/log/iprint -> 601


The correct sym links should be:

/var/opt/novell/iprint -> /media/nss/<iPrintVolName>/var/opt/novell/iprint
/etc/opt/novell/iprint/conf -> /media/nss/<iPrintVolName>/etc/opt/novell/iprint/conf
/var/opt/novell/log/iprint -> /media/nss/<iPrintVolName>/var/opt/novell/log/iprint


Releases after the July update does not introduce this problem, but the newer updates also do not resolve the problem.  The steps in the RESOLUTION section of this TID must be followed.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.