Dash Node

[MangledBlue]

Theoretically the binaries are compiled for ARM6 and therefore should run on both.

Yes - now that I think about it -hummm
There is no NOOBs and Raspian for ARM6 or ARM7 individually - so - as always - you would be correct
lol

 

[studioz]

my MN is been running super stable for almost 1 year , but lately dashd is been going down twice /month .
i decided to follow Reuben's guide and i got everything running except for the restart script
i'm a linux noob so i need your expertise :
i get this error when i type this :
command: [email protected]:~/dashman$ /bin/su xxxxx -c '/home/xxxxx/.dash/dashd 2>&1 >> /home/xxxxx/.dash/rc.local.log'
Password: ***********

Error: [email protected]:~/dashman$ Error: Cannot obtain a lock on data directory /home/xxxxx/.dash. Dash Core is probably already running.

thx in advance for your help

 

[demo]

my MN is been running super stable for almost 1 year , but lately dashd is been going down twice /month .
i decided to follow Reuben's guide and i got everything running except for the restart script
i'm a linux noob so i need your expertise :
i get this error when i type this :
command: [email protected]:~/dashman$ /bin/su xxxxx -c '/home/xxxxx/.dash/dashd 2>&1 >> /home/xxxxx/.dash/rc.local.log'
Password: ***********

Error: [email protected]:~/dashman$ Error: Cannot obtain a lock on data directory /home/xxxxx/.dash. Dash Core is probably already running.

thx in advance for your help

This is probably because you run dashd more than once. There is a .lock file that prevents dashd to run more than once. Maybe your raspi had an ubnormal termination, and the .lock file remains.

1) Check if dashd is running by typing:
ps -efl|grep dashd

It will show the processes, so you will see if dashd is running. If it is running then stop the dashd.

2) If dashd dont stop then you may reboot your raspi to stop the dashd, or in the strange case you reboot and dashd still remains, then try to stop it, and if you still cannot, then you have to check the /etc/init.d file (which requires some linux knowledge) or you can try to type:

ps -efl|grep dashd
kill -9 dashd_procces

where dashd_procces is the process of dashd that you will discover when typing the "ps -efl|grep dashd" command

3) Most probably you wll discover that dashd dont run, so just try opening the directory /home/xxxxx/.dash and delete the file .lock. You may also do this step as your first step, but it is not tottaly safe to delete .lock whenever there is a possiblity that dashd runs.

4) run the dashd again (it will create .lock file again, hoping this new .lock is the correct one)