• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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