Operation Shutdown Printer Agent: Error: 506D0030

  • 7006770
  • 01-Sep-2010
  • 16-Jul-2013


Novell iPrint for Linux


The following message is frequently repeated throughout the iPrint "Latest Client Events" log.

Operation Shutdown Printer Agent:,
 Error: 506D0030 - insufficient rights,  
User Name, Not Bound,  
Address, unknown,  
Object Name: unknown
(Client Interface)

The "Client Interface" status shows BAD in iPrint Health Monitor web page (https://<IPorDNSiPrintServer>/PsmStatus).


The following workarounds will cause the problem to be gone until the Print Manager process crashes again.

Workaround 1:
Use this workaround if having printing unavailable for 1 minute is acceptable.
Type these commands:
rcnovell-ipsmd stop
killall -9 ipsmd
killall -9 iprintgw
rcnovell-ipsmd start

Workaround 2:
Use this workaround if printing cannot be unavailable for 1 minute.
Kill the orphaned iprintgw processes.
  1. At a terminal session to the iPrint server, type:
    • ps -ef | grep iprint
  2. Make note of each orphaned iprintgw process
    • Orphaned iprintgw processes are those with a PPID of 1.  See Note3 below to understand how to find which iprintgw processes have a PPID of 1.
  3. Kill each orphaned iprintgw process.
    • kill -9 <pidFromStep-2>
    • <repeat for each orphaned iprintgw process.>
  4. Confirm only one, non-orphaned iprintgw remains.
    • ps -ef | grep iprint
      • Kill remaining orphaned iprintgw processes.
This is a workaround because these steps don't attempt to prevent the iprintgw processes from becoming orphaned.  These steps will simply stop the above messages from being logged to the Client Interface log.

Additional Information

Note1: Access the "Latest Client Events" log by going to https://<IPorDNSiPrintServer>/PsmStatus/Events/Client

Note2: View the "Client Interface" status by going to https://<IPorDNSiPrintServer>/PsmStatus/Advanced?submit=submit

Note3: When executing the ps -ef command, the process information will be listed as follows:

root      9300     1  0 Aug25 ?        00:04:16 /opt/novell/iprint/bin/iprintgw
root     16745 16743  0 10:12 pts/5    00:00:00 grep iprint
iprint   19601     1  0 Jul19 ?        00:07:03 /opt/novell/iprint/bin/idsd
iprint   19605     1  0 Jul19 ?        00:00:00 /opt/novell/iprint/bin/ipsmd
root     21625     1  0 Jul19 ?        01:25:41 /opt/novell/iprint/bin/iprintgw
iprint   32446 19605  0 Aug31 ?        00:06:26 /opt/novell/iprint/bin/ipsmd
root     32464 32446  0 Aug31 ?        00:00:34 /opt/novell/iprint/bin/iprintgw

Look for the iprintgw processes which have a Parent Process Identifier (PPID) of 1.  In this example, there are two which fit that description; 9300 and 21625.  These two iprintgw processes are called "orphaned" because their PPID of 1, and not the valid PPID which matches the PID of the child ipsmd process.   Note:  The child ipsmd process is the process which has a PPID other than 1.

In this example, the iprintgw PIDs to kill are:
kill -9 9300
kill -9 21625

Note 4:  This problem results from the Print Manager process (ipsmd) crashing.  The ipsmd processes is designed to auto restart after a crash.  Some times, during this crash and auto restart procedure, the previous gateway process (iprintgw) will remain.  We call this an orphaned iprintgw process.  The orphaned gateway process will attempt to communicate to the ipsmd process, but the ipsmd process will not understand the requests.  Each communication attempt will result in an error being placed in the "Latest Client Events" (see above for the exact message).  These messages are harmless, but trigger the Print Manager error threshold and therefore the Print Manager status will show Bad.