> i try to connect to my POP server (vpopmail/qmailadmin) :
[...]
> -ERR aack, child crashed
> Connection closed by foreign host.
I've found there are any number of things that can cause this, and I
couldn't discover what it was until I traced (strace/truss/whatever) the
processes. For example, using the sample script from the FAQ:
env - PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver 0 pop-3 /var/qmail/bin/qmail-popup orbital.inter7.com \
/path/to/strace -o /tmp/logfile \
/home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir
I left the background operator off, because you will likely not want
to leave this running for everyone to connect to and fill your
/tmp/logfile :)
Line 4 will be an addition. Run that, connect and try to authenticate,
then check the log file (/tmp/logfile). Look for things like "file not
found" or "segmentation fault" or something.
In one instance, the tcprules path compiled into vpopmail was off.
- Check your arguments to configure when you compile very carefully.
- 'strings vchkpw' is a good way to look at the paths too. Search for
"tcprules" and make sure the path is right, and search for your tcprules
file (mine was called tcp.smtp, but I had it typoed etc.smtp). If
you've typoed either of them, just look at all the strings. Eg:
strings vchkpw | less
In another instance, I had the path to the qmail-pop3d server wrong (yes,
I am a horrible typer). Check your startup script, and make sure things
are where they are supposed to be. Try running the programs by hand with
the paths you have in the script, and also the PATH you have in the
script if you use any relative pathnames. Eg, under bash:
# PATH="/var/qmail/bin:/usr/local/bin" vchkpw
If you used a relative path for the vchkpw program, and the above line
fails (dependant on your startup script), then you have a problem with the
path to vchkpw. Try that for each program being called.
In yet another instance, vchkpw was segfaulting from a corrupt cdb
database (I assume that, since clearing the database and recreating fixed
it).
Lots of things to try. I couldn't get vpopmail to log this stuff on its
own (is it possible? If not, can it be?), so you may have to use
3rd-party tools.
Ken, could a "troubleshooting" page be started? Maybe referenced in the
FAQ under "What if something goes wrong?" or something? I would have
found that immensely helpful, as would many others judging by the list
archives.
mark
