similar to: lmtp panic in proxy lmtp director

Displaying 20 results from an estimated 700 matches similar to: "lmtp panic in proxy lmtp director"

2012 Mar 15
1
director lmtp -> smtp problem
Hi Timo & Dovecot users, We have a 2-node director setup which front-ends for 4 nodes which share a clustered filesystem (GFS). All nodes run Dovecot 2.0.18. Approximately 40k users, but typically only a few thousand active at any time. The director nodes run sendmail, which deliver mail "locally" using LMTP to the director, which then feeds to SMTP on the real servers (also
2011 Sep 29
1
Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof)
Hello all, today I got this crash from dovecot (2.0.14) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3f9aa)? [0x7f18f10299aa] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3f9f6)
2011 Sep 01
0
Crash in director/lmtp-proxy (lmtp_proxy_output_timeout)
FYI, we saw one panic on our director/lmtp-proxy yesterday. It's running dovecot v2.0.13, so it very well might have been fixed already.., but here it is anyway: Aug 31 11:33:31 loadbalancer1 dovecot:: lmtp(4119): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Aug 31 11:33:31 loadbalancer1 dovecot:: lmtp(4119): Error: Raw
2012 Aug 06
4
Could not evaluate: Could not retrieve information from environment production source(s) for one module, for other is ok
Hi, I have been fighting this issue without success for several days. I am sure some of you have dealt with something similar: I have 2 manifest one for vim which works like a charm : class vim { if $operatingsystem == "Debian" { package {"vim": ensure => present, } package
2010 Jun 03
2
Panic with mail_log activated
Hi, We get intermitend deliver-errors when we have activated the mail_log plugin. The installed version is dovecot-2.0-beta5. Below, the error we get: Jun 02 21:58:11 lda(xxx at uib.es): Panic: file mail-log-plugin.c: line 364 (mail_log_mail_transaction_commit): assertion failed: (ret) Jun 02 21:58:11 lda(xxx at uib.es): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x31c4a35dd0]
2004 Feb 24
3
improve ipfw rules
>> 3. I'm intrested in blocking kazaa/P2P trafic with IPFW any help in this issue you could possibly block connections at known p2p ports. deny tcp from any to any 6699 step but most of the newer protocols use dynamic ports and in turn, are configurable. so ipfw isn't exactly ideal on it's own for this. -r. -----Original Message----- From: Pons [mailto:pons@gmx.li] Sent:
2013 Feb 04
1
Problem loading hdf5 file
*Hi everyone, I am a new subscriber, so I hope I'm posting in the right way. I need to load a hdf5 file, so I installed the hdf5 libraries ad the hdf5 R package; in downloaded a small sample file from the hdf5 website and I could correctly load it. But when I try to load my file: * require(hdf5) rm(list=ls()) ls() hdf5load("my_file.h5", verbosity=3) *I get this error message: *
2010 Dec 29
0
panic with lmtp proxy (assertion failed)
Hello! Got a panic&assertion failed with LMTP proxy. Target Dovecot LMTP server hanged and Dovecot LMTP proxy server started logging panics/assertions. Core dumps were disabled unfortunately, so I don't know if this is helpful at all: Dec 29 15:41:58 lmtp(8853): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Dec 29
2013 Mar 25
1
Unresponsive nodes with no pending task in the dashboard
Hi, Since this morning all nodes are showing as unresponsive. I have faced a similar error before and the problem was fixed restarting the dashboard-workers as there were many pending task in the puppet dashboard. I am using Puppet Enterprise 2.7.1 version. I have already checked/done: * Restarted the puppetmaster server * Check that puppet-dashboard-workers are working * Time is synced
2010 Sep 23
1
Expunged GUID mismatch for UID error
Hi, we have upgraded from v2.0.1 to v2.0.3 yesterday, trying to solve the "dovecot-uidlist: Duplicate file entry" errors. Now, at the moment, we don't get these errors, but when I try to expunge mails from my trash folder I get a lot of errors: Sep 23 14:24:51 imap1 dovecot: imap(user): Error: Mailbox Trash: Expunged GUID mismatch for UID 20193: 442b5ef0c3d3bf3cf4cb619944dce8e4
2008 Aug 25
2
smartd
last night I checked the log messages on the server Dell PE2950 6xSAS 146G I found the smartd running , I did not request such daemon [root at PowerEdge1 pons]# tail -f /var/log/messages Aug 25 08:27:30 PowerEdge1 smartd[8039]: Home page is http://smartmontools.sourceforge.net/ Aug 25 08:27:30 PowerEdge1 smartd[8039]: Opened configuration file /etc/smartd.conf Aug 25 08:27:30 PowerEdge1
2012 Jul 18
5
See puppet output in stdout when running --no-daemonize inside a bash script
I''m simply trying to run puppet inside a bash script but I''m not seeing any output. #!/bin/bash puppet master --mkusers --autosign --verbose --no-daemonize Is there an I/O redirection incantation I''m missing? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit
2010 Jul 19
1
director service and managesieve
Hi, the director service have implemented any support for managesieve-login?. I get the error: managesieve-login: Error: proxy: host not given: user=<xxx>, method=PLAIN, ... any workaround? thanks Xavier
2010 Jul 07
2
dovecot director service
hi, we are using the dovecot-rc1 version, and we are testing the director service, as there is little documentation on this service, a pair of questions.. if i'm not wrong, the proxy_maybe it's not implemented, yet? will be soon? this limitation does not allow use the same two directors servers like mail backend servers? the fairlure of one director server it's automatically
2010 Aug 04
1
doveadm director remove error
Hi, with the version 2.0.rc3, when I try to remove a mail server from director list, get this error: doveadm director remove 10.180.188.21 (null): doesn't exist but the other commands are working without problem ... doveadm director status mail server ip vhosts users 10.180.188.21 100 2 10.180.188.22
2010 Aug 12
1
sessions accounting and monitoring
Hi, we would have some accounting/monitoring of pop and imap sessions in our dovecot servers, which are the 'best' and fair way to do it? using some post-login scripts, parsing the log file, using netstat ... I know in the 2.0 version exists the doveadm who, but only relates to imap sessions... some recommendations? thanks Xavier
2010 Aug 17
1
pigeonhole and utf-8 error
Hi, now, I'm working with the last version of dovecot and pigeonhole sieve, and when apply a sieve filter on a new message, and it try to move this mail to a folder with special character like accent give me the error 'mailbox name not utf-8: ...' >Aug 17 09:22:40 imap1 dovecot: lmtp(19629,miel): Error: kea6K484akytTAAAJBW4rA: sieve: msgid=
2010 Aug 16
5
pigeonhole
Hi, I'm trying to compile the last mercurial release of dovecot-pigeonhole 2.0 and get this error: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/kerberos/include -o .libs/sievec sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so
2013 Mar 20
1
network neighborhood
Hello: I would like to know what is wrong in my configuration. I can't see this server in network neighborhood. samba 3.5.6 joined to my active directory domain. [global] # message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' & security = ADS netbios name = dos realm = EPEPM.CUPET.CU password server = ad.epepm.cupet.cu workgroup =
2020 Jul 09
4
AD Users on Linux Laptop
Hai Rowland, Maybe i didnt understand your reply that well, but why would you change it. All (linux) users have minimum_uid=1000 and start at 1000. All (windows) users (samba) are above minimum_uid=1000 So in my optinion, you should not be needed to change this. Unless your users start below 1000. Also cat /etc/adduser.conf shows ( For Debian/Buster ) # FIRST_[GU]ID to LAST_[GU]ID