Jump to content
Sign in to follow this  
Heisenberg

Codius host stopped receiving payments

Recommended Posts

1 minute ago, rswarthout said:

 


I have used it with success.

 

did you have to put any other commands before starting the script.. or just  login and run script straight away?

Share this post


Link to post
Share on other sites
Posted (edited)

done it so many times now... keep getting 502 gateway... when i check there are issues with codiusd and moneyd:

[root@codius ~]# systemctl status codiusd
● codiusd.service - Codiusd
   Loaded: loaded (/etc/systemd/system/codiusd.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-08-07 12:29:34 AEST; 1min 8s ago
 Main PID: 742 (node)
   CGroup: /system.slice/codiusd.service
           └─742 node /usr/bin/codiusd

Aug 07 12:29:58 codius.example.com codiusd[742]: 2018-08-07T02:29:58.457Z ilp-ws-reconnect:debug debug websocket disconnected with Error: connect ECONNREFUSED 127.0.0.1:7768; reconnect in 5000
Aug 07 12:30:03 codius.example.com codiusd[742]: 2018-08-07T02:30:03.559Z ilp-ws-reconnect:debug debug websocket disconnected with Error: connect ECONNREFUSED 127.0.0.1:7768; reconnect in 5000

[root@codius ~]# systemctl status moneyd-xrp
● moneyd-xrp.service - ILP provider using XRP payment channels
   Loaded: loaded (/etc/systemd/system/moneyd-xrp.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-08-07 12:29:34 AEST; 1min 21s ago
 Main PID: 744 (node)
   CGroup: /system.slice/moneyd-xrp.service
           └─744 node /usr/bin/moneyd xrp:start

Aug 07 12:29:54 codius.example.com moneyd[744]: at Plugin.EventEmitter.emit (/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/eventemitter2/lib/eventemitter2.js:357:19)
Aug 07 12:29:54 codius.example.com moneyd[744]: at Plugin.<anonymous> (/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:476:14)
Aug 07 12:29:54 codius.example.com moneyd[744]: at Generator.next (<anonymous>)
Aug 07 12:29:54 codius.example.com moneyd[744]: at /usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:7:71
Aug 07 12:29:54 codius.example.com moneyd[744]: at new Promise (<anonymous>)
Aug 07 12:29:54 codius.example.com moneyd[744]: at __awaiter (/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:3:12)
Aug 07 12:29:54 codius.example.com moneyd[744]: at Plugin._handleIncomingBtpPacket (/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.js:340:16)
Aug 07 12:29:54 codius.example.com moneyd[744]: at Plugin.<anonymous> (/usr/lib/node_modules/moneyd-uplink-xrp/node_modules/ilp-plugin-btp/src/index.ts:329:18)
Aug 07 12:30:44 codius.example.com moneyd[744]: 2018-08-07T02:30:44.858Z ilp-xrp-channel-watcher checking 0 channels for expiry
Aug 07 12:30:54 codius.example.com moneyd[744]: 2018-08-07T02:30:54.747Z ilp-ws-reconnect:debug websocket disconnected with 1006; reconnect in 5000
[root@codius ~]#
 

 

Edited by vick82

Share this post


Link to post
Share on other sites

i got this issues. can you help ?

systemctl status codiusd
● codiusd.service - Codiusd
   Loaded: loaded (/etc/systemd/system/codiusd.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-08-07 07:43:15 CEST; 4min 21s ago
 Main PID: 20717 (node)
   CGroup: /system.slice/codiusd.service
           └─20717 node /usr/local/bin/codiusd
Aug 07 07:43:26 codius.openswatch.com codiusd[20717]: 2018-08-07T05:43:26.250Z codiusd:SelfTest error Pod upload failed
Aug 07 07:43:31 codius.openswatch.com codiusd[20717]: 2018-08-07T05:43:31.260Z codiusd:SelfTest error Pod upload failed
Aug 07 07:43:36 codius.openswatch.com codiusd[20717]: 2018-08-07T05:43:36.266Z codiusd:SelfTest error Pod upload failed
Aug 07 07:43:36 codius.openswatch.com codiusd[20717]: 2018-08-07T05:43:36.267Z codiusd:SelfTest error Error: Self Test failed. Could not upload pod successfully due to: Service Unavailable
Aug 07 07:43:36 codius.openswatch.com codiusd[20717]: at SelfTest.run (/usr/local/share/.config/yarn/global/node_modules/codiusd/src/services/SelfTest.ts:196:15)
Aug 07 07:43:36 codius.openswatch.com codiusd[20717]: at process._tickCallback (internal/process/next_tick.js:68:7)
Aug 07 07:43:36 codius.openswatch.com codiusd[20717]: 2018-08-07T05:43:36.286Z codiusd:SelfTest error Error: Self test failed: Upload Status=false Http Connection=false WebSocket Connection=false
Aug 07 07:43:36 codius.openswatch.com codiusd[20717]: at SelfTest.run (/usr/local/share/.config/yarn/global/node_modules/codiusd/src/services/SelfTest.ts:202:13)
Aug 07 07:43:36 codius.openswatch.com codiusd[20717]: at process._tickCallback (internal/process/next_tick.js:68:7)
Aug 07 07:44:41 codius.openswatch.com codiusd[20717]: 2018-08-07T05:44:41.190Z codiusd:HyperClient info deleting pod. id=eyl7as5kahzn5fijqtsxtdm6nruw5lzqyb5d3po6csp6w6jrikuq

 

Share this post


Link to post
Share on other sites
Posted (edited)

hi everyone.. just created another. followed the instructions an everything looked ok but something must be wrong as when you go to the webage it only shows this on home,version or peers page : {"message":"Self Test Failed","stats":{"selfTestSuccess":false,"uploadSuccess":true,"httpSuccess":true,"wsSuccess":false,"running":false}}


not coming up on codiushosts.com either.... any ideas ?

Edited by vick82

Share this post


Link to post
Share on other sites
On 8/8/2018 at 2:03 AM, vick82 said:

hi everyone.. just created another. followed the instructions an everything looked ok but something must be wrong as when you go to the webage it only shows this on home,version or peers page : {"message":"Self Test Failed","stats":{"selfTestSuccess":false,"uploadSuccess":true,"httpSuccess":true,"wsSuccess":false,"running":false}}


not coming up on codiushosts.com either.... any ideas ?

"wsSuccess: false" means that the web-socket testing failed. You might want to check that the following lines have been added to your "/etc/nginx/conf.d/codius.conf" file (or /etc/nginx/nginx.conf if that is where you have your Codius-related block placed):

map $http_upgrade $connection_upgrade {

     default upgrade; '' $http_connection;

}

Check out Nathan's tutorial for upgrading the codiusd service for detailed instructions:

https://medium.com/codius/codiusd-1-2-0-upgrading-and-websocket-support-42f712a0cee9

Share this post


Link to post
Share on other sites
Posted (edited)

@vick82

I was having some issues as well with websocket.  I edited   /etc/nginx/conf.d/codius.conf   using the instructions in

  https://medium.com/codius/codiusd-1-2-0-upgrading-and-websocket-support-42f712a0cee9   

That didn't fix my problem at first, but I had edited it using Notepad in Filezilla, and Notepad puts everything on one line and you can't see if the code is formatted properly.  I mean you can't have 2 lines of code on one line or something which is impossible to tell in Notepad.

Someone in Gitter taught me how to edit in shell, then I was able to separate the individual lines of code exactly how it's shown in the medium article and that did the trick.  My codius host is working now.  But to edit it in shell, I had to login into root in PuTTY then 

vc /etc/nginx/conf.d/codius.conf

then type i to insert and modify text 

then ESC and type :x and press enter to save

I hope that helps.

Edited by MsKat141

Share this post


Link to post
Share on other sites

thanks for the response guys.. i ended up just reinstalling again.... had the 502 gate way issue... reboot meant to fix it but didn't... ended up rebooting a 2nd time and then that fixed it... but pod uploading wasn't working kept getting 504 error.. tried reboot still getting the error.. gave up for  the night.. checked the next morning and the 504 error stopped and can upload pods now..  didn't change anything so is there something that delays after a new setup ? no clue... anyway i now have 2 host on 1.2.5 that are working but no contracts yet.. Im also noticing not many contracts running at the moment but of all of them none are running on 1.2.5 hosts

Share this post


Link to post
Share on other sites
32 minutes ago, vick82 said:

thanks for the response guys.. i ended up just reinstalling again.... had the 502 gate way issue... reboot meant to fix it but didn't... ended up rebooting a 2nd time and then that fixed it... but pod uploading wasn't working kept getting 504 error.. tried reboot still getting the error.. gave up for  the night.. checked the next morning and the 504 error stopped and can upload pods now..  didn't change anything so is there something that delays after a new setup ? no clue... anyway i now have 2 host on 1.2.5 that are working but no contracts yet.. Im also noticing not many contracts running at the moment but of all of them none are running on 1.2.5 hosts

The new self-tests in version 1.2.5 take some time to complete and there are retry mechanisms built-in so you might want to give them some time to run.

One of the recommended ways to find out what could be wrong would be to run "systemctl restart codiusd && journalctl -f -u codiusd".

This lets you see in the real-time what is happening in the codiusd service as it runs the various self-tests.

Share this post


Link to post
Share on other sites
2 hours ago, youngm said:

Is there a wait time for a host, previously listed as inactive on codiushosts.com, to become listed as active after fixing issues?

Yes, it usually takes a while, around 15 minutes to half an hour or so based on my own experience.

Share this post


Link to post
Share on other sites

thanks to all for your comments and advice on here! I updated my host this morning and had a web socket error and my host went down. so i followed that medium tutorial updating the config files and boom! back in action! xoxo big kiss, little kiss

Share this post


Link to post
Share on other sites
Sign in to follow this  

×