Bug 13861

Hmmm, access log shows something under mga4, but you need to press Ctrl+R to see it. But will take a look.

CC: (none) => doktor5000

ping.
I have some cups problems lately on cauldron and would like to see an error log...
/var/log/cups/error_log* are from before I upgraded from mga4 to cauldron a half year ago.  Earlier the error log used to be tens of lines a month.
On my wifes computer where I installed cauldron fresh a few months ago there is no error_log files. 
Is it written somewhere else or not at all?

/etc/cups/cupsd.conf contain the line
  LogLevel warn


In system log i see things like below if i start printing two pages within seconds from each other from two instances of Okular, and the second Okular get unresponsive while its connection to cups is held.  That is my problem i experience as a user but to debug first step is to get error logging working...

apr 20 16:06:36 svarten systemd[1]: Started CUPS Scheduler.
apr 20 16:06:36 svarten systemd[1]: Started CUPS Scheduler.
apr 20 16:07:00 svarten cupsd[3170]: Max clients reached, holding new connections...
apr 20 16:07:06 svarten systemd[1]: Started CUPS Scheduler.
apr 20 16:07:06 svarten systemd[1]: Started CUPS Scheduler.

Had a look on my parents box for some other printing issue on mga5.
access_log is displayed. page_log is displayed, although empty, but the file /var/log/cups/page_log is also empty. 

But when clicking on error_log button it says:
Error: not found

The file exists (although it belongs to group sys instead of lp like the other logs, but changing that does not help) and error_log is also completely empty, no matter what LogLevel directive is in cups.conf. I even tried with "debug2" but no content is written.

Really seems like a bug, will have to check our package vs. upstream.

@Thierry: Do you have any idea why error_log logfile is empty?

Assignee: bugsquad => doktor5000
CC: (none) => thierry.vignaud
Status: NEW => ASSIGNED

(In reply to Florian Hubold from comment #3)

> @Thierry: Do you have any idea why error_log logfile is empty?

Cause seems to be shown in bug 16843:

(In reply to w unruh from comment #0)
> Description of problem:
> In all of the documentation for cups, it is stated that that output of for
> example LogLevel debug goes to /var/log/cups/error_log. In fact in the
> cupsd.conf configuration file it states that explicitly. However, Mageia's
> default is to send the logs to the systemd journal. 
> In /etc/cups/cups-files.conf is the line
>  
> ErrorLog journal
> 
> This is extremely confusing and is liable to be overlooked. 
> At least there should be a note in cupsd.conf that the location of the error
> log is set in cups-file.conf

Depends on: (none) => 16843
Hardware: x86_64 => All
Source RPM: cups-1.7.5-1.mga5.src.rpm => cups

Current state cups 2.1.3: at http://localhost:631/admin in firefox, buttons
[ View Access Log ]  ->  an empty page
[ View Error Log ]  -> "Not found"
[ View Page Log ]  ->  an empty page

reloading dont help.

Above after it have asked for root acess.

Strangely if i instead of localhost use http://192.168.0.40:631/admin ;
all buttons result in "Forbidden" ; why do it not ask for root pass then?

Still valid without change.

Reassigning to cups maintainer.

Due to "ErrorLog journal" from /etc/cups/cups-files.conf as mentioned in comment #4 error log seems to not exist as file anmyore, hence cannot be shown via web frontend. Although I still believe this should show the journalctl output then, but this might be an upstream issue.

The other logs are not working as expected, /var/log/cups/access_log is configured in /etc/cups/cups-files.conf and the default AccessLogLevel is actions hence it should show all messages when print jobs are submitted, held, released, modified, or canceled and the same for printers or whole classes.

pagelog is empty, see the comment on that in bug 16843.

BTW; both /var/log/cups/access_log and /var/log/cups/page_log stay at 0 byte size here.

Whiteboard: MGA5TOO => MGA6TOO
Assignee: doktor5000 => thierry.vignaud
Status: ASSIGNED => NEW

No longer in cups 2.3.3.

This CUPS log has been moved into journal by default unless changes have been made in /etc/cups/cups-files.conf. Log messages can be got by "$ journalctl -u 
cups -e".

Therefore, there is a checkbox "Save debug info for problems resolution" in http://localhost:631/admin/?ADVANCEDSETTINGS=YES

This checkbox is not checked by default. Should be for you to debug. See also your journal with "journalctl -u cups -e".

This is upstream recommended way to parse log.

CC: (none) => ouaurelien

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Created attachment 11810 [details]
Screenshot of current cups web interface in mga7

Three buttons to view Acess/Error/Page logs are displayed but not working.
CUPS 2.2.13-1.4.mga7

OK, i can check that button described in comment 8.
It produce an insane amount of useless messages, but that is another problem.

But for the nonworking buttons:
They should either be able to work or be removed.
Is that an upstream problem or some patch we add?

Status: RESOLVED => REOPENED
Resolution: WONTFIX => (none)
Summary: Cups built-in error and log buttons do not work => Cups web UI show buttons for log, error, and page - but none work
Whiteboard: MGA6TOO => MGA7TOO

Mageia 8, CUPS describe itself as 2.3.3op2, tested today:

The nonworking buttons described in Comment 0 are gone, 
and the method described in Comment 8 to get logging works.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED