2019-09-20 - hschneider, Admin
Cookie Disclaimer: This forum uses only essential, anonymous session cookies (xmailforum*), nothing to be scared of.
Printable Version of Topic
Click here to view this topic in its original format |
XMail Forum > XMail Queue Manager > XQM Agent Installation Guide |
Posted by: hschneider Jul 10 2003, 11:11 AM | ||
|
Posted by: hschneider Sep 6 2003, 06:46 AM |
System: Redhat 9.0 Symptom: Openssl is installed and /usr/lib is in my PATH, but I still get ImportError: libcrypto.so.0.9.6: cannot open shared object [...]" Solution: Create a symbolic link from version 0.9.6 to your current lib version, e.g. ln -s /lib/libcrypto.so.0.9.7a /lib/libcrypto.so.0.9.6 Don't confuse /lib with /usr/lib here. RedHar searches /lib at first! |
Posted by: hschneider Sep 18 2003, 11:54 AM | ||
System: All Linux platforms Symptom: Trying to start ./xqmagent results in a Python backtrace dump:
Solution: The Agent does not find its additional files coming with the original archive. Make sure that all *.so files reside in the same folder like xqmagent and that their permissions are set properly. Do NOT copy any of its .so files to another location. |
Posted by: hschneider Sep 26 2003, 12:20 PM |
System: Some Linux platforms, e.g. RedHat 9. Symptom: The Agent cannot restart XMail server, even after defrosting. Solution: Upgrade to Agent >= 1.30 Check your your /etc/xqmagent.conf, if STARTSCRIPT holds a valid path to your XMail startscript. Since Agent 1.30 starting and restarting the server is done the save way via XMail's startscript. This requires the full path to your startscript in /etc/xqmagent.conf. E.g. STARTSCRIPT=/etc/rc.d/init.d/xmail |
Posted by: hschneider Nov 14 2003, 09:59 AM |
System: RedHat 9.0 Symptom: XQM hangs, when querying the queue with the Agent. Solution: The way how threads are handled by the kernel has changed since RedHat 9. See http://www.redhat.com/docs/manuals/linux/R...ease-notes/x86/ for details. Since XQM and XQMAgent use threads extensively, they are both affected by this change. For better compatibility, you should wrap them into a startup script which forces the system to emulate the old thread scheme: ------------------------------ #!/bin/sh export LD_ASSUME_KERNEL=2.4.1 ./xqmagent # or ./xqmwin ------------------------------ Don't forget to do chmod 755 scriptname |
Posted by: hschneider Nov 24 2003, 07:44 AM |
System: Linux Symptom: The Agent does not restart XMail server after a 'Stop Server' or 'Defrost'. Solution: You use an older /etc/xqmagent.conf file. Just add STARTSCRIPT=/etc/init.d/xmail (or whatever your startscript is) to the .conf file. |
Posted by: hschneider Nov 25 2003, 08:37 AM |
System: Tawie Linux Symptom: Openssl is installed, /usr/lib is in my PATH and I created soft links for libssl and libcrypto, but I still get ImportError: libcrypto.so.0.9.6: cannot open shared object [...]" Solution: Tawie seems not to accept soft links to access libraries. Therefore do some real copies. E.g. if you have installed openssl 0.9.7: cd /usr/lib cp libssl.so.0.9.7 libssl.so.0.9.6 cp libcrypto.so.0.9.7 libcrypto.so.0.9.6 |
Posted by: hschneider Jan 22 2004, 02:42 PM | ||
System: Solaris 8 and lower. Symptom: Starting ./xqmagent results in
Solution: Install the postinstall fix from http://xmail.marketmix.com |
Posted by: hschneider Apr 20 2004, 10:32 AM | ||
System: FreeBSD 5.0 and higher Symptom: Starting ./xqmagent results in
Solution: You have to install the FreeBSD 4.6 compatibility layer: CD1/misc/compat4x-XXX-5.0.XXXXXX |
Posted by: hschneider Apr 20 2004, 10:54 AM | ||
System: FreeBSD 5.0 and higher Symptom: Starting ./xqmagent results in
Solution: This seems to be a bug on the FreeBSD 5 development branch. Here its fix: cd /lib ln -s libutil.so.4 libutil.so.3 |
Posted by: hschneider Jul 8 2004, 09:19 AM |
System: NetBSD Symptom: XQM dies with a coredump after being contacted by XQM. XQM says 'Agent not reachable'. Solution: Start the Agent this way: ./xqmagent --debug >/dev/null & This avoids it's process to be detached the usual way, which causes problems with Python's threading engine on this platform. |
Posted by: hschneider Jan 26 2005, 06:36 PM |
System: Debian (and maybe other Unix flavours) Symptom: Application startup fails with: socket.gaierror (-2; 'Name or service not known') Solution: This error is related to DNS resolution. It comes directly from Python's socket support and is caused by a failed resolution on OS level. Use fixed IP addresses in XQM's (or the Agent's) config. Additionally you should check your DNS configuration. |
Posted by: hschneider Dec 10 2005, 08:42 AM | ||
System: All Linux and BSD systems with glibc < 2.2 Symptom:
Use XQMAgent/generic which runs on any system with Python 2.3x installed. Download the file attached, unpack and start with python xqmagent.pyc or python xqmagent.pyc --debug Python can be found here: http://www.python.org Use Version 2.3.x, not 2.4.x if possible. |