KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2438 blocks

[trev59]

It doesn't work for me...

[HSchmirPo]

de.kano.is seem's working again… 

[kano]

It doesn't work for me...

Yeah the main server has died again ... I'm awaiting them to resolve whatever the power problem is

The main server is back up again as at 07:04:12 UTC
however, the provider has stated that they don't guarantee there will be no more interruptions due to the power problem ... so we'll see how long it stays alive this time.

[Experimenter]

Hi Kano,

Any chance to add some geo-redundancy for the main server, in order to avoid such issues in the future?

(I completely understand this is NOT something to be done right now, so it's just an idea to consider for future improvement...)

[kano]

Hi Kano,

Any chance to add some geo-redundancy for the main server, in order to avoid such issues in the future?

(I completely understand this is NOT something to be done right now, so it's just an idea to consider for future improvement...)

The main server is the point that no one talks to directly and manages everything - there of course has to be some main point of control - and yep that's how it is.

Since this is the first time it's happened since I switched to this provider almost 2 years ago - I guess I can say I'm not too concerned yet.

The nodes solve the problem of outages for all other issues since there's many of them.

[trev59]

It works

[Geronimoe]

.DE & .UK both down now 

[dzimmerm56]

Down again here in Central Ohio USA.
I have an old S7LN I use for heating the bedroom and it started beeping due to no data. Hopefully the main server issue gets resolved soon. One would hope the main server is on a VMware host and can be moved to another physical server unless the whole data center is dead.

[comby]

Shall we stay on kano or switch temporary?

[dzimmerm56]

Up and working again in Central Ohio.

[kano]

Well it's back up yet again since 08:48:31 UTC ... but still no notification from the provider stating they've completed working on the power problem.

... and now stated that it's resolved.
OK time to send them some abuse

[MoparMiningLLC]

I have not been able to connect for a while - I have kano pools set up as primary but they attempt to connect and then disconnect and go to secondary pools.

[kano]

I have not been able to connect for a while - I have kano pools set up as primary but they attempt to connect and then disconnect and go to secondary pools.

There were problems on and off from 04:15:42 UTC until 08:48 UTC
All OK since then.

[MoparMiningLLC]

I have not been able to connect for a while - I have kano pools set up as primary but they attempt to connect and then disconnect and go to secondary pools.

There were problems on and off from 04:15:42 UTC until 08:48 UTC
All OK since then.

I have Kano set up as primary pool but it is reading dead so all my kano miners are switching over to slush - I will try a hard reset on them when I get back to the house.

[Steamtyme]

That was the first time I was home and looking at my miners during network issues.

Panicked like a rookie because I just moved my 741's inside, and have been testing their stability while heating the basement. I assumed I had some random temperature spike, but after 10 minutes of staring after the reboot I checked the support channels. Good old facepalm.

I did catch it and reset before I wound up going solo.

[VRobb]

I saw mine had failed over to a solo pool for a while and then came back. All while I was sleeping!
Mine ON!

[MoparMiningLLC]

I have been able to set up 5 of my miners back to Kano - will be watching to see if they stay pointed here or redirect again.

[kano]

I have been able to set up 5 of my miners back to Kano - will be watching to see if they stay pointed here or redirect again.

The failover in the early cgminer code never worked properly coz it was never tested properly (or at all?) by the coder.
They can switch to pool3 and never switch back under various circumstances.

Most of the bmminer code is of course early cgminer code.

[MoparMiningLLC]

I have been able to set up 5 of my miners back to Kano - will be watching to see if they stay pointed here or redirect again.

The failover in the early cgminer code never worked properly coz it was never tested properly (or at all?) by the coder.
They can switch to pool3 and never switch back under various circumstances.

Most of the bmminer code is of course early cgminer code.

since reconnecting today, they have disconnected from the pool twice - for about 8-9 mins and then reconnected.

[kano]

I have been able to set up 5 of my miners back to Kano - will be watching to see if they stay pointed here or redirect again.

The failover in the early cgminer code never worked properly coz it was never tested properly (or at all?) by the coder.
They can switch to pool3 and never switch back under various circumstances.

Most of the bmminer code is of course early cgminer code.

since reconnecting today, they have disconnected from the pool twice - for about 8-9 mins and then reconnected.

There have been no disconnects on the nodes since the datacentre power problem was fixed about 14 hours ago.

The problem will probably be at your end - you'll have to check what's up with your internet connection or ISP.

One thing you can try is using port 80 instead of port 3333 in your connection.
Most ISPs wont mess with port 80 since it's used for web browsing.
Also try port 443 since that's the SSL web browsing port that most all web sites use now
(most web browsers are starting to treat port 80 connections as inferior to 443 no matter what the web site is)
And of course you can try port 81 or port 8080 in your connection.