8

EDIT: As per Jim Rush's advice I'm now using rc.local instead of init.d direclty to run forever start on boot up.

I'm wracking my head on this one.

I'm wanting to start a node app on the raspberry pi startup and reboot. I'm using forever to actually call the app and using init.d for the debian style start instructions.

I've created the kuuyi file within the /etc/init.d directory, given it a permission of 755 and, after editing the file, ran update-rc.d kuuyi defaults to hopefully trigger Raspbian to start it on restart/boot.

Here's my init.d file:

#!/bin/sh #/etc/init.d/kuuyi ### BEGIN INIT INFO # Provides: kuuyi # Required-Start: # Required-Stop: # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Kuuyi ### END INIT INFO case "$1" in start) /usr/local/bin/forever --sourceDir=/home/pi/kuuyi_device -p /root/.forever run.js ;; stop) /usr/local/bin/forever stop --sourceDir=/home/pi/kuuyi_device run.js ;; *) echo "Usage: /etc/init.d/kuuyi {start|stop}" exit 1 ;; esac exit 0

Any ideas as to why this isn't working? I'm running Raspbian on a Raspberry Pi B+. I've run /etc/init.d kuuyi start and forever kicks and begins the app just fine. Its just not happening after booting up the machine.

Any help on this is so appreciated, I'm about as wrung out as an old cheese cloth after dairy day on this one.

Improve this question
1
  • I am not using raspberry-pi. Perhaps you can add this line before case statement : echo "$(date '+%Y%m%d-%H:%M:%S') : args=$@" >> /home/pi/kuuyi-args.log . This will at least confirm whether or not your script is called. Commented May 5, 2015 at 8:34

1 Answer 1

Reset to default
6

I run node (actually nodemon) from /etc/rc.local. Just the command line with & at the end. I also redirect stderr and stdout to log files to troubleshoot startup and crash problems. Getting the permissions right, on any directory that was written to, was one of my early problems.

Example:

PATH=$PATH:/opt/node/bin cd /var/node/RoadsterNode /opt/node/bin/nodemon /var/node/RoadsterNode/app.js < /dev/null >/var/tmp/startup.log 2>/var/tmp/startup.err &
Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

Thanks Jim for this tidbit. I modified my rc.local file with the the forever call like so: /usr/local/bin/forever -l /home/pi/kuuyi_device/out.log -a start /home/pi/kuuyi_device/run.js & ..... still not having luck with it. It's probably cause my script itself is craping out upon start.
@risingtiger Try capturing stdout and stderr to a file so you can see what is happening. You'll note in my added example that I discovered that node wasn't on my path when I set it up.
That seemed to do the trick! I've been struggling with that for a while now. Thank you so much.
You can directly add this to rc.local <your-node-dir>/node <your-app-dir>/app.js > <your-app-dir>/log-file.txt

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.