Occasionally, I see something mentioned about tracing a particular
cyrus process to determine what's going on (or wrong, as the case
may be). How is this done? I'm not getting very far at resolving
my particular problem, so I'd like to know what the proxyd process
thinks it's doing each time it spawns a new connection to itself. Rob On 7/1/11 9:10 AM, Robert Spellman wrote: We have recently upgraded to cyrus 2.4.6. Our environment includes a server running as a murder server, four back end mailstores, and two front end servers. If we mistakenly create a user mailbox on one of the front end servers using cyradm, and then try to manage it (dm, sam, info, lm), cpu load on the front end server increases until the box is unusable. Syslogs show the user cyrus (our admin user) logging in over and over, each time creating a new proxyd process, which explains the high cpu load. |
begin:vcard fn:Robert Spellman n:Spellman;Robert org:Bates College;Information and Library Services adr;dom:;;110 Russell Street;Lewiston;Maine;04240 email;internet:rspell@xxxxxxxxx title:Assistant Directory, Network Services tel;work:207-786-6422 note;quoted-printable:0100011101101111001000000101001001100101011001000101001101101111011110000= 0100001=0D=0A= url:http://www.bates.edu/ version:2.1 end:vcard
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/