Cristian Livadaru's blog

... think again ...

CouchDB Composite Keys With Date Range

We had some performance issues with data saved in CouchDB. The issue was not couchdb, it was our code and failing to use the power of couchdb views. What we wanted to achieve is to generate a call_list for all calls to a service number. We did this by selecting all calls to that number and then in ruby code throwing out what didn’t match the Date range. The result of this was

puts Benchmark.measure { Service.test_old }
  11.840000   3.450000  15.290000 ( 19.758230)

not so much fun when we just want to get a list of the last seven days worth of calls.

The solution to this problem, assuming you are using the couch_potato gem, looks something like this:

view :by_service_id_and_call_start, :key => [:service_id, :call_start]

def self.find_all_by_service_between_range(service_id,start_date,end_date)

The result of this little couchdb view is:

puts Benchmark.measure { Service.test_new }
  0.780000   0.270000   1.050000 (  1.354226)

now that’s more like it :)

Installing Alchemy CMS 3.0

Wanted to give Alchemy 3.0 a spin, but following the guides doesn’t really get you where you want. First of all, you need ruby 2.1 installed. Ruby 2.0 doesn’t do the trick. Then you need to install rails 4.1.1

gem install rails v=4.1.1

after installing the rails gem, create a new project.

rails new foobar

in the projects Gemfile add the alchemy gem AND the alchemy-devise gem!

if you don’t install alchemy-devise you will get an error trying to execute the “alchemy:install” rake task.

