pscheduler-api started (?) multiple times - multilple consecutive entries in the log

[szymontrocha]

I observe it in multiple nodes (both small nodes but also virtual instances in PMP mesh). The info is not much descriptive but it's surprising it is repeated multiple times. In fact I don't know if there is any impact but not sure it's good or what it means to the system as it's always saying "started":
Observed at least with 5.1.4 under U20, U22

Jan 13 14:25:47 psmall-poz1 pscheduler-api[1691265] INFO     Started
Jan 13 14:25:48 psmall-poz1 pscheduler-api[1691265] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:25:53 psmall-poz1 pscheduler-api[1691264] INFO     Started
Jan 13 14:25:54 psmall-poz1 pscheduler-api[1691264] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:25:56 psmall-poz1 pscheduler-api[1691301] INFO     Started
Jan 13 14:25:57 psmall-poz1 pscheduler-api[1691301] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:25:59 psmall-poz1 pscheduler-api[1691322] INFO     Started
Jan 13 14:26:00 psmall-poz1 pscheduler-api[1691322] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:28:46 psmall-poz1 pscheduler-api[1691341] INFO     Started
Jan 13 14:28:47 psmall-poz1 pscheduler-api[1691341] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:28:49 psmall-poz1 pscheduler-api[1691369] INFO     Started
Jan 13 14:28:50 psmall-poz1 pscheduler-api[1691369] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:28:58 psmall-poz1 pscheduler-api[1691387] INFO     Started
Jan 13 14:28:59 psmall-poz1 pscheduler-api[1691387] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:43:46 psmall-poz1 pscheduler-api[1691406] INFO     Started
Jan 13 14:43:47 psmall-poz1 pscheduler-api[1691406] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:43:50 psmall-poz1 pscheduler-api[1693124] INFO     Started
Jan 13 14:43:51 psmall-poz1 pscheduler-api[1693124] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:43:53 psmall-poz1 pscheduler-api[1693150] INFO     Started
Jan 13 14:43:55 psmall-poz1 pscheduler-api[1693150] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:43:57 psmall-poz1 pscheduler-api[1694460] INFO     Started
Jan 13 14:43:59 psmall-poz1 pscheduler-api[1694460] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:44:01 psmall-poz1 pscheduler-api[1694485] INFO     Started
Jan 13 14:44:02 psmall-poz1 pscheduler-api[1694485] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:45:34 psmall-poz1 pscheduler-api[1694515] INFO     Started
Jan 13 14:45:35 psmall-poz1 pscheduler-api[1694515] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:50:19 psmall-poz1 pscheduler-api[1694536] INFO     Started
Jan 13 14:50:20 psmall-poz1 pscheduler-api[1694536] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:53:35 psmall-poz1 pscheduler-api[1695016] INFO     Started
Jan 13 14:53:36 psmall-poz1 pscheduler-api[1695016] INFO     Limits loaded from /etc/pscheduler/limits.conf
Jan 13 14:53:38 psmall-poz1 pscheduler-api[1695055] INFO     Started
Jan 13 14:53:39 psmall-poz1 pscheduler-api[1695055] INFO     Limits loaded from /etc/pscheduler/limits.conf

[mfeit-internet2]

As long as it's not continuous, it's nothing unusual. Apache starts up multiple processes to handle requests and each one produces the started/loaded messages. They eventually die off and new ones start that do the same thing.