On 11/13/23 5:14 AM, Mike Stupalov wrote:
> Heh,
>
> it's funny. Seems as this is an openbsd snmpd issue.
>
> It's report 3 different Uptimes:
> 1. SNMPv2-MIB::sysUpTime.0 = 1:0:58:32.85 (Timeticks converted
> 1:0:58:32.85 -> 89912)
> 2. HOST-RESOURCES-MIB::hrSystemUptime.0 = 7:10:54:04.27
On 11/10/23 3:43 AM, Mike Stupalov wrote:
I've captured the output here:http://keekles.org/OpenBSD.txt
I didn't see an option to kill the escape codes for color though.
That file ok, but this is not debug output.. you must run commands with
-d flag as I written!
With debug I can see required
On 11/9/23 8:02 AM, Mike Stupalov via observium wrote:
Hi,
you have installed observium on OpenBSD or you monitor hosts with OpenBSD.
(I didn’t really understand your notes)
I have observium installed on Linux, and added a couple new OpenBSD hosts as
servers for it to monitor. On OpenBSD
I've setup a couple hosts running openbsd and note that uptime as reported in
observium (I'm on the latest stable 13154) is showing incorrectly. Last
reboot is showing as Jan 1 1970 as well.
Has anyone else seen this on OpenBSD?
Thanks,
--
Bryan Fields
727-409-1194 - Voice
On 8/30/23 4:59 AM, Mike Stupalov via observium wrote:
Hi, should be fixed in r12965.
That's the SVN release, correct?
I updated to current revision 12970, and it's giving the same error. Can you
confirm this pulled the right version?
root@eyes:/opt/observium# svn info
Path: .
Working
I'm running 23.8.12912 (2nd August 2023), svn revision 12959 on Debian 12.
This is the subscription version.
When I go to edit a device and then the "Applications" tab I get an error of
"Oops! Something went wrong."
The below is a quote of the page with the detail errors:
Cannot increment
On 8/24/23 6:45 PM, Kevin Riahi via observium wrote:
I can execute the script as root or with sudo.
Are you running the observium_agent from xinetd? What is the user it's
running as?
Mine is below. I am running 4.8 powerdns authoritative server on ubuntu 22 lts.
root@ns1:~# cat
On 8/24/23 4:18 PM, Ryan, Spencer J. wrote:
I don't have any APC units to test with (we've long ago given up on them and
moved to Eaton), but instead of looking for specific values we let the device
decide if something is good or bad.
We have three generic alerts that cover all of our
Been working on getting this configured and my head around this alert. I've
got it working to alert me of going on battery now, and if the batteries are
marked as bad.
This is specifically tested with an APC Smart-UPS SRT 6000, SKU: SRT6KXLT.
I have three checks:
1: UPS on battery
On 3/22/23 9:33 AM, Ryan, Spencer J. wrote:
> Checking ifHighSpeed is likely the easiest if you don’t already have syslog
> set up.
>
> My 200G LAGs show ifHighSpeed=>20, so it would be easy to check if it’s
> < 20, or != 20 depending on how you want to write the check.
While this
I'm looking at an easy way to send an alert if a LAG member drops.
Running subscription Observium 22.12.12421 and talking a Juniper EX4500 switch.
My thought was to have a global check that looked for ifType = ieee8023adLag
and then if there was some way members changed, but I don't see a way to
11 matches
Mail list logo
