Topic: [DVC]DevCoin - Official Thread - Moderated - page 133. (Read 1058956 times)

Did you reply to me on coinzen.org Flam?

- Nova

[Edit: PS coinzen is under massive spam attacks. You may have been caught up in that. There is a notice in the news at top right of main page to contact [email protected] should such a thing happen. ]

Add everything you do, and we'll work it out.


Hi Flam, no worries, I'll add you back to ongoing. Add yourself to http://www.devtome.com/doku.php?id=devcoin_human_resources as an earning administrator/factotum. Not sure why your coinzen account would have been deleted. Either Nova or tenthirtyone will be able to assist with that.

Hey Hi,

I replied to Nova but he didn' t replied to me.

On top of that my coinzen account was recently deleted for unknown reason so I'm asking here why since I have no reply in private.

I was always here as an admin and I'm willing to continue.

Regards,

Flam.

Do we add ourselves to the other areas we administer? There's 3 total for me but only 1 is on the list.

Sounds great Hunterbunter! Looking forward to the relaunch.

- Nova

Admins Remaining

The following people have replied to Nova regarding interest in continuing.

CryptoAddicto
Alyssa85
Papacrusher
emfox
Dinkleberg
K1773R
Fuzzybear
ranlo
Xeriandros
tenthirtyone
Markm

Of course, Nova and I are a part of that list too. Unthinkingbit is still supplying the accounting files, so will also remain on the list. Everyone who responded, please check http://www.devtome.com/doku.php?id=devcoin_human_resources and edit the first field with more information about your Role/s. Assume that you are the only one that knows what you're supposed to be doing, and that the community needs this information to work properly. Novacadian or I will figure out what to split it into, but we need your input. If you're interested in resurrecting Devcoins, remember that it will only succeed if you do your part.

Smeagol replied, and has asked to be replaced as bounty factotum and business administrator.

Anyone who is not on the list has been removed from the human resources page, as well as the ongoing file, with the assumption that they are no longer interested. Their roles have been replaced with an tag, for future reference. Anyone can apply for any of these roles at any time, and may send Novacadian a message if they are interested in taking one on. The ongoing file shares (including the cuts below) have dropped from 105 to 39 for round 46.

Nodes

I'm not sure of the status of full devcoin nodes. I was running one on Blisterpool but I had to shut that down. I am setting up another server and I will add a full devcoin client to that, and update the ip address in the human resources list when that's done. Anyone else who's either running a node, or can run one, please make a post here. I know it isn't much, but the nodes are subsidized 1 share for the time being. We had about 6 or so on the list, but noone has put any ip addresses on. We will subsidize up to 6 again, as long as the IP addresses are there, and if you've set one up, let us know and you can go on that subsidized list (up to 6).

Devtome

There is an emerging situation with devtome that we should talk about. Jasinlee was in charge of it but seems to have disappeared. About six months ago when there were rumours going around about him, I spoke to him and managed to get access to the hosting service for devtome. It still appears to be running normally, except we seem to have lost a lot of functionality. Currently, only existing writers can write, and no new writers can join, nor can passwords be reset. I can get a full backup of the site if we want to move it, but transferring the domain may be difficult without jasinlee responding. Is there anyone here who is willing to host and administer devtome, if we can manage to get it off its current hosting service? For us to move forward, we need devtome working properly again, and it needs the time and hosting investment from someone who wants to see us succeed.

Should the transfer work out successfully, and we get it running as it should be again, we will revisit the idea of revenue generation. At the moment it is using a bitcoin based advertising agency, and the income is paltry. We will have a discussion about changing it to make it adwords compliable, before implementing anything, and maybe even revisit the idea of updating the css to something more pleasant.

Ad Campaign

Cryptoaddicto has told me that he's ready to launch a huge ad campaign, and is very enthusiastic about it. We need to give him something to write about! For him to be able to continue we need to get devtome working as intended again. I've cut the campaign funding for now, as it has a large reserve, and will reinstate it when we're up and running again.

Faucet

