Control: notfound -1 4.3.27-3+b1
Control: notfound -1 4.3.27-3
Control: found -1 4.3.17-6
Control: fixed -1 4.3.22~beta-1
Control: close -1
Hi David,
david wrote:
> I suppose your findings are both good and bad.
Definitely
> Good that things work for you, bad they aren't for me.
Nope. That's only my test server. I also have Xymon servers running on
Debian Stable.
> > Which version of Xymon do you have running on the server side?
> >
> > Is the server side also running Xymon 4.3.27? Or is it running an
> > earlier version than the client, e.g. 4.3.17 from Debian 8 Jessie?
>
> I suspect this is where the issue lies as I am running Debian 8 with
> only the kernel upgraded via backports to 4.7 at this time. The
> version of Xymon is *4.3.17-6+deb8u1* which is listed as most
> current without using backports.
That's correct. I hence close this bug report as fixed with
xymon 4.3.22~beta-1.
> I'm somewhat loathe to have a mixed system for my daily workhorse,
I prefer Debian stable for servers, too.
> so maybe I'll just live with things as they are now, and just have
> to keep the interface rename using udev .link files.
>
> Other thoughts are appreciated, but I think the problem problem lies
> with the age of the server side application as you seem to indicate.
Well, I actually plan to do an official backport of Xymon after the
freeze. Did that in the past locally, but since others (not only you)
need that, too, I can also put in some more effort and do that
officially.
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE