Looks to me like the code is not prepared to run in a cluster mode. The primary key conflict/duplication suggests that cluster nodes attempt to overwrite each other records. We need a code to record stats from each cluster node separately. So if we sum number of online users on all cluster nodes we get the total number of online users on the whole installation.

This is important to fix as I have to handover license checker to our customer who already uses Tigase.

There are two separate issues - first one is related to connectivity or accessing the resource:

• for the past couple of days I've been having weird issues with seemingly *.tigase.org going down - it was accessible directly using IP and there was correct entries from dig but still resolver returned error - unknown host

• starting latest nightlies (required for the improved licensing, inclusion of additional fields) with the relatively simple config resulted in http-api exceptions - #2271. They may not be related (as some stats were successfully uploaded), however it's worth to note it.

Bottomline - licence checker has mechanism that prevents server from functioning if number of failed attempts to submit the data fails, given that source and target was the same machine tigase went down.

The second issue is related to @CounterDataLogger@, which is relatively old one (#655, I can work on it) that we've been struggling. For tigase.org and remaining services the consensus was that for the moment we can relay on statistics provided by the license checker so this wasn't a priority. This issue is definitely not related to the shutdown / problems with checking licence.

There are no collisions with statistics gather through the licence checking.

Wojtek, thank you for all the explanation but to be honest I do not fully understand what is the status of this. Is the problem solved? I understand the problem with CounterDataLogger which is what I thought is happening, as this logger does not work correctly in a cluster mode yet.

The main question is: do we have working code for the license checker?

And of course we want this to be deployed on both tigase.org and tigase.im as a final test before we hand it over to a customer.

By the way. Problems with tigase.org connectivity you describe sound like DNS service issues. You may try to use a different DNS server. I think we have our own DNS servers.

Artur Hefczyc wrote:

The main question is: do we have working code for the license checker?

And of course we want this to be deployed on both tigase.org and tigase.im as a final test before we hand it over to a customer.

Both nodes on tigase.org were updated to b3680. There were two main issues with the previous deployment:

• groovy handlers from http-api component were gone missing from distribution package;

• there was an introduction of API keys in http-component which resulted in closed connections in the client; currently both nodes are configured with global --api-keys=open_access (v. #2304, they are still protected with regular http auth as previously).

By the way. Problems with tigase.org connectivity you describe sound like DNS service issues. You may try to use a different DNS server. I think we have our own DNS servers.

I know it looks like that, but it happened only about 3-4 times on 2 different machines with different ISPs hence my ruling out DNS issue before.