similar to: Lock file issues

Hi All, Need help regarding the samba version samba-3.0.33-3.37.el5.x86_64 1) In the samba version (samba-3.0.33-3.37.el5.x86_64) that we are planning to use , if we put multiple password server names like the one shown below workgroup = EUROPE --------- we do have a domain named as EUROPE [ as per windows team ] password server = EUREDD-HUB10 EUREDD-HUB09 *

Hi, I exposed few days ago this situation on the IRC, but unfortunately I haven''t found a way to solve it yet. I run the Puppet Master with multiple environments, and everything is working good but a couple of nodes that are causing me some troubles. These nodes are pointing to my production environment and I need to point them back to development to grab some changes I made. I

Within a Samba configuration, is it not advisable to create files on the directory on the local machines themselves? Out setup is like so: Server 1 (where the files reside): /data/shares/app01 Server 2 (mounts the above drive): /data/mounts/app01 If, on Server 1, I create a file: # echo test > /data/shares/app01/test The file is created, but on Server 2, I cannot seem to edit the file as

I'm running beta7 on two machines, with maildir on NFS. I have lockd running on all machines. I've found that Dovecot is highly unstable with NFS when accessing a mailbox on more than one machine at the same time. Both dovecot machines have: mmap_disable = yes lock_method = fcntl NFS is version 3, exported from a third linux machine. All machines are running 2.6.9 kernel. Any ideas

I just loaded 1.0.0 on a new box and am getting the following errors periodically. Apr 19 16:36:00 imap01 dovecot: auth(default): *** glibc detected *** free(): invalid pointer: 0xb7f45d14 *** Apr 19 16:36:00 imap01 dovecot: child 1943 (auth) killed with signal 6 Apr 19 16:36:00 imap01 dovecot: auth(default): *** glibc detected *** malloc(): memory corruption: 0x080920a0 *** Apr 19 16:37:31

I have been getting these assertion failures every couple days, killing the IMAP process. After it happens, I can login immediately and everything is fine until it happens again. Here is the log entry: Sep 10 10:03:41 mailbox-4 dovecot: nh: IMAP(username): file mail-index-view-sync.c: line 666 (mail_index_view_sync_end): assertion failed: (view->log_file_offset >=

I am getting some panics after upgrading from 2.2.13 to 2.2.14 This panic happens for one user only, he is subscribed to 86 folders, on two of them this panic happens quite often - several times a day. The mbox folders seems OK, less than 30M with 30 and 200 messages. Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) hmk GNU gdb 6.8

I am trying to use dovecot. I've got a GFS2 shared volume on two servers with dovecot running on both. On one server at a time, it works. The test I am trying is to attach two mail programs (MUA) via IMAPS (Thunderbird and Evolution as it happens). I've attached one mail program to each IMAPS server. I am trying to move emails around in one program (from folder to folder), and then

Hi all, I have seen this in log: dovecot: Dec 03 06:12:57 Error: IMAP(maurirrr): file mail-index-view-sync.c: line 666 (mail_index_view_sync_end): asser tion failed: (view->log_file_offset >= view->map->hdr.log_file_int_offset) dovecot: Dec 03 06:12:57 Error: IMAP(maurirrr): Raw backtrace: /usr/libexec/dovecot/imap [0x461d5e] -> /usr/libexec/dov ecot/imap [0x461acc] ->

Timo, Output of gdb session on the core file attached. This one only produced the following syslog: IMAP(user): UIDs broken with partial sync in mbox file /var/mail/r/user with no assert. Setup: Solaris 9, gcc 4.0.1 for dovecot build. Jeff Earickson Colby College -------------- next part -------------- Script started on Thu Sep 08 10:05:53 2005 %gdb imap core.rtohara GNU gdb 6.3 Copyright

Under Dovecot 1.0-rc27 on Solaris 10 we noticed this error today affecting one of our users repeatedly: Mar 28 14:02:01 myhost dovecot: IMAP(myuser): file mbox-sync-rewrite.c: line 423 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 28 14:02:01 myhost dovecot: IMAP(myuser): Raw backtrace: 0x7ac54 -> 0x42cd4 -> 0x3e968 -> 0x3f54c -> 0x3f980

2 backtraces: GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as

When attempting to save a message from the INBOX to a folder in a collection (like, .projects.dovecot), I get behavior like this (in GDB). Any clue what might be going wrong? Here's where a SIGABRT happens: 280 return array->buffer->used / array->element_size; This is the stack trace: (gdb) where #0 mail_index_map_get_ext_idx (map=0x1200c0db0, ext_id=0,

I've been having a problem with a crashing Dovecot the last couple of months where it crashes after a couple of weeks of uptime. Been a bit difficult to diagnose. Anyway, we're now running 1.0.9 on a Sun Fire T1000 running Solaris 10. Any good ideas on how to pin-point the problem? - Peter Here's the output from syslog when the last crash happened: May 14 11:46:50 ifm.liu.se

Hi I have a data set that needs to be plotted (see below) When I plot it using the simple plot(read_count ~ Cn), I get box plots for the read_count numbers plotted according to Cn. The Cn's on the x-axis are ordered: 10000, 100, 1000, 40, 400, 4000... How do I plot so that Cn is plotted on the x-axis in an ascending order: 40, 60, 80, .......10000? Thanks for your help. Anjan ID

I'll probably release 1.0.rc28 in a few days. Would be nice to get some testing for it first. http://dovecot.org/nightly/dovecot-latest.tar.gz contains pretty much what it's supposed to be. I've now replied to all the mails I was planning on replying, excluding the few patches that are v1.1 material. If you think I forgot to reply to some mail, please resend it. I think the

Otherwise, we get a failure due to Numerical result out of range. And for safety's sake, we are best capping our request to an aligned value, if the server insists on minimum alignment. Fixes: f3fd935c --- info/nbdinfo.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/info/nbdinfo.c b/info/nbdinfo.c index 1afdf98..2b22f51 100644 --- a/info/nbdinfo.c +++

Hello dovecot users, I have updated the MANAGESIEVE patch to fix the currently known small problems with the protocol implementation. It is designed for rc28, but also compiles cleanly with the current cvs branch_1_0. Change Log V4 ------------- - Added managesieve_implementation_string setting to the managesieve configuration. This can be used to customize the default

Help! I just noticed this error this morning, we have been getting a lot of these in rc28 and rc29, not in rc27 or before: Apr 6 07:22:52 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): mbox file /var/mail/j/jaearick was modified while we were syncing, check your locking settings Pine coughed up an internal error, no core dump, and dovecot basically doubled the size of my mailbox by

Hello dovecot users, I have updated the MANAGESIEVE patch to apply and compile against dovecot 1.0.rc28. Not much has changed with respect to the functionality of the previous version however: ChangeLog vs v2 - Updated source to compile with dovecot 1.0.rc28, tested with rc27 (debian package) - Daemon now uses the same location for .dovecot.sieve as dovecot-lda This is typically