Matteo Mattei

Hello, my name is Matteo Mattei and this is my personal website. I am computer engineer with a long experience in Linux system administration and web software development.

linkedin rss twitter google+ github facebook

How to transfer an entire website via ftp with recursive lftp

In these days I have to transfer some big websites from a server to another and the only way to do it was an FTP connection because the destination server did not provide any other type of access. Because of the number of files was big (about 12GB) I have created a little script to use with lftp opened into a screen session to don’t busy the terminal for days.

So I created a script called sendfiles.sh with the following content:

set ftp:ssl-allow no
open -u username,password example.com
mirror -c -R /source-path /destination-path
quit

Where the following fields are respectively:

username: user name for ftp access
password: password for ftp access
example.com: ftp destination server
source-path: source path on local server
destination-path: remote path on the ftp (where / is the ftp rootdir)

To run the script is sufficient to open a screen session (if you want to leave the process in background on the source server) and issue this command:

lftp -f sendfiles.sh

Install imagemagick with PHP imagick extension on CentOS

To install imagemagick with PHP imagick extension on Linux CentOS you must follow these steps:

yum install ImageMagick
yum install ImageMagick-devel
pecl install imagick

If you have an error like this:

root@myhost [~]# pecl install imagick
downloading imagick-3.0.1.tgz ...
Starting to download imagick-3.0.1.tgz (93,920 bytes)
.....................done: 93,920 bytes
13 source files, building
running: phpize
Configuring for:
PHP Api Version:         20090626
Zend Module Api No:      20090626
Zend Extension Api No:   220090626
Please provide the prefix of Imagemagick installation [autodetect] :
building in /var/tmp/pear-build-root/imagick-3.0.1
running: /root/tmp/pear/imagick/configure --with-imagick
checking for egrep... grep -E
checking for a sed that does not truncate output... /bin/sed
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
ERROR: `/root/tmp/pear/imagick/configure --with-imagick' failed

Look at your /tmp folder… pretty surely it is mounted with noexec flag. Remount it without noexec and retry:

mount -o remount,rw /tmp

At the end of the installation, create an inclusion file for imagick.so module and restart apache:

echo "extension=imagick.so" > /etc/php.d/imagick.ini
/etc/init.d/httpd restart

Test the correct load of the imagick module with:

php -m | grep imagick

MySQL error 1153 in max_allowed_packet

Today I have got an anomalous error during a database import on mysql:

ERROR 1153 (08S01) at line 3854: Got a packet bigger than 'max_allowed_packet' bytes

To solve this is sufficient to edit the mysql configuration file (/etc/my.cnf on Linux) and fill a suitable big value for max_allowed_packet. In my case I set it to 100M.

Restart mysqld daemon and now the import will gone fine!


Script to remove .svn directories from a project

When you want to distribute your own sources without any .svn directories is sufficient to create an export of the project with this command:

svn export svn://path_to_repository projectname

But often I have not access to the repository, so I remove any .svn directory by hand.

For a couple of directories is not a problem but today I have a big project with hundreds of directories, so I created a little script to help me:

find . -type d -name .svn -exec rm -r '{}' \;

Replace “.” with your root folder.


Codesourcery G++ for ColdFire on OpenSuse 10.3 and some problems during IDE installation

In these days at work we are evaluating to buy a cross-compiler IDE of ColdFire developed by CodeSourcery G++. The development environment is substantially Eclipse optimized for that cross-compiler. During installation of the package we have discovered a lot of problems running the IDE installation and the next license installation.

From the official site must download the *.bin package that contains all the necessary, but after run, we have always obtained this error:

eclipse.bin: xcb_xlib.c:52: xcb_xlib_unlock: Assertion `c->xlib.lock’ failed

To solve this issue is sufficient to insert this line into ~/.bashrc:

export LIBXCB_ALLOW_SLOPPY_LOCK=1

and reload the file:

source ~/.bashrc

Well, proceed with installation and complete it. At the end a wizard license will be prompt but it was never appear to us, may be because of some problem about the MAC address of our virtual machine (we work under vmware). So, we have prepared a new computer with native Linux, put it out of the net (probably the license evaluation file it will be downloaded directly from Internet during installation), waiting the wizard appear, download the license from CodeSourcery site by hand and import it to the wizard itself.

Only after all these fix and tries we were finally able to work with the new development environment. Unfortunately, using it we have discovered that sometimes Eclipse crashes with no sense and we have not yet understand why.


OpenSuse 10.3 CD and DVD with fault installer? Reinstalling the bootloader!

Today I tested the new OpenSuse 10.3 with KDE both in CD and DVD version on an old Packard Bell Desk Pro. After a long wait during installation, at automatic reboot it will be prompt a classic black screen with the message “Operative System not present”. After a vanished search on the net looking for some informations, I thought that the installer was failed to install the bootloader and so I have just tried to do it manually. Here there are all the steps I follow:

  • Boot OpenSuse installation CD/DVD and enter in Recovery mode
  • Run grub ed enter in its own shell
  • From here run these commands:
grub> root (hd0,1)
grub> setup (hd0)
grub> quit

Where:

  • hd0,1 => sda2
  • hd0 => sda </li>

Restart the system and magically the installation will go on.