Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy 1.1; Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
Errors in the diagnostic log: - suggest that the Orbix Daemon is not running, when in fact it is. - indicate that the Device and Services Daemon fails to connect to the Extreme Coordinator. - Clients connecting to CORBA servers get timeout errors. See PR details for error messages. |
|
|
|
||
Cause |
Incorrect entries in the TCP/IP hosts file. The Locator Daemon updates the TCP/IP hosts file on each Prinergy node to improve Orbix performance by making IP address <-> hostname lookup faster. For example, opening a job window in Workshop can be up to 5 seconds faster with this compared to without. |
|
|
|
||
Solution |
1. Remove the incorrect IP address entries in the hosts file. 2. Restart Prinergy. See PR details for more detailed instructions. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
daemon, orbix |
|
|
|
||
Technical contact(s) |
Simon Chen |
|
Submitted by |
||
Date submitted |
||