similar to: Login processes in Dovecot

Hello, I have configuration question. Running FreeBSD 9.0 / AMD64 / Dovecot 2.1.8 version and cannot get over 1024 processes. I`ve increased process_limit in imap and pop3 and still have messages in syslog like: maxproc limit exceeded by uid 89, please see tuning(7) and login.conf(5). Did I forget to increase some other value? System values are higher - kern.maxprocperuid: 8192 and

Hello, I still cannot get dovecot running with more then 1000 processes, but hard limit is 8192 per user in box. I tried everything, including modifying startup script of dovecot to set ulimit -u 8192. Could it be some dovecot bug or dovecot<>freebsd bug? I also tried to set client_limit=2 in imap service to spawn more imap clients in one process, but still I am over 1000 processes with

Hello everyone, First of all, great job on the 4.8-R. We have been a long standing user of FreeBSD and are very happy with everything. Now my question. I am trying to stress test a new Dell PowerEdge server and find the limits of its hardware and my tuning. Here are the server stats: * 2x Xeon 2.8 with SMP compiled, hyperthreading NOT compiled in kernel * 4 GB of RAM, 8 GB of swap on Raid 1

Hi All, I just upgraded to the new 1.1rc5 from 1.0 that I had been using and it advised me to increase the file descriptor limit. I'm not sure how to do this. There is a command built into tcsh that allows me to do this called limit, but sudo limit 4224 doesn't work, and usually dovecot is started from the rc.local file if I recall right, and I'm not sure how to set this up from

I woke up to a frozen box this morning - it froze up a few more times before I got a handle on it. Basically, the box runs idle but refuses to do disk IO, or does it -very- slowly. Top shows processes stuck in 'ffsvget', 'inode', and 'vlruwk' state. I can get the box responsive again by setting sysctl kern.maxvnods=100000. It starts up with kern.maxnodes=36079. I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The chroot(2) man page describes a sysctl called 'kern.chroot_allow_open_directories' which controls whether a process can chroot() and is already subject to the chroot() syscall. It seems that this sysctl can be trivially changed from within a chroot'd process (ie: if that process has superuser privileges). Is this sysctl meant to

I've now seen this on two different VMs on two different ESXi servers (Xeon based hosts but different hardware otherwise and at different facilities): Everything runs fine for weeks then (seemingly) suddenly/randomly the clock STOPS. In the first case I saw a jump backwards of about 15 minutes (and then a 'freeze' of the clock). The second time just 'time standing

Hello, I have the following entries in /boot/loader.conf: kern.ipc.shm_use_phys="1" kern.ipc.semmns="500" kern.ipc.semmni="40" kern.ipc.semmap="500" which are set correctly. Unfortunately, the following two entries kern.ipc.shmmax="512000000" kern.ipc.shmall="65526" do not change the corresponding values according to

Hi, Anybody have success with postgresql 8.1.3 on a new Intel OS X box? All hints welcome, please! I installed postgres 8.1.3 via darwinports, and everything is great until the initdb step. Initdb fails on shmget saying it couldn''t allocate enough memory (see below). So, I edited /etc/rc and increased kern.sysv.shmmax from 4194304 to 41943040 (4MB to 40MB) After reboot and

Hi, For 3 days uptime serve about 40 client Windows workstation with traffic average 50 Mbps - 80 Mbps (Video streaming) running on FreeBSD system with 16 GB RAM already installed. # uname -smrv FreeBSD 12.1-STABLE FreeBSD 12.1-STABLE r364492 GENERIC amd64 # pkg info samba\* samba410-4.10.17 I got this produce error in /var/log/message, any clue for this problem? Sep 14 10:20:15 BEC-STG-P1

Hello, I was wondering if it was possible to limit user access on /proc without having to use securelevels. For some reason chmod 751 /proc (or 750) does nothing. Is this possible on FreeBSD 4.9 ? Can't find anything about it in the manual pages. Just want to prevent lusers from running: for file in /proc/*/cmdline; do cat $file; echo; done Greetz, Jimmy Scott

By default FreeBSD 7.0 shipped with the sysctls set to: kern.maxfiles: 12328 kern.maxfilesperproc: 11095 We recently bumped up against these limits in an unfortunate way and we are going to raise them. I have some questions: * why are the numbers set the way they are? They aren't round numbers, they aren't powers of 2. But they were arrived at somehow with planning and thought

Hello everyone, I am trying to tweak some of the sysctl tunables for the ix (ixgbe) driver in FreeBSD 9.2 since I am experiencing less than ideal performance and it seems like I can't find any: # sysctl -a | grep -i ixgbe device ixgbe I am running 9.2-RC4. Any input appreciated. Thanks, -- Rumen Telbizov Unix Systems Administrator <http://telbizov.com>

I finally got a 10G card that is recognized by FreeBSD (9.1-stable): ... ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.4.8> port 0xecc0-0xecdf mem 0xd9e80000-0xd9efffff,0xd9ff8000-0xd9ffbfff irq 40 at device 0.0 on pci4 ix0: Using MSIX interrupts with 9 vectors ix0: RX Descriptors exceed system mbuf max, using default instead! ix0: Ethernet address: 90:e2:ba:29:c0:54

I recently put together a new machine w/ a SuperMicro H8SCM and an AMD Opteron 4228 HE... I've having an issue where the clock on the machine skips around... The wierd part is that it's very sudden when it happens... ntp sometimes brings it back, but it can't when the clock gets too far ahread (1000 seconds), ntp dies... In order to catch it happening, I ran a sleep 60 loop

Am 26.01.2015 um 02:13 schrieb Leander Sch?fer: > I just checked my ulimit again and it really seems like it has more > than enough - so I still don't understand what I've configured wrong > here ;/ > > root at WM-01 [~]$ su -m dovecot -c "ulimit -a" > socket buffer size (bytes, -b) unlimited > core file size (blocks, -c) unlimited > data

Hi, I got this error when i tried to type for some of those. "sysctl: unknown oid...." any idea.. my server seems to be very lagged, where else the network connection seems fine, i think BSD itself as my other redhat box is fine. What else can i do to get optimum protection. Thanks. ----- Original Message ----- From: "Per Engelbrecht" <per@xterm.dk> To:

I've figured this one out... Just wanted to get it into the dovecot mailing list archive so that somebody in the future might find it if they need it. Running Dovecot on Mac OS X 10.4.11 and using LaunchDaemon to start. Following a system crash, dovecot failed to restart with this in the system log... Feb 4 10:04:29 G520X2 launchd: org.dovecot: exited with exit code: 89 Feb 4

I first met this problem when our (60 students) internetgateway refused to boot its new kernel, it was a 4.7-RELEASE. Then i loaded the old kernel and went home to check if my 4.8-STABLE does likewise. And the answer was yes! Both kernels were GENERIC + these options taken from the dummynet man pages: options DUMMYNET options NMBCLUSTERS options HZ When i boot the machine

We have 10 SuperMicro PDSMi+ 5015M-MTs that are panic'ing every few days. This started shortly after upgrade from 6.2-RELEASE to 6.3-RELEASE with freebsd-update. Other than switching to a debugging kernel, a little sysctl tuning, and patching with freebsd-update, they are stock. The debugging kernel was built from source that is also being patched with freebsd-update. These systems are