• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved PSA service (exited)

Dukemaster

Regular Pleskian
Hi,
I just made a control test of most services, like nginx, mysqp/mariadb, sw-engine, sw-server,... and psa --> PLESK.
Makes me wonder why "only" this core service is running in state "exited"?
Do I have to fix or do something?

[QUOTE
root@server:~# service psa status
psa.service - Plesk Panel
Loaded: loaded (/lib/systemd/system/psa.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2019-11-05 11:51:07 CET; 2min 58s ago
Main PID: 24439 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/psa.service

Nov 05 11:51:06 server.example.com systemd[1]: Starting Plesk Panel...
Nov 05 11:51:07 server.example.com systemd[1]: Started Plesk Panel.
root@server:~#
][/QUOTE]
 
Last edited:
This is just an auxiliary oneshot script/service that launches the entire stack and successfully completes. Its purpose is to start, do some work, and then exit.
Therefore, it is marked as exited: the service was started, did everything it should, and exited with status 0
Since this is not a daemon - it cannot be active running - it requires an active process.
 
Back
Top