# Pmm-agent is not running. Please re-run \`pmm-agent setup\` with --config-file flag **URL:** \ **Category:** Percona Monitoring and Management (PMM)\ **Created:** [June 21, 2023, 9:27am UTC](https://forums.percona.com/t/pmm-agent-is-not-running-please-re-run-pmm-agent-setup-with-config-file-flag/22998 "2023-06-21T09:27:14Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![farhan.ext](https://avatars.discourse-cdn.com/v4/letter/f/6f9a4e/32.png) [@farhan.ext](https://forums.percona.com/u/farhan.ext)\ **Post date:** [June 21, 2023, 9:27am UTC](https://forums.percona.com/t/pmm-agent-is-not-running-please-re-run-pmm-agent-setup-with-config-file-flag/22998/1 "2023-06-21T09:27:14Z")
Hello, i am getting this below error while configuring mysql host: [root@stg01 rroot]# pmm-admin config --force --server-insecure-tls --server-url=[https://admin:password@pmm-server-IP](https://admin:password@pmm-server-IP) Checking local pmm-agent status… pmm-agent is not running. Please re-run `pmm-agent setup` with --config-file flag. [root@stg01 rroot]# Please suggest / provide any fix? ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [June 21, 2023, 3:04pm UTC](https://forums.percona.com/t/pmm-agent-is-not-running-please-re-run-pmm-agent-setup-with-config-file-flag/22998/2 "2023-06-21T15:04:51Z")
Hello @farhan.ext, Can you `systemctl restart pmm-agent`? ---
**Author:** ![farhan.ext](https://avatars.discourse-cdn.com/v4/letter/f/6f9a4e/32.png) [@farhan.ext](https://forums.percona.com/u/farhan.ext)\ **Post date:** [June 22, 2023, 12:01pm UTC](https://forums.percona.com/t/pmm-agent-is-not-running-please-re-run-pmm-agent-setup-with-config-file-flag/22998/3 "2023-06-22T12:01:14Z")
Hello, I did but same error: [root@stg01 ~]# systemctl restart pmm-agent [root@stg01 rroot]# pmm-admin config --force --server-insecure-tls --server-url=[https://admin:password@pmm-server-IP](https://admin:password@pmm-server-IP) Checking local pmm-agent status… pmm-agent is not running. Please re-run `pmm-agent setup` with --config-file flag. [root@stg01 rroot]# ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [June 22, 2023, 2:57pm UTC](https://forums.percona.com/t/pmm-agent-is-not-running-please-re-run-pmm-agent-setup-with-config-file-flag/22998/4 "2023-06-22T14:57:40Z")
How did you install PMM? Is it possible you installed v1 and not v2? On RHEL9, this is the correct package: `pmm2-client-2.37.1-6.el9.x86_64` If you did `yum install pmm-client` then you got v1, not v2. ---
**Author:** ![farhan.ext](https://avatars.discourse-cdn.com/v4/letter/f/6f9a4e/32.png) [@farhan.ext](https://forums.percona.com/u/farhan.ext)\ **Post date:** [June 23, 2023, 4:56am UTC](https://forums.percona.com/t/pmm-agent-is-not-running-please-re-run-pmm-agent-setup-with-config-file-flag/22998/5 "2023-06-23T04:56:10Z")
I installed using below command: rpm -Uvh pmm2-client-2.37.0-6.el7.x86\_64.rpm ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [August 7, 2023, 2:41pm UTC](https://forums.percona.com/t/pmm-agent-is-not-running-please-re-run-pmm-agent-setup-with-config-file-flag/22998/6 "2023-08-07T14:41:12Z")
Can you provide the error logs of PMM-agent after you restarted it? It looks like a clean restart but clearly something didn’t work internally. ---
**Author:** ![Denis\_Subbota](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/denis_subbota/32/23607_2.png) [@Denis\_Subbota](https://forums.percona.com/u/Denis_Subbota)\ **Post date:** [March 13, 2026, 10:09am UTC](https://forums.percona.com/t/pmm-agent-is-not-running-please-re-run-pmm-agent-setup-with-config-file-flag/22998/7 "2026-03-13T10:09:49Z")
Hey Team, When hitting a similar issue, I found this topic, and found that it also may happen due to SELinux in an enforced state. It usually happens after reboot of OS, when SElinux was disabled before, but started right after reboot. Regards, Denis Subbota. Managed Services, Percona.