The pScheduler server is the component that does the heavy-lifting of scheduling and managing tasks. It consists of multiple daemon processes and makes extensive use of PostgreSQL. This document describes basic usage of the server.
pScheduler consists for four daemon processes that run as separate services. The four services are:
- pscheduler-scheduler - This process is what puts new runs on the schedule or marks a run as a non-starter if it can not find an available slot.
- pscheduler-runner - This process is what executes runs on the schedule using the selected tool
- pscheduler-archiver - This process executes archiver plug-ins using the results of runs. Archivers generally send results to long-term storage or to applications for further processing.
- pscheduler-ticker - This process handles basic maintenance of pScheduler
These services can be started/stopped with systemctl or the service command depending on the operating system. For example:
Using systemctl (e.g. CentOS 7/Debian 8):systemctl start pscheduler-scheduler systemctl start pscheduler-runner systemctl start pscheduler-archiver systemctl start pscheduler-ticker
Using the service command (e.g. CentOS 6/Debian 7):/sbin/service pscheduler-scheduler start /sbin/service pscheduler-runner start /sbin/service pscheduler-archiver start /sbin/service pscheduler-ticker start
In addition to these processes, it also requires Apache HTTPD and PostgreSQL daemons to be running. Apache provides the web server where pScheduler accepts REST API requests and PostgreSQL is where the schedule is stored. The name of these processes is dependent on the operating system:
- CentOS (all versions): httpd and postgresql-9.5
- Debian (all versions): apache2 and postgresql
By default pScheduler logs to syslog facility local4. It sets-up rsyslogd to redirect all logging to the following file:
If you are using an alternative syslog implementation to rsyslogd then you will need to configure it to redirect local4 manually