Bug 957658
| Summary: | Permissions are wrong on /var/run/zabbix/zabbix_server.pid | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Trever Adams <trever> |
| Component: | zabbix | Assignee: | Dan Horák <dan> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | brett.lentz, dan, nelsonab, volker27 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-05-07 15:48:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Trever Adams
2013-04-29 08:21:06 UTC
Ok, I think I have figured out more of what is going on. It doesn't seem to be failing to start because of the log or pid permission problem. It is because /usr/lib/systemd/system/zabbix-server-pgsql.service has the following line: ExecStart=/usr/sbin/zabbix_server It should be either the following, or zabbix-server-pgsql should be setting up a symlink: ExecStart=/usr/sbin/zabbix_server_pgsql The permissions are still messed up. tmpfiles.d doesn't seem to be able to do beyond basic owner,group,world modes so I cannot suggest a forced adding of a posix user for zabbixsrv. Any reason for both zabbix and zabbixsrv users? If so, then maybe they should have different run and log directories. Sorry, I take that back about the symlink. I removed the zabbix-server and zabbix-server-pgsql packages, reinstalled, the symlinks are right. It is the permissions. It appears that if you set the owner to zabbixsrv and group to zabbix for the log and run directory, things work. *** This bug has been marked as a duplicate of bug 904041 *** |