Jump to content

Recommended Posts

have error with orbitcoind on ubuntu 13.10 x64. First its running good and updating.During update its crash.

Having that log in db.log:

 

 

__db_meta_setup: /root/.Orbitcoin/blkindex.dat: unexpected file type or format
file blkindex.dat has LSN 11/4849786, past end of log at 11/4391289
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment

 

And that in debug.log:

 

Orbitcoin version v1.3.0.0-orb (2014-01-04 11:58:03 -0700)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 01/11/14 07:58:42
Default data directory /root/.Orbitcoin
Used data directory /root/.Orbitcoin
dbenv.open LogDir=/root/.Orbitcoin/database ErrorFile=/root/.Orbitcoin/db.log
Bound to [::]:15298
Bound to 0.0.0.0:15298
Loading block index...


************************
EXCEPTION: St13runtime_error       
CDB() : can't open database file blkindex.dat, error 22       
Orbitcoin in AppInit()       
 

What a problem may be there?

Thanks!

Share this post


Link to post
Share on other sites

Whats going on? http://orb.broken-arrow.pl pool 48 hours on that pool and now no one confirmed no one unconfirmed?

417065    already

 

So - pool paying or not? Actually, pool owner check what going on please

 

Pool Hash Rate 0.814 MH/s Pool Efficiency 99.03% Current Active Workers 6 Current Difficulty 0.02690828 Est. Next Difficulty 0.02553694 (Change in 1 Blocks) Est. Avg. Time per Round (Network) 32 seconds Est. Avg. Time per Round (Pool) 2 minutes 23 seconds Est. Shares this Round 1763 (done: 279638.57%) Next Network Block 417065    (Current: 417064)

Share this post


Link to post
Share on other sites

I can't help but wonder why the fix comes into effect so far out in the chain: block 41700

 

it's going to take rather some time to reach this block....not to mention that a relative small group of miners should now be able to pickup all the blocks before that.....

 

Or am I being to negative here?

Share this post


Link to post
Share on other sites

no your not being to negative the dev shows up once every 10 days or so. This coin would be really popular but only if it had an active dev. Yeah having the fix at 417 is ridiculous. 

Share this post


Link to post
Share on other sites

Unfortunately if you ran wallet 1.3.2 it was an unofficial fork

So maybe the best move for now will be to stop daemon, clean up database and run it once again to sync everything from the beginning. Right?

Share this post


Link to post
Share on other sites

So maybe the best move for now will be to stop daemon, clean up database and run it once again to sync everything from the beginning. Right?

 

my guess is it will take at least a week, if not longer, before we reach 417.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

Cryptocurrenytalk Logo

 

News, information, and discussions about cryptocurrencies, blockchains, technology, and events. Blockchaintalk is your source for advice on what to mine, technical details, new launch announcements, and advice from trusted members of the community. Cryptocurrencytalk is your source for everything crypto. We love discussing the world of cryptocurrencies.

 

   
×

Important Information

By using CRYPTOCURRENCYTALK.COM, you agree to our Terms of Use.