On Mon, 2014-07-07 at 15:42 +0200, Ole-Morten Duesund wrote:
On 7 Jul 2014 15:01, Paul Stimpson
<paul(a)stimpsonfamily.co.uk> wrote:
Hi,
I'm not sure if there is a problem but for the last couple of months,
I've been seeing about 1 NAGIOS alert a week and various VPN problems
that seems to say that there may be intermittent connectivity issues
within the cluster.
I'm seeing SSH warnings most commonly that my VOS is uncontactable even
though I was logged in during some of them. I had a 10 hour backup file
age NAGIOS warning today. I've also recently seen my VPN dropping out
much more frequently than usual.
Has anybody else experienced any symptoms please or is it just me?
I usually have a mosh-connection running to my VMs and lately they've occasionally
lost connection for a few seconds (5-10) at a time. Don't know if it's related but
I haven't noticed it before.
- om
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
I see occasional blips where a Nagios instance I have running from
Bitfolk will complain that some things outside of Bitfolk are down when
they aren't.
These don't last very long at all. Sometimes when I've had Nagios open
I'll see soft alarms for one or two rounds and they go right back to
green afterwards. Occasionally they'll stay around long enough to send
out an alarm notification (4 rounds), but then go back to green very
quickly.
It's not like everything lights up, seems to only to be one route at a
time (my Nagios setup is checking things in various places with various
providers, and it does seem to take largely different routes to these),
so I've always just put it down to transient routing issues on the
Internet.
For what it's worth, it doesn't seem to always be the same few
systems/locations/providers having issues, so from what I can tell it
doesn't seem to be any one specific fault.
I've always put the quick and seemingly-automatic resolutions to the
issues down to the traffic automatically re-routing down another path
after various upstream routers have had enough time to realise there's
an issue.
So I'd suggest that perhaps it's not really a Bitfolk fault but just
routers doing what they're supposed to be doing: routing around problems
when they appear?
Hope this helps,
--
Aaron