The Stupidity of an Emerging War

So we all can accept that Ukraine was and is in a mess. The former President Viktor Yanukovych was not a good guy. There was a barely palatable agreement for Ukraine to transition to a new government and elections in a year. Europe and Russia also agreed to this.

But then the radical right got involved  and since then  everything that could go wrong has gone wrong. The West has been complicit in by pulling out of an agreement with Russia, the new Ukrainian government is also complicit in stupidity by bringing in the fascists into cabinet and demanding the removal of language rights for ethnic Russians, and Russia, well, Russia does what Russia does and therefore is also complicit in stupidity.

The press is along for the ride and on all side media is controlled to manipulate and pander to the public.

And all this will cause lives to be lost on an an unnecessary and contrived war.

Will people allow themselves, their sons and daughters be sent to another useless slaughter? Is this just a distraction from something else?

And the Canadian Government, that dot in the letter "i" of the word shit parrots what its allies want to hear to gain political point for votes sleepwalking to disaster.

An inability to configure correctly on your part does not consistute a bug on my part

Ever wonder how, in an organisation that is constantly laying off people, how some manage to not be touched by that layoff when they clearly are depriving a village of an idiot?

 I was recently reminded of this when a well known individual (lets call him Raoul) insisted our software had  a bug even though this was clearly a misconfiguration.

Now, please do not misunderstand me, I like helping people. I especially like helping people who try, who try to understand, who do their homework, who listen. But eventually my patience recedes like a middle aged male hairline for those who constantly ask the same question, who, despite repeated explanations, with diagrams, and sock puppets just continue down their blind alley. I finally in the end give up, and put them on my block list.

And so, Raoul emerged again. I had been down this road before with him, and it reminded me, of previous encounters he has had either directly with me, or with my other colleagues.

An issue was presented to me from another colleague, little did I know who was the cause at this point that SSL was the cause of the bug. Here was my first warning.

Beware of people who present answers to you when they are asking you questions.

I have had to endure this before, when something does not work it must be that thing we do not know or understand, in this case, it was SSL. Lets ignore for a moment that they could connect, get almost everything working over SSL, yet for this one item, it did not work, so it must be SSL. Many do not understand that with SSL, the coms are working, or not. There is not "kind of". Its like being "kind of" pregnant.

The problem was caused by the configuration of a load balancer. This thing was configured to key off a hostname but they neglected to include a domain name. In addition, as a flaw of the device it read the HOST HTTP header. The RFC states that the host header can have a HOST and PORT but the port can be omitted if it corresponds to the protocol default. However, it should expect an explicit port definition. In this case, it could not.

This was not a problem with our product. This was a misconfiguration at best and at worse a load balancer that is not RFC compliant. Yet despite frequent explanations, references, displays of traffic, Raoul insisted it was bug. Ok, lets takes this to a logical progression. A bug is raised, but what can we fix in our code?

 And then, how much time do I have to waste when someone either cannot or will not attempt to listen and learn?

Ubuntu 12.04 + virtualbox

So a linux VM running in virtualbox crashed. Well, they all crashed.

But when I restarted the server I was hit with a couple of error. The core one was this:

Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

Scary. But, google is my friend. I found this post in an Ubuntu forum:

http://askubuntu.com/questions/205154/virtualbox-etc-init-d-vboxdrv-setup-issue

It was an excellent review of the problem. The steps that worked for me were:

sudo apt-get install linux-headers-`uname -r`

My headers were up to date so this was not that important, but should be performed regardless.

Then reconfigure dkms and load module:

sudo dpkg-reconfigure virtualbox-dkms  
sudo modprobe vboxdrv

This  got me farther but then received another network error which was solved with:

sudo modprobe vboxnetflt

And now we seem to be back in business.