Open Xu-Xihe opened 3 months ago
Indeed, cups needs quite a bit of ram and or disk space to spool big files. Maybe check out the processes while running the print job : create a shell in the container and check cpu/memory usage. Also, you might find additional log messages within the container that give a clue as to what went wrong (https://serverfault.com/questions/911797/where-does-cups-keep-print-job-information or https://xinet.support.northplains.com/hc/en-us/articles/360020687639-Checking-the-CUPS-Logs-and-Job-Files-on-the-Xinet-Server)
Unfortunately, I no longer have this setup available to test, so I can only help with suggestions and cannot debug myself.
I checked all of them but got nothing. There's even no error-files for cups. I noticed that on the Apple Community, someone has share the same question as I am facing. I suppose that the problems is between the virtual Airprint Printer and the IOS17 printing programme. They may have compatibility issues.
By the way, I'm using this image on my Openwrt router with an arm64 chip. May this causes these issues?
Unfortunately, I never used this on arm64, maybe someone from the growing community can share their experience.
I have already set nearly everything. I tested the notes and webs, they work well. But, when I try to print pdfs, things is changed. I tested a bit and found some wrrong. They could be divide to two conditions by their size. Whatever the kind of file is, the fails could be divided to two conditions by their size. For small one, they could be print successfully. But when big one (photos/pdfs with images etc.) is printed, they will fail. (The size limition seens to be around 100k) On IOS, it will show a pop-up tip says
The printer is no longer available
, and give two choice:try again
andcancel
. In the website interface, I could see the task inheld since
. And if the big files finally printed, their will be a warn:When I use
docker logs -f <name-of-your-container>
to show logs, it looks like this:I searched around, added
DefaultEncryption Never
intocupsd.conf
and restart, but still can't print big files and continuousl showing the pop-up tip. Sometimes I found, after I pressedprint
for a long time, my printer will work suddenly and print what I wanted before. I suppose that is because the network between IOS and CUPS is not steady enough for big ones to convey. But I have no idea why it is so weak.