Guys need help. Problem with update wallet
compilation terminated.
make[2]: *** [qt/test/qt_test_test_dash_qt-test_main.o] Error 1
make[2]: Leaving directory `/home/user/DashCoin/src'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/user/DashCoin/src'
make: *** [install-recursive] Error 1
More lines pls EDIT: also try "./configure --disable-tests" instead of "./configure" |
|
|
|
is it normal to have the debug log flooded with these messages:
2015-08-27 15:48:10 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-08-27 15:48:10 mnw - invalid message - Masternode not in the top 10 (11)
2015-08-27 15:48:10 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-08-27 15:48:10 mnw - invalid message - Masternode not in the top 10 (11)
2015-08-27 15:48:10 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-08-27 15:48:10 mnw - invalid message - Masternode not in the top 10 (11)
2015-08-27 15:48:10 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (12)
2015-08-27 15:48:10 mnw - invalid message - Masternode not in the top 10 (12)
2015-08-27 15:48:10 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
***** **** 20 0 1721m 1.2g 65m S 116.9 4.0 4:23.91 dashd
10-20 minutes after a start - yes, it's a known one https://github.com/dashpay/dash/issues/578 |
|
|
|
Our build system now produce linux files that are not recognized by Ubuntu file explorer as executables though they are. I wrote yet another simple script  to install dash-qt from downloaded archive and to give it a nice icon. Here is what you need to do: 1) After you extracted downloaded archive you should have dash-0.12.0 folder somewhere. Go inside it, create a file named install_dash_qt.sh and edit it with your favorite editor: #!/bin/bash
sudo -s install -m 0755 -o root -g root -t /usr/local/bin bin/dash-qt
echo "[Desktop Entry]
Name=Dash-Qt
Comment=Dash - Reinventing Cryptocurrency https://www.dashpay.io
Type=Application
Exec=dash-qt %u
Terminal=false
Icon=/usr/share/pixmaps/dash128.xpm
MimeType=x-scheme-handler/dash
Categories=Applications;Finance;" > ~/Desktop/Dash-Qt.desktop
chmod u+x ~/Desktop/Dash-Qt.desktop
sudo cp ~/Desktop/Dash-Qt.desktop /usr/share/applications/
sudo wget -O /usr/share/pixmaps/dash128.xpm https://github.com/dashpay/dash/raw/master/share/pixmaps/bitcoin128.xpm 2) Right click on empty space in that folder and choose "Open in Terminal". In command line issue: chmod u+x install_dash_qt.sh to make file executable and to run it. Enter your password and shortly after you should have a nice icon on your Desktop and the same icon in Applications. Enjoy!  PS. This script reguires wget. Install it first if you don't have it already sudo apt-get install wget EDIT: "su -c" requires you to set root password which "normal"/non-developer users do not have at all (by ubuntu's default) Changed script to use "sudo -s" instead, give it a try if you had problems before |
|
|
|
I don't think so  snip UdjinM6, I do believe the crontab method is indeed the most stable way of doing this and this should work. I am probably thinking this is harder than it is. But I have struggled in the past to get permissions of the crontab user, file permissions, and directory just right so everything runs. Just trying to save someone else a little of that time I wasted... No problems at all doing it in another way. I didn't mean to force everyone to use my script, it was just few statements in your post that doesn't feel like they are 100% correct But yeah, there are multiple ways to achive the same result and there could be some unexpected troubles using either method. EDIT: so, once again, no troubles and thank you for providing alternative version that worked for you. |
|
|
|
.......
Actually, crontabs may require a restart or server reboot. Might also need to run with sudo crontab -e if running server as root.
..A server I rented didn't have crontab installed so this isn't always a no brainer...
If you don't have crontab installed, try this: apt-get update
apt-get upgrade
apt-get install cron Then you need to reboot for the cron process to take effect. Add your crontab with crontab -e or sudo crontab -e Then activate your crontab. I think sudo service cron restart Then to stop you need to edit the crontab and then restart the cron service. Seems more complicated to me. I don't think so ...
crontab is the program used to install, deinstall or list the tables used to drive the cron( 8 ) daemon in Vixie Cron. Each user can have their own crontab, and
though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly.
...
For standard Debian systems, all users may use this command.
...
...
cron searches its spool area (/var/spool/cron/crontabs) for crontab files (which are named after accounts in /etc/passwd); crontabs found are loaded into memory.
...
cron then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute.
...
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on the /etc/crontab file) has changed, and if it has, cron will then
examine the modtime on all crontabs files and reload those which have changed. Thus cron need not be restarted whenever a crontab file is modified. Note that
the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
...
|
|
|
|
12.2.49
after reindex => "yes"
i get this now for 10min. is everything working as it should?
/lots of Y/
dashd -reindex |
|
|
|
How to start dashd automatically again after it crashed.
This will work if dashd crashes, but if the process is still running and maxes out memory, then this won't work. yep, we are still investigating... |
|
|
|
How to start dashd automatically again after it crashed. run: add line: */1 * * * * /home/dashuser/mn_watch.sh >/dev/null 2>&1 use any editor you like and save this as "mn_watch.sh" file in user "dashuser" home directory: #!/bin/bash
if [ -z `pidof dashd` ]; then
/home/dashuser/dashd
fi
add executable flag: PS. Use appropriate username, not "dashuser" from my example  I also assumed that dashd is located in your user home directory, change path if needed. PPS. not tested but should work EDIT: ooops, tested and fixed |
|
|
|
Should the white paper still be translated, or is it too outdated? Yeah, I guess it should be translated, it's quite up to date imo. Still can't find time do finish ru translation though... |
|
|
|
merde, je ne parlais pas francais Oh, triste... |
|
|
|
Help needed after i upgraded to Windows 64x 0.12.0.46 version i keep getting the below error everytime i try launching DASH.  Make sure you are actually running v12 and not the old (v11) link or file. If for whatever reason you want to run v11 after you installed (and run) v12 go to %appData%/Dash folder and remove (rename) masternode.conf |
|
|
|
If my AWS shutdown my server and I have no back up. Did I lose my coins?
No, if you are using Hot/Cold MN setup your coins never leave your local wallet. |
|
|
|
V12.0.45 is working great for me, really impressive work, all the new tools, wallet repair, backups, syncing budgets, sporks, everything is super slick. It feels like a huge step forward, looking forward to what we can do with the budget system.  v12.0.45 crashed all my MNs every two days. Still can't find the problem. Very frustrating. Since 8 days without any payment for all my MNs. "crashed" - daemon (process) died or you mn just dropped out of list? If it actually died - what your vps specs are? all daemons on my digital ocean droplet (Ubuntu 14.04) died, masternode debug can't find coin, need to restart from hot wallet. Then qt-wallet on my Debian machine where I host my hot wallet hang on the "Synchronizing budgets... 100%" msg, can't even click on anything. Twice the whole Debian machine crashed with the wallet together. Never seen an update like that. If you're interested I could try to send you the debug.log. Thanks in advance. That's weird... mine are on DO too and they feel fine. Checklist: - "txindex=1" in dash.conf - 1 run with -reindex after that ^^^ - start-many/alias from local after reindex is finished - "masternode debug" on remote should give you "Masternode successfully started", if it's not try this https://dashtalk.org/threads/v12-release.5888/page-15#post-63716 |
|
|
|
V12.0.45 is working great for me, really impressive work, all the new tools, wallet repair, backups, syncing budgets, sporks, everything is super slick. It feels like a huge step forward, looking forward to what we can do with the budget system. v12.0.45 crashed all my MNs every two days. Still can't find the problem. Very frustrating. Since 8 days without any payment for all my MNs. "crashed" - daemon (process) died or you mn just dropped out of list? If it actually died - what your vps specs are? |
|
|
|
|
Show Posts
