ISPConfig installation fails

Discussion in 'Installation/Configuration' started by the_dude, May 10, 2006.

  1. the_dude

    the_dude New Member

    Hello

    I'm trying to install ISPConfig on a SuSE Linux 10.0. I followed the steps described in http://www.howtoforge.com/perfect_setup_suse_10.0.

    The install goes fine until the "Configuring extensions" section where it fails with the following message:

    Configuring extensions
    .
    .
    .
    checking for MySQL support... yes
    checking for specified location of the MySQL UNIX socket... no
    checking for MySQL UNIX socket location... no
    checking for mysql_close in -lmysqlclient... no
    checking for mysql_errno in -lmysqlclient... no
    configure: error: Try adding --with-zlib-dir=<DIR>. Please check config.log for more information.
    ERROR: Could not configure PHP
    cd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    mv: cannot stat `binaries/aps.tar.gz': No such file or directory
    mv: cannot stat `binaries/spamassassin.tar.gz': No such file or directory
    mv: cannot stat `binaries/uudeview.tar.gz': No such file or directory
    mv: cannot stat `binaries/clamav.tar.gz': No such file or directory
    mv: cannot stat `binaries/cronolog': No such file or directory
    mv: cannot stat `binaries/cronosplit': No such file or directory
    mv: cannot stat `binaries/ispconfig_tcpserver': No such file or directory
    mv: cannot stat `binaries/zip': No such file or directory
    mv: cannot stat `binaries/unzip': No such file or directory
    tar: spamassassin.tar.gz: Cannot open: No such file or directory
    tar: Error is not recoverable: exiting now
    tar: Child returned status 2
    tar: Error exit delayed from previous errors
    mv: cannot stat `spamassassin': No such file or directory
    tar: uudeview.tar.gz: Cannot open: No such file or directory
    tar: Error is not recoverable: exiting now
    tar: Child returned status 2
    tar: Error exit delayed from previous errors
    mv: cannot stat `uudeview': No such file or directory
    tar: clamav.tar.gz: Cannot open: No such file or directory
    tar: Error is not recoverable: exiting now
    tar: Child returned status 2
    tar: Error exit delayed from previous errors
    mv: cannot stat `clamav': No such file or directory
    tar: aps.tar.gz: Cannot open: No such file or directory
    tar: Error is not recoverable: exiting now
    tar: Child returned status 2
    tar: Error exit delayed from previous errors
    ./setup2: line 794: ispconfig_tmp/php/bin/php: No such file or directory
    ERROR: Das mitgelieferte PHP-Binary funktioniert auf Ihrem System nicht! Die Installation bricht hier ab!

    Since I am a newbie to the subject, any help would be appreciated!
     
  2. Norman

    Norman HowtoForge Supporter

    I think I already replied to this question earlier...
    doesnt look like you are running as a user with enough privileges to read those files.
     
  3. falko

    falko Super Moderator

    As Norman said, you must run this as root. And then make sure you have zlib installed.
     
  4. silent

    silent New Member

    Hello the_dude :)

    I had the same error yesterday while installing on Fedora Core 5.

    Thanks to the @xinefnarg's post, I have solved it.
    http://www.howtoforge.com/forums/showthread.php?t=3371&highlight=ERROR%3A+PHP

    Hope this helps to you also.

    My mistake was to untar the ispconfig tarball in to the directory "/root/ispconfig".
    Please use as a different directory other than this.

    I am not sure but during the setup process the installaion files were removed.
    In fact the message was correct:
    Code:
    mv: cannot stat `binaries/aps.tar.gz': No such file or directory
    ...
    ./setup2: line 794: ispconfig_tmp/php/bin/php: No such file or directory
    

    May be Falko can modify the setup for the users like me, so the setup can give a warning at the beginning about "Thou shall not use the directory as "ispconfig" to untar the tarball in!"
    :)

    May be there is a warning somewhere on the documentation, and I missed it.

    Have a nice day.
     

Share This Page