5B4AIT Blog

Hi. After like 2 days of debugging I could pinpoint the problem to a mutex variable that was accessed outside a mutex lock = memory violation and failure.

Say that you have  a MUTUAL EXCLUSIVE variable called rmut in a multi threaded environment

Before you do an operation you invike mutex_lock then you do some stuff and finally unlock the variable.

pthread_mutex_lock(&rmut);

…do something clever …

pthread_mutex_unlock(&rmut);

I realized that I had forgotten to lock one memory area in the logon procedure resulting in memory violation error.

Servers have been up for almost 48 hours without any stops. I think I have solved it.

73

Kelly

Debugging software. 6 servers monitor.

From top:

Chicago, Sweden 1, London, Australia, Iceland, Sweden 2

Am currently running SE 1 and 2, IS, UK, US HamSphere servers

Today I gave up the useless mysql master/slave ring replication. It is unstable and totally unpredicatable. If it syncs out it is a living hell getting it back in sync.
Currently I am using one master, but aiming for a master / master replication between 2 servers for redundancy and divide the access from the radio servers to these.

73
Kelly

The normal DXCC award is 100 countries, right…
So I was thinking doing the following.

DXHC, DX Hundred Club or DX HamSphere Club

25 verified countries = Bronze Award including a 1 month subscription
50 verified countries = Silver Award including a 3 months subscription
75 verified countries = Gold Award including a 6 months subscription
100 verified countries = Platinum Award (The real DXHC Award) including a 1 year subscription
150 verified countries = Diamond Award including a 2 years subscription

A verified QSO is when QSL cards has been fully exchanged.

Open for comments.

73
Kelly

Greetings blog readers!

It has been some time since I updated the blog. Since my last update we have released the April 2012 newsletter and started testing multi-path propagation on HamSphere. You can try this mode on the SE server using the 40 meter band.

Other things in the works: Completion and securing the server platform including database replication. Also we are still working to get the new master server fully operational.

Interesting upcoming projects: Currently I am also working on on a DXHC-Reward certificate (DX HamSphere Club). Operators will be automatically issued Bronze, Silver, Gold and Platina awards depending on the number of worked countries (Fully Verified via QSL cards) when they have reached the targets. There might also be other benefits like extended subscriptions etc for DX achievements.

73
Kelly

Finally I am finished with the Log book and QSL statistics page.
I hope you will like it http://www.hamsphere.com/logstats.php

73
Kelly

The new main server has been installed and it is now up at server6.hamsphere.com
Perhaps you can give me some ping feedback. It seems a lot faster and I am currently transferring data from the old server. We will run both main servers in parallell until July 2012.

73
Kelly

After 10 hours work I found the reason for the replication problems and managed to fix it. Database replication is clearly not a walk in the park. Since we have many servers, we always need to let it run for some hours before you can connect the Database “daisy chain” together for full replication. If you connect the chain before it is properly synchronized, the whole system gets instable and starts oscillating with corrupt data as a result.

All servers are go.

73
Kelly

The HamSphere network is using database replication between the servers.
Today I have changed the replication order to optimize the data flow.
Server US, IS,GB and AU will be down during this maintenance.

Kelly