gems/activesupport-4.1.1/lib/active_support/inflector/methods.rb:238:in `const_get': uninitialized constant User (NameError)

adding alchemy-devise to the Gemfile solves this issue.

gem 'alchemy_cms', github: 'magiclabs/alchemy_cms', branch: 'master'
gem 'alchemy-devise', github: 'magiclabs/alchemy-devise', branch: 'master'

run the alchemy installer

bundle exec rake alchemy:install

create the user migrations and migrate.

bundle exec rake alchemy_devise:install:migrations db:migrate

now you’re all set to play around with alchemy 3.0

Fencing With IPMI on Debian Wheezy

Setting up the first cluster on Debian wheezy (7.0) caused some issues when trying to fence with IPMI. First issue was that the node tried a “clean” shutdown before really powering down. To solve this issue, you need to tell GRUB to disable ACPI. Edit /etc/default/grub and add “acpi=off” to GRUB_CMDLINE_LINUX_DEFAULT


Second issue: I wanted the fencing to just power off the node, not reboot it. Turns out, Pacemaker prior to version 1.1.10, ignores the ‘action=”…”’ and debian wheezy installs Pacemaker 1.1.7-1. To solve this, you need to set the pcmk_reboot_action instead. Thanks to for this hint. The CRM configuration would look something like this:

primitive impi-fencing-store2 stonith:fence_ipmilan \
        params pcmk_host_list="store2" ipaddr="" login="foo" passwd="bar" lanplus="true" pcmk_reboot_action="off" \
        op monitor interval="60s"

Provisioning Gigaset IP Pro

I don’t know what drugs the people at gigaset are consuming, but this is by far the sickest provisioning I have ever seen. If you can’t use the gigaset provided provisioning server (because you need to use the contact form, to contact gigaset and beg the to create an account for you! wtf?)

So, first of all on your web server you need some special directories. Let’s assume our provisioning url will be: on your web server under device you need to create sub directories depending on the phone model you want to provision. In this example I will be using the gigaset N510IP Pro. This device expects a directory 42/2 to be present. For more details check the gigaset wiki

Looking at the wiki you will see that some files will be requested as well:

  • master.bin
  • version.bin
  • wl_xx.bin
  • baselines.bin
  • siu_444.bin
  • configuration XML

You can get a template for the xml from the gigaset wiki

but this List is missing some files. Not sure if they are needed but here are my files under the device directory

|-- 42
|   |-- 2
|   |   `-- master.bin
|   `-- webuil
|       `-- 194
|           `-- version.bin
|-- xxxx.xml
`-- sifs
    |-- sifsroot.bin
    |-- sih_4xx.bin
    |-- sit_44x.bin
    `-- siu_444.bin

So, where do you get the files? Searching through the gigaset wiki there is no reference to the files. The answer is, you need to download them from the gigaset provisioning server -

master.bin version.bin sifsroot.bin sih_4xx.bin sit_44x.bin siu_444.bin

After you have all files, copy them to your server in the correct directory and edit the siu_444.bin file. It’s a bin file but still can be edited. The original content look like this:


so in our case, if we have a xml file on the server, we will edit it like this:


This will make the gigaset request where will be the MAC address from the phone. The XML File is some other twisted sick stuff which I will not go into now. But it’s important to update the version on each edit (see comments in file):

<VERSION value="1001131110"/>^M

Give the handsets a name. This would be the first handset:

<SYMB_ITEM ID="BS_AE_Subscriber.stMtDat[0].aucTlnName[0]" class="symb_item" value='"Handset1"'/>

this the second

<SYMB_ITEM ID="BS_AE_Subscriber.stMtDat[1].aucTlnName[0]" class="symb_item" value='"Handset2"'/>

and so on.

Also enable each account used. For 5 accounts it would look like this:

<SYMB_ITEM ID="BS_IP_Data1.ucB_SIP_ACCOUNT_IS_ACTIVE_1" class="symb_item" value="0x1"/>
<SYMB_ITEM ID="BS_IP_Data1.ucB_SIP_ACCOUNT_IS_ACTIVE_2" class="symb_item" value="0x1"/>
<SYMB_ITEM ID="BS_IP_Data1.ucB_SIP_ACCOUNT_IS_ACTIVE_3" class="symb_item" value="0x1"/>
<SYMB_ITEM ID="BS_IP_Data1.ucB_SIP_ACCOUNT_IS_ACTIVE_4" class="symb_item" value="0x1"/>
<SYMB_ITEM ID="BS_IP_Data1.ucB_SIP_ACCOUNT_IS_ACTIVE_5" class="symb_item" value="0x1"/>

and do not forget to add you provisioning url to the configuration, otherwise it will be replaced by the default:

<SYMB_ITEM ID="BS_IP_Data1.aucS_DATA_SERVER[0]" class="symb_item" value='""'/>

Amazon, You’re Drunk, Go Home

Looks like someone at amazon was in a bad mood. What we ordered, 4 extensions for a stair gate, nothing really large.

I was wondering why amazon sent me 4 emails that the item was shipped, well I found out today. Every extension was sent with a separate package, the result after unwrapping

wtf? amazon?

Installing Homer Sip Capture on Debian

apt-get install git-core build-essential mysql-server libmysqlclient-dev bison flex
cd /usr/src
git clone --depth 1 git:// kamailio
cd src
make FLAVOUR=kamailio cfg
make modules-cfg include_modules="db_mysql sipcapture"
make modules
make instal
cp modules/sipcapture/examples/kamailio.cfg /usr/local/etc/kamailio/

Create tables

mysql -p homer_db < modules/sipcapture/sql/create_sipcapture.sql

Sending Mail With Postfix on Redhat 5.5 Over Amazon SES

I’m not really a fan of redhat, neither of sendmail. Today I had to set up mail send on a Red Hat Enterprise Linux Server release 5.5 where sendmail was already installed. This was the easy part to fix. First remove sendmail, forcing it to ignore dependencies.

rpm -e sendmail  --nodeps

Then install postfix

yum install postfix

Now to the SES part, well, no need to reinvent the wheel, just check out this debian Howto for SES

For red hat of course you need to do use yum install stunnel. Unfortunately there is no start up script. Here you can get a startup script for stunnel That’s it. … did I mention I don’t like red hat?

Openfire SSL With Intermediate CA

I have delayed this for over a year and every day just clicking away the warning about the expired cert. Now I finally allocated some time to solve this issue. The Openfire Web interface doesn’t really tell you what to do and how to paste the certificate contents. First go to Server Settings -> Server Certificates -> Import

Paste your private key in the first field. In the certificate field paste your certificate first, followed by the intermediate certificate. The important part is: you must not have a line break after —–END CERTIFICATE—– or —–END RSA PRIVATE KEY—–

These lines must be the last line of the text box else the import will fail! This should save me some time in 2014 :)

Create Shared Objects With Distribution Lists in Zimbra

If you need a shared object (calender, address book) with multiple users, the best way to do this is by using a distribution list. So let’s get started. First create a distribution list and add all your users you want to it. You might also want to disable the option “Can receive mail” and also enable “Hide in GAL” to avoid some confusion.

Then create a resource where you will create your shared object. By using a resource you can create your shared calender or address book without wasting a license.

After you created the resource, click on view mail, go to the calender and add a share.

Use the distribution address as email for the share.

Now go back to the distribution list and click edit.

Go to the shares tab and click ob publish shares.

Enter the mail of the resource, click on find shares, select the desired share and click on “Publish selected share”

The advantage of using this method is that newly added users to the distribution list will automatically get permissions for the share and as soon as a user is removed from the distribution list the share permissions will be revoked!