apparently the same thing happens to the doorjam script in init.d if you
service doorjam start
but doorjam/index.js does get started automatically - and health.js does
if anyone knows what's going on please document it somewhere...?
On Tue, 9 Jun 2015, Jake wrote:
on omnidoor, see
/etc/rc5.d/S18doorhealth -> ../init.d/doorhealth
root@omnidoor:/etc/init.d# service doorhealth start
/usr/local/bin/psy start --logfile /var/log/sudobot.log --name doorhealth --
throw new TypeError('Arguments to path.join must be strings');
TypeError: Arguments to path.join must be strings
at Array.filter (native)
at Object.exports.join (path.js:358:36)
at Object.<anonymous> (/usr/local/lib/node_modules/psy/cmd.js:38:40)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
however, running the same command at the commandline seems to work:
root@omnidoor:/etc/init.d# /usr/local/bin/psy start --logfile
/var/log/sudobot.log --name doorhealth -- node /root/sudobot/health.js
no idea why this is. also, i renamed /root/doorjam-health to /root/sudobot
in a vain attempt to reduce confusion. probably health.js should be called
doorhealth.js since the command psy log doorhealth only works if the process
--name is doorhealth...
substack, did you have anything trying to auto-start health.js on omnidoor?
because Marc and I made this to do that, since sudobot just complains
continuously until it can get ahold of "doorhealth"
access mailing list