Displaying 4 results from an estimated 4 matches similar to: "Upssched not getting called from UPSMON"
2018 Sep 21
1
Upssched not getting called from UPSMON
Ah yes sorry I forgot to specify I am on CentOS 7 and the newest NUT for that is 2.7.2
On 9/21/18, 9:04 AM, "Denny Page" <denny at cococafe.com> wrote:
Where syslog output ends up is an OS specific question and depends upon the configuration of the system logger in use.
On most systems the logging information will be found in /var/log. On most Linux systems, the
2018 Sep 14
0
snmp-ups driver for APC smartUPS No supported device detected. Nut-scanner finds the device
OS: CentOS 7
NUT Version: 2.7
Installed NUT through: yum install nut
UPS: APC smart UPS srt3000 with NMC
I am trying to set up NUT with snmp for my apc ups. Heres the config;
[ups6]
Driver = snmp-ups
Port: ups6.domain.name (also tried 192.168.24.9)
Snmp_version = v3
secLevel = authPriv
secName = ups6
2009 Jul 09
1
Premature end of script headers: upsimage.cgi
hi-
i'm using version 2.4.1, courtesy of debian testing, and noticed that
in the web interface, the image for the battery voltage bar graph
wasn't displaying. the other images (change, input, output, load)
seem to be fine. the browser reports "500 internal server error", and
apache reports "Premature end of script headers: upsimage.cgi,
referer:
2018 Sep 21
0
Upssched not getting called from UPSMON
Where syslog output ends up is an OS specific question and depends upon the configuration of the system logger in use.
On most systems the logging information will be found in /var/log. On most Linux systems, the default system log is /var/log/messages.
Denny
> On Sep 20, 2018, at 13:30, Ito-Cole, Kaeny (Student) <Kaeny.Ito-Cole.stu at gtri.gatech.edu> wrote:
>
> First