Re: cannot run a node.js app using systemd on debian jessie

2016-04-14 Thread Daniel Keast
On Thu, Apr 14, 2016 at 11:21:06AM -0600, jstaff-emplyprep wrote: > > > On 04/13/2016 05:12 PM, li...@rickv.com wrote: > >just asking, these aren't from the leftpad problem with npm? > >have you run 'npm cache clear'? > > not the cause, and sad if this is the best info we can get - losing faith

Re: cannot run a node.js app using systemd on debian jessie

2016-04-14 Thread jstaff-emplyprep
On 04/13/2016 05:12 PM, li...@rickv.com wrote: just asking, these aren't from the leftpad problem with npm? have you run 'npm cache clear'? not the cause, and sad if this is the best info we can get - losing faith in Debian. On Wed, Apr 13, 2016 at 04:19:02PM -0600, jstaff-emplyprep

Re: cannot run a node.js app using systemd on debian jessie

2016-04-13 Thread lists
just asking, these aren't from the leftpad problem with npm? have you run 'npm cache clear'? On Wed, Apr 13, 2016 at 04:19:02PM -0600, jstaff-emplyprep wrote: no, it is not a sym link I really think something is wrong with systemd in Jessie - we have been unable to run node, ruby unicorn, an

Re: cannot run a node.js app using systemd on debian jessie

2016-04-13 Thread jstaff-emplyprep
no, it is not a sym link I really think something is wrong with systemd in Jessie - we have been unable to run node, ruby unicorn, and wsgi - all ran pre-systemd maybe it's buggy, maybe it's just looking for something not in docs/tutorials should not be this hard though. On 04/13/2016 0

Re: cannot run a node.js app using systemd on debian jessie

2016-04-13 Thread Dominique Dumont
On Tuesday 12 April 2016 16:52:51 jstaff-emplyprep wrote: > ok, using systemctl status -l => lacks ExecStart setting >=> Executable path is not absolute, ignoring > > don't we have the full path ? what is it looking for ? May be your /usr/local/bin/node is a relative link... > if it's behi

Re: cannot run a node.js app using systemd on debian jessie

2016-04-12 Thread jstaff-emplyprep
ok, using systemctl status -l => lacks ExecStart setting => Executable path is not absolute, ignoring don't we have the full path ? what is it looking for ? if it's behind an NGINX proxy, does that matter ? On 04/12/2016 01:27 AM, Dominique Dumont wrote: On Monday 11 April 2016 15:35:19 js

Re: cannot run a node.js app using systemd on debian jessie

2016-04-12 Thread jstaff-emplyprep
error (Reason: Invalid argument) systemd[12329]: Failed at step EXEC sp... webpage.service lacks ... systemctl daemon-reload' recommended unfortunately the returned "..." error msg does not help much and running sudo daemon-reload just returns the prompt On 04/12/2016 01:27 AM, Dominique Dumon

Re: cannot run a node.js app using systemd on debian jessie

2016-04-12 Thread Dominique Dumont
On Monday 11 April 2016 15:35:19 jstaff-emplyprep wrote: > $ sudo service webpage restart > Failed to restart webpage.service: Unit webpage.service failed to > load: Invalid argument. See system logs and 'systemctl status > webpage.service' for details. Could you run 'systemctl status

cannot run a node.js app using systemd on debian jessie

2016-04-11 Thread jstaff-emplyprep
the systemd service as shown below fails to run with the error show below - we cannot figure out why. Can someone explain what is wrong with the setup and/or show a setup that works ? any help greatly appreciated as info: we can run "node server.js" from the command line as below: cd /h