1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • cups and "Removing document files"

    From William Unruh@2:250/1 to All on Mon Jul 12 18:01:27 2021
    Cups is dumping error messages into my /var/log/cups/error_log file

    D [12/Jul/2021:09:48:37 -0700] [Job 143] Removing document files.
    D [12/Jul/2021:09:48:37 -0700] cupsdMarkDirty(---J-)
    D [12/Jul/2021:09:48:37 -0700] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files"

    But none of the files are actually removed from /var/spool/cups


    Since I have about 20 cxxxxxx type files in /var/spool/cups it cycles
    through these about 1 ever 10 sec giving me the above errors for each
    of them.
    I have put
    PreserveJobHistory Yes
    into /etc/cups/cupsd.conf
    and restarted, but it makes no difference.

    What can I do to stop this nonesense

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Mon Jul 12 19:31:41 2021
    On Mon, 12 Jul 2021 13:01:27 -0400, William Unruh <unruh@invalid.ca> wrote:

    Cups is dumping error messages into my /var/log/cups/error_log file

    D [12/Jul/2021:09:48:37 -0700] [Job 143] Removing document files.
    D [12/Jul/2021:09:48:37 -0700] cupsdMarkDirty(---J-)
    D [12/Jul/2021:09:48:37 -0700] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files"

    Try running (as root) ...

    systemctl stop cups.service
    chgrp -cR lp /var/spool/cups
    systemctl start cups.service
    lpq

    If the lpq then shows there are stopped jobs use lprm to remove them with
    "lprm job-id(s)" replacing job-id(s) by the job numbers shown by lpq.

    Regards Dave Hodgins

    --
    Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
    email replies.

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Mon Jul 12 22:21:39 2021
    On 2021-07-12, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
    On Mon, 12 Jul 2021 13:01:27 -0400, William Unruh <unruh@invalid.ca> wrote:

    Cups is dumping error messages into my /var/log/cups/error_log file

    D [12/Jul/2021:09:48:37 -0700] [Job 143] Removing document files.
    D [12/Jul/2021:09:48:37 -0700] cupsdMarkDirty(---J-)
    D [12/Jul/2021:09:48:37 -0700] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files"

    Try running (as root) ...

    systemctl stop cups.service
    chgrp -cR lp /var/spool/cups
    systemctl start cups.service
    lpq

    If the lpq then shows there are stopped jobs use lprm to remove them with "lprm job-id(s)" replacing job-id(s) by the job numbers shown by lpq.

    Unfortunately both /var/spool/cups and all files in it are already group
    lp.

    sudo ls -la /var/spool/cups
    total 836
    drwx--x--- 3 root lp 4096 Jul 12 09:44 .
    drwxr-xr-x 12 root root 4096 Feb 21 2020 ..
    -rw------- 1 root lp 1074 Apr 20 07:28 c00106
    -rw------- 1 root lp 1045 Apr 20 11:44 c00107
    -rw------- 1 root lp 1074 Apr 20 08:45 c00108
    -rw------- 1 root lp 825 Apr 20 09:26 c00109
    -rw------- 1 root lp 1074 Apr 20 09:11 c00110
    -rw------- 1 root lp 1118 May 12 11:01 c00111
    -rw------- 1 root lp 1114 May 24 14:11 c00112
    ....

    And lpq -a shows empty.

    sudo lpq -a
    no entries

    Should /var/spool/cups be readable/writeable by lp?
    The above permission were what was installed by Mageia

    Note that the above permissions are identical to those on another Mga8
    machine where I do not get those error messages.


    Regards Dave Hodgins


    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim Whitby@2:250/1 to All on Tue Jul 13 00:09:23 2021
    On Mon, 12 Jul 2021 21:21:39 +0000, William Unruh wrote:

    On 2021-07-12, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
    On Mon, 12 Jul 2021 13:01:27 -0400, William Unruh <unruh@invalid.ca>
    wrote:

    Cups is dumping error messages into my /var/log/cups/error_log file

    D [12/Jul/2021:09:48:37 -0700] [Job 143] Removing document files.
    D [12/Jul/2021:09:48:37 -0700] cupsdMarkDirty(---J-)
    D [12/Jul/2021:09:48:37 -0700] cupsdSetBusyState: newbusy="Dirty
    files", busy="Dirty files"

    Try running (as root) ...

    systemctl stop cups.service chgrp -cR lp /var/spool/cups systemctl
    start cups.service lpq

    If the lpq then shows there are stopped jobs use lprm to remove them
    with "lprm job-id(s)" replacing job-id(s) by the job numbers shown by
    lpq.

    Unfortunately both /var/spool/cups and all files in it are already group
    lp.

    sudo ls -la /var/spool/cups total 836 drwx--x--- 3 root lp 4096 Jul
    12 09:44 .
    drwxr-xr-x 12 root root 4096 Feb 21 2020 ..
    -rw------- 1 root lp 1074 Apr 20 07:28 c00106 -rw------- 1 root lp
    1045 Apr 20 11:44 c00107 -rw------- 1 root lp 1074 Apr 20 08:45 c00108 -rw------- 1 root lp 825 Apr 20 09:26 c00109 -rw------- 1
    root lp 1074 Apr 20 09:11 c00110 -rw------- 1 root lp 1118 May
    12 11:01 c00111 -rw------- 1 root lp 1114 May 24 14:11 c00112 ...

    And lpq -a shows empty.

    sudo lpq -a no entries

    Should /var/spool/cups be readable/writeable by lp?
    The above permission were what was installed by Mageia

    Note that the above permissions are identical to those on another Mga8 machine where I do not get those error messages.

    Interesting. The group lp cannot read or write to these files.
    Maybe changing the mode to 660 would help?



    Regards Dave Hodgins



    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: XSUsenet (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Tue Jul 13 01:44:49 2021
    On 2021-07-12, Jim Whitby <news@spockmail.net> wrote:
    On Mon, 12 Jul 2021 21:21:39 +0000, William Unruh wrote:

    On 2021-07-12, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
    On Mon, 12 Jul 2021 13:01:27 -0400, William Unruh <unruh@invalid.ca>
    wrote:

    Cups is dumping error messages into my /var/log/cups/error_log file

    D [12/Jul/2021:09:48:37 -0700] [Job 143] Removing document files.
    D [12/Jul/2021:09:48:37 -0700] cupsdMarkDirty(---J-)
    D [12/Jul/2021:09:48:37 -0700] cupsdSetBusyState: newbusy="Dirty
    files", busy="Dirty files"

    Try running (as root) ...

    systemctl stop cups.service chgrp -cR lp /var/spool/cups systemctl
    start cups.service lpq

    If the lpq then shows there are stopped jobs use lprm to remove them
    with "lprm job-id(s)" replacing job-id(s) by the job numbers shown by
    lpq.

    Unfortunately both /var/spool/cups and all files in it are already group
    lp.

    sudo ls -la /var/spool/cups total 836 drwx--x--- 3 root lp 4096 Jul
    12 09:44 .
    drwxr-xr-x 12 root root 4096 Feb 21 2020 ..
    -rw------- 1 root lp 1074 Apr 20 07:28 c00106 -rw------- 1 root lp
    1045 Apr 20 11:44 c00107 -rw------- 1 root lp 1074 Apr 20 08:45
    c00108 -rw------- 1 root lp 825 Apr 20 09:26 c00109 -rw------- 1
    root lp 1074 Apr 20 09:11 c00110 -rw------- 1 root lp 1118 May
    12 11:01 c00111 -rw------- 1 root lp 1114 May 24 14:11 c00112 ...

    And lpq -a shows empty.

    sudo lpq -a no entries

    Should /var/spool/cups be readable/writeable by lp?
    The above permission were what was installed by Mageia

    Note that the above permissions are identical to those on another Mga8
    machine where I do not get those error messages.

    Interesting. The group lp cannot read or write to these files.
    Maybe changing the mode to 660 would help?

    Yes. It is the same on two different computers, one of which does not
    give those error messages, and the other which does. I tried to change
    the permission to rwxrwx--- with root.lp, but that makes no difference
    either.


    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Tue Jul 13 02:05:26 2021
    On Mon, 12 Jul 2021 20:44:49 -0400, William Unruh <unruh@invalid.ca> wrote:
    Yes. It is the same on two different computers, one of which does not
    give those error messages, and the other which does. I tried to change
    the permission to rwxrwx--- with root.lp, but that makes no difference either.

    Try running the lpq command again with those permissions.

    Regards, Dave Hodgins

    --
    Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
    email replies.

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Tue Jul 13 05:30:55 2021
    On 2021-07-13, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
    On Mon, 12 Jul 2021 20:44:49 -0400, William Unruh <unruh@invalid.ca> wrote:
    Yes. It is the same on two different computers, one of which does not
    give those error messages, and the other which does. I tried to change
    the permission to rwxrwx--- with root.lp, but that makes no difference
    either.

    Try running the lpq command again with those permissions.

    Yes, I did.
    No change. Nothing waiting to print.

    However I did discover that something (not msec) is changing the
    permissions back to 710


    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)