[XMR] Monero - A secure, private, untraceable cryptocurrency - page 717.

c789

hero member

Activity: 850

Merit: 1000

Congratulations and thanks to all who made v0.9 possible!

I downloaded the linux64 binaries today as well as blockchain.raw. I used this to create the blockchain (used my actual path to download.raw):
sudo blockchain_import --input-file /path/to/your/download.raw --verify 0

After that process completed, I ran this command:
sudo ./bitmonerod

...and got this error message:

Code:

Creating the logger system
2016-Jan-02 00:43:04.712691 Initializing cryptonote protocol...
2016-Jan-02 00:43:04.712868 Cryptonote protocol initialized OK
2016-Jan-02 00:43:04.713234 Initializing p2p server...
[1451713384] libunbound[4214:0] info: warning: unsupported algorithm for trust anchor . DS IN
[1451713384] libunbound[4214:0] warning: trust anchor . has no supported algorithms, the anchor is ignored (check if you need to upgrade unbound and openssl)
2016-Jan-02 00:43:04.743525 Set limit-up to 2048 kB/s
2016-Jan-02 00:43:04.743885 Set limit-down to 8192 kB/s
2016-Jan-02 00:43:04.744098 Set limit-up to 2048 kB/s
2016-Jan-02 00:43:04.744425 Set limit-down to 8192 kB/s
2016-Jan-02 00:43:04.745453 Binding on 0.0.0.0:18080
2016-Jan-02 00:43:04.745744 Net service bound to 0.0.0.0:18080
2016-Jan-02 00:43:04.745867 Attempting to add IGD port mapping.
2016-Jan-02 00:43:08.832162 Added IGD port mapping.
2016-Jan-02 00:43:08.832325 P2p server initialized OK
2016-Jan-02 00:43:08.832571 Initializing core rpc server...
2016-Jan-02 00:43:08.832728 Binding on 127.0.0.1:18081
2016-Jan-02 00:43:08.832939 Core rpc server initialized OK on port: 18081
2016-Jan-02 00:43:08.833045 Initializing core...
2016-Jan-02 00:43:08.833459 Loading blockchain from folder /home/mike/.bitmonero/lmdb ...
2016-Jan-02 00:43:08.833574 option: fastest
2016-Jan-02 00:43:08.833667 option: async
2016-Jan-02 00:43:08.833759 option: 1000
2016-Jan-02 00:43:08.834491 LMDB memory map needs resized, doing that now.
2016-Jan-02 00:43:08.834707 LMDB Mapsize increased. Old: 10215MiB, New: 11239MiB
2016-Jan-02 00:43:08.908128 Error attempting to retrieve a hard fork version from the db
2016-Jan-02 00:43:08.908449 ERROR /DISTRIBUTION-BUILD/src/daemon/daemon.cpp:146 Uncaught exception! Error attempting to retrieve a hard fork version from the db
2016-Jan-02 00:43:08.908585 Deinitializing rpc server...
2016-Jan-02 00:43:08.908876 Deinitializing p2p...
2016-Jan-02 00:43:08.910596 Deinitializing core...
2016-Jan-02 00:43:08.911011 Closing IO Service.
2016-Jan-02 00:43:08.957527 Deinitializing cryptonote_protocol...

Any ideas? EDIT: All files in the log directory were empty.

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: boolberry on January 01, 2016, 06:56:35 PM

Congratulations on the new release!

Minor bug report:

When syncing from scratch the "days behind" is off by a factor of two. I did not look at the relevant code yet but assume that the proper equation going forward (for 2 minute blocks) was improperly applied to the "days behind" notifications for historical (1 minute) blocks.

Noted here: https://github.com/monero-project/bitmonero/issues/591

Hueristic

legendary

Activity: 3836

Merit: 4969

Doomed to see the future and unable to prevent it

https://thehackernews.com/2015/12/north-korea-red-star-os.html

Febo

legendary

Activity: 2744

Merit: 1288

Quote from: boolberry on January 01, 2016, 06:56:35 PM

Congratulations on the new release!

Minor bug report:

When syncing from scratch the "days behind" is off by a factor of two. I did not look at the relevant code yet but assume that the proper equation going forward (for 2 minute blocks) was improperly applied to the "days behind" notifications for historical (1 minute) blocks.

lol i was wondering how come there was 1200 days of existence, now it makes sense.

boolberry

sr. member

Activity: 378

Merit: 250

Congratulations on the new release!

Minor bug report:

When syncing from scratch the "days behind" is off by a factor of two. I did not look at the relevant code yet but assume that the proper equation going forward (for 2 minute blocks) was improperly applied to the "days behind" notifications for historical (1 minute) blocks.

XMRpromotions

sr. member

Activity: 336

Merit: 250

Quote from: ArticMine on January 01, 2016, 05:26:34 PM

