When running as a systemctl service, the new cmdExec.log functionality will cause the bot to fail to start if the permissions are incorrectly set (I needed to chmod 666 cmdExec.log). It runs fine if started manually with node bot.js.
If the file doesn't exist, then the service cannot create the file at all.
When running as a systemctl service, the new cmdExec.log functionality will cause the bot to fail to start if the permissions are incorrectly set (I needed to chmod 666 cmdExec.log). It runs fine if started manually with node bot.js.
If the file doesn't exist, then the service cannot create the file at all.