Displaying 20 results from an estimated 2269 matches for "stales".
Did you mean:
stale
2016 Jun 27
2
query "Data stale" from the cmdline
Hi Charles,
On Monday, 27. June 2016 08:59:02 Charles Lepple wrote:
> > is there a way to query from the cmdline if the UPS data is stale?
>
> The "data stale" state applies to the entire set of variables for an UPS,
> so if the exit code of `upsc` is zero, the data set is not stale.
> > "upsc" outputs a lot of information, but not if the data is stale.
2016 Jun 27
2
query "Data stale" from the cmdline
Hello,
is there a way to query from the cmdline if the UPS data is stale?
"upsc" outputs a lot of information, but not if the data is stale.
Example output from a "stale" UPS on the server:
(nut version: nut-2.7.2-3.el7)
# upsc apcsmart
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2014/09/01
battery.runtime: 1320
2009 May 05
5
upsd flapping in the breeze
Hi,
I have had a long standing problem with NUT talking to 110V MGE UPSs on
FreeBSD, I was recently investigating again and noticed that upsd seems
overly noisy, eg..
May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale
May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver
May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale
May 5
2016 Oct 13
2
Data Stale at random intervals
Here are the results of a restart as well as a stop/start. Seems like it may be the server? I tried to run the nut-server service with gdb, but no luck getting it to work so far. Thanks!
________________________________
From: Charles Lepple <clepple at gmail.com>
Sent: Wednesday, October 12, 2016 8:20 PM
To: Daniel Shields
Cc: nut-upsuser at lists. alioth. debian. org
Subject: Re:
2007 Jan 27
2
"no longer stale" when disconnected with 2.0.5 newhidups
Hello,
I'm using driver newhidups with APC Back-UPS CS 500. Most things works fine
except the following:
After I disconnect the UPS the upsd write "Data for UPS [apc] is stale -
check driver" in /var/log/messages. In the same second it tells "UPS [apc]
data is no longer stale". This repeats all the time the ups is
disconnected:
Jan 25 14:45:03 degpn026w226 kernel: usb
2016 Oct 14
0
Data Stale at random intervals
Just an update, these messages are in the syslog when nut is no longer able to communicate with the server:
Oct 14 01:41:59 golgotha upsmon[1300]: Poll UPS [nailbunny at localhost] failed - Data stale
Oct 14 01:42:04 golgotha upsmon[1300]: Poll UPS [nailbunny at localhost] failed - Data stale
Oct 14 01:42:09 golgotha upsmon[1300]: Poll UPS [nailbunny at localhost] failed - Data stale
Oct 14
2015 Sep 14
2
stale/dead ups logic
hi:
when testing nut in our environment, we found something that nut
maybe tune for "stale/dead ups" situation. currently the "dead ups"
are assume alive(eg: host shutdown unnecessary), unless it is in the
"OB" state before going to stale.
our environment (ServerA + ServerB forms a cluster):
ServerA-> usb to UPSA -> two PS power by UPSA and UPSB
2010 Jan 20
2
Odd message: "correct auth, but ..."
I'm getting dozens of these at a very high rate:
[Jan 20 09:15:27] NOTICE[16958]: chan_sip.c:12687 check_auth: Correct auth, but based on stale nonce received from '"" <sip:121 at gnat.com>;tag=as5f1a9480'
[Jan 20 09:15:28] NOTICE[16958]: chan_sip.c:12687 check_auth: Correct auth, but based on stale nonce received from '"" <sip:130 at
2008 Feb 16
3
Unitek UPS 1250xD - megatec_usb driver
Hi All,
I am a newcomer to Nut, so firstly hello :-)
I am keen to implement Nut and have been digging around most of the
day to see how to get my two Unitek 1250xD UPS devices working.
I have now managed to get nut installed (from source 2.2.0) and have
(I think) success. I found a post here:
http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-December/003573.html
which was
2008 Feb 16
3
Unitek UPS 1250xD - megatec_usb driver
Hi All,
I am a newcomer to Nut, so firstly hello :-)
I am keen to implement Nut and have been digging around most of the
day to see how to get my two Unitek 1250xD UPS devices working.
I have now managed to get nut installed (from source 2.2.0) and have
(I think) success. I found a post here:
http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-December/003573.html
which was
2016 Oct 15
2
Data Stale at random intervals
Ran with gdb:
gdb /lib/nut/usbhid-ups
run -u nut -a nailbunny -x bus=010 -x vendorid=0764 -x productid=0501 -DDDDD
Same result as when I ran normally. Driver just stops communicating with no errors or messages in the logs. Not sure where to go from here as I'm not seeing anything to follow up on.
________________________________
From: Daniel Shields <grungelizard9 at
2006 May 07
0
updateinfo and stale data
Hi,
FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse
1200 USBS.
I set the ups.conf up as :
[ellipse]
driver=mge-utalk
port=/dev/cuaa1
desc="Ellipse"
When I go to start it I get :
Network UPS Tools - UPS driver controller 2.0.3
Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3)
Could not get multiplier table: using raw
2017 Dec 21
1
seeding my georeplication
Thanks for your response (6 months ago!) but I have only just got around to
following up on this.
Unfortunately, I had already copied and shipped the data to the second
datacenter before copying the GFIDs so I already stumbled before the first
hurdle!
I have been using the scripts in the extras/geo-rep provided for an earlier
version upgrade. With a bit of tinkering, these have given me a file
2006 Sep 28
3
MGE Pulsar M 3000 communication problems
Hallo,
I installed nut 2.0.4 on a Solaris 8 and tried two things:
First I wanted the ups to connect via usb, but I could not compile the
usb drivers. Make usb told me: no target named usb found
Second, because both ups and host have serial ports I tried to get it
working with serial.
The driver starts very fine, but takes a long time to detect the ups.
Upsd starts too, but while get in
2015 Jan 02
2
Data stale error after short while
Ok - before stale data:
After stale data:
$ lsusb -d 0665:
Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
After stale data:
And the gzipped log attached:
On 2 January 2015 at 21:56, Charles Lepple <clepple at gmail.com> wrote:
> On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote:
>
> Not sure what other logs I can provide to try
2016 Jun 27
0
query "Data stale" from the cmdline
On Jun 27, 2016, at 4:46 AM, Thomas Jarosch wrote:
>
> Hello,
>
> is there a way to query from the cmdline if the UPS data is stale?
The "data stale" state applies to the entire set of variables for an UPS, so if the exit code of `upsc` is zero, the data set is not stale.
>
> "upsc" outputs a lot of information, but not if the data is stale.
> Example
2005 Oct 02
3
What does the error "stale nonce' mean?
I'm receiving the following error over and over, adnauseam:
Oct 1 23:59:53 NOTICE[3194]: chan_sip.c:5890 check_auth: stale nonce
received from 'CNAME-CID <sip:5551212@192.168.1.X>'
Does anyone know what "stale nonce" is?
Thanks!
Paul Conn
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2017 Jul 20
1
Error while mounting gluster volume
Hi Team,
While mounting the gluster volume using 'mount -t glusterfs' command it is
getting failed.
When we checked the log file getting the below logs
[1970-01-02 10:54:04.420065] E [MSGID: 101187]
[event-epoll.c:391:event_register_epoll] 0-epoll: failed to add fd(=7) to
epoll fd(=0) [Invalid argument]
[1970-01-02 10:54:04.420140] W [socket.c:3095:socket_connect] 0-: failed to
register
2012 Sep 11
1
Back UPS ES and data stale with disconnected device
Hello NUT Team!
I continue playing with NUT for Windows and USBHID-UPS driver I've got from Frederic to fix "Data Stale" problem.
It seems there is something wrong when Network UPS Tools service is starting with disconnected USB cable. UPSMON is writing "Data Stale" to output and continue do it infinitely, even the cable is connected back. Here is a short log:
Network
2015 Jan 02
0
Data stale error after short while
Sorry, I messed up my reply a bit.
The output of the lsusb command is the same before and after the data goes
stale.
$ lsusb -d 0665:
Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
And the output of the /lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 command is
the same as in the previous attachment. I truncated the "before" log
because it just carried on with