Some kind of DOS attack?
Got three "GOT INCOMPLETE BLOCK FROM PEER" messages and then p2pool stopped. Peer IP is 192.203.228.65
Now just got another one.
Is this you by any chance? 2013-04-29 16:39:08.307039 Incoming connection to peer 74.100.64.248:56708 established. p2pool version: 1100 '11.2' 2013-04-29 16:39:08.472251 Sending 1 shares to 74.100.64.248:56708 2013-04-29 16:39:08.474522 Lost peer 74.100.64.248:56708 - Connection was closed cleanly. 2013-04-29 16:39:08.475089 > in handle_share_hashes: 2013-04-29 16:39:08.475163 > Traceback (most recent call last): 2013-04-29 16:39:08.475245 > Failure: twisted.internet.error.ConnectionDone: Connection was closed cleanly. That particular peer is having a lot of trouble: $ grep 'Lost peer' log | awk '{print $5}' | sed -e 's/:.*//' | sort | uniq -c | sort -nr 168 74.100.64.248 5 123.159.6.63 2 216.153.20.29 .. nothing else more than one.. The #2 on the list is doing things like this: 2013-04-29 08:50:54.110763 Connection timed out, disconnecting from 123.159.6.63:54137 2013-04-29 08:50:54.111417 Lost peer 123.159.6.63:54137 - 2013-04-29 08:50:54.111508 Connection was aborted locally, using 2013-04-29 08:50:54.111569 L{twisted.internet.interfaces.ITCPTransport.abortConnection}. Are either of those two yours? No. But see PM.
|
|
|
Ref earlier, this is my command line for LTC cgminer --scrypt -I 18 -d 0 --remove-disabled --thread-concurrency 22400 -u 1 -p 2 --url http://127.0.0.1:9327 --auto-fan This gives me around 500kh/s. I played with the clock speeds. Raising the mem clock didn't seem to help much with the hashrate. Above 1900, the screen started flickering but the hashrate had stayed about the same. Playing with the engine clock didn't seem to have the drastic effect claimed from the README but the 60% was out-of-range I think so it looks like I may have to lower the mem clock? I think I need to run some various options with that to get an idea of what's going on. Any other suggestions much appreciated.
|
|
|
First line of Wikipedia A Ponzi scheme is a fraudulent investment operation that pays returns to its investors from their own money or the money paid by subsequent investors, rather than from profit earned by the individual or organization running the operation.
Dude, don't try to use facts and logic to convince Charie; Charlie is immune to logic and facts just bounce right off him. If the item was paid for using a customer's money who is after in queue, then effectively, it is a ponzi scheme. Jut because there is snake oil in the equation does not mean that there is not fraud. Of course nobody would want to hear what a lawyer has to say. Moses was a man, all men are mortal, therefore all men are Moses? Just because there is fraud* doesn't not imply a Ponzi scheme. Do words mean anything to people anymore? *This is a generalization. I am not saying there is or is not in the case of BFL.
|
|
|
Here's a pretty big one. Unless I'm missing something.
So I have GPUs 0, 1 and 2. I want to use GPUs 1 and 2 for one instance of cgminer. GPU 0 is irrelevant for now.
Originally I had created a cgminer.conf using the write setting option with all 3 GPUs. No problem, I do
cgminer -d 1 -d 2 --remove-disabled -c cgminer.conf
Get an error "Too many values passed to set temp cutoff". "No problem" thinks I "I'll just go in an edit the three values per parameter down to two".
This appears to work. Except I notice that the fan is coming on early, my GPU temps are low compared to what I'm used to (shared fan) and my intensity on GPU 2 is bouncing all over the place. Clearly it looks like cgminer is reading the conf file, applying (or not applying) the first entry to GPU 0, the second to GPU 1 and leaving GPU 2 at the defaults.
In case I had just misunderstood the format of the conf file for what I wanted to do, once I set up the temperature cutoffs and intensity interactively, I wrote out the conf file.
Manual inspection reveals that the conf file contains three data values for each option, just like my original file. Sure enough, when I try to use it with the command line above, "Too many values passed to set temp cutoff".
It appears that there appears to be some crossed-up logic on how cgminer handles the config file between reads and writes when the --remove-disabled option is used.
For now, I guess I can just pass the options on the command line but thought you should know about this (apparent) bug.
|
|
|
Some kind of DOS attack?
Got three "GOT INCOMPLETE BLOCK FROM PEER" messages and then p2pool stopped. Peer IP is 192.203.228.65
Now just got another one.
|
|
|
Just as a note to my earlier issues with the GPUs on the 5970, when I got home, I powered off my system for 30 minutes and it looks like things are back. I guess the card got into a weird state when the power glitched.
Though what I'm thinking now is to put the old 6770 in with the 5970 and mine bitcoins there and put the 7950 in another system to mine litecoins
I guess that brings up that if there were any kind of way to put a "total card reset" into cgminer, it might be a good thing.
|
|
|
Replace money with product.
You can't as it's part of the definition. It's like saying stealing an apple is grand-theft-auto if you replace "Car" with "fruit".
|
|
|
First line of Wikipedia A Ponzi scheme is a fraudulent investment operation that pays returns to its investors from their own money or the money paid by subsequent investors, rather than from profit earned by the individual or organization running the operation.
|
|
|
(1) This does not mean BFL is not a ponzi scheme.
No, what means that it is not a Ponzi scheme is that it does not have the essential aspects of a Ponzi scheme even if it turns out they are commiting some other kind of fraud or incompetent or simply unlucky or whatever else you might want to ascribe their tardy delivery schedule to.
|
|
|
I can see the hacked-together thing. Everything is modular. Heck, even the major part of the engine is already there. Basically it's just some glue logic and a fancy interface to tie it all together. If you have note readers and receipt printers and the like lying around and libraries to drive them (where required), there's no reason that you couldn't cobble something that works together quickly. Of course, the 80/20 rule applies and there's a lot more to getting a shipping product out there than having a working prototype.
|
|
|
Use 2 gminers - one for 7xxx and 6xxx one for 5xxx
That's what I was doing but my 5970 is misbehaving as it shows up but does 0/0 on one or both GPUs and then reports sick, whatever. But it has randomly in the past too. I'm wondering if my 12V lines are not keeping up. It's a reflowed unit so possibly it is just not doing so well.
|
|
|
Just upgraded to ubuntu 13.04 - cgminer didn't like it:
cgminer/cgminer: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory
Current cgminer is built on 12.10 equivalent ... cgminer on 12.10 gave me lots of hardware errors at any decent level of intensity with Litecoin mining. Couldn't get it to work at all with 13.1 or 13.3 (hangs/crashes at the version screen, runs with -T but doesn't produce useful work). I am now on 12.08 which seemed to be mining OK for about two hours with both BTC and LTC at the same time but then we had a power blip and things aren't working right anymore (not sure if hardware or software, had to bail and go to bed). Max intensity I can mine LTC with on the 7950 is 18 at about 520kh/s. This post is more informational than looking for a solution to any problems (though any advice always appreciated). Details: OS: Win7 64bit Video: Sapphire 7950 (slot 0), HID 5970 (slot 1) CPU: AMD quad something.
|
|
|
For the same reason we normally deal with gold in ounces or grams instead of kilos.
Speak for yourself.
|
|
|
Here comes the panic again? Fun times! I'm going to buy a crazy amount of coins at $100 if it gets there.
not nearly as violent as the last time we bounced off $0.12. Nowhere near the volume. I doubt we'll even retest $0.12 Please don't tell me you actually jumped on the "Lets use millibitcoin and pretend this is sustainable" bandwagon? Well, going straight to micro would be a little cumbersome at this stage.
|
|
|
this one's a little more interesting:
While that's an interesting theory, here's a competing one: The bomb knocked the timer down. It does seem to be hanging directly over where the explosion happened. Another competing theory is that the two images are from two different races. I considered that but I did a search for yamamoto and 1:25:33 and that is apparently the time of a person from the Boston marathon, 2013. Not that I'm necessarily buying into it but...
|
|
|
Make sure something isn't eating up your bandwidth. I had trouble until I worked out that bitcoind was munching on mine (though I also turned off QOS which I haven't turned back on yet).
What have you done with Bitcoind? I just stopped it and restarted it. Whoever was connected must have connected to someone else. Either it hasn't been an issue since or when it has been, I haven't noticed it. Longer term, I need to turn my QOS back on and put p2pool up in the priorities and bitcoind down (probably down in the crawl category). Though it's possibly I'm going to upgrade my internet before then anyway.
|
|
|
I don't know much about the blockchain format but I wonder if there would be much mileage in merely indexing into the blockchain data and only storing the indexes in the database...
|
|
|
I'll have to have a closer look. I'm thinking I'd like something of this but more for event-based notification rather than aggregate/historical data.
There may be some way to improve the speed of the inserts too. I'll take a look at that.
I'll appreciate it. You may want to peruse the GitHub issue. Absolute first thing in my book would be to give up on sqlite. It's really not meant for this kind of abuse. Other than that though... Edit: That is to say, you could continue to offer sqlite as an option but I wouldn't waste any time trying to optimize it.
|
|
|
Another point to consider is that right now, any move Satoshi makes with his coins is likely to risk his/her/their anonymity.
|
|
|
He never moved a single coin. Not entirely true, he did some test transfer to Hal Finney, but that's it. He/they may be dead, or he/they may be planning to dump his/their stash at once. If not, why Satoshi did not sell coins till now? Why Satoshi did not buy anything with bitcoins? Is all in the blockchain. His coins never moved apart from some well documented transactions to early cooperators.
Maybe he accidentally formatted his hard-drive
|
|
|
|