Unable to open file "/var/spool/cups/d00004-001" - Permissiondenied

[Evan Bradley]

Nevermind.  A coworker fixed this problem by setting the permissions on the $prefix/var/spool/cups directory to allow all users to execute...which is exactly what I tried.  For some reason my changes were disregarded when the cups service was recycled, but they are maintained now.

<sigh>  O_o

Thanks anyway!


Evan

> I'm having this same problem, and if I manually change the permissions with a 'chmod +x', they are reset as soon as the cups scheduler is restarted.
>
> Any updates?
>
>
> Evan
>
> > Thanks Rob,
> > This is weird, I set the permissions on that directory to have the cups group and cups changes them back:
> > #chgrp lp /var/spool/cups
> > #ls -al /var/spool/cups
> > drwx--x--- 4 root lp 72 Jul 16 09:35 /var/spool/cups
> > #/etc/init.d/cups restart
> > cups: restarted scheduler.
> > #ls -al /var/spool/cups
> > drwx--x--- 4 root nogroup 72 Jul 16 09:35 /var/spool/cups
> >
> > I'll try working with this, but if you know which config or file is changing that on me it would probably save me some time...
> > Kyle
> >
> > > Kyle Jones wrote:
> > > > Hello,
> > > > I am trying to get cups working on a non-standard Debian install and after much fiddling I am finally able to get cups to get to the point of allowing me to set up printers and attempt to print a test page.
> > > > The problem seems to be that the jobs stops at "Unable to open file "/var/spool/cups/d00004-001" - Permission denied"
> > > > Below is a copy of the cups log as well as my cupsd.conf and an ls -al /var/spool/cups
> > > >
> > > > Any help would be greatly appreciated.
> > > > If this is a particularly difficult problem to solve then I would be willing to talk $s...
> > > > Thanks,
> > > > Kyle
> > > >
> > >
> > > I had the same problem.  A quick truss showed:
> > >
> > > 13056:  open64("/usr/local/var/spool/cups/d00004-001", O_RDONLY) Err#13
> > > EACCES [file_dac_search]
> > >
> > > The file_dac_search was a dead giveaway (I love Solaris 10).  It turned
> > > out that the cups user had no execute access on /usr/local/var/spool.  A
> > > quick chmod +x on that directory fixed the problem.  Check the
> > > permissions on every directory leading down to your spool directory.
> > >
> > > Rob
> >
>