Emailed the following to Troy:<\/p>\n
“Could you check someone out for me. I’m on the library reference desk right & we ran into an issue where there were about 15 print jobs that were all routing through just one printer on the first floor. The printer 593528 was on, said ready. But nothing was coming out. And I find it slightly strange that with that many print jobs, they weren’t routed equally between the two. Could you check it out & make sure nothing funky is up?”<\/p>\n
His follow-up:<\/p>\n
“Unfortunately that is a goprint bug. not 5 minutes ago, I finished sending another very lengthy email to goprint\u2019s engineers to try and get a solution to that problem. The issue is that goprint is seeing that other printer as offline, even though it isn\u2019t. GoPrint checks the printer statuses on a frequent basis, and at some point it becomes \u201cstuck\u201d. And in this case, its become stuck in \u201coffline\u201d status. so it wont route any jobs to it. This is the same cause of when one of the printers gets turned off because of a jam or something, and goprint continues to send jobs to it because its stuck in an \u201conline\u201d phase.<\/p>\n
To fix it, I have to keep restarting the goprint service on the server. This causes about a 30 second outage. I don\u2019t like to do it during business hours, but sometimes I have no choice. Like now\u2026because Im seeing 5 printers as offline, that shouldn\u2019t be.”<\/p>\n
We found a window of time for him to resolve the problem, but thought I’d throw it on here for posterity’s sake.<\/p>\n","protected":false},"excerpt":{"rendered":"
Emailed the following to Troy: “Could you check someone out for me. I’m on the library reference desk right & we ran into an issue where there were about 15 print jobs that were all routing through just one printer on the first floor. The printer 593528 was on, said ready. But nothing was coming… <\/p>\n