That looks like the same issue as #589487 and others. Either make sure the sysvinit script cleans up the environment to make it is safe to be run, have the daemon do so to be safe to be started via sysvinit scripts, or add a workaround to the postinst script (fixes this particular problem, but not if the sysvinit script gets called in some other environment).
Ansgar
