[cups] Unable to print via CUPS from MacOS Sierra

Lucian Botha lucianbotha at gmail.com
Mon Oct 31 03:00:55 PDT 2016


Hi Helge

Papercut has no errors also I get the exact same behavior using my old
server which doesn't have papercut.

Lucian

On Thu, Oct 27, 2016 at 10:59 AM, Helge Blicke <helgeblischke at web.de> wrote:

> I'd first look at any logging from the
> papercut backend, especially regarding SELinux.
> As CUPS is concerned, the job has
> printed successfully.
>
> Helge
>
>
> > Am 26.10.2016 um 11:15 schrieb Lucian Botha <lucianbotha at gmail.com>:
> >
> > Hi
> >
> > I have the attached my logs, I have set it on verbose to make sure we
> catch
> > what ever errors might cause this. The job I'm attaching ran at 07:44
> hence
> > the extract from that time for all files/logs. Like I explain in the
> post,
> > we're getting to the printer and nothing prints even though we don't see
> > any errors and the printers log (also attached) shows that it printed
> with
> > success.
> >
> > Regards,
> > Lucian
> >
> >> On Tue, Oct 25, 2016 at 7:44 PM, Michael Sweet <msweet at apple.com>
> wrote:
> >>
> >> Lucian,
> >>
> >>> On Oct 24, 2016, at 8:08 AM, Lucian Botha <lucianbotha at gmail.com>
> wrote:
> >>>
> >>> We have a CUPS server running on Ubuntu 14.04 which has about 10 HP
> >>> printers configured. We have a mix of Windows, Linux and Mac clients
> >>> printing to the server flawlessly.
> >>>
> >>> Flawlessly, until some of the Macs were upgraded to Sierra recently.
> Now,
> >>> if a user tries to print via the server, the client behaves normally,
> as
> >>> does cups. The job is processed through the server and the job log
> shows
> >>> the job printed ok. However, nothing emerges out of the printer. The
> Mac
> >>> clients can print directly to the printer using AirPrint.
> >>>
> >>> We had an older version of cups so we built a new 16.04 server with the
> >>> latest cups, same result. We can print directly to the printer from the
> >>> print server on port 9100 so that part is working ok.
> >>>
> >>> Is it safe to assume the problem does not lie with cups, rather with
> >> MacOS
> >>> 12.12? Anyone have any troubleshooting ideas?
> >>
> >> At this point there is not enough information to say.  You'll need debug
> >> logs from both the client and server systems, and a copy of the spool
> file
> >> that gets to the CUPS server.
> >>
> >> _________________________________________________________
> >> Michael Sweet, Senior Printing System Engineer
> >>
> >> _______________________________________________
> >> cups mailing list
> >> cups at cups.org
> >> https://lists.cups.org/mailman/listinfo/cups
> >>
> > <client_log.txt>
> > <server_log.txt>
> > _______________________________________________
> > cups mailing list
> > cups at cups.org
> > https://lists.cups.org/mailman/listinfo/cups
> _______________________________________________
> cups mailing list
> cups at cups.org
> https://lists.cups.org/mailman/listinfo/cups
>



More information about the cups mailing list