Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PF 14.0 Cluster pfcmd fixpermissions file, Warnings when syncing files #8308

Open
PeriklisZisis opened this issue Sep 13, 2024 · 0 comments
Open

Comments

@PeriklisZisis
Copy link

Describe the bug
Cluster with 3 nodes. When running the command /usr/local/pf/bin/cluster/sync --as-master on the "master" node , the command finishes with no error. However on the other 2 nodes there are warnings like :

pf2 httpd.webservices-docker-wrapper[1050842]: httpd.webservices(4954) WARN: [mac:unknown] Problem trying to run command: sudo PF_GID=995 PF_UID=996 /usr/local/pf/bin/pfcmd fixpermissions file /usr/local/pf/conf/security_events.conf called from fix_file_permissions. Child exited with non-zero value 1 (pf::util::safe_pf_run)

pf2 httpd.webservices-docker-wrapper[1050842]: httpd.webservices(4954) INFO: [mac:unknown] Successfully downloaded configuration /usr/local/pf/conf/security_events.conf from pf1 (pf::api::notify_configfile_changed)

The files are getting synced eventually, however there is this warning for each of the files that getting synced.

When running the command manually : sudo PF_GID=995 PF_UID=996 /usr/local/pf/bin/pfcmd fixpermissions file /usr/local/pf/conf/security_events.conf
The output is the expected one : Fixed permissions on file /usr/local/pf/conf/security_events.conf

To Reproduce
Steps to reproduce the behavior:

  1. Go to master node and run /usr/local/pf/bin/cluster/sync --as-master
  2. Check packetfence.log on the other 2 nodes

Expected behavior
No warnings

  • Fresh installation with PacketFence-ISO-v14.0.0.iso
  • OS: Debian 12, PF 14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant