RE: [vchkpw] Problems upgrading from 5.2 to 5.4.0
I've turned domain quotas off, and the problem was solved. Thanks for helping. Hi all, I'm having some problems trying to upgrade my vpopmail 5.2 to 5.4.0. The compilation goes well (no errors at this stage), but after the instalation, just a few minutes later, the load of the server begins to get high, very high... :-(. When issuing a top, I see a lot of process of vdelivermail eating all cpu resources:
RE: [vchkpw] Problems upgrading from 5.2 to 5.4.0
Fernando Costa de Almeida wrote: Hi all, I'm having some problems trying to upgrade my vpopmail 5.2 to 5.4.0. The compilation goes well (no errors at this stage), but after the instalation, just a few minutes later, the load of the server begins to get high, very high... :-(. When issuing a top, I see a lot of process of vdelivermail eating all cpu resources: I bet you now have quota support enabled, and you did not before. Actually, I already had quota support enabled, but just for user accounts, not for the entire domain. That means that the first time vdelivermail attempts to deliver mail to an account it must scan all the existing mail to determine the file space being used. Can the new feature of domain quota be causing this behaviour too? Although I had enabled the domain quota support, I did not set any domain quota yet. Even in this case, will vpopmail still scan my domains in order to calculate these disk usages? You can either disable quota support, or just live with it. Once everyone has received their first new email their disk usage information will be cached, and the number of full directory scans will go way down. It is bad at first because every new message is to a user without cached disk usage information. Rick
[vchkpw] Problems upgrading from 5.2 to 5.4.0
Hi all, I'm having some problems trying to upgrade my vpopmail 5.2 to 5.4.0. The compilation goes well (no errors at this stage), but after the instalation, just a few minutes later, the load of the server begins to get high, very high... :-(. When issuing a top, I see a lot of process of vdelivermail eating all cpu resources: -- Last pid: 94268; load averages: 34.92, 14.57, 8.28 up 6+01:40:03 16:22:59 175 processes: 36 running, 119 sleeping, 20 zombie CPU states: 40.5% user, 0.0% nice, 58.0% system, 1.6% interrupt, 0.0% idle Mem: 76M Active, 300M Inact, 89M Wired, 23M Cache, 61M Buf, 12M Free Swap: 1500M Total, 348K Used, 1500M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 92591 vpopmail 62 0 2516K 1456K RUN 0:05 3.50% 3.47% vdelivermail 92083 vpopmail 61 0 2516K 1460K RUN 0:08 3.33% 3.32% vdelivermail 91842 vpopmail 61 0 2516K 1244K RUN 0:10 3.28% 3.27% vdelivermail 92320 vpopmail 62 0 2516K 1452K RUN 0:06 3.29% 3.27% vdelivermail 92588 vpopmail 62 0 2516K 1456K RUN 0:05 3.30% 3.27% vdelivermail 92773 vpopmail 63 0 2516K 1456K RUN 0:04 3.28% 3.22% vdelivermail 93178 vpopmail 62 0 2516K 1456K RUN 0:03 3.26% 3.08% vdelivermail 93464 vpopmail 62 0 2516K 1448K RUN 0:02 2.90% 2.49% vdelivermail 93366 vpopmail 61 0 2516K 1464K RUN 0:02 2.58% 2.29% vdelivermail -- My guess is that the bootleneck is in the filesystem, but I cant figure out how to avoid this.. Here is my configure command: ./configure --enable-tcpserver-file=/RAID0/vpopmail/etc/tcp.smtp --enable-auth-module=ldap \ --enable-roaming-users=y --enable-logging=p --disable-clear-passwd --enable-domainquotas=y \ --enable-md5-passwords=n --enable-file-locking=n --disable-users-big-dir /RAID0 points to a dedicated disk, where I put the queue and the archives related to roaming users (open smtp, tcp.cdb, etc), trying to achieve better IO performance My configuration is: FreeBSD 4.9-p4 Vpopmail 5.4.0 (was 5.2) OpenLDAP Qmail 1.03 Thanks in advance! ___ ALMEIDA, Fernando Costa de Computeasy Informtica www.computeasy.com.br BSD USER BSD050945 ICQ 72293951
Re: [vchkpw] Problems upgrading from 5.2 to 5.4.0
Fernando Costa de Almeida wrote: Hi all, I'm having some problems trying to upgrade my vpopmail 5.2 to 5.4.0. The compilation goes well (no errors at this stage), but after the instalation, just a few minutes later, the load of the server begins to get high, very high... :-(. When issuing a top, I see a lot of process of vdelivermail eating all cpu resources: I bet you now have quota support enabled, and you did not before. That means that the first time vdelivermail attempts to deliver mail to an account it must scan all the existing mail to determine the file space being used. You can either disable quota support, or just live with it. Once everyone has received their first new email their disk usage information will be cached, and the number of full directory scans will go way down. It is bad at first because every new message is to a user without cached disk usage information. Rick