|
From Btc-guild January 24, 2014
"There was a brief (3-4 minute) restart on all servers this afternoon in order to apply a critical patch to all stratum servers. This patch was required before the next difficulty update, which is likely to push the network difficulty beyond the 2.1 billion mark. The original stratum code was written with difficulty barely at the 1-million mark, and was not written to anticipate network difficulty exceeding the maximum size of a 32-bit variable."
Does something simialiar affect to p2pool, are all the versions of the bitcoind, leveldb or what ever depedencies ready for exceeding the maximum size of a 32-bit variable?
|
|
|
|
With 120Gh -> 0-3 shares a day, one orphan means 30-50% off.
No, it really doesn't. Everyone on p2pool has orphans. That's the nature of a block chain with a 30 second target, and is unavoidable. The p2pool shares are just used to divide up the bitcoins (as with other pools). As long as your orphan rate isn't higher than others', you get your fair share of the bitcoins. Yes there is variance. You might get an orphan, which makes your earnings go down in the short run. But others are also constantly getting orphans, which makes your earnings go up. With a little patiences it balances out and ends up in your favor. If you want immediate gratification, yes go ahead look elsewhere. If you want better returns over time, stay with p2pool. Sounds like youre washed your brain with this, open your eyes. |
|
|
|
I wonder why theres not 5000 miners on p2pool, is it because of people cant do the math. Or is it because the difficulty rises every ~10 days and time is money?
Or what do you think the reason might be?
Put that way, the answer has to be that people can't do math. Difficulty rising will reduce your earnings no matter how you mine. Unless of course you upgrade, which is what a lot of people end up doing (otherwise you won't me a miner for long), in which case again you are looking at a long term proposition to smooth out short term fluctuations in your earnings. Oh no, I realised that im getting allmost nothing on p2pool with 120gh nowdays - so I swiched to another pool, and now I can expect ~0.10 / 3 days. p2pool earnings with 120gh - its easy to notice that I was loosing day by day - little but still loosing 2014-01-19 17:13:20 0.00477012 BTC 2014-01-18 23:41:08 0.00479305 BTC 0.00477196 BTC 2014-01-17 06:18:47 0.01245325 BTC 2014-01-16 12:55:33 0.02006893 BTC 2014-01-15 11:45:28 0.01547546 BTC 0.0154557 BTC 0.01545295 BTC 2014-01-14 19:14:27 0.0041062 BTC 0.00410603 BTC On a normal pool it looks like this: 2014-01-20 12:08:01 0.04748497 BTC 2014-01-21 12:53:48 0.043208 BTC 2014-01-22 18:32:54 0.04321408 BTC So.. You MUST be vigilant with P2Pool, you aren't going to see the real profit from it until you have run it for at least 30 days. Note, this is from the following post: https://bitcointalk.org/index.php?topic=153232.0Patience If you are beginning on P2Pool you should expect irregular payments which can be frustrating. P2Pool is attracting more and more hashrate (from a low 200GH/s in March 2013 to a high 1.4TH/s in July 2013) but its variance is still somewhat high. First you should be prepared to mine for a couple of days to check that your configuration is good enough (study the efficiency value displayed by your node's main page). If your efficiency is near or above 100%, you can expect more income on P2Pool than in most traditional pools. The only question for you is how long you are willing to wait for variance becoming negligible. On P2Pool with the current hashrate, you should expect to be in the 80-120% luck range in a couple of weeks. I've never seen P2Pool get <80% luck during more than a month. In 6 months I've seen both near 120% luck in a month and near 80% luck in another. As I wrote elsewhere: add your hashrate by joining us and variance will go down! Note: P2Pool's payment method is PPLNS, with its current configuration you have to wait approximately 72 hours (on Bitcoin, this changes with other coins) to get the first "full" payments. These payments are mined coins (unlike most other pools), they are usable after 120 confirmations not 6 (but you get them as soon as the block is found which makes them usable as quickly as most other pools). Over half a year ive been mining on p2pool.... See the numbers, with 120Gh i get more from other pools thats it. What ever you say, it doesnt change the fact. Numbers wont lie. 500 Gh is the min gear one should have to be able to use p2pool now. Then should have atleast 8 shares a day. With 120Gh -> 0-3 shares a day, one orphan means 30-50% off. If that is your idea of good pool for 120Gh - dont tell me. |
|
|
|
You were not "losing day by day." What you had was the normal random fluctuations (and not even that much fluctuation). From the 14th to the 16th your earnings went up, then from the 16th to the 18th they went down. Overall you probably got about what you were supposed to. If you stick with it your earnings will continue to go up and down a little, and again you will get about what you are supposed to (which is more than other pools since you won't pay pool fees, and won't ever suffer losses from a pool being dishonest or getting hacked).
Its the same to me if theres a small fee, nothing comes for free but bad taste into mounth sometimes.
|
|
|
|
You were not "losing day by day." What you had was the normal random fluctuations (and not even that much fluctuation). From the 14th to the 16th your earnings went up, then from the 16th to the 18th they went down. Overall you probably got about what you were supposed to. If you stick with it your earnings will continue to go up and down a little, and again you will get about what you are supposed to (which is more than other pools since you won't pay pool fees, and won't ever suffer losses from a pool being dishonest or getting hacked). p2pool earnings with 120gh - its easy to notice that I was loosing day by day - little but still loosing
2014-01-19 17:13:20
0.00477012 BTC
2014-01-18 23:41:08
0.00479305 BTC
0.00477196 BTC
2014-01-17 06:18:47
0.01245325 BTC
2014-01-16 12:55:33
0.02006893 BTC
2014-01-15 11:45:28
0.01547546 BTC
0.0154557 BTC
0.01545295 BTC
2014-01-14 19:14:27
0.0041062 BTC
0.00410603 BTC
On a normal pool like this below :
2014-01-20 12:08:01
0.04748497 BTC
2014-01-21 12:53:48
0.043208 BTC
2014-01-22 18:32:54
0.04321408 BTC
So..
Yeah well, i like p2pool - but my 120gh isnt enough. Waiting for more power to be able to be back. |
|
|
|
I wonder why theres not 5000 miners on p2pool, is it because of people cant do the math. Or is it because the difficulty rises every ~10 days and time is money?
Or what do you think the reason might be?
Put that way, the answer has to be that people can't do math. Difficulty rising will reduce your earnings no matter how you mine. Unless of course you upgrade, which is what a lot of people end up doing (otherwise you won't me a miner for long), in which case again you are looking at a long term proposition to smooth out short term fluctuations in your earnings. Oh no, I realised that im getting allmost nothing on p2pool with 120gh nowdays - so I swiched to another pool, and now I can expect ~0.10 / 3 days. p2pool earnings with 120gh - its easy to notice that I was loosing day by day - little but still loosing 2014-01-19 17:13:20 0.00477012 BTC 2014-01-18 23:41:08 0.00479305 BTC 0.00477196 BTC 2014-01-17 06:18:47 0.01245325 BTC 2014-01-16 12:55:33 0.02006893 BTC 2014-01-15 11:45:28 0.01547546 BTC 0.0154557 BTC 0.01545295 BTC 2014-01-14 19:14:27 0.0041062 BTC 0.00410603 BTC On a normal pool it looks like this: 2014-01-20 12:08:01 0.04748497 BTC 2014-01-21 12:53:48 0.043208 BTC 2014-01-22 18:32:54 0.04321408 BTC So.. |
|
|
|
100 Gh isnt enough to be mining on a p2pool
Sigh, this same myth keeps getting repeated over and over again. 100 GH (or really any GH) is just fine with p2pool, as long as you realize that your normal $23/day mining revenue will fluctuate from day to day, not get paid every single day like clockwork. Over the course of a few weeks you will get close to what you expect. It just requires a bit of patience. The only real downside is that it takes some resources (computer, bandwidth, time) to run a p2pool node and maybe it isn't worth it for a $23/day operation. I wonder why theres not 5000 miners on p2pool, is it because of people cant do the math. Or is it because the difficulty rises every ~10 days and time is money? Or what do you think the reason might be? |
|
|
|
Looking at the graphs page on my P2Pool site I have some questions. I set one of my avy's to a different wallet ID. The avy does 106~107GH/s, I see the hashing graph which has -mean 106GH/s. The other bar graph below it that I guess is for the BTC's (it show's BTCs on my main wallet ID) is completely blank, there isn't even the slightest blue line. I wonder if this is a fault in the data making not appear normally or if it's something else? If you want to see what I mean have a look at my page. You can see the main wallet which shows the data under its hashing data, but the second one shows nothing under its hashing data. Thanks http://p2pool.smoothrunnings.ca:9332/ 100 Gh isnt enough to be mining on a p2pool, you wil get 0-2 shares a day, 500Gh is the reasonable minimium to be able to get ~10 shares a day, it can be several days witout a share on a 100Gh. If you start up with a 100Gh, you wont be able to get the best out of your p2pool node - theres alot settings you can tune - but not without shares. Theres also that - when you have good luck and p2pool have bad luck, and when p2pool have good luck and you have bad situation, not to mention that if you get your only share just when a block is found -> its orphan then  Share difficulty is skyhigh, If you want to make coins with 100gh theres other pools that pay for every share + you get namecoins aswell for your efforts  If its 0.03 you get from a normal pool / day with 100Gh, let me say one day without a share on a p2pool 6 blocks found, next day 1 orphan 1 good -blocks found 2, third day 3 shares no blocks. On a normal pool its 0.09 on p2pool its ~0.01, is 100Gh enough? If the third day end up with 5 blocks it could be ~ 0.04- 0.07 for those three days. |
|
|
|
Would a high performance p2pool be more limited by cpu or disk I/O?
P2pool is limited to only use 1 core, celeron does as good job as xeon, because its written in Python... Ssd helps bitcoind alot, and bitcoind uses all cores available - theres no issues with it. Theres small performance gain if bitcoind is on ramdisk vs ssd- not worth it. |
|
|
|
Has anyone any idea how to run p2pool with pp ? http://www.parallelpython.com/I think it could help boost performance, if its running on all cores instead of normal python is on one core only. This would be the case with intel atom 330 prosessors for example ( 4 threads - 2 cores) 4x1600 mhz. Installed p2pool on such a thing but there is peaks with 100% sometimes on one core, allthough the system is compiled with minimal gentoo -march=native... Tried that jython 2.7 but had problems with twisted web with it.. Have to run it on i7 4.5ghz 32gb ram for now  |
|
|
|
The pool I ran for bitcoins averaged ~110-115% efficiency, but that was on a dedicated server (not a VPS) in Germany with 1gbit/1gbit switch (200mbps guaranteed but in practice could 99% of the time get 80MB/s + ). Averaged around 3-5% DOA for me and about 2-4% orphans.
When I initially tried to set up my home connection, I was getting around 0-1% DOA and 15-20% orphans. A few percentage of the orphan rate was from being in the US instead of France/Germany/Netherlands where most of these dedicated servers & VPS are running. Most was from my 768kbps upstream cap.
Later on I was able to set it up w/ 0-1% DOA and an orphan rate under 10% (though it still wasn't as good as just using German remote server, after share time got changed to 30s)... anyway, the deal is, just have bitcoind connect to 1 or 2 servers & also your p2pool node need only connect to a handful of servers... you just have to pick the right ones. I have no clue what those are anymore. (ie, change outgoing connections to 0 and handpick the servers to connect to)
ed: i think you can find a VPS for a couple of bucks to run a bitcoind relay on
That's a decent idea about running a VPS for a bitcoind relay. I could stick p2pool on there too while I'm at it. It still doesn't solve the high share difficulty problem though. M Youre right on this, and because sharedif is so high - there will be less and less new users. Its impossible to try to get the best out of p2pool with lets say 120gh when you get from 0 to 3 shares a day. Sad but this is it. Or is this shit. |
|
|
|
I hope Eligius is up soon, hate to read nonsense writings. Hate it so much that soon going to choose another pool.  Edit: There should be a list of things thats going on, what has done and how are things expected to go. I dont know how others find this situation explained on a forum like this, but I dont find this fun. Reading this forum is like thorwing time to garbage, newer ever going to do this again - wait and read nonsense. |
|
|
|
I'm running a node for testing right now in a 2.6 Ghz Core i7 16GB RAM PCI-e SSD...and Ubuntu Server 12.04
My question is, I'm getting periodic spikes in both the getblocktemploate latency (upwards of 30s for a spike) and DOAs reported up from 4% to almost 30% then it calms down and I get a share. I have 17 shares 1 orphan 117% Efficiency. I've got about 1.4TH/s on the node. When this happens the p2pool app pegs CPU and then slowly calms down. I've tuned bitcoind for max block size etc. from the tuning guide as well. I have 6 out and 8 in p2pool connections.
I've also noticed my bitcoind has 98 connections and some of them have huge Recv-Q and Send-Q numbers... I'm on a 50 down 5 up cable modem so the connection shouldn't be the problem. I'm thinking those "dead" connections to bitcoind aren't doing me any good.
My payouts are going up for each share found, but the Spikes in DOA don't seem right. Any ideas what could be happening?
I think that with your 5mbit upload the most you can handle is 10-15 bitcoind connections, more if you choose them carefully. Those random connections eats your upload bandwith - because theres allways someone downloading blockchain.. |
|
|
|
You should probably stop feeding the troll. He'll never use p2pool long enough or with any objectivity. He just knows he doesn't like it without having a valid reason.
I ran p2pool for 4 months when I was mining with GPUs. It worked fine then. Heck, I had a public node with other miners using it 24/7. But, that was 6 months ago. I stopped using p2pool because it couldn't cope with my shiny new ASICMiner Blades. I left hoping things would be fixed and I'd be back. Time has moved on, p2pool has been left back in August 2013 with all sorts of issues, which the devs won't or can't fix. They do the "it's someone else's fault" thing that every other software developer defaults to when they don't have a clue. I still love the idea of p2pool, but its SO FUCKING FRUSTRATING that it isn't being fixed so it WORKS. How can it be expected to become more commonly used when it's so frigging wobbly and fussy? It's no wonder so many people flock to BTCGuild and Ghash.io - they both just work, no messing, no fuss. I stink that p2pool works like a charm, the only bad thing in it is share difficulty, if it could be divided to 1/10 from what it is now.... There would be alot of happy people smiling here and there ?  |
|
|
|
|
lucky lucky, it newer ends.
|
|
|
|
|
Works great on Gentoo, how about avx and v.17?
|
|
|
|
A (somewhat) antisocial solution would be a fake bitcoind node that generates empty blocks.
You don't need a "fake" bitcoind to make empty blocks. It's a simple setting in bitcoin.conf. Though if you don't have the bandwidth to propagate proper blocks, you'd be better off mining with a pool that can. Since december 21 only 1 dead share, zero orphans . Nothing to do with network ! Cpu load 100% all the time because mining XPM. Think again. |
|
|
|
|
how lucky im, ive been posting shares over a week, 0 d 0 o. finnish pool, ive got enough with the noise i took those bflscs outside, dead is rising now.
If i only know how to share namecoins.
|
|
|
|
|
To start p2pool as daemon, not sure if its explained somewhere but didnt found it.
One can start it like this: nohup python run_p2pool.py ....... > /dev/null 2>&1 &
So then you can restart X or even logout without killing p2pool.
> /dev/null 2>&1 & at the end makes nohup not to log anything and the & makes it run as a daemon
If you want to read that useless log it can be done - tail -f /p2pool/data/bitcoin/log
|
|
|
|
I got error when I found a share today: 2013-12-12 01:01:36.423805 P2Pool: 17345 shares in chain (17349 verified/17349 total) Peers: 31 (21 incoming)
2013-12-12 01:01:36.423930 Local: 2356GH/s in last 10.0 minutes Local dead on arrival: ~1.4% (0-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:36.423978 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-12-12 01:01:36.424015 Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:39.436918 P2Pool: 17345 shares in chain (17349 verified/17349 total) Peers: 31 (21 incoming)
2013-12-12 01:01:39.437093 Local: 2357GH/s in last 10.0 minutes Local dead on arrival: ~1.3% (0-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:39.437174 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-12-12 01:01:39.437264 Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:41.593547 GOT SHARE! Jupiter 23877a5a prev a9d32777 age 80.86s
2013-12-12 01:01:41.622728 > Error while processing Event callbacks:
2013-12-12 01:01:41.622811 > Traceback (most recent call last):
2013-12-12 01:01:41.622846 > File "/home/user/p2pool/p2pool/bitcoin/worker_interface.py", line 136, in <lambda>
2013-12-12 01:01:41.622882 > lambda header, user, coinbase_nonce: handler(header, user, pack.IntType(self._my_bits).pack(nonce) + coinbase_nonce),
2013-12-12 01:01:41.622915 > File "/home/user/p2pool/p2pool/work.py", line 403, in got_response
2013-12-12 01:01:41.622981 > self.node.set_best_share()
2013-12-12 01:01:41.623012 > File "/home/user/p2pool/p2pool/node.py", line 297, in set_best_share
2013-12-12 01:01:41.623043 > self.best_share_var.set(best)
2013-12-12 01:01:41.623073 > File "/home/user/p2pool/p2pool/util/variable.py", line 74, in set
2013-12-12 01:01:41.623103 > self.changed.happened(value)
2013-12-12 01:01:41.623133 > --- <exception caught here> ---
2013-12-12 01:01:41.623162 > File "/home/user/p2pool/p2pool/util/variable.py", line 42, in happened
2013-12-12 01:01:41.623192 > func(*event)
2013-12-12 01:01:41.623232 > File "/home/user/p2pool/p2pool/node.py", line 96, in broadcast_share
2013-12-12 01:01:41.623271 > peer.sendShares([share for share in shares if share.peer_addr != peer.addr], self.node.tracker, self.node.known_txs_var.valu
e, include_txs_with=[share_hash])
2013-12-12 01:01:41.623322 > File "/home/user/p2pool/p2pool/p2p.py", line 291, in sendShares
2013-12-12 01:01:41.623355 > assert tx_hash in known_txs, 'tried to broadcast share without knowing all its new transactions'
2013-12-12 01:01:41.623394 > exceptions.AssertionError: tried to broadcast share without knowing all its new transactions
2013-12-12 01:01:41.660075 New work for worker! Difficulty: 599.266435 Share difficulty: 1076527.143944 Total block value: 25.061445 BTC including 243 transa
ctions
2013-12-12 01:01:41.691285 New work for worker! Difficulty: 200.000000 Share difficulty: 1076527.143944 Total block value: 25.061445 BTC including 243 transa
ctions
2013-12-12 01:01:42.448631 P2Pool: 17346 shares in chain (17350 verified/17350 total) Peers: 31 (21 incoming)
2013-12-12 01:01:42.448763 Local: 2360GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:42.448800 Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~125.8% (25-126%) Current payout: 0.0080 BTC
2013-12-12 01:01:42.448837 Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:45.462377 P2Pool: 17346 shares in chain (17350 verified/17350 total) Peers: 31 (21 incoming)
2013-12-12 01:01:45.462555 Local: 2369GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:45.462638 Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~125.8% (25-126%) Current payout: 0.0080 BTC Then found another share and it was fine: 2013-12-12 01:04:22.130684 Local: 2329GH/s in last 10.0 minutes Local dead on arrival: ~1.6% (1-3%) Expected time to share: 30.1 minutes
2013-12-12 01:04:22.130717 Shares: 1 (1 orphan, 0 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-100%) Current payout: 0.0000 BTC
2013-12-12 01:04:22.130754 Pool: 115TH/s Stale rate: 20.5% Expected time to block: 9.4 hours
2013-12-12 01:04:22.335429 New work for worker! Difficulty: 691.171186 Share difficulty: 1241624.893775 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:22.377099 New work for worker! Difficulty: 200.000000 Share difficulty: 1241624.893775 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:25.143566 P2Pool: 17351 shares in chain (17355 verified/17355 total) Peers: 31 (21 incoming)
2013-12-12 01:04:25.143681 Local: 2325GH/s in last 10.0 minutes Local dead on arrival: ~1.7% (1-3%) Expected time to share: 30.2 minutes
2013-12-12 01:04:25.143714 Shares: 1 (1 orphan, 0 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-100%) Current payout: 0.0000 BTC
2013-12-12 01:04:25.143750 Pool: 120TH/s Stale rate: 20.5% Expected time to block: 9.0 hours
2013-12-12 01:04:27.234256 GOT SHARE! Jupiter3 89d9ea47 prev faed7137 age 4.87s
2013-12-12 01:04:27.349609 New work for worker! Difficulty: 614.131984 Share difficulty: 1103231.495636 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:27.391143 New work for worker! Difficulty: 200.000000 Share difficulty: 1103231.495636 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:28.156049 P2Pool: 17352 shares in chain (17356 verified/17356 total) Peers: 31 (21 incoming)
2013-12-12 01:04:28.156144 Local: 2327GH/s in last 10.0 minutes Local dead on arrival: ~1.7% (1-3%) Expected time to share: 30.2 minutes
2013-12-12 01:04:28.156176 Shares: 2 (1 orphan, 0 dead) Stale rate: ~50.0% (9-91%) Efficiency: ~63.3% (11-115%) Current payout: 0.0114 BTC
2013-12-12 01:04:28.156213 Pool: 121TH/s Stale rate: 21.1% Expected time to block: 8.9 hours
2013-12-12 01:04:30.834454 Peer sent entire transaction 90e0bb504ac630d2e08ddf489731341236812c22179e74fedde6a6b5d96282ad that was already received
2013-12-12 01:04:31.166570 P2Pool: 17352 shares in chain (17356 verified/17356 total) Peers: 31 (21 incoming)
Also, adjusting share diff works for my node, just fine. p2pool gives work to my workers and reporting share time: 2013-12-12 01:06:00.703104 Got new merged mining work!
2013-12-12 01:06:00.740053 New work for worker! Difficulty: 570.368318 Share difficulty: 1024614.009517 Total block value: 25.021775 BTC including 157 transactions
2013-12-12 01:06:00.767854 New work for worker! Difficulty: 200.000000 Share difficulty: 1024614.009517 Total block value: 25.021775 BTC including 157 transactions
2013-12-12 01:06:01.621688 P2Pool: 17351 shares in chain (17355 verified/17355 total) Peers: 31 (21 incoming)
2013-12-12 01:06:01.621786 Local: 2352GH/s in last 10.0 minutes Local dead on arrival: ~1.8% (1-3%) Expected time to share: 30.4 minutes But on webpage it says: Pool rate: 121TH/s (21% DOA+orphan) Share difficulty: 487000
Node uptime: 4.0 days Peers: 10 out, 21 in
Local rate: 2.41TH/s (1.5% DOA) Expected time to share: 14.5 minutes So we have different share diff and ETA for workers in p2pool log, and different share diff nad ETA on p2pool front page. But adjusting itself works very good, I have Expected time to share in p2pool log always auto-adjusted to ~30 minutes. EDIT: Both shares I found has been orphaned couple of minutes later!!! :O With series of errors. Whole log here: http://lenny.dnsd.me/p2pool.logShares: 2 (2 orphan, 0 dead) Stale rate: ~100.0% (34-100%) Efficiency: ~0.0% (0-80%) Current payout: 0.0000 BTC Can someone explain how it happened? I did have same thing going with my node, what i did was rebuild everything needed with p2pool with useflag soap enabled, havent seen that error since. Not sure if it was that, but that error doesnt show up anymore.. |
|
|
|
|
Show Posts
