similar to: thunderbird not receiving new incoming mail: Timeout while waiting for lock for transaction log file

Hi, okay when I configure ices I used the configuration file that appears in the manual. I am seeing that I need to force the password as the password I set in the configuration file is not getting sent - stills says form the debug information that "letmein" is being sent, which is not hte password I have set in the configuration tile. also I am getting the following error after I

On Fri, 27 Dec 2002, Geoff Shang wrote: > Hi: > > Assuming you've got sufficient bandwidth at the server to serve a 128k > stream, and sufficient bandwidth at the receiving end to receive it, what > version of icecast are you using? <p>Hi Geoff, I am using Icecast Version 1.3.12. well shouldnt there be some type of auto bandwidth decrease if the client is not able to

can anybody explain to me the mountpoint that is mentioned by icecast version 1.3.12? I see that the mountpoint is /default what does this mean and how can I change it in the icecast.conf file. I am running this on a freebsd 4.7 STABLE release. - Noah <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from

is there a maiil list out ther efor shout related issues - or is the best place to post them? <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe

Hello, Dovecot 1.2.5, centos 5.4. We are using NFS for mail, but indexes are local and on a ramdisk. However I'm getting logs such as: Mar 02 11:47:14 POP3(USERDELETED): Error: Timeout while waiting for lock for transaction log file /ramdisk/indexes/DOMAINDELETED/USERDELETED/.INBOX/dovecot.index.log Our NFS is rather busy, and we having other warnings to that affect, but wouldn't

dovecot 2.1.x and 2.2.x has "just worked" with a minimal configuration for just about anything I've ever thrown at it. Now, with 2.3.0, there is one user (and only one user) that continually sees horrible delays, which is not surprising given the logs: Error: imap(user)<70175><356C8oljxrCBUppP>: Timeout (180s) while waiting for lock for transaction log file

This is an old thread (but still the best search match for the error message). Several other people pointed at NFS, so it got me to look. Indeed what appear to happen (for me at least) was .... The folders being imapped, some of them were on a NFSv3 mount. The NFS server had been shutdown. The imap process appeared to hang (presumably trying to read from the defunct NFS mount point) this

I have a user that gets client timeout errors when he tries to delete/clean up his massive "Spam" folder (many thousands of mail messages). He uses Thunderbird and has it configured to use "Move to Trash" when he deletes messages. I find the following in Dovecot's log file when it happens: Aug 28 10:38:22 ifm.liu.se dovecot: [ID 107833 mail.error] IMAP(bpn): Timeout

Hello, We still have problems with our updated dovecot servers... The problem now is that we are having errors like: Jul 9 10:22:02 myotis31 dovecot: lmtp(15431, <user>): Error: Timeout (180s) while waiting for lock for transaction log file /var/indexes/<user>/.INBOX/dovecot.index.log Jul 9 10:22:02 myotis31 dovecot: lmtp(15431, <user>): Error: +4YfCwKS+k9HPAAAmo+UlA:

Hi, Up until yesterday, our environment which consists an NFS maildir file store with multiple front end servers, was working fine. We've verified that the server clocks and machines clocks are in sync. Starting yesterday afternoon, We are getting ~850 log entries of the form 'Timeout while waiting for lock for transaction log files' or 'Our dotlock file was modified,

Hello all I am using acts_as_ferret in user model. Error Message: -------------- ActiveRecord::StatementInvalid: Mysql::Error: Lock wait timeout exceeded; try restarting transaction: UPDATE `users` SET `updated_at` = ''2009-12-28 14:31:50'', `active_till` = ''2009-12-28 14:31:50'' WHERE `id` = 21 Where: ------ calls#audit

Hi All; I am using Background in my configuration, and I noticed the following so if any can help: 1) If I pressed 1 twice (11), so it runs the step related to first 1 and then it runs the step related to second 1, so it does buffering for my input and run two steps, how can I make it run only the step related to first entered digit "1" and does not do buffering (so ignoring the second

Hi All - I'm setting up a corporate emergency broadcast system that uses an autodialer to contact all company employees. Everything works fine except if the auto-dialed calls go to the end users' voicemail. If that happens, asterisk starts playback of the emergency message while the voicemail system on the other end is playing its outgoing message. The result is that the beginning (or

>Message: 10 >Date: Wed, 26 Jan 2005 17:53:39 -0500 (EST) >From: "Sean A. Newton" <nester-asterisk@wewt.net> >Subject: Re: [Asterisk-Users] Re: Polycom and call waiting again.. >To: Asterisk Users Mailing List - Non-Commercial Discussion > <asterisk-users@lists.digium.com> >Message-ID: >

Hi there, is there any known issues when using ActiveRecord::Base.transaction with models who tables have constraints applied? I have two models: one (is associated with model two) two (has MySQL foreign key and unique key constraints) I''m doing something like this: ActiveRecord::Base.transaction one.create two.create(reference to one) one.create two.create(reference to

I found the culprit. The original yum process from November 4th was stalled. I killed this and the lock problem has been resolved. -- *** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal

A short while ago I reported a network interruption while performing a YUM update on a server. A check of the logs as recommended by a list member indicated that the update process had succeeded. However, I am now encountering the following problem on that same server and my nastily suspicious mind is trying to tell me that the previous event and this situation are somehow related. >

Have sent a backport request https://review.gluster.org/19730 at release-3.10 branch. Hopefully this fix will be picked up in next update. On Fri, Mar 16, 2018 at 4:47 PM, Marco Lorenzo Crociani < marcoc at prismatelecomtesting.com> wrote: > Hi, > I'm hitting bug https://bugzilla.redhat.com/show_bug.cgi?id=1442983 > on glusterfs 3.10.11 and oVirt 4.1.9 (and before on glusterfs

Hi, this patch it's already available in the community version of gluster 3.12? In which version? If not, there is plan to backport it? Greetings, ??? Paolo Il 16/03/2018 13:24, Atin Mukherjee ha scritto: > Have sent a backport request https://review.gluster.org/19730 at > release-3.10 branch. Hopefully this fix will be picked up in next update. > > On Fri, Mar 16, 2018 at

Hi, I'm hitting bug https://bugzilla.redhat.com/show_bug.cgi?id=1442983 on glusterfs 3.10.11 and oVirt 4.1.9 (and before on glusterfs 3.8.14) The bug report says fixed in glusterfs-3.12.2-1 Is there a plan to backport the fix to 3.10.x releases or the only way to fix is upgrade to 3.12? Regards, -- Marco Crociani