iPrint configured on a clustered traditional Linux file system (ext3, reiserfs, etc) fails to load.

  • 7008562
  • 11-May-2011
  • 26-Apr-2012


Novell iPrint for Linux
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3


iPrint configured on a clustered traditional Linux file system (ext3, reiserfs, etc) fails to load.
The following error is seen in the /var/opt/novell/log/ipsmd.log file:
May 11 14:15:37 WARNING PSMChildSigHandler1: child with pid 30584 terminated with signal 11
May 11 14:15:37 WARNING The kernel has indicated that a gateway, ilprsrvrd or accounting process is gone.
May 11 14:15:37 INFO The iPrint Manager has unloaded successfully.
May 11 14:15:37 WARNING A child process has gone or the iPrint Manager has just experienced a fatal error. It will be restarted by its monitor process.
May 11 14:15:37 INFO Starting print manager process with pid: 30997
May 11 14:15:37 INFO Starting iprintgw process with pid: 31039
May 11 14:15:37 INFO iPrint Manager '<Print Manager>' has successfully loaded.
May 11 14:15:40 WARNING A low memory error occurred while initializing the Job Production Manager.
May 11 14:15:43 WARNING The print manager (30997) received signal: 17 from process (31039) running with uid (107).
Upgrading from OES2 SP1 to OES2 SP3 caused the the print manager to not load.


Do the following to resolve the issue:
  1. Modify the rights on the /var/opt/novell/run/iprint/ directory.
    #chown iprint.www /var/opt/novell/run/iprint/

  2. Offline and then online the cluster resource.
    #cluster offline <iPrint_Cluster_Server>
    #cluster online <iPrint_Cluster_Server> <ClusterNodeName>

  3. The iPrint services should now be loaded correctly.

Additional Information

The issue can be detect by running the following command:
rpm -qa | grep iprint-server | xargs rpm -V
Output looks like this:
S.5....T  c /etc/opt/novell/iprint/httpd/conf/iprint_g.conf
S.5....T  c /etc/opt/novell/iprint/httpd/conf/iprint_ssl.conf
.....U..    /var/opt/novell/run/iprint
The "U" on the file means that the user rights differ from the ones being used when the rpm was installed.