similar to: stale subscription

Apologies if this is the wrong mailing list but no list in particular seems appropriate. I was disappointed to discover in the 9.2-RC's that ntpd was still 4.2.4p8. I notice that that same (legacy) ntpd version is in stable/10 and, presumably, likely to end up in the new 10.0 release; so I thought I should speak up in the hope that it is not yet too late for the current ntpd stable release

Hi, I'm a bit curious of error messages of the type "remote operation failed: Stale NFS file handle". All clients using the file system use Gluster Native Client, so why should stale nfs file handle be reported? Regards, /jon -------------- next part -------------- An HTML attachment was scrubbed... URL:

Dear R-users, I am trying to develop a function that takes another function as an argument, changes its default values and returns a list of things, among which the initial function with its default arguments changed. An example of what i will like to obtain below: ## initial function myfun <- function(x, a=19, b=21){ return(a * x + b) } ## this is the function i will like to create ##

Hello, since updating two of our backup mailservers from dovecot 1.1.16 to 1.2.4 i get the following errors from dovecot-deliver when receiving (smtp) mail. Oct 16 00:10:42 mail3 dovecot: deliver(user): write_full(/home/r/user/.temp.backupmail.22774.d17050a07b2108e8) failed: Stale NFS file handle Oct 16 00:10:42 mail3 dovecot: deliver(user): copy: i_stream_read() failed: Stale NFS file handle Oct

I thought this would be relatively straightforward....I would create .subscriptions by doing an ls -1 of ~/mail. I'm running into some problems. 1) the ~/mail directories haves directories in them for 5% of the accounts! AFAIK, our mail sevice has always been UWIMAP with mbox format INBOXes, and it was my understanding that the mbox format is flat and NOT hierarchical and thus I'd

Icecast 1.3.12 fixes the current known exploit for icecast as well as closing many other potential holes. Thanks to diz for the original report and analysis and to dave from jetcafe.org for a comprehensive prophylatic patch. <p>Again, I warn: DO NOT RUN ICECAST AS ROOT. DO NOT RUN ICECAST AS A PRIVELEDGED USER. <p>If you have been running icecast as root, there is an exploit in

Icecast 1.3.12 fixes the current known exploit for icecast as well as closing many other potential holes. Thanks to diz for the original report and analysis and to dave from jetcafe.org for a comprehensive prophylatic patch. <p>Again, I warn: DO NOT RUN ICECAST AS ROOT. DO NOT RUN ICECAST AS A PRIVELEDGED USER. <p>If you have been running icecast as root, there is an exploit in

Hello, I'm using dovecot 1.0.7 and have a problem with subscription files. The documentation says that this file ("subscriptions" or ".subscriptions" in the root of the maildir, I've tried both) holds the informations about the subscribed folders. I've created such a file with these lines: Trash Sent Drafts INBOX.prova INBOX.prova4 And configured a client

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

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

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

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

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 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.

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

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 to troubleshoot this? > Two things: - the output of 'lsusb -d 0665:' before and after the 'stale data' warning - the output of '/lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 | tee /tmp/nutdrv_qx.log' (Please gzip nutdrv_qx.log before

Yes. I am one of them. ---Aki TuomiDovecot oy -------- Original message --------From: Raffaele Gambelli <R.Gambelli at hitachi-systems-cbt.com> Date: 23/02/2018 12:25 (GMT+02:00) To: dovecot at dovecot.org Subject: Re: Stale mailbox lock file Thanks Aki, do you know if this list is read by dovecot developers team too? Could you point me to the right list otherwise? Raffaele Gambelli

On Jun 27, 2016, at 9:11 AM, Thomas Jarosch wrote: > > Jun 27 14:56:24 server upsd[3123]: Data for UPS [apcsmart] is stale - check driver > Jun 27 14:56:24 server upsd: Data for UPS [apcsmart] is stale - check driver ... > Jun 27 14:58:38 server upsd: UPS [apcsmart] data is no longer stale Two minutes is a bit longer than what I was expecting for stale data. If you have a USB

We are using Samba 3.0.33 as a PDC and file server for Windows XP clients, but seem to be suffering lots of stale connections. smbstatus still shows connections from users already logged out and even from systems which have already been shut down. Restarting the samba service, cleans up all stale connections. We tried deadtime = 5 in the samba configuration file, but this does not help at all.