Faucet has about 20m dvc (http://devcoinblockexplorer.info/address/1EpJKJbpeoXnYGtoB8F6re78FMAtvNRWMf), cutting funding from 8 shares to 1 for now until it needs more.

looks like your wallet is corrupted. As sidhujag says try to export your private keys and re-import them into a fresh setup.

export keys: dumpprivkey [your public key here]
import keys: importprivkey [label]

Try to dump your private key.. Save this key.. Delete entire data folder and resync wallet then import private key.

Anyone at all?

file wallet.dat has LSN 82/686, past end of log at 1/476
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
file wallet.dat has LSN 1/611, past end of log at 1/476
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
file wallet.dat has LSN 82/686, past end of log at 1/1103
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
DB_ENV->log_flush: LSN of 82/686 past current end-of-log of 1/1103
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 9
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 82/686, past end of log at 1/1730
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
DB_ENV->log_flush: LSN of 82/686 past current end-of-log of 1/2022
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 9
PANIC: fatal region error detected; run recovery
wallet.dat: write failed for page 12
wallet.dat: unable to flush page: 12
DB_ENV->log_flush: LSN of 82/2259 past current end-of-log of 1/2022
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 17
txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: fatal region error detected; run recovery



Moving 82.200.205.55:52333 to tried
receive version message: version 32501, blocks=179471, us=109.235.185.115:4331, them=82.200.205.55:52333, peer=82.200.205.55:52333
trying connection 81.130.202.35:52333 lastseen=12,7hrs
connection timeout
trying connection 89.100.143.21:52333 lastseen=12,8hrs
connection timeout
trying connection 178.38.161.227:52333 lastseen=12,7hrs
connection timeout
trying connection 123.2.246.157:52333 lastseen=13,3hrs
connection timeout
trying connection 5.76.164.15:52333 lastseen=19,4hrs
GetMyExternalIP() received [109.235.185.115] 109.235.185.115:0
GetMyExternalIP() returned 109.235.185.115
AddLocal(109.235.185.115:52333,4)
connection timeout
trying connection 99.41.184.131:52333 lastseen=12,6hrs
connection timeout
trying connection 89.100.143.21:52333 lastseen=12,8hrs
connection timeout
trying connection 180.251.214.16:52333 lastseen=13,4hrs
connection timeout
trying connection 39.47.104.149:52333 lastseen=13,4hrs
connection timeout
trying connection 83.86.176.147:52333 lastseen=13,4hrs
connected 83.86.176.147:52333
send version message: version 70001, blocks=179471, us=109.235.185.115:52333, them=83.86.176.147:52333, peer=83.86.176.147:52333
Added time data, samples 8, offset -1 (+0 minutes)
Moving 83.86.176.147:52333 to tried
receive version message: version 32501, blocks=179471, us=109.235.185.115:4341, them=83.86.176.147:52333, peer=83.86.176.147:52333
trying connection 89.100.143.21:52333 lastseen=12,8hrs
Added 2 addresses from 83.86.176.147: 12 tried, 5678 new
connection timeout
trying connection 180.251.214.16:52333 lastseen=13,4hrs
connection timeout
trying connection 116.118.81.3:52333 lastseen=107,8hrs
connection timeout
trying connection 123.2.246.157:52333 lastseen=13,3hrs
connection timeout
trying connection 178.38.161.227:52333 lastseen=12,7hrs
NotifyKeyStoreStatusChanged
connection timeout
trying connection 78.50.144.201:52333 lastseen=10,7hrs
connection timeout
trying connection 64.156.193.100:52333 lastseen=10,6hrs
connected 64.156.193.100:52333
send version message: version 70001, blocks=179471, us=109.235.185.115:52333, them=64.156.193.100:52333, peer=64.156.193.100:52333
socket closed
disconnecting node 64.156.193.100:52333
trying connection 82.19.10.61:52333 lastseen=12,6hrs
connection timeout
trying connection 180.252.137.161:52333 lastseen=90,1hrs

Hmm...we need more information.

In your devcoin folder you will see two files, db.log and debug.log. Open them up and paste the last 50-100 lines or so.

tried... doesnt help

Try the console app devcoind?

http://savepic.net/6572527.htm

Any way of fixing this? - over 4 million coins stuck (((

Hmm works here..  windows 7

Yes tried everything.... same error - something about runtime and an usual closing....

I use the same version ill try it in a bit... did you try to delete your data folder (keeping your wallet.dat) and rescanning the blockchain?

Anyone? Why does the wallet shut itself down when i try to move coins?

1.0.16 windows 32..... chain updates excellent and shows balance right and all transactions from 2 years back....