Environment
Novell iPrint for Linux
Situation
The Print Manager or Driver Store within iManager show a status of Down, but the ipsmd or idsd is running on the server.
In case A: Clicking the REFRESH button within the Print Manager or Driver Store iManager page will cause the true status of ACTIVE to be shown.
In case A: Clicking the REFRESH button within the Print Manager or Driver Store iManager page will cause the true status of ACTIVE to be shown.
In case B: The status will continue to show as DOWN and the objects cannot be managed via iManager.
Resolution
Case A Cause:
A 672 error will show in the Print Manager or Driver Store error log. For example, the Driver Store error log, /var/opt/novell/log/iprint/idsd.log, reports the following:
WARNING directorySetVersion(): DSIModifyAttrVal failed on object CN=[DriverStore],OU=[OrganizationUnit],O=[Organization] with error -672
Case A Workaround:
Manually assign the Print Manager and/or Driver Store to be a trustee of itself and add Supervisor rights.
Restart the Print Manager (rcnovell-ipsmd restart) and/or Driver Store (rcnovell-idsd restart).
Case B Cause:
A 672 error will show in the Print Manager or Driver Store error log. For example, the Driver Store error log, /var/opt/novell/log/iprint/idsd.log, reports the following:
WARNING directorySetVersion(): DSIModifyAttrVal failed on object CN=[DriverStore],OU=[OrganizationUnit],O=[Organization] with error -672
The Print Manager eDirectory object, or similarly the Driver Store object, should have a trustee of itself with Supervisor rights. But, for reasons unknown at this time, in some situations that trustee assignment is not made.
Case A Workaround:
Manually assign the Print Manager and/or Driver Store to be a trustee of itself and add Supervisor rights.
Restart the Print Manager (rcnovell-ipsmd restart) and/or Driver Store (rcnovell-idsd restart).
Case B Cause:
This is being investigated by Novell
Case B Workaround:
Click the REFRESH button within the Print Manager iManager page to show the correct status.
Additional Information
Additional Information for Case A
When the Driver Store object loads for the first time, the Driver Store process (idsd) attempts to contact an eDir server. The eDir server the Driver Store chooses to contact is the server defined in DSServer1 [SomeServer] in the /etc/opt/novell/iprint/conf/idsd.conf. The Driver Store process (idsd) attempts to modify the Driver Store eDirectory object's "Version" attribute. The eDir server returns a -672 No Access message. In the /var/opt/novell/log/iprint/idsd.log this failure is recorded as:
WARNING directorySetVersion(): DSIModifyAttrVal failed on object CN=[DriverStore],OU=[OrganizationUnit],O=[Organization] with error -672
If the idsd is successful in updating that attribute, then it will update the "Status" attribute to the value of "2" (which means Active). Because of the previous 672 error trying to modify the "Version" attribute, the "Status" attribute is never updated. Therefore, iManager believes the Driver Store is Down, even though the process is running. The Driver Store is functional and can be managed using iprintman (see KB 3000249).
WARNING directorySetVersion(): DSIModifyAttrVal failed on object CN=[DriverStore],OU=[OrganizationUnit],O=[Organization] with error -672
If the idsd is successful in updating that attribute, then it will update the "Status" attribute to the value of "2" (which means Active). Because of the previous 672 error trying to modify the "Version" attribute, the "Status" attribute is never updated. Therefore, iManager believes the Driver Store is Down, even though the process is running. The Driver Store is functional and can be managed using iprintman (see KB 3000249).
Additional Information for Case B
- Create an alias DNS name
- update /etc/hosts file with a new name to resolve the IP of the server
- for example:
- 10.10.3.5 somecrazyname.companydomain.com
- Attempt to use AuthLDAPDNURL against that name.
- update the iprint_ssl.conf
- for example:
- Restart Apache
- rcapache2 restart
- Manage the Print Manager
- You will see a blank page in Firefox, or Page Cannot Be Displayed in IE
- Change iprint_ssl.conf back to the IP address or real DNS name and restart apache
- Manage the Print Manager
- The status will show DOWN, even though the print manager is running.