Install stops...ERROR: Could not make OpenSSL

Discussion in 'Installation/Configuration' started by limpkinw, Feb 17, 2008.

  1. limpkinw

    limpkinw New Member

    After having problems with Feisty I Switched over to Etch, unfortunately I get the exact same error. Yes I have read through this forum and the few fixes or suggestions I have found offer no relief to my problem. I have been doing this now for about 40 hours and am at the end of my rope.

    uname -a
    Linux zz54-vps338.zzservers.net 2.6.19-4-generic-amd64 #2 SMP Sat Oct 6 01:35:53 UTC 2007 x86_64 GNU/Linux

    And the Error...I have the done this a few times now and followed the perfect guide to the letter, no errors on anything previous to this.

    I am avail on yahoo im blue_fire pretty much 24/7 for any suggestions.

    Thanks so much for reading :)

    Code:
    gcc -DMONOLITH -I.. -I../include  -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -m64 -DL_ENDIAN -DTERMIO -O3 -Wall -DMD32_REG_T=int   -c -o dsaparam.o dsaparam.c
    gcc -DMONOLITH -I.. -I../include  -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -m64 -DL_ENDIAN -DTERMIO -O3 -Wall -DMD32_REG_T=int   -c -o x509.o x509.c
    gcc -DMONOLITH -I.. -I../include  -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -m64 -DL_ENDIAN -DTERMIO -O3 -Wall -DMD32_REG_T=int   -c -o genrsa.o genrsa.c
    gcc -DMONOLITH -I.. -I../include  -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -m64 -DL_ENDIAN -DTERMIO -O3 -Wall -DMD32_REG_T=int   -c -o gendsa.o gendsa.c
    gcc -DMONOLITH -I.. -I../include  -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -m64 -DL_ENDIAN -DTERMIO -O3 -Wall -DMD32_REG_T=int   -c -o s_server.o s_server.c
    /tmp/ccljUmbI.s: Assembler messages:
    /tmp/ccljUmbI.s:431: Error: Incorrect register `%rax' used with `l' suffix
    /tmp/ccljUmbI.s:439: Error: Incorrect register `%rbx' used with `l' suffix
    /tmp/ccljUmbI.s:459: Error: Incorrect register `%rdx' used with `l' suffix
    /tmp/ccljUmbI.s:460: Error: Incorrect register `%rbx' used with `l' suffix
    make[1]: *** [s_server.o] Error 1
    make[1]: Leaving directory `/root/tmp/install_ispconfig/compile_aps/openssl-0.9.7m/apps'
    make: *** [sub_all] Error 1
    ERROR: Could not make OpenSSL
    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!
    zz54-vps338:~/tmp/install_ispconfig#
    
     
    Last edited: Feb 17, 2008
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    This error occurs when you ise a 32Bit Linux userland and a 64Bit Linux kernel.

    There are 2 possible solutions:

    1) Install a 32Bit kernel instead of the 64Bit Kernel.
    3) Reinstall your system and use the 64Bit debian installation CD instaed of the 32Bit installation CD.
     
  3. limpkinw

    limpkinw New Member

    Unfortunately my provider does the actual software install so I am at the mercy of what they have available, which I guess doesn't include the above.

    No workarounds?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    There is no problem installing a 32Bit kernel. You can do this with apt:

    apt-get install linux-image-2.6-686-smp

    afterwards you will have to reboot the server and then check with:

    uname -a

    if it really runs on the new kernel. The compile problem is not sipconfig specific as it is the compilation of openssl that would fail in general. Your provider shall not mix up 32bit and 64nbit software on the system! This might cause several software to fail or run unstable or it causes compilazion problems as the one above.
     
  5. limpkinw

    limpkinw New Member

    That is great, I hate to press my luck but any knowledge of a good walk thru for this, I have been looking thru search engines and havn't found anything that makes me comfortable performing this with putty, mainly when I get to the message about initrd/boot loader
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Just run the command above and reboot afterwards. If you are not sure, post the lines that appeared to your screen during kernel pacakge installation here.
     
  7. limpkinw

    limpkinw New Member

    This is the part that makes me leary

    When I installed lilo it creates no lilo.conf file so I am quite lost at the moment

    Code:
     You are attempting to install an initrd kernel image (version 2.6.18-6-686) This will not work   │
     │ unless you have configured your boot loader to use initrd. (An initrd image is a kernel image    │
     │ that expects to use an INITial Ram Disk to mount a minimal root file system into RAM and use     │
     │ that for booting).                                                                               │
     │                                                                                                  │
     │ As a reminder, in order to configure LILO, you need to add an 'initrd=/initrd.img' to the        │
     │ image=/vmlinuz stanza of your /etc/lilo.conf                                                     │
     │                                                                                                  │
     │ I repeat, You need to configure your boot loader -- please read your bootloader documentation    │
     │ for details on how to add initrd images.                                                         │
     │                                                                                                  │
     │ If you have already done so, and you wish to get rid of this message, please put                 │
     │  "do_initrd = Yes"                                                                               │
     │ in /etc/kernel-img.conf. Note that this is optional, but if you do not, you will continue to     │
     │ see this message whenever you install a kernel image using initrd.                               │
     │                                                                                                  │
     │  Do you want to abort now?       
     
    Last edited: Feb 17, 2008
  8. falko

    falko Super Moderator ISPConfig Developer

    What's in /etc/lilo.conf, and what's the output of
    Code:
    ls -la /boot
    ?
     
  9. limpkinw

    limpkinw New Member

    ls -la/boot

    Code:
    outwarhosting:~# ls -la /boot
    total 6432
    drwxr-xr-x  2 root root    4096 Feb 17 23:18 .
    drwxr-xr-x 22 root root    4096 Feb 18 07:07 ..
    -rw-r--r--  1 root root  723178 Feb 10 23:00 System.map-2.6.18-6-686
    -rw-r--r--  1 root root   70682 Feb 10 22:04 config-2.6.18-6-686
    lrwxrwxrwx  1 root root      15 Feb 17 20:00 debian.bmp -> /boot/sarge.bmp
    -rw-r--r--  1 root root 4489939 Feb 17 19:59 initrd.img-2.6.18-6-686
    -rw-r--r--  1 root root 1260861 Feb 10 23:00 vmlinuz-2.6.18-6-686
    


    lilo.conf does not exist....
     
  10. falko

    falko Super Moderator ISPConfig Developer

    ???
    What's the output of
    Code:
    updatedb
    locate lilo.conf
    ?
     
  11. Becks

    Becks New Member

    I've resolved this issue!
    It is a problem if your vServer is 32-Bit and your Hoster runs 64-Bit.
    If so, uname -a tells make the wrong system version, so i faked the output of uname to replace x86_64 with i386 and now it works.
     
  12. falko

    falko Super Moderator ISPConfig Developer

    Just out of curiosity, how did you do this?
     
  13. Becks

    Becks New Member

    Just wrote a little script and rename original uname to uname2

    Here is the content of script named uname:
    /bin/uname2 $1 | sed 's/x86_64/i386/g'
     
  14. dmz

    dmz New Member

    Lilo on host

    Hello,
    I noticed this posting on our daily google alerts for ZZ Servers.

    Let me start by saying that I am with ZZ Servers.

    Ok now to the comment about this post. The virtual servers at zzservers do not use pygrub, and as such do not allow for customers to install their own kernels (this prevents someone from installing a non-xen aware kernel and causing the other customers on the hosts massive problems).
    However we also realize that our system builds may be causing people problems as it is a 64Bit dom0 system and as such most systems are deployed with a 64Bit kernel as well.
    We are reworking our system build scripts to support the native xen kernel provided by each distribution, and hopefully also the ability to choose 32 or 64 bit systems (assuming xen cooperates for us).

    As for faking the kernel, it may help with the build but it may cause future problems with the build wanting to talk with systems using a 32bit addressing system but the system is expecting 64bit.

    For now please have patience for a few days while we correct the hosts.

    Also, have you tried: apt-get install openssl

    That does work, and is the primary reason you choose ubuntu or debian; so you can avoid compiling from source (and is why most other customers do not have issues with the virtual hosts;)

    Regards
    David M. Zendzian
    Managing Partner
    ZZ Servers, LLC
     
  15. till

    till Super Moderator Staff Member ISPConfig Developer

    The compilation of OpenSSL is part of the ispconfig installation process and can not be circumvented by installing openssl with apt.
     
  16. dmz

    dmz New Member

    ISP Config & openssl

    Ahh, I did not realize that you were using ispconfig...

    Well we are working on getting the correct kernel installed and once we get past the current issue (it doesn't recognize the disk device properly) we will provide the upgrade for you.

    There are other tools for managing hosted services, but I understand that if you are use to ispconfig you want to use it.

    We will have some solution for you soon.

    David
     

Share This Page