jobs just hang in queued status

[mowglie]

i used cloudprint & cupscloudprint on an Ubuntu 12.04 LTS server, no gui and no Chromium browser. running cloudprint -d on server & all clients are also same ubuntu.

uploaded all my cups printers to GCP just fine (via cloudprint). all the GCP ready printers came to my print server fine too (via cupscloudprint).

i can print fine to GCP ready printers (using the above GCP/CUPS combo) & directly to the non-GCP printers (aka using CUPS only, no GCP).

but when i print to a non-GCP ready printer via GCP, the job gets to GCP & is shown as being queued, but remains so & never prints.

other symptoms:
sometimes (not always) the server now shows error message "ERROR: Couldn't connect to Cloud Service: will try again in 60 secs."
something dumps a file into the /tmp directory on the server and this happens every minute until the print job is cancelled in GCP.

i've searched extensively & cant find the cause or solution. I do not want to load a gui and chromium onto a minimal server. cloudprint+cupscloudprint should = printing to non-GCP printers from my clients.

pls help!

[davesteele]

I haven't heard of anyone running both cloudprint and cupcloudprint. At a minimum, I'd make sure you are not attempting to serve your GCP-ready printers through cloudprint.

[mowglie]

Uhh there r entire sites detailing doing this. U do realize these 2 tools
do entirely different things?

[davesteele]

Yes, I realize.

Good luck.

[armooo]

Can you provide debug logging output when this happens? You can do that by running with cloudprint.py -v.