Downloaded the new 0.9 release for GNU/LInux. What a difference. Under 60 MB RAM vs over 9.2 GB RAM for the 0.8.8.6 release. A major list of improvements https://github.com/monero-project/bitmonero/releases and some that were not even mentioned such as including the code for the tail emission.

I upgraded from one of the 0.8.8.7 betas so there was no need to re-sync the db. The wallet did require a re-sync, after copying wallet.bin.address.txt and wallet.bin.keys. Do not copy wallet.bin over it will generate an error.

What a great start to 2016 for Monero. I want to thank the development team for all of their hard work in 2015!

ArticMine

legendary

Activity: 2282

Merit: 1050

Monero Core Team

Downloaded the new 0.9 release for GNU/LInux. What a difference. Under 60 MB RAM vs over 9.2 GB RAM for the 0.8.8.6 release. A major list of improvements https://github.com/monero-project/bitmonero/releases and some that were not even mentioned such as including the code for the tail emission.

I upgraded from one of the 0.8.8.7 betas so there was no need to re-sync the db. The wallet did require a re-sync, after copying wallet.bin.address.txt and wallet.bin.keys. Do not copy wallet.bin over it will generate an error.

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: nzminer on January 01, 2016, 05:10:49 PM

OK, that sums it up well thanks

Anyway, the connectivity issue im not sure what is the cause, as it was working fine earlier.

I dont have any firewall or anything that could be the cause.

Don't know then, maybe reboot, check antivirus or other stuff that might be blocking it.

Quote

I wonder if CPU mining is still profitable?
I believe its now GPU mineable now?

CPU is profitable if your electricity rates are low to moderate and you have a CPU with AES-NI. It is GPU mineable too, but efficiency between CPU and GPU is close to the same. GPU is more scalable since you can buy more cards.

EDIT: noted AES-NI as a requirement for CPU mining to be efficient. Core 2 Quad is too old. It can mine, but not very efficiently.

ArticMine

legendary

Activity: 2282

Merit: 1050

Monero Core Team

Quote from: nzminer on January 01, 2016, 04:52:29 PM

...
This is crap to learn this, why is the transaction fee so high just because i got small payouts?

I dont really understand how this all works. Are my XMR broken into tiny fragments instead of their own unit?

Seems i wasted alot of time mining this if they are unspendable.

Quite honestly if this is a concern, I would just wait it out. If the price of XMR increases then the fees in XMR terms will likely drop and the relative fee to clean up the dust will also drop.

nzminer

legendary

Activity: 1918

Merit: 1001

OK, that sums it up well thanks

Anyway, the connectivity issue im not sure what is the cause, as it was working fine earlier.

I dont have any firewall or anything that could be the cause.

I wonder if CPU mining is still profitable?
I believe its now GPU mineable now?

I was getting 20 Kh/s with my Core2 Quad.

Febo

legendary

Activity: 2744

Merit: 1288

Quote from: nzminer on January 01, 2016, 04:52:29 PM

Quote from: smooth on January 01, 2016, 04:46:34 PM

As saddambitcoin explained, the early pool payouts were really not usable. The transaction fee will be extremely high to spend them even with the sweep_dust command.

The only other option is to archive that wallet into cold storage and hope that in the future the value of XMR goes up so much that dust becomes worth more (and tx fees relatively less).

This is crap to learn this, why is the transaction fee so high just because i got small payouts?

I dont really understand how this all works. Are my XMR broken into tiny fragments instead of their own unit?

Seems i wasted a lot of time mining this if they are unspendable.

In first weeks pools were sending pays after they found block so if you gave them 0.1% of hashrate, you got 0.1% of block reward. So unless you were mining with lots CPUs, you were getting tiny amounts of XMR what is not good because, you now have problems spend it ( This part is same as with bitcoin, but i dont have words to explain it. You got small amounts of XMR smaller then are transaction fees)

Latter, pools started sending to smaller miners, their reward only after they mined for 1 XMR or once a week( i forgot the exact number)

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: nzminer on January 01, 2016, 04:48:31 PM

2016-Jan-02 10:46:40.876620 [P2P8]Failed to connect to any of seed peers, contin
uing without seeds

This is some sort of connectivity issue, firewall, DNS config, etc. Your node is not able to connect.

smooth

legendary

Activity: 2968

Merit: 1198

Yes it is broken into tiny fragments. Instead of waiting until you had 1-2 XMR (or even 0.1 XMR) to pay you, the pool sent you pieces of some tiny amount like 0.004349098706. Each of those fragments now needs to be spent individually. That's how (nearly) every coin works.

This problem was fixed long ago, and most pools have a more reasonable payout threshold now.

The fees are not really high, they are something like 0.005 USD for a small transaction. The problem is that 0.004349098706 is worth like fifth of a USD cent. That is just not economical to process.

nzminer

legendary

Activity: 1918

Merit: 1001

Quote from: smooth on January 01, 2016, 04:46:34 PM

As saddambitcoin explained, the early pool payouts were really not usable. The transaction fee will be extremely high to spend them even with the sweep_dust command.

