Bug 16843

Summary:	Defaults for cups error_log and page_log have changed making it difficult to debug and breaking old script
Product:	Mageia	Reporter:	w unruh <unruh>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	doktor5000, marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	cups	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	13861

Description w unruh 2015-09-28 01:53:54 CEST

Description of problem:
The defaults for the /var/log/cups/error_log and page_log have changed, making
debugging and accounting difficult, and breaking accounting scripts.

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.

The second problem with cupsd.conf is that the line
PageLogFormat
is there uncommented which means that nothing is sent to the page logs (Knowing that that is the result of having no format string on that command is not something most people would know). Either this command needs to be commented out, or a note attached saying that in order to get page_log output one needs to insert a format (as detailed in man cupsd.conf) . As it is I was simply flummoxed for many days why no output was coming out in page_log.

When defaults change, there needs to be an explanation to users of how to recover from those changes. I have scripts which use page_log to do accounting and with nothing in page_log, they do not work.

Version-Release number of selected component (if applicable):

cups-2.0.2-5.mga5

How reproducible:
Always.

Reproducible:

Steps to Reproduce:

Samuel Verschelde 2015-09-28 09:19:52 CEST

Assignee: bugsquad => thierry.vignaud

Florian Hubold 2015-11-25 19:52:21 CET

Blocks: (none) => 13861

Comment 1 Marja Van Waes 2018-04-18 08:57:30 CEST

@ w unruh,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Florian Hubold 2018-07-16 13:40:36 CEST

CC: (none) => doktor5000

Comment 2 Florian Hubold 2018-07-16 13:41:35 CEST

This issue is still present, nothing has happened to the configuration or defaults since the report.

Version: 5 => 6

Comment 3 Aurelien Oudelet 2020-08-16 17:56:12 CEST

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) => OLD
CC: (none) => ouaurelien

Comment 4 Aurelien Oudelet 2020-08-16 18:09:03 CEST

See also 13861.