Bug 40904 – cleanup /var/cache/univention-printserver/ after release update

Bug 40904 - cleanup /var/cache/univention-printserver/ after release update


Summary:	cleanup /var/cache/univention-printserver/ after release update

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Printserver
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1-x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:	51605
	Show dependency tree / graph

Reported:	2016-03-15 16:19 CET by Felix Botner
Modified:	2020-07-03 10:35 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Botner

2016-03-15 16:19:41 CET

Seen in several customer environments. 

Somehow some old printer change commands survived in the cups command cache /var/cache/univention-printserver/, e.g.

/var/cache/univention-printserver/1437651522.287814.sh
/usr/sbin/univention-lpadmin '-u' 'allow:all' '-o' 'auth-info-required=none' '-p' 'printer1' '-m' 'postscript/Kyocera/es/Kyocera_Mita_FS-1900_es.ppd.gz' '-
v' 'socket://10.15.1.1:9100' '-E'

The ppd 'postscript/Kyocera/es/Kyocera_Mita_FS-1900_es.ppd.gz' is totally outdated and lpadmin fails. 

During start of /etc/init.d/cups these commands are executed and removed if successful, but as the ppd is outdated and lpadmin fails, the command above never gets removed but restarted every time executed the cupsd is (re)started.

Now somebody makes a change on printer1 (activates quota, changes ip address), after some time cups is restarted and the command cache executed. Although the command in the cups cache fails, it still reverts some changes of printer1.

We may need to cleanup /var/cache/univention-printserver/ at some point.
Not sure when.

Ticket 2016030807000045
Ticket 2016031421000328

Comment 1 Stefan Gohmann

2019-01-03 07:21:41 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.