Autostart dashing not working

Third party integrations HADashboard
1

After some attempts I managed to get hadashboard running on my Pi3. Main challenge I am facing now is to have it autorun. I edited the init file dashing as below. I copy it to /etc/init.d and chmod it correctly. Now when I manually run dashing te word “dashing” will be written on my screen over and over and ultimately locks up my pi. What am i doing wrong?

NAME=dashing
DASHING_DIR=/home/pi/hadashboard
DAEMON=/etc/init.d/dashing
PIDFILE="$DASHING_DIR/$NAME.pid"
DAEMON_OPTS=“start -d -P $PIDFILE”
GEM_HOME=/home/pi/.rvm/rubies/ruby-2.3.3/bin/gem

2

What version of ruby did you install and is the path correct?

Mine looks like this.

NAME=dashing
DASHING_DIR=/home/pi/hadashboard
DAEMON=/usr/local/bin/dashing
PIDFILE="$DASHING_DIR/$NAME.pid"
DAEMON_OPTS="start -d -P $PIDFILE"
GEM_HOME=/usr/local/lib/site_ruby/gems/1.9.1
3

Hi,

I had dashing automatically started on my RPi3 today, and I have the same value as BarryHampants for DAEMON :

# Must be a valid filename
NAME=dashing
DASHING_DIR=/home/pi/hadashboard
DAEMON=/usr/local/bin/dashing
PIDFILE="$DASHING_DIR/$NAME.pid"
DAEMON_OPTS="start -d -P $PIDFILE"
GEM_HOME=/var/lib/gems/2.1.0

I installed it manually, not with docker

For the GEM_HOME path, I used the command

gem environment

And used the first line given in the GEM PATH section :

RubyGems Environment:
  - RUBYGEMS VERSION: 2.2.2
  - RUBY VERSION: 2.1.5 (2014-11-13 patchlevel 273) [arm-linux-gnueabihf]
  - INSTALLATION DIRECTORY: /var/lib/gems/2.1.0
  - RUBY EXECUTABLE: /usr/bin/ruby2.1
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - SPEC CACHE DIRECTORY: /home/pi/.gem/specs
  - RUBYGEMS PLATFORMS:
    - ruby
    - arm-linux
  - GEM PATHS:
     - /var/lib/gems/2.1.0
     - /home/pi/.gem/ruby/2.1.0
     - /usr/share/rubygems-integration/2.1.0
     - /usr/share/rubygems-integration/2.1
     - /usr/share/rubygems-integration/all
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - https://rubygems.org/
  - SHELL PATH:
     - /usr/local/sbin
     - /usr/local/bin
     - /usr/sbin
     - /usr/bin
     - /sbin
     - /bin
     - /usr/local/games
     - /usr/games
4

Tried all your suggestions, but even after the tip of @nicop4 it still doesn’t work.

pi@pi:~ $ gem environment
RubyGems Environment:
  - RUBYGEMS VERSION: 2.6.8
  - RUBY VERSION: 2.3.3 (2016-11-21 patchlevel 222) [armv6l-linux-eabihf]
  - INSTALLATION DIRECTORY: /home/pi/.rvm/gems/ruby-2.3.3
  - USER INSTALLATION DIRECTORY: /home/pi/.gem/ruby/2.3.0
  - RUBY EXECUTABLE: /home/pi/.rvm/rubies/ruby-2.3.3/bin/ruby
  - EXECUTABLE DIRECTORY: /home/pi/.rvm/gems/ruby-2.3.3/bin
  - SPEC CACHE DIRECTORY: /home/pi/.gem/specs
  - SYSTEM CONFIGURATION DIRECTORY: /home/pi/.rvm/rubies/ruby-2.3.3/etc
  - RUBYGEMS PLATFORMS:
    - ruby
    - armv6l-linux
  - GEM PATHS:
     - /home/pi/.rvm/gems/ruby-2.3.3
     - /home/pi/.rvm/gems/ruby-2.3.3@global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - https://rubygems.org/
  - SHELL PATH:
     - /home/pi/.rvm/gems/ruby-2.3.3/bin
     - /home/pi/.rvm/gems/ruby-2.3.3@global/bin
     - /home/pi/.rvm/rubies/ruby-2.3.3/bin
     - /usr/local/sbin
     - /usr/local/bin
     - /usr/sbin
     - /usr/bin
     - /sbin
     - /bin
     - /usr/local/games
     - /usr/games
     - /home/pi/.rvm/bin
     - /home/pi/.rvm/bin
     - /home/pi/.rvm/bin

Based on that I changed dashing to:

NAME=dashing
DASHING_DIR=/home/pi/hadashboard
DAEMON=/usr/local/bin/dashing
PIDFILE="$DASHING_DIR/$NAME.pid"
DAEMON_OPTS="start -d -P $PIDFILE"
GEM_HOME=/home/pi/.rvm/gems/ruby-2.3.3

But if I know run dashing (in /etc/init.d) I get “Could not locate Gemfile or .bundle/ directory”…
If I simply go to /home/pi/hadashboard and execute “dashing start” from there everything works perfectly.

5

You have to be in the correct directory when you run dashing start or it will break. That is what the dashing_start.sh script does in the distro - run that instead of “dashing start” in your startup script (after editing it appropriately for your path to dashing) and it should work.

6

Same problem here from /home/pi/hadashboard/ run perfectly… but i cant make it to start… can somebody point how we can check this values? i.e GEM_HOME, DASHING DIR, PATH, etc ???

7

Ok, tried to document steps a bit, but it is still not working. See documented steps below.

# Must be a valid filename
NAME=dashing
#DASHING_DIR is where hadashboard is installed. Do note the trailing slash as it is a directory
DASHING_DIR=/home/pi/hadashboard/
#DAEMON can be found by typing "which dashing"
DAEMON=/home/pi/.rvm/gems/ruby-2.3.3/bin/dashing
#Don't change the PIDFILE
PIDFILE="$DASHING_DIR/$NAME.pid"
#Don't change the DAEMON_OPTS
DAEMON_OPTS="start -d -P $PIDFILE"
#GEM_HOME is the first line under "Gem Paths" when you type "gem environment"
GEM_HOME=/home/pi/.rvm/gems/ruby-2.3.3

I decided to change hadashboard_start.sh to below and to add that to the crontab @reboot.
#!/bin/bash

cd /home/pi/hadashboard

start-stop-daemon --start --quiet --chdir /home/pi/hadashboard/ --exec /home/pi/.rvm/gems/ruby-2.3.3/bin/dashing -- start -d -P /home/pi/hadashboard/dashing.pid

EDIT: this also doesn’t work… :disappointed:

8

tonight im gonna start with a fresh instalation, and I´ll try docker for RPI, if it works i´ll post the steps.

@aimc I know you´re the Jedi here, any recomendations?

Thanks!!!

9

The whole start up thing is hard to help with because it is different for every platform …

All I can say is, use the force …