Error: configure: error: Problem with libXpm.(a|so) or libX11.(a|so)
This happens most times when compiling with gd enabled for the first time. Reinstall X11 libraries and try again:
cd /usr/ports/x11/libX11/
make deinstall
make install
Archive for the ‘Apache’ category
configure: error: Problem with libXpm.(a|so) or libX11.(a|so)
December 7th, 2009EasyApache Fails Due to YUM Failing
November 15th, 2009EasyApache requires a working package manager to be able to run properly, as it needs to confirm several RPMs are up to date before proceeding with the build.
!! The server's system package manager, 'YUM', failed. !!
!!
This is the command that failed:
yum --exclude=kernel* -y install aspell aspell-devel automake19 gettext
libstdc++.x86_64 libpng-devel openssl libpng-dev zlib-devel autoconf261
libidn-devel gmake libidn libXpm openssl-devel automake coreutils patch
libltdl3-devel libltdl libopenssl0.9.7-static-devel libtool-ltdl-devel
libXpm-devel sed libXpm-dev lsof krb5-dev flex glibc-dev expat-dev krb5-devel
pspell-devel libstdc++-devel.x64_64 xorg-x11-devel libtool-ltdl libssl-dev
pam-devel libopenssl0-devel zlib1-devel expat-devel pspell libopenssl0-dev
expat glibc-devel gcc-c++ zlib bison libjpeg-devel libtool-libltdl-devel
libtool openssl-dev libopenssl0 libz-devel libjpeg-dev pam-dev fileutils
libltdl-devel libopenssl0.9.7-devel e2fsprogs-devel make libstdc++-dev.x86_64
libX11-devel gd cpp xorg-x11-dev gcc ssl-dev autoconf lex
!!
!!
Since EasyApache was unable to resolve it automatically you should:
1) Manually run the failed YUM command (shown above) via SSH
2) See if your particular error is addressed at
http://www.cpanel.net/support/could_not_ensurepkgs.htm
3) Resolve the YUM problem manually
4) Re-run EasyApache
!!
!! Please visit
http://www.cpanel.net/support/could_not_ensurepkgs.htm
for help with this error. !!
!! Restoring original working apache !!
First things first. Try running ‘yum -y update’ and see if it completes. You may see the following when running yum update.
error: rpmdbNextIterator: skipping h# 27 region trailer: BAD, tag 1507328 type 1507328 offset -1507328 count 1507328
error: rpmdbNextIterator: skipping h# 65 region trailer: BAD, tag 724250418 type 825833527 offset -740320047 count 842150704
error: rpmdbNextIterator: skipping h# 69 region trailer: BAD, tag 942410249 type 1952543335 offset -1702113073 count 842610488
error: rpmdbNextIterator: skipping h# 99 region trailer: BAD, tag 1814980474 type 4544080 offset -1598245200 count 1212502623
and so on and so on….
Then it’ll actually show packages that require updates, and experience a segmentation fault.
---> Package hotplug.x86_64 3:2004_04_01-7.10 set to be updated
---> Package fetchmail.x86_64 0:6.2.5-6.0.1.el4_8.1 set to be updated
--> Running transaction check
Segmentation fault
[root@vps ~]#
This means that your RPM database is corrupt, which is easily fixed with the following:
[root@vps ~]#rm -f /var/lib/rpm/__db.*
[root@vps ~]#rpm -vv --rebuilddb
Once that finishes, run ‘yum update’ again, and it should complete successfully. If so, you’re all set. Go ahead and retry your easyapache build.
How to install imagick for PHP
November 10th, 2009The imagick.so PHP module can’t currently be installed via PECL, due to it’s inability to write to /var/tmp. To get around that, you can install it manuall:
# yum install ImageM* netpbm gd gd-* libjpeg libexif gcc coreutils make
# cd /usr/local/src
# wget http://pecl.php.net/get/imagick-2.2.2.tgz
# tar zxvf ./imagick-2.2.2.tgz
# cd imagick-2.2.2
# phpize
# ./configure
# make
# make test
# make install
This will compile imagick.so, and move it to your extensions directory specified in php.ini. Now you’ll need to add the following to php.ini:
extension=imagick.so
and restart apache:
/scripts/restartsrv_httpd
suphp 500 error, Premature end of script headers
September 26th, 2009
[Sat Sep 26 22:02:33 2008] [error] [client 111.222.333.444] Premature end of script headers: phpinfo.php
[Sat Sep 26 22:02:33 2008] [error] [client 111.222.333.444] File does not exist: /home/username/public_html/500.shtml
First step: ensure that you’re using proper permissions on your files for suphp. Your php files should have 644 permissions, and ownership of the user whose home folder the files are in.
If ownership and permissions are correct, it could be a memory issue. I’ve found that some users who experience this error are running out of available memory for php to execute properly. You can try switching your PHP handler to cgi or fcgi, which will actually display an “out of memory” error in apache’s error_log, but suphp will not.
[Sat Sep 26 08:48:02 2009] [error] [client 111.222.333.444] Premature end of
script headers: php5
[Sat Sep 26 08:48:02 2009] [error] [client 111.222.333.444] File does not exist:
/home/username/public_html/500.shtml
[Sat Sep 26 08:48:02 2009] [error] [client 111.222.333.444] Out of memory
If you do have available RAM, but PHP isn’t able to use it, try increasing the RLimit value in httpd.conf and see if your script will execute then. If you look at “free” and you don’t have much free memory, you may need to upgrade your server or VPS.
no listening sockets available, shutting down
September 24th, 2009(98)Address already in use: make_sock: could not bind to address [::]:80
no listening sockets available, shutting down
Unable to open logs
First let’s see what process is listening on that port:
lsof -i :80
Once you see what process is listening, you can kill it off
kill PID
replacing PID with the process ID number.
