All print jobs queued up

413 views
Skip to first unread message

Kyle Beatty

unread,
Oct 1, 2012, 2:35:01 PM10/1/12
to gcp-dev...@googlegroups.com
Since the latest Chrome update, my users have been unable to print to any of the cloud printers I have had set up for them. Every job goes into queued status. I have already deleted and re-added all 33 printers with the only change being the first 4 print jobs printed fine. Since then, every job has the queued status. Cloud print had been working fine for me and my users until Friday.


Yuri Dolgov

unread,
Oct 1, 2012, 7:04:33 PM10/1/12
to Google Cloud Print Developers
Hey Kyle,

sorry to hear that,

we didn't notice any change from our side, it looks like same percentage of print jobs are still getting printed.
Can you give us some more info on what Chrome version do you use and what kind of printers do you use?
How those printers are connected? Are they Cloud Ready or you use Cloud Print Connector in Chrome to
register them?


On Mon, Oct 1, 2012 at 11:35 AM, Kyle Beatty <kbe...@friendscentral.org> wrote:
Since the latest Chrome update, my users have been unable to print to any of the cloud printers I have had set up for them. Every job goes into queued status. I have already deleted and re-added all 33 printers with the only change being the first 4 print jobs printed fine. Since then, every job has the queued status. Cloud print had been working fine for me and my users until Friday.





--
- Yuri

Albert Bodenhamer

unread,
Oct 1, 2012, 7:24:23 PM10/1/12
to gcp-dev...@googlegroups.com
Did something possibly change in the network?  It sounds as though outgoing connections on port 5222 (XMPP) are being blocked so the connector can't get notifications.
--
Albert Bodenhamer | Software Engineer | abodenha@chromium.org 

Kyle Beatty

unread,
Oct 1, 2012, 7:53:42 PM10/1/12
to gcp-dev...@googlegroups.com
I'm using Version 22.0.1229.79 m. That showed up on Friday I believe. I didn't notice it was a problem until a teacher came in on Sunday and couldn't print. We have a mix of Chromeboxes, Chromebooks, and Windows XP/7 machines. None of them can print to our cloud print server. They could print on Friday, but not since then. I don't think anything changed on the network. We don't block anything going out of our firewall and the machine the cloud print is set up on is excluded from any firewall rules. We use a mix of HP LaserJets, and Sharp copiers. We have been using the cloud print connector successfully since it was first released. I'm attaching a screenshot of what our current queue looks like.
Albert Bodenhamer | Software Engineer | abod...@chromium.org 
cloudprint.png

Yuri Dolgov

unread,
Oct 1, 2012, 10:05:40 PM10/1/12
to Google Cloud Print Developers
I think starting from version 22 we now prefer 413 port over 5222 port for push notification, could that be a problem for your case?

I agree with Albert here, it seems that push notifications that we send to your connector are not getting through.
Gene, Vitaly can you help to debug this problem?
--
- Yuri

Vitaly Buka

unread,
Oct 1, 2012, 10:28:52 PM10/1/12
to gcp-dev...@googlegroups.com
Can you try to do following on machine with connector:
1. Close all chrome instances
2. Run chrome with --enable-logging --v=1
3. Try to print something (reproduce issue)
4. Close all chrome processes
5. Find log file, something like C:\Users\USER_NAME\AppData\Local\Google\Chrome\User Data\chrome_debug.log
6. Send file to me, vital...@chromium.org, or ge...@chromium.org

Gene Gutnik

unread,
Oct 1, 2012, 11:22:27 PM10/1/12
to gcp-dev...@googlegroups.com
Hi Kyle,
I assume you are running Chrome connector on Windows machine, correct? To check if the problem is with delivering notifications or somewhere else could you please try following on the machine running Chrome connector:

