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

equipoise

hero member

Activity: 794

Merit: 1000

Monero (XMR) - secure, private, untraceable

Quote from: DemocraticRepublicOfDave on January 21, 2016, 10:11:52 AM

Hi all,

Quick question - have older wallet.dat files (pre seed) been depricated in v0.9.1?

When I try to run simple wallet I get the following error :

Code:

Error: failed to load wallet: invalid signature

However if I run an older simplewallet with the v0.9.1 bitmonerod the wallet file is accepted and syncs.

It this just a question of creating a new wallet (with new address) and transfering fund from old (using old simplewallet) to new?

Just want to check before I try this.

Cheers

Dave

Did you tried deleting the .bin and restoring from the .keys? My pre-seed .keys is still working. Backup your wallet first.

DemocraticRepublicOfDave

member

Activity: 77

Merit: 10

Hi all,

Quick question - have older wallet.dat files (pre seed) been depricated in v0.9.1?

When I try to run simple wallet I get the following error :

Code:

Error: failed to load wallet: invalid signature

However if I run an older simplewallet with the v0.9.1 bitmonerod the wallet file is accepted and syncs.

It this just a question of creating a new wallet (with new address) and transfering fund from old (using old simplewallet) to new?

Just want to check before I try this.

Cheers

Dave

Lina28011

newbie

Activity: 1

Merit: 0

Please give conf file for 7950

Afros

newbie

Activity: 19

Merit: 0

Quote from: Drhiggins on January 20, 2016, 11:04:55 PM

Quote from: dEBRUYNE on January 20, 2016, 09:50:44 PM

Quote from: Rabinovitch on January 20, 2016, 09:48:36 PM

Well, I left bitmonerod opened for several days. Here is what I see today:

This was asked on #monero yesterday as well:

Quote

ERROR {2} {p1} 2016-01-19 15:32:37.489227 [abstract_tcp_server2.inl+494 ::do_se nd_chunk] send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(1000), s hutting down connection
Server send que max count 1000? Is that something i should rise or what is causing that
TL123: it's on the list of things to fix, it's harmless and does go away, or else just restart the daemon

I got this very same thing earlier this week as well. I didn't take a screen shot of it but this was it.

Happened to me twice. Both times it happened around two days after restarting the daemon. Last time i left it to run for 3 hours in order to see if it corrects itself but it kept showing errors and the incoming connections were dropping so i restarted the daemon.

aiwe

legendary

Activity: 1750

Merit: 1101

karbo.io

Continue testing new Wolf's AMD miner.

Interesting behavior on one pool: it kinda looses connection to this paricular pool, i.e. after some time mining (it may be an hour or more, or even less) it continues mining and says it found shares but without the message that share is accepted and pool says last share submitted is for example an hour ago.

It happens only on one pool of all that I tried. On others it was mining quite long (no less than 10 hours) without issues and shares were rewarded.

It's a pity because I liked that pool for its generous rewards and now I have to monitor it

aiwe

legendary

Activity: 1750

Merit: 1101

karbo.io

I also had this red screen in daemon

Drhiggins

sr. member

Activity: 306

Merit: 251

Quote from: dEBRUYNE on January 20, 2016, 09:50:44 PM

Quote from: Rabinovitch on January 20, 2016, 09:48:36 PM

Well, I left bitmonerod opened for several days. Here is what I see today:

This was asked on #monero yesterday as well:

Quote

ERROR {2} {p1} 2016-01-19 15:32:37.489227 [abstract_tcp_server2.inl+494 ::do_se nd_chunk] send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(1000), s hutting down connection
Server send que max count 1000? Is that something i should rise or what is causing that
TL123: it's on the list of things to fix, it's harmless and does go away, or else just restart the daemon

I got this very same thing earlier this week as well. I didn't take a screen shot of it but this was it.

aminorex

legendary

Activity: 1596

Merit: 1030

Sine secretum non libertas

Quote from: smooth on January 16, 2016, 07:25:00 PM

I was helping by drinking whiskey.

We all need to contribute in our areas of comparative advantage.

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

Quote from: Rabinovitch on January 20, 2016, 09:48:36 PM

Well, I left bitmonerod opened for several days. Here is what I see today:

This was asked on #monero yesterday as well:

Quote

ERROR {2} {p1} 2016-01-19 15:32:37.489227 [abstract_tcp_server2.inl+494 ::do_se nd_chunk] send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(1000), s hutting down connection
Server send que max count 1000? Is that something i should rise or what is causing that
TL123: it's on the list of things to fix, it's harmless and does go away, or else just restart the daemon

Rabinovitch

legendary

Activity: 2030

Merit: 1076

BTCLife.global participant

Well, I left bitmonerod opened for several days. Here is what I see today:

Drhiggins

sr. member

Activity: 306

Merit: 251

aiwe

legendary

Activity: 1750

Merit: 1101

karbo.io

Drhiggins

sr. member

Activity: 306

Merit: 251

Quote from: aiwe on January 19, 2016, 02:13:47 PM

Concerning Wolf's AMD miner.

After two days of mining I can tell it is quite stable. Crashed only twice when Photoshop was using GPU too. It also takes 13% of CPU - i7 2600K during work.

It is too early, but judging from charts on dwarfpool, my personal hashrate is almost the same as it was before with rival miner.

P.S. We should have started own thread for this.

So I downloaded windows version of that miner that Wolf linked the other day but for the life of me I'm not sure how to get it to run in widows? I have 6x 280x's on a rig that I want to get running and do some comparisons to Claymore on power draw and hash rate. Then again I'm no expert with command line stuff, I'm getting better but still not sure how to run that miner.

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: Drhiggins on January 19, 2016, 10:42:07 PM

