ERROR: The PHP binary coming with ISPConfig does not work properly on your system! Th

Discussion in 'Installation/Configuration' started by shadowspank, Jan 24, 2008.

  1. shadowspank

    shadowspank New Member

    I cant seem to find what the problem is I had a running ISPconfig install I am upgrading from .18 to .19 I have fedora core 4 running I have never had any problems from what I am finding on the site people get this error when doing a brand new install and they missed a few things. I have checked and all the sites that have PHP are running and I also have databases setup and they are working fine and so is the email so what gives. I notcied the error with gcc so I checked that I have the current version here is how I checked that.

    [root@server1 install_ispconfig]# atp-get install gcc

    output: Reading Package Lists... Done
    Building Dependency Tree... Done
    gcc is already the newest version.
    0 upgraded, 0 newly installed, 0 removed and 12 not upgraded.

    I run sites for friends and Famley and was going to update everything and add a site that my mom wants to make but running into problems and now ISPconfig will not even run :( please help thanks

    Installing PHP SAPI module: apache
    [activating module `php5' in /root/ispconfig/httpd/conf/httpd.conf]
    cp libs/libphp5.so /root/ispconfig/httpd/libexec/libphp5.so
    chmod 755 /root/ispconfig/httpd/libexec/libphp5.so
    cp /root/ispconfig/httpd/conf/httpd.conf /root/ispconfig/httpd/conf/httpd.conf.bak
    cp /root/ispconfig/httpd/conf/httpd.conf.new /root/ispconfig/httpd/conf/httpd.conf
    rm /root/ispconfig/httpd/conf/httpd.conf.new
    Installing PHP CLI binary: /root/ispconfig/php/bin/
    Installing PHP CLI man page: /root/ispconfig/php/man/man1/
    Installing build environment: /root/ispconfig/php/lib/php/build/
    Installing header files: /root/ispconfig/php/include/php/
    Installing helper programs: /root/ispconfig/php/bin/
    program: phpize
    program: php-config
    Installing man pages: /root/ispconfig/php/man/man1/
    page: phpize.1
    page: php-config.1
    Installing PDO headers: /root/ispconfig/php/include/php/ext/pdo/
    checking build system type... i686-pc-linux-gnu
    checking host system type... i686-pc-linux-gnu
    checking target system type... i686-pc-linux-gnu
    creating target.h - canonical system defines
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking for gawk... (cached) gawk
    checking for gcc... gcc
    checking for C compiler default output file name... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking for style of include used by make... GNU
    checking dependency style of gcc... gcc3
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether ln -s works... yes
    checking whether make sets $(MAKE)... (cached) yes
    checking for a sed that does not truncate output... /bin/sed
    checking for grep that handles long lines and -e... /bin/grep
    checking for egrep... /bin/grep -E
    checking for ld used by gcc... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking for /usr/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking how to recognize dependent libraries... pass_all
    checking how to run the C preprocessor... gcc -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for g++... g++
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking dependency style of g++... gcc3
    checking how to run the C++ preprocessor... g++ -E
    checking for g77... no
    checking for xlf... no
    checking for f77... no
    checking for frt... no
    checking for pgf77... no
    checking for cf77... no
    checking for fort77... no
    checking for fl32... no
    checking for af77... no
    checking for xlf90... no
    checking for f90... no
    checking for pgf90... no
    checking for pghpf... no
    checking for epcf90... no
    checking for gfortran... gfortran
    checking whether we are using the GNU Fortran 77 compiler... yes
    checking whether gfortran accepts -g... yes
    checking the maximum length of command line arguments... 98304
    checking command to parse /usr/bin/nm -B output from gcc object... ok
    checking for objdir... .libs
    checking for ar... ar
    checking for ranlib... ranlib
    checking for strip... strip
    checking if gcc supports -fno-rtti -fno-exceptions... no
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc static flag -static works... yes
    checking if gcc supports -c -o file.o... yes
    checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... no
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    configure: creating libtool
    appending configuration tag "CXX" to libtool
    checking for ld used by g++... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
    checking for g++ option to produce PIC... -fPIC
    checking if g++ PIC flag -fPIC works... yes
    checking if g++ static flag -static works... yes
    checking if g++ supports -c -o file.o... yes
    checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    appending configuration tag "F77" to libtool
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    checking for gfortran option to produce PIC... -fPIC
    checking if gfortran PIC flag -fPIC works... yes
    checking if gfortran static flag -static works... yes
    checking if gfortran supports -c -o file.o... yes
    checking whether the gfortran linker (/usr/bin/ld) supports shared libraries... yes
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    checking for ANSI C header files... (cached) yes
    checking for a supported version of gcc... ok (4.0.2)
    checking for gcc bug PR27603... ok, bug not present
    checking for gcc bug PR28045... configure: error: your compiler has gcc PR28045 bug, use a different compiler, see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28045
    ERROR: Could not configure ClamAV
    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 873: ispconfig_tmp/php/bin/php: No such file or directory
    ERROR: The PHP binary coming with ISPConfig does not work properly on your system! The installation routine stops here!
     
  2. wpwood3

    wpwood3 New Member

    You are getting that error because ISPConfig 2.2.19 updated ClamAV to 0.92 and PHP to 5.2.5. They will not compile on the version of gcc you have (4.0.2).

    Unfortunately, gcc 4.0.2 is the latest in the FC4 repository. The best solution is to update to FC7, FC8 or CentOS. Then you will have gcc 4.1.2.
     
  3. shadowspank

    shadowspank New Member

    I was hoping someone would not say what you just said but I do guess its time to upgrade as FC4 is going to be unsupported.
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

  5. shadowspank

    shadowspank New Member

    I did as you said in your post Till but I ran into an error where ispconfig would start but was unable to startssl. So I put the error into Google as I always do and it always points to this site :) thank god for that. Well something was wrong with the ssl key so I did as you told another person to recrate the SSL cert using the commands below and everything fired right up. Thanks for your help you guys are great keep up the great work. I do plan on upgrading to a new version of linux but just dont have the time, Question whats the best and most stable linux distro now adays.

    openssl genrsa -des3 -passout pass:mypasswrd -out /root/ispconfig/httpd/conf/ssl.key/server.key2 1024

    openssl req -new -passin pass:mypasswrd -passout pass:mypasswrd -key /root/ispconfig/httpd/conf/ssl.key/server.key2 -out /root/ispconfig/httpd/conf/ssl.csr/server.csr -days 365

    openssl req -x509 -passin pass:mypasswrd -passout pass:mypasswrd -key /root/ispconfig/httpd/conf/ssl.key/server.key2 -in /root/ispconfig/httpd/conf/ssl.csr/server.csr -out /root/ispconfig/httpd/conf/ssl.crt/server.crt -days 365

    openssl rsa -passin pass:mypasswrd -in /root/ispconfig/httpd/conf/ssl.key/server.key2 -out /root/ispconfig/httpd/conf/ssl.key/server.key

    chmod 400 /root/ispconfig/httpd/conf/ssl.key/server.key
     
  6. falko

    falko Super Moderator ISPConfig Developer

    I'd recommend Debian. :)
     
  7. unclecameron

    unclecameron New Member

    The longer you hang onto the FC4 box, the more problems you'll have, I know, I'm stuck migrating stuff off a production FC5 box that can't really be taken offline for a rebuild. There are ways around it, but it will become more and more painful. Different story if you use something with long term support like RedHat/CentOS/Debian, generally updates for those stay around for years.
     
  8. crypted

    crypted New Member

    As noted in two other posts, CentOS 5.x will have this issue even with the latest version of GCC. Take the standard steps suggested by TILL to fix...
     
  9. shadowspank

    shadowspank New Member

    question about Debian. I have an extra box laying around that I can install it on and get ISP up and running. Once I get the database and all the domains moved over and I am happy with the way things are running. Can I just take the hard drive out and put it in my server box or will there be problems with doing that.
     
  10. falko

    falko Super Moderator ISPConfig Developer

    If the IP addresses are the same, then that's no problem.
     

Share This Page