search for: stale

Displaying 20 results from an estimated 2252 matches for "stale".

Did you mean: stage
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. you are right. The exit code is exactly what...
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.runtim...
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 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:39 egbert upsd[96662]: UPS [ups1] data is no longer sta...
2016 Oct 13
2
Data Stale at random intervals
...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: [Nut-upsuser] Data Stale at random intervals On Oct 12, 2016, at 8:13 PM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > Wow. Okay, well I let the debug run all day. Nothing in the logs even with debug cranked to level 5. Attached are the last 1000 lines before it quit. I'm really stumped now...
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 4-1: USB disconnect, address 3 Jan 25 14:45:06 degpn026w226 upsd[4275]: Data for UPS [ap...
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 01:42:14 golgotha upsmon[1300]: Poll UPS [nailbunny at localhost] failed - Data stale Oct 14 01:42:19 golg...
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 -&g...
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 gnat.com>;tag=as15e2228a' [Jan 20 09:15:28] NOTICE[16958]:...
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
...where to go from here as I'm not seeing anything to follow up on. ________________________________ From: Daniel Shields <grungelizard9 at hotmail.com> Sent: Friday, October 14, 2016 12:02 AM To: Charles Lepple Cc: nut-upsuser at lists. alioth. debian. org Subject: Re: [Nut-upsuser] 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] f...
2006 May 07
0
updateinfo and stale data
...Connected to UPS [ellipse]: mge-utalk-cuaa1 May 6 21:49:35 soekris upsd[61873]: Startup successful May 6 21:49:36 soekris mge-utalk[61871]: updateinfo: Cannot update system status May 6 21:49:55 soekris last message repeated 2 times May 6 21:49:55 soekris upsd[61873]: Data for UPS [ellipse] is stale - check driver May 6 21:49:56 soekris upsd[61873]: UPS [ellipse] data is no longer stale May 6 21:50:04 soekris mge-utalk[61871]: updateinfo: Cannot update system status May 6 21:50:04 soekris upsd[61873]: Data for UPS [ellipse] is stale - check driver May 6 21:50:05 soekris upsd[61873]: UPS [e...
2017 Dec 21
1
seeding my georeplication
....173166] D [MSGID: 0] [client-rpc-fops.c:2910:client3_3_lookup_cbk] 0-video-backup-client-4: gfid changed for /path/file.txt [2017-12-21 16:36:37.173212] D [MSGID: 0] [client-rpc-fops.c:2941:client3_3_lookup_cbk] 0-stack-trace: stack-address: 0x7fe39ebdc42c, video-backup-client-4 returned -1 error: Stale file handle [Stale file handle] [2017-12-21 16:36:37.173233] D [MSGID: 0] [dht-common.c:2279:dht_lookup_cbk] 0-video-backup-dht: fresh_lookup returned for /path/file.txt with op_ret -1 [Stale file handle] [2017-12-21 16:36:37.173250] D [MSGID: 0] [dht-common.c:2359:dht_lookup_cbk] 0-video-backup-dh...
2006 Sep 28
3
MGE Pulsar M 3000 communication problems
...emon.info] Startup successful Sep 27 15:32:08 suncore upsd[958]: [ID 702911 daemon.info] Connected to UPS [mge3000-1]: mge-shut-ttyb Sep 27 15:32:13 suncore upsd[959]: [ID 702911 daemon.info] Startup successful Sep 27 15:34:12 suncore upsd[959]: [ID 702911 daemon.notice] Data for UPS [mge3000-1] is stale - check driver Sep 27 15:34:26 suncore upsd[959]: [ID 702911 daemon.notice] UPS [mge3000-1] data is no longer stale Sep 27 15:34:38 suncore upsd[959]: [ID 702911 daemon.notice] Data for UPS [mge3000-1] is stale - check driver Sep 27 15:34:53 suncore upsd[959]: [ID 702911 daemon.notice] UPS [mge3000...
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 <raa...
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 output from a "stale" UPS on the ser...
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: http://lists.digium.com/pipermail/asterisk-users/attachments/20...
2017 Jul 20
1
Error while mounting gluster volume
...l.c:632:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [1970-01-02 10:54:04.420429] I [glusterfsd-mgmt.c:1824:mgmt_rpc_notify] 0-glusterfsd-mgmt: Exhausted all volfile servers [1970-01-02 10:54:04.420480] E [MSGID: 101063] [event-epoll.c:550:event_dispatch_epoll_handler] 0-epoll: stale fd found on idx=0, gen=0, events=0, slot->gen=2 [1970-01-02 10:54:04.420511] E [MSGID: 101063] [event-epoll.c:550:event_dispatch_epoll_handler] 0-epoll: stale fd found on idx=0, gen=0, events=0, slot->gen=3 [1970-01-02 10:54:04.420534] E [MSGID: 101063] [event-epoll.c:550:event_dispatch_epoll...
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 UPS Tools upsmon 2.6.5-3691:37...
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 the same output...