Jump to content
FUBAR2208

Two host but only one shows up on codiushosts.com

Recommended Posts

Okay this one works       host.soulardcodiushost.site

This one works but doesn't show up on codius host.com       host2.soulardcodiushost.site

Everything shows good for systemctl status codiusd, hyperd, moneyd-xrp and also pings just fine.

Any ideas?

Let me know.

Thanks,

FUBS

Share this post


Link to post
Share on other sites
4 hours ago, FUBAR2208 said:

Okay this one works       host.soulardcodiushost.site

This one works but doesn't show up on codius host.com       host2.soulardcodiushost.site

Everything shows good for systemctl status codiusd, hyperd, moneyd-xrp and also pings just fine.

Any ideas?

Let me know.

Thanks,

FUBS

https://host2.soulardcodiushost.com/info seems to be not responding to https requests.

You might want to ensure that your firewall settings for host2 allow incoming traffic to port 443.

 

Share this post


Link to post
Share on other sites
6 hours ago, Cobalt said:

https://host2.soulardcodiushost.com/info seems to be not responding to https requests.

Im using .site , not .com

I re did the port for the fire wall anyway and it said 

"Warning: ALREADY_ENABLED: 443:tcp"

I'm not sure what is going on....

Umm...I'm using gator host or host gator for the domain "soulardcodiushost.site"

I'm using this one domain for the two servers. (don't know if this information helps and/or is the problem)

Both host.soulardcodiushost.site and host2.soulardcodiushost.site have their own static IPs through google VM and come back Green for all the systemctl status commands....

Ideas?

I just thought about this....

for the second host...i pre put in the "disable self-test" line for services..........do i need to let it do it's self test ....then go back in and put disable self test in?

Edited by FUBAR2208

Share this post


Link to post
Share on other sites
1 minute ago, FUBAR2208 said:

Im using .site , not .com

I re did the port for the fire wall anyway and it said 

"Warning: ALREADY_ENABLED: 443:tcp"

I'm not sure what is going on....

Umm...I'm using gator host or host gator for the domain "soulardcodiushost.site"

I'm using this one domain for the two servers. (don't know if this information helps and/or is the problem)

Both host.soulardcodiushost.site and host2.soulardcodiushost.site have their own static IPs through google VM and come back Green for all the systemctl status commands....

Ideas?

If you refer to https://host2.soulardcodiushost.site/info, it responds with:

{"fullMem":false,"acceptingUploads":true,"serverFreeMemory":18041588736,"serverUptime":143594,"serviceUptime":142705.487,"avgLoad":0.00146484375,"numPeers":6,"currency":"XRP","costPerMonth":5,"uri":"https://host2.soulardcodiushost.site","selfTestSuccess":false,"runningContracts":0}

Specifically, the selfTestSuccess:false means that the new self-test (implemented in version 1.2.0/1.2.1) is failing in your host. This also results in your host not getting peered with the rest of the Codius hosts. It will be necessary to check your codiusd logs to find out why the self-test is failing and make the necessary rectifications before host2 can get peered with the rest.

Share this post


Link to post
Share on other sites

host.soulardcodiushost.site/info (shows up on codiushosts.com) gives me the same thing as host2.soulardcodiushost.site/info (does not shot up on codiushosts.com)

Both say self test false....but i also have the "Environment="CODIUS_DISABLE_SELF_TEST=true" on both host(which is why i assume that's why the self test is false)

 

Share this post


Link to post
Share on other sites
2 minutes ago, FUBAR2208 said:

host.soulardcodiushost.site/info (shows up on codiushosts.com) gives me the same thing as host2.soulardcodiushost.site/info (does not shot up on codiushosts.com)

Both say self test false....but i also have the "Environment="CODIUS_DISABLE_SELF_TEST=true" on both host(which is why i assume that's why the self test is false)

It would be good to take a read of Nathan's tutorial regarding the upgrading to version 1.2.0:

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

It seems that adding Environment="CODIUS_DISABLE_SELF_TEST=true" will allow codiusd to start but in this state it won’t broadcast itself to the rest of the network, nor receive any network broadcasts. (italicised text quoted verbatim from the tutorial).

and the rationale for this self-test implementation:

The Codius network is growing fast, with an astounding number of hosts being launched since the announcement in June. But without consistency among hosts, it invalidates a portion of that achievement. To ensure that growth in the network is meaningful, we must enforce proper configuration for all members of the Codius network.

 

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

×
×
  • Create New...