Topic: [ANN] [QRK] Quark | POW/POS | 0.10.6.3 - New Self Moderated Thread - page 14. (Read 64318 times)

strange, i had the error that my wallet was 2 weeks behind,... did the "add nodes" configuration, restarted and now it kinda stucked at 3 weeks now

I asked yesterday and am waiting for a reply.

Hi, glad to help

yes, you can create a systemd service like this: /etc/systemd/system/quarkMN1.service:
[Unit]
Description=quarkcoin MN1 service
After=network.target
 [Service]
User=root
Group=root
Type=forking
#PIDFile=/root/.quarkcoin/quarkd.pid
ExecStart=/root/bin/quarkd_MN1.sh
ExecStop=/root/bin/quark-cli_MN1.sh stop
Restart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=10s
StartLimitInterval=120s
StartLimitBurst=5
 [Install]
WantedBy=multi-user.target

Then /root/bin/quarkd_MN1.sh:
#!/bin/bash
quarkd -daemon -conf=/root/.quarkcoin_MN1/quarkcoin.conf -datadir=/root/.quarkcoin_MN1 $*

quark-cli_MN1.sh:
#!/bin/bash
quark-cli -conf=/root/.quarkcoin_MN1/quarkcoin.conf -datadir=/root/.quarkcoin_MN1 $*

start service:
systemctl start quarkMN1

and set in crontab: crontab -e
@reboot systemctl start quarkMN1

and if you don't want to corrupt database when restart, create a link to: /etc/rc6.d
@K99_stop_nodes (without extension), from /root/bin/stop_nodes.sh:
contain stop masternode command: systemctl stop quarkMN1

and you are really ready with your masternode!

Hi, got a problem in setting up a masternode. Like to do it with nodehub.io.
Did all in a right way (i think/hope) but dont runs. Download newest version (10.7.3)

after download runs full synchron-> changed the masternode.conf (add xxxxxxxxxxxxxxxxxxxxxxxx 00.000.000.00:00000 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx00
)  -> didnt run (error ) -> add "txindes=1" -> didnt run -> clean masternode.conf -> runs again full synchron

Error is : Enabling Masternode support requires turning on transaction indexing. Please add txindex=1 to your configuration and start with -reindex (-reindex in console doesnt help, unknown)

Yes - i have set a passphrase. When i change in the running wallet the msternode.con and write in the console "masternode start-alias "xxxxxxxxxxxxxxxx" walles says "your wallet is locked, passphrase is required (code-1) but cant fill anywhere the passphrase. When i go to masternodes tab and click "start all" or start missing" i will asked for the passphrase and fill in. but wallet cant find any own masternode.

What i do wrong ?

thanks for help

@Dev, do you know when AEX opens their wallet?
I'm waiting more than one month. Opend several tickets to get more information.
They always told me "wallet upgrade is in progress". Do you have more details? 

I mean if you resync without the bootstrap it should not crash.

it seems a very big problem to me...what if i make a masternode it means i have to wait at least 18 - 24 hours to start it?? i think it will be a problem...what if i have to send coins to someone..."hey, don't worry, it takes only 24 hours to resync and send it to you..."

Hi. Why don't you try without the bootstrap then? I've done the same thing and it took me less than a day to be fully synced.

Wow! Thank you so much to both F0nzy and AggroHead! @AggroHead I'm pretty new in command only interface and unix/linux OS. I didn’t know that the client file needs to be in bin folder. Also i was in wrong directory  Anyways, it's working now. Should I make a systemd service in order to start automatically in case of power outrage? My PC will start automatically in such case.

and then run watch command again

Thank you for the input. From your command, it seems that it doesn’t find the log file. However, it is there! Entering the other commands separately I always get "quark-cli: command not found" I've putted it in root/.quarkcoin. Is there something I am missing here 

You can use this command to follow-up sync-status:

A big thank you! I thought is more complicated because of the shitcoins I have been dealing with recently. You have a beer from me once I buy some QRK. I have another question and I hope you are willing to help. I've made it to start with "chmod +x quarkd" and "./quarkd -reindex". But I’ve been struggling to make the command for checking the status (quarkcoin-cli masternode status) to work. Whatever I try it prints ": command not found" Any suggestions for that? It's still reindexing according to htop.

good morning, is there any group/channel to talk easily to the devs?? any discord, telegram...
the new wallet is not working...i synced and closed, ok. now i can't reopen...the wallet keeps charging blocks forever and freeze and i have to use bootstrap again, and everything start again...charging blocks, freeze, bootstrap, again and again and again...

Hello,
it's easy, than 1x1

In windows:
 - Download wallet, create an address, name it: MN1
 - Send exactly 10000 QRK to this address
 - Wait 15 confirmations
 - generate masternode key, and outputs in wallet debug window: (with this commands: masternode genkey, masternode outputs)
 - exit from wallet
 - create masternode.conf file in the QuakCoin directory, and put in this information (replace with your MN information):
mn1 127.0.0.2:13721 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
 - start wallet, in masternodes you will see masternode record
 
Create an ubuntu VPS, with minimum 4GB ram:
 - install QRK wallet
 - create .quarkcoin directory in your root or home
 - create quarkcoin.conf in this direcdtory
 - put into the config file your masternode data
 - start wallet, wait while syncronized
 - when ready in windows wallet start your masternode
 - ready, wait rewards
 - send some QRK to my wallet: QZnw4QtVkmCQiJz3YpTzrWNjERKTngU1Ri

it's all!

Ubuntu quarkcoin.conf example:
Example:

server=1
listen=1
daemon=1

