Bitcoin Forum
June 16, 2024, 08:10:41 PM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: « 1 ... 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 [65] 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 »
  Print  
Author Topic: [ANN] Elacoin | Released | Fair Elastic Scrypt Mining | No Premine  (Read 133887 times)
arjay45
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
May 14, 2013, 09:20:14 AM
 #1281

The node 96.126.118.229 is owned by me. I have it automatically restarting when it segfaults -- which it does every few minutes. But well, what can you do. If there's a fix in the morning I'll pull it in and recompile (about 8 hrs from now).

-addnode=96.126.118.229

I have lots of bandwidth, and should have low latency to US/Canada. The server is in Dallas, TX.

BTW - Which distribution are you running?  Debian 6.0 here, segfaults definitely occurring.  The comments in the code for CBigNum suggest that older versions of Ubuntu will seg fault if difficulty is set incorrectly.  Apparently not restricted to Ubuntu.  So while it's happening as the result of an external library (certain versions of OpenSSL), there's already comments in the code saying it runs the risk of segfaulting if set incorrectly.

Ubuntu 12.04 LTS Server. Other people are saying litecoind doesn't segfault for them (and hasn't in months) yet elacoind is segfaulting. So I don't think it's my libraries. But I'm sleepy. Hopefully OP finds the bug and fixes it.
Milkshake (OP)
Member
**
Offline Offline

Activity: 98
Merit: 10


Milkshake


View Profile
May 14, 2013, 09:21:01 AM
 #1282

Using these two nodes - hope they are right?

addnode=199.204.38.220
addnode=96.126.118.229

What is the size of the blockchain?

The one starting with 199 is mine, the one starting with 96 belongs to arjay45.  Between the two of them, you'll probably connect to one or the other between crashes of elacoind.  Both of us are seeing elacoind crash (segfault) every few minutes.
Not sure how the segfault is happening, our PoW limit values are the same as LTC.

Originally the value was high, however that has being fixed.

TradeFortress has left me negative trust and has provided no proof to substantiate his claim. He has done this to discredit me as I am investigating him.
Magic8Ball
Legendary
*
Offline Offline

Activity: 1050
Merit: 1000


View Profile
May 14, 2013, 09:21:43 AM
 #1283

Using these two nodes - hope they are right?

addnode=199.204.38.220
addnode=96.126.118.229

What is the size of the blockchain?

The one starting with 199 is mine, the one starting with 96 belongs to arjay45.  Between the two of them, you'll probably connect to one or the other between crashes of elacoind.  Both of us are seeing elacoind crash (segfault) every few minutes.
Not sure how the segfault is happening, our PoW limit values are the same as LTC.

Originally the value was high, however that has being fixed.

Ha ha - so I am covered Tongue

Up till 4k blocks; not much left.
Cyberdyne
Hero Member
*****
Offline Offline

Activity: 630
Merit: 500



View Profile
May 14, 2013, 09:21:54 AM
 #1284

It does bring something new to the table...constant crashing.

Mt Gox Coin?

r3animation
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


View Profile
May 14, 2013, 09:22:02 AM
 #1285

The node 96.126.118.229 is owned by me. I have it automatically restarting when it segfaults -- which it does every few minutes. But well, what can you do. If there's a fix in the morning I'll pull it in and recompile (about 8 hrs from now).

-addnode=96.126.118.229

I have lots of bandwidth, and should have low latency to US/Canada. The server is in Dallas, TX.

BTW - Which distribution are you running?  Debian 6.0 here, segfaults definitely occurring.  The comments in the code for CBigNum suggest that older versions of Ubuntu will seg fault if difficulty is set incorrectly.  Apparently not restricted to Ubuntu.  So while it's happening as the result of an external library (certain versions of OpenSSL), there's already comments in the code saying it runs the risk of segfaulting if set incorrectly.

Ubuntu 12.04 LTS Server. Other people are saying litecoind doesn't segfault for them (and hasn't in months) yet elacoind is segfaulting. So I don't think it's my libraries. But I'm sleepy. Hopefully OP finds the bug and fixes it.

