similar to: pam_start() failed: system error

I would guess this is unlikely to be dovecot's fault, but I'm wondering if anyone has any ideas of what might have happened based on the evidence. My best guess is some kind of resource limit was reached but I don't see any evidence in the logs, and the condition is now gone. Suddenly this morning, one (and only one) of my dovecot servers decided to start failing all logins since

Hi, I am running dovecot with postfix and OTRS2 on a fresh Ubuntu 8.10 Server system. OTRS2 is configured to poll new email to otrs-incoming at localhost via POP3 every 5 minutes. It works, but after approximately 20 hours it suddenly stops working and only a restart of dovecot helps. The outage starts at different times during night (00:15 on Thursday, 1:15 on Friday, 3:20 on

Just setup a new server on the weekend with Ubuntu 8.10 beta, and Dovecot 1.1.4. Every now and then, the IMAP server dies, and won't let users authenticate. It happens about once or twice a day. In /var/log/mail.log, you can see dovecot complaining about critial errors: Oct 21 14:46:16 tachikoma dovecot: imap-login: Login: user=<jason>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS

I'm running SVM from e1071 package on a data with ~150 columns (variables) and 50000 lines of data (it takes a bit of time) for radial kernel for different gamma and cost values. I get a very large models with at least 30000 vectors and the prediction I get is not the best one. What does it mean and what could I do to ameliorate my model ? Jerzy Orlowski

Hello, I'm now dealing with funny problem. I try to use Dovecot (2.1.rc1, actually) and mbox format to store old mailing, to keep logic of "one folder = one file". If I'd choose Maildir, I'd be able to create hierarchical folders (like "OldMail -> Maillists -> Dovecot"), and in fact on disk such a folders would be stored as real folders with dots in

>From /var/log/auth.log (Dovecot 1.1.4 on Ubuntu 8.10): Feb 10 08:29:06 home dovecot-auth: PAM unable to dlopen(/lib/security/pam_ck_connector.so): libdbus-1.so.3: failed to map segment from shared object: Cannot allocate memory Feb 10 08:29:06 home dovecot-auth: PAM adding faulty module: /lib/security/pam_ck_connector.so English, please? :) Strangely, it seemed to disappear after increasing

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Running Dovecot 1.1.3 and after dovecot has been running for awhile it will just stop authenticating. Only fix is to stop and restart dovecot. Here is the errors in the logs: ct 4 09:34:32 goku dovecot: [ID 107833 mail.info] auth-worker(default): pam(KVogel22,74.125.78.25): lookup service=dovecot Oct 4 09:34:32 goku dovecot: [ID 107833

Howdy, Googling: dovecot: auth-worker(default): pam_start() failed: Critical error - immediate abort dobbeltganger dovecot: auth-worker(default): pam(user,1.2.3.4): lookup service=dovecot dobbeltganger out of memory [4543] returns just 3 references. Examining memory server side reveals use of virtual memory but not 100% OS: Ubuntu 14.04 client 10.04 server-side. Email client: Thunderbird

Hi, I'm going to migrate my company-mailserver to new hardware. I would like to take the opportunity to archive some older mail. But I would like to have it still accessible, would this be possible with dovecot ? I mean, I would like to put that older mail from different users (I got about 50 users) on some read-only media but mount that media in the users mail-dirs. That way I will have

> > > Another nice feature to add would be a "bandwidth" limit (so just a new > > > <limit> type entry). If you are running icecast2 on linux you can handle bandwidth limitations using QoS more specificly iproute2. That way icecast2 doesnt have to take up extra resources to handle bandwidth limitations. resources here cbq bash script

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi In connection.c arround line 847 icecast2 does: if (global.clients >= client_limit) { client_send_504(client, "The server is already full. Try again later."); global_unlock(); return; } Then just a little bit later, does the same thing in the if (source) {} block. Is this code

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 13 Feb 2004, Dave St John wrote: > I think that would be a good feature to add in icecast2, dont get me wrong, > im just saying with QoS > you have far much more flexibility in handling bandwidth. > tcp/ip packets can be marked with iptables and then ran threw tc which you > could then prioritize your packets You mean by using

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 13 Feb 2004, Geoff Shang wrote: > Mihai RUSU wrote: > > > Another nice feature to add would be a "bandwidth" limit (so just a new > > <limit> type entry). > > Problem with this is, what do you do once the limit has been reached? Who > do you kick? Or do you just not allow anymore listeners? I

I think that would be a good feature to add in icecast2, dont get me wrong, im just saying with QoS you have far much more flexibility in handling bandwidth. tcp/ip packets can be marked with iptables and then ran threw tc which you could then prioritize your packets set a limit and a burst for variable bitrates. (http://svana.org/kleptog/Packet-Shaping-HOWTO.txt) I know there isnt any "drop

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I will need to find a solution for server side limit of clients bandwidth depending on their IPs (because we have very fast local connections with local ISPs and slow "external" connections with the rest of the Internet). Initially I think I'll just start 2 icecast servers (one for "local" clients, one for

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 13 Feb 2004, Dave St John wrote: > > > > Another nice feature to add would be a "bandwidth" limit (so just a > new > > > > <limit> type entry). > If you are running icecast2 on linux you can handle bandwidth limitations > using QoS > more specificly iproute2. You mistunderstood me. No, I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I have recently downloaded icecast 2 (I am an old icecast 1.x user) and tried to use it with my ices 0.2.3 (which works on icecast 1) but fails on login. Also I have tried with MuSe 0.8.1 and same error too. After some digging into the sources I found the problem to be with _check_pass_icy() which receives a "strange" pass to compare

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 16 Jan 2004, Deven Phillips wrote: > Okay, > > I am using libshout to stream to a NullSoft Shoutcast server. I am > using libmad and libmp3lame to do re-encoding on the fly. I am streaming > to the server (currently) with shout_send_raw(). When I try to use > shout_metadata_add(), I get a segfault in strdup(). Anyone have

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I have started to add bandwidth <limit> option to icecast. My ideea is to compute the current bandwidth by estimation on each sock_write*() call. Something like this: 1. initially we set kbps = 0, kbps_time = now and kbps_bytes = 0 2. after some time, a sock_write*() function is called which in turn calls sock_kbps_update(nobytes);

Hello List, I have a question about dovecot-1.1.0-beta3 but first I'll ramble a little bit: Recently I upgraded a 0.99 installation of dovecot to 1.0.5. All went relatively smoothly until the dovecot-auth process began returning "out of memory" after a day. There is a rather large user base here. The current setup is using passdb pam with blocking=yes, with pam_ldap.so handling