Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#41659 - [unifi] Add "WorkingDirectory=/usr/lib/unifi" in systemd service
Attached to Project:
Community Packages
Opened by Sean Lynch (seanl) - Friday, 22 August 2014, 23:06 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 25 August 2014, 12:53 GMT
Opened by Sean Lynch (seanl) - Friday, 22 August 2014, 23:06 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 25 August 2014, 12:53 GMT
|
DetailsDescription:
unifi will not start due to inability to find its log directory Additional info: * Version: 3.2.1-1 * config and/or log files etc. Steps to reproduce: 1. Install unifi package 2. systemctl start unifi 3. wait about 10 seconds 4. journalctl -e Expected results: Unifi starts and works Actual results: Unifi fails with the following in the journal: Aug 22 15:15:18 dib java[18862]: log4j:ERROR setFile(null,true) call failed. Aug 22 15:15:18 dib java[18862]: java.io.FileNotFoundException: logs/server.log (No such file or directory) Looking at the CWD of the process shows it is /. Adding WorkingDirectory=/usr/lib/unifi to the unit file makes the problem go away. |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Monday, 25 August 2014, 12:53 GMT
Reason for closing: Fixed
Additional comments about closing: unifi-3.2.1-2
Monday, 25 August 2014, 12:53 GMT
Reason for closing: Fixed
Additional comments about closing: unifi-3.2.1-2
Could you give me the output of:
$ getent passwd unifi
unifi:x:113:113::/usr/lib/unifi:/bin/bash