I have seen problems like that after replacing the server by a new one: When I 
falsely copied over the complete /home/vpopmail and /var/qmail directories from 
the old systems, I overwrote the newly compiled binaries on the target 
systems...

Johannes

Am 15.02.12 16:38, schrieb Dan McAllister:
I know I'm johnny-come-lately on this one, but have you checked to make sure 
your filesystem (whichever one holds /tmp) isn't full?

I tend to get these errors when I've accidentally let /var (which is the home 
of /var/tmp -- which is the target of my sym-link /tmp) get full....

Dan
IT4SOHO

On 2/14/2012 11:38 PM, Angus McIntyre wrote:
Délsio Cabá wrote:
Try to upgade gcc and recompite it again
gcc seems to be the latest approved version for CentOS. QMT was built with
that version.

I'm also having trouble with POP. The logs don't show any problems (except
for a 'status 256' response) but no mail is transferred.

When I manually run a POP session, I get:

/home/vpopmail/bin/vchkpw: error while loading shared libraries:
libresolv.so.2: failed to map segment from shared object: Cannot allocate
memory
-ERR unable to write pipe
Connection closed by foreign host.

Again, raising the softlimit on the pop3 supervisor doesn't seem to solve
this problem.

Do I need to do anything after editing the 'run' file to raise the
softlimit? I've been simply restarting qmail with 'qmailctl restart', but
perhaps something else is needed to get the changes to take effect?

Angus

--
Johannes Weberhofer
Weberhofer GmbH, Austria, Vienna

---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
     If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
    Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]


Reply via email to