0001097: Systemd expexts bareos-fd to be on port 9102

ID	Project	Category	View Status	Date Submitted	Last Update

0001097	bareos-core	file daemon	public	2019-07-03 01:07	2019-07-04 15:56

Reporter	gnif	Assigned To	arogge
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	duplicate
Platform	Linux	OS	Debian	OS Version	9
Product Version	18.2.6

Summary	0001097: Systemd expexts bareos-fd to be on port 9102
Description	On some systems I need to run Bareos on a different port as 9102 conflicts with the sphinx search indexer, however the system.d unit specifically looks for a pid file with the bareos-fd port of 9102 causing systemd to think that startup of the bareos-fd has failed. While this can be worked around, when any updates to the system are performed that require a restart of bareos, the failure to restart the package causes the apt package manager to halt any further work.
Steps To Reproduce	1) Install bareos-filedaemon on Debian 9 2) Set the port in mysqlf.conf to anything other then 9102 3) Try to restart the service via `systemctl restart bareos-fd`
Tags	No tags attached.

Date Modified	Username	Field	Change
2019-07-03 01:07	gnif	New Issue
2019-07-03 09:32	arogge	Assigned To	=> arogge
2019-07-03 09:32	arogge	Status	new => confirmed
2019-07-03 09:32	arogge	Note Added: 0003407
2019-07-04 15:56	arogge	Relationship added	duplicate of 0000928
2019-07-04 15:56	arogge	Status	confirmed => closed
2019-07-04 15:56	arogge	Resolution	open => duplicate

arogge 2019-07-03 09:32 manager ~0003407	We know that this is an issue and it is already on our to-do list. However, there's no easy fix from our side. The systemd unit needs the literal pid-file, but bareos uses its port number in the pid-file's name. The fix is to use Type=notify in systemd, but this needs some work in the daemons.