- Close all Chrome windows.
- Open "Task Manager", click Processes tab, add Command Line column (menu View -> Select Columns... -> select Command Line down in the list -> click OK)
- See if you still have Chrome process running. If you do make sure command line contains "--type=service" string. (if you don't have Chrome process with "--type=service" that is the problem)
- Select Chrome process with "--type=service" in command line and click "End Process" button.
- Now you should have no Chrome processes running.
- Start Chrome browser now.
- Make sure Chrome process with "--type=service" also got started. (If it does not, go to Chrome menu -> Settings -> Advanced Settings check that Cloud Print is enabled. If so, "--type=service" should start now.) If for some reasons process did not start or cloud print is disabled in settings, let me know.
- Now, a Chrome process "--type=service" should poll all queued jobs and start printing them. If it does not - let me know, may be you have orphan/duplicate printers issue. If it does, wait until it printed the last job and try sending a new job to one of your printers. If it printed all old jobs, but failed to print new ones, it is likely and issue delivering print jobs notifications.

Could you please try steps above and let me know results.
Thanks,
Gene


On Mon, Oct 1, 2012 at 4:53 PM, Kyle Beatty <kbe...@friendscentral.org> wrote:

Albert Bodenhamer

unread,
Oct 2, 2012, 12:34:57 PM10/2/12
to gcp-dev...@googlegroups.com
On Mon, Oct 1, 2012 at 7:05 PM, Yuri Dolgov <ydo...@google.com> wrote:
I think starting from version 22 we now prefer 413 port over 5222 port for push notification, could that be a problem for your case?

That change doesn't go live until 23 and the fallback behavior is the same as what currently exists.



--
Albert Bodenhamer | Software Engineer | abodenha@chromium.org 

Kyle Beatty

unread,
Oct 3, 2012, 10:53:41 AM10/3/12
to gcp-dev...@googlegroups.com
This is a Windows 2003 server so there isn't a "Command line" column so I can't tell if it is running as a service.  I have tried running that line from the Run box, but Chrome never opens. There is a spawning of Chrome processes, but they all die and nothing gets printed. If I leave Chome open on the server, some jobs get processed for a while and then they get queued up again.

thanks,
Kyle
chrome_debug.log

Gene Gutnik

unread,
Oct 3, 2012, 5:27:37 PM10/3/12
to gcp-dev...@googlegroups.com
Could you please try Process Explorer from Microsoft (http://technet.microsoft.com/en-us/sysinternals/bb896653), it should be able to show a command line for the process (right-click on the columns header -> Select Comulns... -> Command Line).

Also, could you please try using Chrome Beta (https://www.google.com/landing/chrome/beta/) instead of Stable for Cloud Print. New beta has a fix, trying to connect to port 443 instead of 5222 for XMPP notifications, and I think it might make notifications more stable in your case. Could you please try it and let me know?

The two possible problems I can see from your description are:
- Cloud print process is crashing / exiting for some reasons (specific print job?)
- Notification mechanism failed, so we can't notify connector about new jobs.

In the first case, you should see no chrome.exe with "--type=service" command line running.
In the second, chrome beta might help.

Thanks,
Gene

Kyle Beatty

unread,
Oct 4, 2012, 8:37:13 AM10/4/12
to gcp-dev...@googlegroups.com
Gene,

I was able to see the command line for the chrome process and I did see the type=service. Also, I installed the beta version, but immediately upon startup, I got the "Aw Snap" page. I uninstalled the beta and was able to reinstall the stable version without any issues.  Today is probably the worst day for me to get any great data on printing issues, as both the middle and high school students and faculty are out on field trips all day. Nice to be them, huh?  I can do some solo testing, but it won't be the same.

Kyle
--
 
Kyle Beatty
Network Administrator
Friends' Central School
610-658-6514
"If you think there is a better way, 
there probably is. Just ask us."
The Fishbowl 

Jeff Ruedinger

unread,
Oct 4, 2012, 9:41:01 AM10/4/12
to gcp-dev...@googlegroups.com
I am having the same issue with my ChromePrint Server. I have several jobs hung up. I have followed the steps in the listing and I do have the --type=service line in the chrome.exe process. 

Gene Gutnik

unread,
Oct 11, 2012, 7:37:13 PM10/11/12
to gcp-dev...@googlegroups.com
HI Kyle,
Do you still have problems printing to Cloud Print?
Gene

Bjorn Behrendt

unread,
Oct 18, 2012, 11:21:00 AM10/18/12
to gcp-dev...@googlegroups.com
I am having the same issue.   Cloudprint works for a day or so then stops.   If I go onto the server and open up chrome all the qued print jobs start.   What service is crashing and how can I fix it.

Yuri Dolgov

unread,
Oct 31, 2012, 11:19:43 PM10/31/12
to Google Cloud Print Developers
Hey Bjorn, does it still happen for you? If so can you send us Chrome version that you are using and OS?
--
- Yuri

Bjorn Behrendt

unread,
Nov 1, 2012, 11:53:28 AM11/1/12
to gcp-dev...@googlegroups.com
Version 23.0.1271.52 beta-m with windows 2003 server R2 standard.

The problem is that the computer is a server and does not stay logged in, or should not stay logged in for security reasons.    I put a helpdesk ticket in and I have been added to an early bata program of a chromeprint service that I am hoping will be a better fit for a school.



Bjorn Behrendt M.Ed ~ Never Stop Learning
   Google Apps For Education Certified Trainer
My Sites
 ~ Edlisten.com EdListen 3: Creating a Student Podcast Show 1 (10/26/2012)
 ~ AskBj.net ~ Online Training and Ed Tech Resources
 ~ VTed.org ~ Vermont's Personal Learning Network

gClassFolders ~ Create Google folders for your class.
Reply all
Reply to author
Forward
0 new messages