Open Tech Notes

New blog

I am starting a new blog now

PROPFIND request failed on ‘/path/to/repo’ and PROPFIND of ‘/path/to/repo’: 301 Moved Permanently

There are a lot of reasons cause this problem in SVN client. But the problem is in server side.
Here is a comprehensive explain about this issue :
http://www.checkupdown.com/status/E301.html

For my case, whenever I create a folder under /opt/lampp/htdocs and if the name is same with ‘path/to/repo’ , it will cause this error message:

Error: PROPFIND request failed on ‘/reponame’ 
Error: PROPFIND of ‘/reponame’: 301 Moved Permanently (http://www.vancouvereasy.com) 

Let Apachefriends supports Pspell extension for PHP 5.2.5

Apachefriends is great project that facilitate the configuration of LAMP,  but it’s latest version(1.6.5a) does not support Pspell extension for PHP which is required in our development team.

Fortunately, Apachefriends project provides a development package so that I can take advantage of it to re-compile the PHP. My Linux version is CentOS 4.5 final, all the steps are pretty straightforward:

1) Download latest apachefriends packages (both working package and development package) and install them.
2) Download PHP 5.2.5 and untar it
3) yum install pspell-devel
4) Download libbz2 and install it
5) Hack the PHP configuration
    
   This is the original apachefriends’s php configuration

./configure –prefix=/opt/lampp –with-apxs2=/opt/lampp/bin/apxs –with-config-file-path=/opt/lampp/etc –with-mysql=/opt/lampp –enable-inline-optimization –disable-debug –enable-bcmath –enable-calendar –enable-ctype –enable-dbase –enable-discard-path –enable-exif –enable-filepro –enable-force-cgi-redirect –enable-ftp –enable-gd-imgstrttf –enable-gd-native-ttf –with-ttf –enable-magic-quotes –enable-memory-limit –enable-shmop –enable-sigchild –enable-sysvsem –enable-sysvshm –enable-track-vars –enable-trans-sid –enable-wddx –enable-yp –with-ftp –with-gdbm=/opt/lampp –with-jpeg-dir=/opt/lampp –with-png-dir=/opt/lampp –with-freetype-dir=/opt/lampp –without-xpm –with-zlib=yes –with-zlib-dir=/opt/lampp –with-openssl=/opt/lampp –with-expat-dir=/opt/lampp –enable-xslt=/opt/lampp –with-xsl=/opt/lampp –with-dom=/opt/lampp –with-ldap=/opt/lampp –with-ncurses=/opt/lampp –with-gd –with-imap-dir=/opt/lampp –with-imap-ssl –with-imap=/opt/lampp –with-gettext=/opt/lampp –with-mssql=/opt/lampp –with-sybase=/opt/lampp –with-interbase=shared,/opt/interbase –with-mysql-sock=/opt/lampp/var/mysql/mysql.sock –with-oci8=shared,instantclient,/opt/lampp/lib/instantclient –with-mcrypt=/opt/lampp –with-mhash=/opt/lampp –enable-sockets –enable-mbstring=all –with-curl=/opt/lampp –enable-mbregex –enable-zend-multibyte –enable-exif –with-bz2=/opt/lampp –with-sqlite=shared,/opt/lampp –with-libxml-dir=/opt/lampp –enable-soap –enable-pcntl –with-mysqli=/opt/lampp/bin/mysql_config –with-mime-magic –with-pgsql=shared,/opt/lampp/postgresql –with-iconv –enable-dio –with-pdo-mysql=/opt/lampp –with-pdo-pgsql=/opt/lampp/postgresql –with-pdo-sqlite –with-ming=shared,/opt/lampp

Because we only use MySQL , so I remove other database support from it such as:

–with-pdo-pgsql=/opt/lampp/postgresql
–with-pgsql=shared,/opt/lampp/postgresql
–with-oci8=shared,instantclient,/opt/lampp/lib/instantclient
–with-interbase=shared,/opt/interbase

Of course, in order to support Pspell extension, add this at the end

–with-pspell=/usr

6) re-compile the php

Done!   

“ip route” causes problem

After I re setup the server, there are two weird things happened.

1) I use SSH remotely access the server, after I input the password, it took me about 20 seconds to login in.
2) some clients complained that they could not access the website whereas others could.

After dinner, I came across my friend’s home, in his computer, the website could not be accessible.

Then, I was thinking … he used different ISP, the ip address in his computer starts with 64 whereas mine starts with 24.

I login the server again and type "ip route" and found there was an entry forward all ip start with 64 to one special ip address.(who set this?)

After I deleted this ip route, the two problems above are gone!

Two hard drives failed at the same time on RAID5

Obviously, it is a huge disaster, 2 out of 3 hard drives failed in RAID5 coincidently at the same time. Fortunately, I have the backup, but still, it is painful to recovery every details.