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 in > Debian. >
Can we see your unit file? > > > > > > > > > > >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, and wsgi - all ran pre-systemd > >> It's been flawless for me, it took a little reading to understand the differences from sysvinit though. > >>maybe it's buggy, maybe it's just looking for something not in > >>docs/tutorials > >> > >>should not be this hard though. > >> Have you tried this: https://wiki.archlinux.org/index.php/systemd#Investigating_systemd_errors or this? https://wiki.archlinux.org/index.php/systemd#Diagnosing_problems_with_a_specific_service > >> > >> > >>On 04/13/2016 03:58 AM, Dominique Dumont wrote: > >>>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 behind > >>>>an NGINX proxy, does that matter ? > >>>I don't think so. > >>> > >>>HTH > >>> > >> > >> > > > > > >
