Bug 51109 – univention-samba cron job starts nonexistent script every 30 min, spamming a log file

Bug 51109 - univention-samba cron job starts nonexistent script every 30 min, spamming a log file


Summary:	univention-samba cron job starts nonexistent script every 30 min, spamming a ...

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Samba
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:	Samba maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2020-04-15 16:51 CEST by Arvid Requate
Modified:	2020-11-11 19:56 CET (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.017
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 Arvid Requate

2020-04-15 16:51:41 CEST

A customer running univention-samba-slave-pdc has these log messages in
/var/log/univention/samba-sync.log :

/usr/sbin/jitter: line 48: /usr/share/univention-samba/slave-sync: No such file or directory
/usr/sbin/jitter: line 48: /usr/share/univention-samba/slave-sync: No such file or directory
/usr/sbin/jitter: line 48: /usr/share/univention-samba/slave-sync: No such file or directory

This is caused by /etc/cron.d/univention-samba running a non-existent script every 30 minutes.

Comment 1 Arvid Requate

2020-11-11 19:56:59 CET

Either we remove the call from univention-samba/debian/univention-samba.cron.d
or preferably we restore the script, which has been removed via Bug 47095.
If we restore it, then we should adjust it and remove two calls from it: Bug 23103