txindex=1
masternode=1
externalip=93.104.214.182
masternodeprivkey=7F2rNf7RtChq6BCqJBdt4oVnB1spWquZ5BZBquMp8Cd7E1rDwtE

#orig
addnode=120.243.239.150
addnode=120.243.240.171
addnode=120.78.154.47
...


Check your masternode:
quarkcoin-cli masternode status

if it's ok, then output:
{
    "vin" : "CTxIn(COutPoint(bd0611a90f, 1), scriptSig=)",
    "service" : "93.104.214.182:13721",
    "pubkey" : "QRdg2MYzNNKZdmVbeZp3rWQ2yGazU8JSdd",
    "status" : "Masternode successfully started"
}

Great,
now it's works!

Aex exchange is not open yet？？

0.10.7.3->Debugging window->Console  like this: addnode "101.132.153.65:13721" "add"

Hello all! I have recently stuble across your coin and read all the pages in this threat. It’s very interesting and cool so I want to participate. I want to host a masternode on Ubuntu server but there is so little information and can’t figure it out. Things like quarkcoin deamon and such... Is there any guides or at least some more information? It will be great!

Maybe someone can tell what the problem is?

2019-09-08 17:19:17 Loaded 352 addresses from peers.dat  43ms
2019-09-08 17:19:17 AddLocal([2602:30a:c0b1:4230:21d7:727b:bb55:a167]:11973,1)
2019-09-08 17:19:17 Discover: COREY-PC - 2602:30a:c0b1:4230:21d7:727b:bb55:a167
2019-09-08 17:19:17 AddLocal([2602:30a:c0b1:4230:3c37:69bc:6218:d1e7]:11973,1)
2019-09-08 17:19:17 Discover: -PC - 2602:30a:c0b1:4230:3c37:69bc:6218:d1e7
2019-09-08 17:19:17 dnsseed thread start
2019-09-08 17:19:17 init message: Done loading
2019-09-08 17:19:17 net thread start
2019-09-08 17:19:17 addcon thread start
2019-09-08 17:19:17 dumpaddr thread start
2019-09-08 17:19:17 stakemint thread start
2019-09-08 17:19:17 ThreadStakeMinter started
2019-09-08 17:19:17 opencon thread start
2019-09-08 17:19:17 msghand thread start
2019-09-08 17:19:17 upnp thread start
2019-09-08 17:19:17 QuarkMiner started
2019-09-08 17:19:17 GUI: PaymentServer::LoadRootCAs : Loaded  0  root certificates
2019-09-08 17:19:18 receive version message: /Satoshi:0.10.6.3/: version 70004, blocks=7144300, us=172.11.20.35:50155, peer=1
2019-09-08 17:19:18 Added time data, samples 2, offset +1 (+0 minutes)
2019-09-08 17:19:25 No valid UPnP IGDs found
2019-09-08 17:19:25 upnp thread exit
2019-09-08 17:19:28 Loading addresses from DNS seeds (could take a while)
2019-09-08 17:19:29 8 addresses found from DNS seeds
2019-09-08 17:19:29 dnsseed thread exit
2019-09-08 17:19:30 receive version message: /Satoshi:0.10.6.3/: version 70004, blocks=7144300, us=172.11.20.35:50158, peer=2
2019-09-08 17:19:30 Added time data, samples 3, offset -1 (+0 minutes)
2019-09-08 17:19:36 receive version message: /Satoshi:0.10.6.5/: version 70004, blocks=7131156, us=172.11.20.35:50160, peer=3
2019-09-08 17:19:36 Added time data, samples 4, offset +0 (+0 minutes)
2019-09-08 17:19:37 receive version message: /Satoshi:0.10.6.3/: version 70004, blocks=7111857, us=172.11.20.35:50161, peer=4
2019-09-08 17:19:37 Added time data, samples 5, offset -1 (+0 minutes)
2019-09-08 17:19:37 nTimeOffset = +0  (+0 minutes)
2019-09-08 17:19:38 receive version message: /Satoshi:0.10.6.3/: version 70004, blocks=7144300, us=[2602:30a:c0b1:4230:3c37:69bc:6218:d1e7]:50162, peer=5
2019-09-08 17:19:38 Added time data, samples 6, offset +0 (+0 minutes)
2019-09-08 17:19:38 receive version message: /Satoshi:0.10.6.3/: version 70004, blocks=7144300, us=172.11.20.35:50163, peer=6
2019-09-08 17:19:38 Added time data, samples 7, offset +70 (+1 minutes)
2019-09-08 17:19:38 nTimeOffset = +0  (+0 minutes)
2019-09-08 17:19:39 receive version message: /Satoshi:0.10.6.5/: version 70004, blocks=7131156, us=[2602:30a:c0b1:4230:3c37:69bc:6218:d1e7]:50164, peer=7
2019-09-08 17:19:39 Added time data, samples 8, offset +0 (+0 minutes)
2019-09-08 17:50:43 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 18:10:14 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 18:32:07 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 18:36:28 receive version message: /Satoshi:0.10.6.3/: version 70004, blocks=7076106, us=172.11.20.35:50953, peer=15
2019-09-08 18:49:43 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 19:07:20 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 19:27:20 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 19:30:24 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 19:34:29 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 19:38:52 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 19:43:31 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 19:48:17 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 19:52:55 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 19:57:33 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:02:14 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:06:58 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:11:34 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:16:19 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:20:55 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:26:05 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:28:30 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:32:18 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:34:37 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:38:26 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:40:45 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:44:34 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:46:52 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:50:40 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:53:01 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2019-09-08 20:56:45 socket recv error An existing connection was forcibly closed by the remote host.  (10054)