Project

General

Profile

Actions
Copy link

Bug #27184

closed

[smart_proxy_dynflow_core] "PID file /var/run/foreman-proxy/smart_proxy_dynflow_core.pid not readable (yet?) after start"

Added by Adam Ruzicka almost 6 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Adam Ruzicka
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
1724494
Pull request:
https://github.com/theforeman/smart_proxy_dynflow/pull/64
Fixed in Releases:
smart_proxy_dynflow-0.2.5
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1724494

Description of problem:
After reboot of Capsule, the service 'smart_proxy_dynflow_core' shows message

"PID file /var/run/foreman-proxy/smart_proxy_dynflow_core.pid not readable (yet?) after start"

Version-Release number of selected component (if applicable):
tfm-rubygem-smart_proxy_dynflow_core-0.2.1-5.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Reboot cpasule server
2. systemctl status smart_proxy_dynflow_core
3.

Actual results:
Jun 26 17:29:25 capsule01 systemd1: Starting Foreman smart proxy dynflow core service...
Jun 26 17:29:29 capsule01 systemd1: PID file /var/run/foreman-proxy/smart_proxy_dynflow_core.pid not readable (yet?) after start.
Jun 26 17:29:29 capsule01 systemd1: Started Foreman smart proxy dynflow core service.

Expected results:
The service should start without any warning/error

Jun 26 17:29:25 capsule01 systemd1: Starting Foreman smart proxy dynflow core service...
Jun 26 17:29:29 capsule01 systemd1: Started Foreman smart proxy dynflow core service.

Additional info:
if the service is restarted, everything runs fine

  1. foreman-maintain service restart --only smart_proxy_dynflow_core
Actions
Copy link

Also available in: Atom PDF