similar to: Finding and defeating a stale object

Hi, IN one of my unit tests I get an ActiveRecord::StaleObjectError: Attempted to update a stale object object.save! in object I have apart from other stuff an after_save method, which calls object.assosication.update_attributes(...) If I remove that line from my code my tests succeeds. Unfortunetly, I do not understand why an update_attributes call can generate an StaleObjectError. Maybe

I''m running into a couple of stale object problems with methods that at first glance appear fairly atomic - eg Message.update(params[:id], {:body => params[:value]}) Of course, Rails has to instantiate the object & validate it before it updates the database, so it''s not actually atomic, hence the occasional staleobject error. So I''ve been wondering about

An ESTALE error usually means the gfid could not be found. Does repeating the "rm -rf" delete the directory? Regards, Nithya On 3 January 2018 at 12:16, Jeevan Patnaik <g1patnaik at gmail.com> wrote: > Hi all, > > I haven't found any root cause or workaround for this yet. Can any one > help me in underatanding the issue? > > Regards, > Jeevan. > >

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.

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

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

Hello I'm using nut 2.2.0 on FreeBSD 7.0-RC1. I've got two UPSes (Back-UPS RS 1500) connected to the host, and I often see them to go away. All the system logs are full of "Poll UPS [ups1 at upshost] failed - Data stale". What causes this issue? Is this a known issue, is it going to be fixed? What farther investigations should I do to get some more info on this issue? --

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

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

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

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

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:

Hi We're using asterisk 1.8.3.2 and are finding incidences of stale channels remaining after both parties have hung up. We have tried to hang the channel up using channel request hangup But by it's definition, it will not work as it only executes the hangup as soon as the the channel is written to or read from but as the channel is stale, it will not be written to or read from so the

Hi, After running rm -rf on a directory, the files under it got deleted, but the directory was not deleted and was showing stale file handle error. After 18 minutes, I'm able to delete the directory. So could anyone help me in knowing what could have happened or when in general I get such errors. The following is NFS log: [2017-12-21 13:56:01.592256] I [MSGID: 108019]

Hi all, I haven't found any root cause or workaround for this yet. Can any one help me in underatanding the issue? Regards, Jeevan. On Dec 21, 2017 8:20 PM, "Jeevan Patnaik" <g1patnaik at gmail.com> wrote: > Hi, > > > After running rm -rf on a directory, the files under it got deleted, but > the directory was not deleted and was showing stale file handle

Hello all. I have installed Nut on a Raspberry PI and all looks to be configured correctly, but I get stale data and communications lost at random intervals. I tried running nut-driver in gcc to see if I could find any clues there, but it ran for about 24 hours with no sign of an issue. However, when I let Nut run normally, it seems to be anywhere from 2 to 8 hours and the data goes stale and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a server with a faulty power supply that resets the server every 4/5 hours. While I wait for the supplier to change the PS, I am facing an issue with MySQL. When the system comes back on, mysqld script starts the daemon, but the connections via /var/lib/mysql/mysql.sock don't work because MySQL doesn't delete and recreate the stale

I have already tried disabling sharding on a test oVirt volume... The results were devastating for the app, so please do not disable sharding. Best Regards, Strahil NikolovOn Nov 27, 2019 20:55, Olaf Buitelaar <olaf.buitelaar at gmail.com> wrote: > > Hi Tim, > > That issue also seems to point to a stale file. Best i suppose is first?to determine if you indeed have the same shard

<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> <div style="font-family: Verdana, Arial, Helvetica, sans-serif;">So you don't know when this piece of code is executed:</div> <div style="font-family: Verdana, Arial, Helvetica, sans-serif;"><br></div> <div style=""><pre

Hello Timo, I'm running dovecot-1.0.rc15 (imap and pop) postfix-2.3.5,1 procmail-3.22_6 (which is my LDA) on FreeBSD 6.1-STABLE I'm still using the mbox format (I'm planning to migrate to Maildir soon), mailboxes are on an NFS filesystem. I regulary see stale dotlocks files (either from dovecot (29 bytes, hold the pid of the process) or procmail (1 byte) and processes