So it looks like the defacto ban period set in the daemon is 24 hours.

Yes that's right. After 24 hours the ban will lift, and connections are again allowed with that peer. This does not mean that necessarily a connection will be made with that peer. But if another connection is made and the peer still misbehaves, it will be banned again. This repeats indefinitely. So you will get, potentially, a small amount of pestering every 24 hours from a misbehaving node until it gets re-banned.

I think the manual ban command allows you to set a different timeout, but that shouldn't normally be necessary.

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: Hueristic on January 19, 2016, 11:55:28 PM

Hmmm, is there a way to get a list of all banned nodes? Could it have anything to do with the lowered hashrate.

The bans are local, something your own node does to protect itself. You can see your own local list with "bans". There is no global list.

Hueristic

legendary

Activity: 3836

Merit: 4969

Doomed to see the future and unable to prevent it

Hmmm, is there a way to get a list of all banned nodes? Could it have anything to do with the lowered hashrate.

Drhiggins

sr. member

Activity: 306

Merit: 251

So it looks like the defacto ban period set in the daemon is 24 hours.

oblox

legendary

Activity: 1442

Merit: 1018

Quote from: Drhiggins on January 19, 2016, 10:18:20 PM

Quote from: luigi1111 on January 19, 2016, 10:12:50 PM

Quote from: Drhiggins on January 19, 2016, 10:10:33 PM

So can someone tell me how the daemon is (-8days) ahead]

I think this daemons data may be corrupted. I have this running on an old spindle HHD (slower than hell) I have an SSD on the way and I think I'll just re-sync from scratch once installed but any Ideas why this message shows up? My other open daemon is running fine with no errors on another machine.

2016-Jan-19 20:12:33.976115 [P2P6][31.6.70.206:34959 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:33.976115 [P2P2][45.63.14.235:48551 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:45.021900 [P2P7][107.170.19.65:42753 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:52.769040 [P2P3][217.118.66.161:41543 INC]Sync data returned u
nknown top block: 919725 -> 913363 [6362 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:53.972043 [P2P7][107.170.19.65:42756 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:59.248541 [P2P3][107.170.19.65:42758 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started

You seem to be connected to a few naughty peers. I'd suggest spanking them. (107.170.19.65:42753 and below, note the others say "SYNCHRONIZED OK")

Ok so just block them through the the daemon with the ban feature I assume?

Noticed the same thing on a Win7 9.1 build today. These are the peers I have banned:

Drhiggins

sr. member

Activity: 306

Merit: 251

Quote from: smooth on January 19, 2016, 10:20:03 PM

Quote from: Drhiggins on January 19, 2016, 10:18:20 PM

Quote from: luigi1111 on January 19, 2016, 10:12:50 PM

Quote from: Drhiggins on January 19, 2016, 10:10:33 PM

So can someone tell me how the daemon is (-8days) ahead]

I think this daemons data may be corrupted. I have this running on an old spindle HHD (slower than hell) I have an SSD on the way and I think I'll just re-sync from scratch once installed but any Ideas why this message shows up? My other open daemon is running fine with no errors on another machine.

2016-Jan-19 20:12:33.976115 [P2P6][31.6.70.206:34959 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:33.976115 [P2P2][45.63.14.235:48551 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:45.021900 [P2P7][107.170.19.65:42753 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:52.769040 [P2P3][217.118.66.161:41543 INC]Sync data returned u
nknown top block: 919725 -> 913363 [6362 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:53.972043 [P2P7][107.170.19.65:42756 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:59.248541 [P2P3][107.170.19.65:42758 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started

You seem to be connected to a few naughty peers. I'd suggest spanking them. (107.170.19.65:42753 and below, note the others say "SYNCHRONIZED OK")

Ok so just block them through the the daemon with the ban feature I assume?

Are you sure they aren't banned already? It should happen automatically but I'm not sure that every possible sort of bad peer behavior does get blocked. If it is the case that they escape the ban then yes you can ban them manually.

Ok cool, well its good to know someone is watching all these I.P.'s There are some shady motherF$#@'s out there. Will do and I'll keep an eye on my daemon's running. Thanks for the help.

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: Drhiggins on January 19, 2016, 10:18:20 PM

Quote from: luigi1111 on January 19, 2016, 10:12:50 PM

Quote from: Drhiggins on January 19, 2016, 10:10:33 PM

So can someone tell me how the daemon is (-8days) ahead]

I think this daemons data may be corrupted. I have this running on an old spindle HHD (slower than hell) I have an SSD on the way and I think I'll just re-sync from scratch once installed but any Ideas why this message shows up? My other open daemon is running fine with no errors on another machine.

2016-Jan-19 20:12:33.976115 [P2P6][31.6.70.206:34959 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:33.976115 [P2P2][45.63.14.235:48551 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:45.021900 [P2P7][107.170.19.65:42753 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:52.769040 [P2P3][217.118.66.161:41543 INC]Sync data returned u
nknown top block: 919725 -> 913363 [6362 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:53.972043 [P2P7][107.170.19.65:42756 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:59.248541 [P2P3][107.170.19.65:42758 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started

You seem to be connected to a few naughty peers. I'd suggest spanking them. (107.170.19.65:42753 and below, note the others say "SYNCHRONIZED OK")

Ok so just block them through the the daemon with the ban feature I assume?

Are you sure they aren't banned already? It should happen automatically but I'm not sure that every possible sort of bad peer behavior does get blocked. If it is the case that they escape the ban then yes you can ban them manually.

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