[XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 343.

informer

member

Activity: 238

Merit: 10

Quote from: Litoshi on August 24, 2014, 10:04:36 AM

Sell and Buy now available at Cryptsy

I'm afraid to move anymore right now. Not FUD'ing. I withdrew 1110 from bter 27 hours ago. I got an email saying it was on Crypti side from bter. After this all came back up I logged into bter and found it is still pending. I need my 1000 in my wallet so I can truly start forging. I want my coins on cryptsy, I've been using them for a while now. But until I can ensure that my withdrawals are completed, I'm not moving anything.

AWS EC2 Ubuntu 14.04

informer

bigvern

member

Activity: 100

Merit: 10

We are now on v0.1.5. Everything appears in order and the market has been turned back on.

BigVern

GreXX

hero member

Activity: 518

Merit: 500

As SyRenity said, Cryptsy has integrated 0.1.5 and is finalizing testing. For instance I have a test transaction from last night that still hasn't shown so we are waiting to make sure everything looks good before they give the go ahead. Poloniex and BTER are still integrating as far as I know. The important part is that we know the syncing and fork issues have been rectified and the new 0.1.5. nodes are syncing and forging as intended.

We will keep you updated on exchange integration. Once the exchanges have 0.1.5. loaded and working, we should be stable and be able to conduct some normal business for a while!

Litoshi

hero member

Activity: 700

Merit: 500

Member of the Crypti Foundation Board of Directors

Sell and Buy now available at Cryptsy

informer

member

Activity: 238

Merit: 10

Quote from: Wulfcastle on August 24, 2014, 09:51:09 AM

Quote from: SyRenity on August 24, 2014, 09:47:58 AM

Quote from: Wulfcastle on August 24, 2014, 09:32:07 AM

I still run forever start app.js, everytime it reboots and everything seems to be working perfectly in the back end, but when I got to the web wallet, nothing loads

Your node might made it into a black-list that we implemented in 0.1.4 (which bans for some period the suspected attacking node).

If you run on cloud, try to change the IP. Also make sure you erased the blockchain.

No it runs fine and everything loads when I complete the installation process, I can access the web wallet fine, it's only once I reboot my server that it stops functioning. After rebooting the server the web wallet simply doesn't display anymore

Wulf, If you restarted you're instance in AWS you need to start the node again. make sure you "cd 0.1.5" the "forever start app.js" then wait two minutes before trying wallet/node website.

AWS EC2 Ubuntu 14.04

informer

vytasz7

hero member

Activity: 561

Merit: 500

its not on hold any more

Wulfcastle

hero member

Activity: 546

Merit: 500

Quote from: SyRenity on August 24, 2014, 09:58:40 AM

Quote from: Wulfcastle on August 24, 2014, 09:51:09 AM

No it runs fine and everything loads when I complete the installation process, I can access the web wallet fine, it's only once I reboot my server that it stops functioning. After rebooting the server the web wallet simply doesn't display anymore

Probably because the "forever" is not running on boot.

Here is for example a guide how to make forever run as service (not tested by us):
http://www.linuxfunda.com/2013/12/15/how-to-install-and-configure-forever-as-a-service-to-run-node-js-application-ubuntu-12-04/

The problem is even when I run

Code:

forever start app.js

After booting the web wallet doesn't work anymore.

Litoshi

hero member

Activity: 700

Merit: 500

Member of the Crypti Foundation Board of Directors

Quote from: SyRenity on August 24, 2014, 09:56:39 AM

Quote from: Wulfcastle on August 24, 2014, 09:54:23 AM

Also, is BTER on 0.1.5? Yesterday my withdrawal came through and reflected in my balance, but today it's like the transaction was erased or didn't happen. Did you guys reset the blockchain or could it be that BTER was on the same fork as me yesterday leading to me receiving the withdrawal?

We still looking to hear from them and Poloniex, Cryptsy already on latest 0.1.5 (however we are still looking for their tests to complete).

Cryptsy is showing my balance, but trading is on hold while they "do maintainance"

vytasz7

hero member

Activity: 561

Merit: 500

i ve just goten xcr to cryptsi from bter

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: Wulfcastle on August 24, 2014, 09:51:09 AM

No it runs fine and everything loads when I complete the installation process, I can access the web wallet fine, it's only once I reboot my server that it stops functioning. After rebooting the server the web wallet simply doesn't display anymore

Probably because the "forever" is not running on boot.

Here is for example a guide how to make forever run as service (not tested by us):
http://www.linuxfunda.com/2013/12/15/how-to-install-and-configure-forever-as-a-service-to-run-node-js-application-ubuntu-12-04/

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: Wulfcastle on August 24, 2014, 09:54:23 AM

Also, is BTER on 0.1.5? Yesterday my withdrawal came through and reflected in my balance, but today it's like the transaction was erased or didn't happen. Did you guys reset the blockchain or could it be that BTER was on the same fork as me yesterday leading to me receiving the withdrawal?

We still looking to hear from them and Poloniex, Cryptsy already on latest 0.1.5 (however we are still looking for their tests to complete).

Once done, they will pass over transactions using the newly exposed getTransaction function (https://github.com/crypti/crypti-docs/blob/master/api.md#2-6-get-specific-transaction-details) to see if any transactions have to be re-transmitted.

Wulfcastle

hero member

Activity: 546

Merit: 500

SyRenity

Also, is BTER on 0.1.5? Yesterday my withdrawal came through and reflected in my balance, but today it's like the transaction was erased or didn't happen. Did you guys reset the blockchain or could it be that BTER was on the same fork as me yesterday leading to me receiving the withdrawal?

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: informer on August 24, 2014, 09:36:36 AM

That's what worked for me. Without having to rebuild. I just downloaded 0.1.5.zip extracted it, ed25519 gyp fix and presto.

Quote from: BrokenRam on August 24, 2014, 09:42:16 AM

Was getting "Can't forge, node not synchronized!" for over a minute, so just stopped the node. So might have sync'ed up given enough time... no patience on my part

With stop/edit/start took under 10secs to synchronized. Also deleted the blockchain.db before starting up the node again.

Thanks, I've updated the guide to stop/start just in case.

Wulfcastle

hero member

Activity: 546

Merit: 500

Quote from: SyRenity on August 24, 2014, 09:47:58 AM

Quote from: Wulfcastle on August 24, 2014, 09:32:07 AM

I still run forever start app.js, everytime it reboots and everything seems to be working perfectly in the back end, but when I got to the web wallet, nothing loads

Your node might made it into a black-list that we implemented in 0.1.4 (which bans for some period the suspected attacking node).

If you run on cloud, try to change the IP. Also make sure you erased the blockchain.

No it runs fine and everything loads when I complete the installation process, I can access the web wallet fine, it's only once I reboot my server that it stops functioning. After rebooting the server the web wallet simply doesn't display anymore

elephantas1

sr. member

Activity: 378

Merit: 250

still no info about bter withdraws?

informer

member

Activity: 238

Merit: 10

Quote from: SyRenity on August 24, 2014, 09:47:58 AM

Quote from: Wulfcastle on August 24, 2014, 09:32:07 AM

I still run forever start app.js, everytime it reboots and everything seems to be working perfectly in the back end, but when I got to the web wallet, nothing loads

Your node might made it into a black-list that we implemented in 0.1.4 (which bans for some period the suspected attacking node).

If you run on cloud, try to change the IP. Also make sure you erased the blockchain.

Yes, you have to delete blockchain.db otherwise it becomes blockchain.db.1

AWS EC2 Ubuntu 14.04

informer

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: Wulfcastle on August 24, 2014, 09:32:07 AM

I still run forever start app.js, everytime it reboots and everything seems to be working perfectly in the back end, but when I got to the web wallet, nothing loads

Your node might made it into a black-list that we implemented in 0.1.4 (which bans for some period the suspected attacking node).

If you run on cloud, try to change the IP. Also make sure you erased the blockchain.

BrokenRam

newbie

Activity: 16

Merit: 0

Quote from: SyRenity on August 24, 2014, 09:24:50 AM

Quote from: BrokenRam on August 24, 2014, 09:23:49 AM

Looks to be working from my end with Forging enabled.

Likewise, instead of restarting the node. I stopped, edited configuration file and then started the node.

So the command forever restart app.js did not work for you, only stop/edit/start?

Was getting "Can't forge, node not synchronized!" for over a minute, so just stopped the node. So might have sync'ed up given enough time... no patience on my part

With stop/edit/start took under 10secs to synchronized. Also deleted the blockchain.db before starting up the node again.

informer

member

Activity: 238

Merit: 10

Quote from: SyRenity on August 24, 2014, 09:24:50 AM

Quote from: BrokenRam on August 24, 2014, 09:23:49 AM

Looks to be working from my end with Forging enabled.

Likewise, instead of restarting the node. I stopped, edited configuration file and then started the node.

So the command forever restart app.js did not work for you, only stop/edit/start?

That's what worked for me. Without having to rebuild. I just downloaded 0.1.5.zip extracted it, ed25519 gyp fix and presto.

informer

atleticofa

sr. member

Activity: 406

Merit: 250

Everything fine now

Good job devs

Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 343. (Read 804700 times)