• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Horde redirect.php and Segmentation fault (11) problem

zooming

Regular Pleskian
Hello,

I'm having problems with Horde.

It has worked fine for months, then it stopped, and I don't know why.

After the login, the browser tries to download the redirect.php file (an empty file).

A record is placed in /var/log/httpd/error_log when this happens:

[notice] child pid 9934 exit signal Segmentation fault (11)

After some research, I have found the line that triggers this error in the redirect.php file:

IMP_Session::createSession($imapuser, $pass, $sessArray['server'], $sessArray))

Looking for this function name in Google, I have found some Bug reports:

http://gablog.eu/online/taxonomy/term/36

http://bugs.horde.org/ticket/?id=711

http://groups.google.com/group/mail...ash:+Unable+to+look+up+user+name&rnum=1&hl=en

http://www.nabble.com/Unable-to-login-after-install-td9500720.html

Everything in these posts are related to some "IMAP toolkit" or Horde running chrooted and "/etc/password" file access.

But until now I haven't found what has trigged this problem, since it was working fine, and I haven't upgrade or changed anything, and I haven't fixed it yet either.

Can you help me?

Thank you.
Alexandre
 
This problem cropped up for us, too. The problem for us was the Apache file descriptors restriction, aparently because of the number of virtual hosts on the server. This fixed it for us:

mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e "replace into misc (param,val) values ('apache_pipelog', 'true')"
/usr/local/psa/admin/sbin/websrvmng -v -a
 
Back
Top