> I think i have solved it. Will know for certain in a bit more then a
> month though.
> Apparently aiccu goes off the track when the system time is more
> then a certain amount of seconds off. At least with the clock off
> more then 145 seconds it will refuse to start.
> When the situation occurs while it is running, it apparently kills
> the IPv6 routing. As my network is dual-stack and a lot of
> workstations are indeed dual stack, this causes significant delay on
> any browsing, as it needs for IPv6 to time out.
Thanks! I'm reassigning to aiccu in the hope that it can provide
better diagnostics (for example to syslog). Thanks again for your
patience in tracking this down.
Hope that helps,
> I've now added an ntp server to the setup.
> What bugs me is that a reboot would solve it. So apparently the
> hardware clock remains OK, and only the system time goes off.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org