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.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
When trying to start any JTP on a secondary server, the status always reads "Starting". No JTP processes are listed in the processes list in the task manager. The process does not even attempt to start. You are using DHCP and DNS servers at your site. Communication between primary and secondary seems to be okay. You are able to ping the primary from the secondary. You are able to ping the secondary from the primary. No errors in diagnostic logs on the secondary server. Confirmed Araxi Service account has the same password as the primary. Message from primary server: i 04Aug99 04:36:23.171-UTC [245.228] GALILEO ARAXI PDeviceAndServiceD.StartAService228 DASS_Service.cpp(413): DASS_Service::Start: Starting JTP: supraassem.exe NEWTON ProofOnNewton_as_PROOF Z 04Aug99 04:37:24.109-UTC [245.456] GALILEO ARAXI PDeviceAndServiceD.XCON_JobSub::XCON_Callback::run DASS_OpCon.cpp(173): DASS_OpCon::CommandResponseMsg: Message from Extreme: Error starting JTP: supraassem.exe |
|
|
|
||
Cause |
There is a static entry in the Domain Name Server (DNS). It has the same host name but resolves to an IP address that has been assigned to another server. When you are pinging the secondary server, you get a proper reply, but from the wrong server. If you run ipconfig on the secondary, you will notice the address is different than the one resolved on the primary. When Device and Services Daemon starts the JTPs on the secondary, it communicates with Extreme Coordinator, which contracts supralauncher to start the process on the secondary server. In this case, Coordinator cannot contact supralauncher because of the wrong IP address. |
|
|
|
||
Solution |
1) Get the correct IP address: Run ipconfig on the secondary. 2) Add the correct IP address to the hosts file on the primary. Located at %systemroot%\system32\drivers\etc\hosts. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
JTP, networking |
|
|
|
||
Technical contact(s) |
Simon Chen |
|
Submitted by |
||
Date submitted |
||