Same, I gave up and used the windows daemon.
BulletCoin
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
May 14, 2013, 09:22:31 AM
 #1286

So when it is the re-launch going to be?
Inform at least 3 days before.
JimmyFL
Member
**
Offline Offline

Activity: 84
Merit: 10



View Profile
May 14, 2013, 09:22:43 AM
 #1287

Using these two nodes - hope they are right?

addnode=199.204.38.220
addnode=96.126.118.229

What is the size of the blockchain?

The one starting with 199 is mine, the one starting with 96 belongs to arjay45.  Between the two of them, you'll probably connect to one or the other between crashes of elacoind.  Both of us are seeing elacoind crash (segfault) every few minutes.
Not sure how the segfault is happening, our PoW limit values are the same as LTC.

Originally the value was high, however that has being fixed.

Yes, there is a segfault problems... 2x 12.04 + 1x10.04 (ubuntu Wink) and segfaults are happening like every 10min...
pjheinz
Member
**
Offline Offline

Activity: 84
Merit: 10


MEC - MFLtNSHN6GSxxP3VL8jmL786tVa9yfRS4p


View Profile
May 14, 2013, 09:23:16 AM
 #1288

wait im mining but do i have to make an address none of the cmd promt help commands work
..how do i get my address and ect..

♠♠♠https://btce-bot.me♠♠♠ Most popular BTC-E bot made! ♠♠♠ Free Trial Available!! ♠♠♠
MrWizard
Sr. Member
****
Offline Offline

Activity: 252
Merit: 250


View Profile
May 14, 2013, 09:23:42 AM
 #1289

Using these two nodes - hope they are right?

addnode=199.204.38.220
addnode=96.126.118.229

What is the size of the blockchain?

The one starting with 199 is mine, the one starting with 96 belongs to arjay45.  Between the two of them, you'll probably connect to one or the other between crashes of elacoind.  Both of us are seeing elacoind crash (segfault) every few minutes.
Not sure how the segfault is happening, our PoW limit values are the same as LTC.

Originally the value was high, however that has being fixed.
Been running a fresh install of lubuntu in a virtual machine since the launch.  Not a single segfault.

"I walked into the room dripping in Bitcoins.  Yea dripping in Bitcoins."
(BTC) 168DCCeGmDy3xTWRimLVhvKtK3yEWbpsSg     (LTC) LbYS8VFqFSU7B9bfaHD11seQMtrtYEKpLe
(BBQ) bNVZErvwLzpEG7H3kt1fycWspzRQB1MJzL
r3animation
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


View Profile
May 14, 2013, 09:24:22 AM
 #1290

Using these two nodes - hope they are right?

addnode=199.204.38.220
addnode=96.126.118.229

What is the size of the blockchain?

The one starting with 199 is mine, the one starting with 96 belongs to arjay45.  Between the two of them, you'll probably connect to one or the other between crashes of elacoind.  Both of us are seeing elacoind crash (segfault) every few minutes.
Not sure how the segfault is happening, our PoW limit values are the same as LTC.

Originally the value was high, however that has being fixed.
Been running a fresh install of lubuntu in a virtual machine since the launch.  Not a single segfault.

What version?
MrWizard
Sr. Member
****
Offline Offline

Activity: 252
Merit: 250


View Profile
May 14, 2013, 09:24:56 AM
 #1291

Using these two nodes - hope they are right?

addnode=199.204.38.220
addnode=96.126.118.229

What is the size of the blockchain?

The one starting with 199 is mine, the one starting with 96 belongs to arjay45.  Between the two of them, you'll probably connect to one or the other between crashes of elacoind.  Both of us are seeing elacoind crash (segfault) every few minutes.
Not sure how the segfault is happening, our PoW limit values are the same as LTC.

Originally the value was high, however that has being fixed.
Been running a fresh install of lubuntu in a virtual machine since the launch.  Not a single segfault.


What version?

