Unable to Start pf9-comms Service on the Node.

Problem

  • pf9-comms fails to start on the node.

  • The following errors are reported in journalctl logs:

test-cluster-master systemd[1]: Starting Platform9 Communications Service...
test-cluster-master systemd[32426]: Failed at step USER spawning /bin/mkdir: No such process
test-cluster-master systemd[1]: pf9-comms.service: control process exited, code=exited status=217
test-cluster-master systemd[1]: Failed to start Platform9 Communications Service.
test-cluster-master systemd[1]: Unit pf9-comms.service entered failed state.
test-cluster-master systemd[1]: pf9-comms.service failed.

Environment

  • Platform9 Managed OpenStack - All versions

  • Platform9 Managed Kubernetes - All versions

  • pf9-comms

Cause

The ownership for directory /var/log/pf9/comms is incorrect. The directory should be owned by the pf9 user and pf9group.

Resolution

  1. Change the ownership of /var/log/pf9/comms to pf9 user and pf9group.

# chown -R pf9:pf9group /var/log/pf9/comms/


© 2025 Platform9. All Rights Reserved

On This Page
Unable to Start pf9-comms Service on the Node.ProblemEnvironmentCauseResolution