Bug 35557 – Error message from logrotate in case s4-connector is stopped

Bug 35557 - Error message from logrotate in case s4-connector is stopped


Summary:	Error message from logrotate in case s4-connector is stopped

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:	38232
	Show dependency tree / graph

Reported:	2014-08-04 15:09 CEST by Arvid Requate
Modified:	2020-07-03 20:54 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
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:

Flags:	requate: Patch_Available+

Attachments
logrotate.patch (558 bytes, patch) 2014-08-04 15:11 CEST, Arvid Requate	Details \| Diff
View All 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

2014-08-04 15:09:59 CEST

For Bug 35500 the postrotate script logrotate.d/univention-s4-connector was adjusted to "crestart" instead of "restart". This has the side effect that logrotate issues an error message in case the S4 Connector isn't running:


root@master40:~# /etc/init.d/univention-s4-connector stop
Stopping univention-s4-connector daemon.
done.

root@master40:~# logrotate -f /etc/logrotate.d/univention-s4-connector
invoke-rc.d: initscript univention-s4-connector, action "crestart" failed.
error: error running non-shared postrotate script for /var/log/univention/connector-s4.log of '/var/log/univention/*-s4.log '

Comment 1 Arvid Requate

2014-08-04 15:11:51 CEST

Created attachment 6044 [details]
logrotate.patch

Maybe we should do this (or better adjust the univention-s4-connector init script to return 0 on crestart?).

Comment 2 Stefan Gohmann

2017-06-16 20:40:16 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 3 Ingo Steuwer

2020-07-03 20:54:34 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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