13.04 32-bit.

"I walked into the room dripping in Bitcoins.  Yea dripping in Bitcoins."
(BTC) 168DCCeGmDy3xTWRimLVhvKtK3yEWbpsSg     (LTC) LbYS8VFqFSU7B9bfaHD11seQMtrtYEKpLe
(BBQ) bNVZErvwLzpEG7H3kt1fycWspzRQB1MJzL
jt7382
Full Member
***
Offline Offline

Activity: 203
Merit: 100


View Profile
May 14, 2013, 09:25:00 AM
 #1292

What do I need to do if getinfo shows my blockcount as 0?
joee
Member
**
Offline Offline

Activity: 69
Merit: 10


View Profile
May 14, 2013, 09:26:10 AM
 #1293

What do I need to do if getinfo shows my blockcount as 0?

does it show connections?
arjay45
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
May 14, 2013, 09:26:14 AM
 #1294

Using these two nodes - hope they are right?

addnode=199.204.38.220
addnode=96.126.118.229

What is the size of the blockchain?

The one starting with 199 is mine, the one starting with 96 belongs to arjay45.  Between the two of them, you'll probably connect to one or the other between crashes of elacoind.  Both of us are seeing elacoind crash (segfault) every few minutes.
Not sure how the segfault is happening, our PoW limit values are the same as LTC.

Originally the value was high, however that has being fixed.
Been running a fresh install of lubuntu in a virtual machine since the launch.  Not a single segfault.


What version?

13.04 32-bit.

Ah I'm 64-bit, I wonder if that's the issue.
KrLos
Hero Member
*****
Offline Offline

Activity: 768
Merit: 1000



View Profile
May 14, 2013, 09:27:43 AM
 #1295

i'm done... i didn't sleep for this... and was a waste of my time... good day?
jt7382
Full Member
***
Offline Offline

Activity: 203
Merit: 100


View Profile
May 14, 2013, 09:28:20 AM
 #1296

What do I need to do if getinfo shows my blockcount as 0?

does it show connections?

I'm seeing 1 or 2 connections. Using the nodes here.

addnode=199.204.38.220
addnode=96.126.118.229

and the peer list that was on dropbox earlier.
WindMaster
Sr. Member
****
Offline Offline

Activity: 347
Merit: 250


View Profile
May 14, 2013, 09:29:09 AM
 #1297

13.04 32-bit.

Ah I'm 64-bit, I wonder if that's the issue.

64-bit here as well, with segfault issue, core dumped and traced to CBigNum's overloaded >> function.  I didn't compile in line number debugging info so I haven't narrowed it down further than just backtracing the stack and looking what function it happens in.
AlternativeCypt
Newbie
*
Offline Offline

Activity: 28
Merit: 0



View Profile
May 14, 2013, 09:29:37 AM
 #1298

Silly pump scheme going wrong
ictin
Full Member
***
Offline Offline

Activity: 258
Merit: 100


Look ARROUND!


View Profile
May 14, 2013, 09:29:41 AM
 #1299

can someone post the whole block chain? I have some problem downloading it. I am at block 857 and is working like with 1 block/s

JimmyFL
Member
**
Offline Offline

Activity: 84
Merit: 10



View Profile
May 14, 2013, 09:29:48 AM
 #1300

Using these two nodes - hope they are right?

addnode=199.204.38.220
addnode=96.126.118.229

What is the size of the blockchain?

The one starting with 199 is mine, the one starting with 96 belongs to arjay45.  Between the two of them, you'll probably connect to one or the other between crashes of elacoind.  Both of us are seeing elacoind crash (segfault) every few minutes.
Not sure how the segfault is happening, our PoW limit values are the same as LTC.

Originally the value was high, however that has being fixed.
Been running a fresh install of lubuntu in a virtual machine since the launch.  Not a single segfault.


What version?

13.04 32-bit.

Ah I'm 64-bit, I wonder if that's the issue.

Maybe, my computers are also 64b
Pages: « 1 ... 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 [65] 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!