How do I trace a job in the Hosted logs? - c06379354
This information was shared by Mark Onischke in March 2017.
PDH Servers (Spool1)
http://psyslog.prod.printeron.net/synced/ppdh4001/
http://psyslog.prod.printeron.net/synced/ppdh4002/
http://psyslog.prod.printeron.net/synced/ppdh4501/
http://psyslog.prod.printeron.net/synced/ppdh4502/
Replication Server ( Customers do not see this server – only replicates jobs for redundancy)
http://psyslog.prod.printeron.net/synced/ppdh4510/
PDH Servers (Spool2)
http://psyslog.prod.printeron.net/synced/2000/
http://psyslog.prod.printeron.net/synced/ppdh2002/
http://psyslog.prod.printeron.net/synced/2500/
http://psyslog.prod.printeron.net/synced/ppdh2502/
PAS Servers
Status/PasPort/Processing Servers (Building A)
http://psyslog.prod.printeron.net/synced/at-5001/
http://psyslog.prod.printeron.net/synced/at-5002/
Status/PasPort/Processing Servers (Building E)
http://psyslog.prod.printeron.net/synced/at-5501/
http://psyslog.prod.printeron.net/synced/at-5502/
Processing Only Servers (Building A)
http://psyslog.prod.printeron.net/synced/at-5003/
http://psyslog.prod.printeron.net/synced/at-5004/
http://psyslog.prod.printeron.net/synced/at-5005/
http://psyslog.prod.printeron.net/synced/at-5006/
http://psyslog.prod.printeron.net/synced/at-5007/
Processing Only Servers (Building E)
http://psyslog.prod.printeron.net/synced/at-5503/
http://psyslog.prod.printeron.net/synced/at-5504/
http://psyslog.prod.printeron.net/synced/at-5505/
http://psyslog.prod.printeron.net/synced/at-5506/
http://psyslog.prod.printeron.net/synced/at-5507/
If you are looking for a specific job , follow these steps to make your life easier:
- Open the Status Server Log for AT-5001,5002,5501 and 5502
- Search for Job Reference number. (Example Below)
- The highlighted string will tell you which Processing server received the job. This will make it easier to locate the job instead of searching all the logs.
03-03-2017 08:59:39:188 0x0F78 E03 485394268 New Print job added to system.
03-03-2017 08:59:39:190 0x0F78 T01 485394268 File format ID: 0 - PON-PrintPassThru-FormatID
03-03-2017 08:59:39:194 0x036C T05 Received pending job notification.
03-03-2017 08:59:39:843 0x036C T03 485394268 Job Submitted to server (at-5505) for processing.
03-03-2017 09:14:58:384 0x10D0 T03 485394268 Removing completed and queried record.
The PAS servers can send to any of the 4 PDH’s because it’s a roundrobin DNS ( which is normally Spool1 ) . PDH servers are harder to read.
The current will always be pdh.log.
You need to match up time and date on the PDH logs for previous days or weeks.
Match the time with the PAS logs, then open the PDH log that is timestamped newer, but closest to the job timeframe. (example : pdh.log-2017-03-03-3.log 03-Mar-2017 03:26 10M )
Then open up the PDH log and do a search for the Job reference Number (referred to as the Transaction ID in the PDH logs). At this stage you'll also see the Job ID which will be referenced within PDH.
03/Mar/2017 08:59:41,643 - [INFO] h: Successfully renamed print job data file - the job is ready to be added to the system.
03/Mar/2017 08:59:41,644 - [INFO] g: Successfully received job: 8341362
03/Mar/2017 08:59:41,644 - [INFO] g: printer name: 300789874006
03/Mar/2017 08:59:41,644 - [INFO] g: document name: PO0001000004969400001.data
03/Mar/2017 08:59:41,644 - [INFO] g: document size: 13.6220703125
03/Mar/2017 08:59:41,644 - [INFO] g: document pages: 1
03/Mar/2017 08:59:41,644 - [INFO] g: user IP: 10.5.234.111
03/Mar/2017 08:59:41,644 - [INFO] g: user Email: sapp25.p3chem.net
03/Mar/2017 08:59:41,644 - [INFO] g: Transaction ID: 485394268
03/Mar/2017 08:59:41,692 - [INFO] g: Deferring notification of Client with ID: JE7H-AP75-PQ06 of available print job; event age: 24308; remainingTime: 28829
03/Mar/2017 08:59:41,709 - [INFO] ListenerPJAFileWriter: Alerting peer atat4001.prod.printeron.net of update to job with ID: 8341362
03/Mar/2017 08:59:41,709 - [INFO] ListenerPJAFileWriter: NotifyPeer request to peer:http://at4001.prod.printeron.net:631 for job with ID: 8341362 accepted because current message queue length: 0 is less than specified limit: 10000
03/Mar/2017 08:59:41,709 - [INFO] ListenerPJAFileWriter: About to update peer at:http://at4001.prod.printeron.net:631 of update to job with ID: 8341362
03/Mar/2017 08:59:41,727 - [INFO] ListenerPJAFileWriter: Peer athttp://at4001.prod.printeron.net:631 successfully notified of update to job with ID: 8341362
03/Mar/2017 08:59:41,727 - [INFO] ListenerPJAFileWriter: Alerting peer atat4501.prod.printeron.net of update to job with ID: 8341362
03/Mar/2017 08:59:41,727 - [INFO] ListenerPJAFileWriter: NotifyPeer request to peer:http://at4501.prod.printeron.net:631 for job with ID: 8341362 accepted because current message queue length: 0 is less than specified limit: 10000
03/Mar/2017 08:59:41,728 - [INFO] ListenerPJAFileWriter: About to update peer at:http://at4501.prod.printeron.net:631 of update to job with ID: 8341362 03/Mar/2017 08:59:41,739 - [INFO] ListenerPJAFileWriter: Peer athttp://at4501.prod.printeron.net:631 successfully notified of update to job with ID: 8341362
03/Mar/2017 08:59:41,739 - [INFO] ListenerPJAFileWriter: Alerting peer atat4502.prod.printeron.net of update to job with ID: 8341362
03/Mar/2017 08:59:41,739 - [INFO] ListenerPJAFileWriter: NotifyPeer request to peer:http://at4502.prod.printeron.net:631 for job with ID: 8341362 accepted because current message queue length: 0 is less than specified limit: 10000
03/Mar/2017 08:59:41,739 - [INFO] ListenerPJAFileWriter: About to update peer at:http://at4502.prod.printeron.net:631 of update to job with ID: 8341362 03/Mar/2017 08:59:41,754 - [INFO] ListenerPJAFileWriter: Peer athttp://at4502.prod.printeron.net:631 successfully notified of update to job with ID: 8341362
03/Mar/2017 08:59:41,754 - [INFO] ListenerPJAFileWriter: Replicating job with ID:8341362 with other cluster at http://p4bak.prod.printeron.net:631
03/Mar/2017 08:59:41,754 - [INFO] h: Successfully added job with ID:8341362 to the system