we inserted a timeout between activation attempts in order to not consume too much cycles for the time the dhcbdb server isn't yet started. So I assume its fixed in latest gutsy (0.6.5-0ubuntu15).
If you still see it in that version, feel free to reopen.
we inserted a timeout between activation attempts in order to not consume too much cycles for the time the dhcbdb server isn't yet started. So I assume its fixed in latest gutsy (0.6.5-0ubuntu15).
If you still see it in that version, feel free to reopen.