Once the avSchedulerInputParameters.json file is reconfigured it will start the service as a PM2 service.
Below are some useful PM2 option and samples on each option:
1.On the directory where npm install audienceview@version was executed.
2.Enter cd [AUDIENCEVIEW SERVER]\node_modules\pm2\bin\
3.Execute one of the following options:
The node pm2 list scheduler command lists all of the services being run in PM2.
The following is an example of the information that is returned:
Name |
mode |
status |
? |
cpu |
memory |
scheduler |
fork |
stopped |
0 |
0% |
0 B |
The node pm2 stop scheduler command stops the scheduler from running.
The following is an example of the information that is returned:
[PM2] Applying action stopProcessId on app [scheduler](ids: 0)
[PM2] [scheduler](0) √
|
The node pm2 start scheduler command starts the scheduler.
The following is an example of the information that is returned:
[PM2] Applying action restartProcessId on app [scheduler](ids: 0) [PM2] [scheduler](0) √ [PM2] Process successfully started
|
The node pm2 restart scheduler command restarts the scheduler. If changes have been made to the avSchedulerInputParameters.json file you can restart the scheudler to make the changes take effect. This can also be accomplished using the node pm2 stop scheduler/node pm2 start scheduler
The following is an example of the information that is returned:
[PM2] Applying action restartProcessId on app [scheduler](ids: 0) [PM2] [scheduler](0) √
|
The node pm2 show scheduler command displays the status of the scheduler.
The following is an example of the information that is returned:
[PM2] Applying action restartProcessId on app [scheduler](ids: 0) [PM2] [scheduler](0) √
Code metrics value
Add your own code metrics: http://bit.ly/code-metrics Use `pm2 logs scheduler [--lines 1000]` to display logs Use `pm2 monit` to monitor CPU and Memory usage scheduler |