pm2 startup systemd - failed because the service did not take the steps required by its unit configuration

What's going wrong?

Job for pm2-wololo.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status pm2-wololo.service" and "journalctl -xe" for details.

How could we reproduce this issue?

Following this guide https://www.digitalocean.com/community/tutorials/how-to-set-up-a-node-js-application-for-production-on-ubuntu-18-04

Supporting information

$ pm2 report

===============================================================================
--- PM2 REPORT (Mon Sep 24 2018 04:45:23 GMT+0000 (Coordinated Universal Time)) 
===============================================================================
--- Daemon -------------------------------------------------
pm2d version         : 3.1.3
node version         : 10.11.0
node path            : /usr/bin/pm2
argv                 : /usr/bin/node,/usr/lib/node_modules/pm2/lib/Daemon.js
argv0                : node
user                 : wololo
uid                  : 1000
gid                  : 1000
uptime               : 12min
===============================================================================
--- CLI ----------------------------------------------------
local pm2            : 3.1.3
node version         : 10.11.0
node path            : /usr/bin/pm2
argv                 : /usr/bin/node,/usr/bin/pm2,report
argv0                : node
user                 : wololo
uid                  : 1000
gid                  : 1000
===============================================================================
--- System info --------------------------------------------
arch                 : x64
platform             : linux
type                 : Linux
cpus                 : Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
cpus nb              : 1
freemem              : 545316864
totalmem             : 1033383936
home                 : /home/wololo
===============================================================================
--- PM2 list -----------------------------------------------
┌──────────┬────┬──────┬──────┬────────┬─────────┬────────┬──────┬───────────┬────────┬──────────┐
│ App name │ id │ mode │ pid  │ status │ restart │ uptime │ cpu  │ mem       │ user   │ watching │
├──────────┼────┼──────┼──────┼────────┼─────────┼────────┼──────┼───────────┼────────┼──────────┤
│ hello    │ 0  │ fork │ 2152 │ online │ 0       │ 5m     │ 0.1% │ 32.9 MB   │ wololo │ disabled │
└──────────┴────┴──────┴──────┴────────┴─────────┴────────┴──────┴───────────┴────────┴──────────┘
===============================================================================
--- Daemon logs --------------------------------------------
┌──────────┬────┬──────┬──────┬────────┬─────────┬────────┬─────┬───────────┬────────┬──────────┐
│ App name │ id │ mode │ pid  │ status │ restart │ uptime │ cpu │ mem       │ user   │ watching │
├──────────┼────┼──────┼──────┼────────┼─────────┼────────┼─────┼───────────┼────────┼──────────┤
│ hello    │ 0  │ fork │ 2152 │ online │ 0       │ 5m     │ 0%  │ 32.9 MB   │ wololo │ disabled │
└──────────┴────┴──────┴──────┴────────┴─────────┴────────┴─────┴───────────┴────────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

Start by following the linked DigitalOcean guide and inspecting the generated systemd startup configuration for pm2-wololo.service. Run systemctl status pm2-wololo.service, journalctl -xe, and pm2 report to compare the failed service with the running PM2 daemon; done means the service starts successfully under its unit configuration.