The only other option is to archive that wallet into cold storage and hope that in the future the value of XMR goes up so much that dust becomes worth more (and tx fees relatively less).

This is crap to learn this, why is the transaction fee so high just because i got small payouts?

I dont really understand how this all works. Are my XMR broken into tiny fragments instead of their own unit?

Seems i wasted alot of time mining this if they are unspendable.

nzminer

legendary

Activity: 1918

Merit: 1001

Quote from: saddambitcoin on January 01, 2016, 04:41:45 PM

Sweep dust sends all dust outputs back to yourself with mixin 0 - essentially consolidates your dust outputs so that you can spend them.

Because you were pool mining early on, unfortunately you have a lot of dust. Pools have since stopped sending out such small payments.

Ok, there is alot i dont know in this area.

So i my balance is showing 3XMR more than i really have? My current balance is what the mining pool said i had earned so never gave it much thought.

Im also having trouble with the new daemon, ive removed the old blockchain, and started fresh and and this is the errors coming up:

2016-Jan-02 10:46:26.995873 [RPC0]ERROR C:/msys64/DISTRIBUTION-BUILD/src/crypton
ote_core/blockchain.cpp:1614 Ours and foreign blockchain have only genesis block
in common... o.O
2016-Jan-02 10:46:26.995873 [RPC0]ERROR C:/msys64/DISTRIBUTION-BUILD/src/rpc/cor
e_rpc_server.h:77 Failed to on_get_blocks()
2016-Jan-02 10:46:40.876620 [P2P8]Failed to connect to any of seed peers, contin
uing without seeds

smooth

legendary

Activity: 2968

Merit: 1198

As saddambitcoin explained, the early pool payouts were really not usable. The transaction fee will be extremely high to spend them even with the sweep_dust command.

The only other option is to archive that wallet into cold storage and hope that in the future the value of XMR goes up so much that dust becomes worth more (and tx fees relatively less).

GingerAle

legendary

Activity: 1260

Merit: 1008

Quote from: nzminer on January 01, 2016, 04:35:30 PM

Quote from: smooth on December 31, 2015, 08:15:36 PM

Quote from: nzminer on December 31, 2015, 06:31:04 PM

Quote from: saddambitcoin on December 31, 2015, 06:16:46 PM

Ok, that is because the transfer is not being made.

Can you confirm you are sending your transaction with 0 mixin?

If you type "help" and see the "sweep_dust" option you can also try that.

I sent with the recommended level of 3 mixin. I tried sweep_dust and it says its an unknown command.

Not having the sweep_dust command means your version of the wallet is old. You should get the version from github, one of the recent beta builds, or wait for the new release. But like saddambitcoin said, you can just use mixin 0 with the older wallet. The world won't come crashing down because one person used mixin 0.

What exactly is the sweep_dust command supposed to do exactly?
It was going to charge me a fee of 1.5 XMR and then remove 3 XMR from my wallet. I said no.

remove 3 xmr from your wallet? that sounds weird.

basically if you have any dust outputs, this command sweeps them all into a transaction to yourself. Dust outputs are kinda useless, so if you don't sweep them, your wallet probably won't use them to craft a transaction anyway. Alternatively, you could wait until confidential ring transactions whatever is implemented, because maybe dust doesn't have the same effect...

to understand the dust problem and why sweep_dust was necessary, checkout some of the MRL publications... I think this one is MRL 4.

labs.getmonero.org

saddambitcoin

legendary

Activity: 1610

Merit: 1004

Sweep dust sends all dust outputs back to yourself with mixin 0 - essentially consolidates your dust outputs so that you can spend them.

Because you were pool mining early on, unfortunately you have a lot of dust. Pools have since stopped sending out such small payments.

nzminer

legendary

Activity: 1918

Merit: 1001

Quote from: smooth on December 31, 2015, 08:15:36 PM

Quote from: nzminer on December 31, 2015, 06:31:04 PM

Quote from: saddambitcoin on December 31, 2015, 06:16:46 PM

Ok, that is because the transfer is not being made.

Can you confirm you are sending your transaction with 0 mixin?

If you type "help" and see the "sweep_dust" option you can also try that.

I sent with the recommended level of 3 mixin. I tried sweep_dust and it says its an unknown command.

Not having the sweep_dust command means your version of the wallet is old. You should get the version from github, one of the recent beta builds, or wait for the new release. But like saddambitcoin said, you can just use mixin 0 with the older wallet. The world won't come crashing down because one person used mixin 0.

What exactly is the sweep_dust command supposed to do exactly?
It was going to charge me a fee of 1.5 XMR and then remove 3 XMR from my wallet. I said no.

fluffypony

donator

Activity: 1274

Merit: 1060

GetMonero.org / MyMonero.com

Quote from: boestin on January 01, 2016, 02:10:09 PM

The link on the getmonero site still points to the previous version..

Fixed, sorry about that

Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 717. (Read 4671660 times)