All domains resolving to Hey, it worked !

s1nn0n

Verified User
Joined
Jul 31, 2006
Messages
12
I have now restored our server using the admin backup, but all the sites are resolving to the default apache new install message.

Code:
 Hey, it worked !
The SSL/TLS-aware Apache webserver was
successfully installed on this website.

If you can see this page, then the people who own this website have just installed the Apache Web server software and the Apache Interface to OpenSSL (mod_ssl) successfully. They now have to add content to this directory and replace this placeholder page, or else point the server at their real content.

    ATTENTION!
    If you are seeing this page instead of the site you expected, please contact the administrator of the site involved. (Try sending mail to <webmaster@domain>.) Although this site is running the Apache software it almost certainly has no other connection to the Apache Group, so please do not send mail about this site or its contents to the Apache authors. If you do, your message will be ignored. 

The Apache online documentation has been included with this distribution.
Especially also read the mod_ssl User Manual carefully.

Your are allowed to use the images below on your SSL-aware Apache Web server.
Thanks for using Apache, mod_ssl and OpenSSL!



I guess its a DNS issue, any one have any ideas?

Ta.
 
Its hard to help you if you don't give us a domain to check.
 
death4glory.com resolves to 85.234.142.250. Is that the ip give to the domain in the control panel? Also try restarting apache.
 
Just tried restarting apache and now get:

Code:
Starting httpd: Syntax error on line 66 of /etc/httpd/conf/httpd.conf:
Cannot load /usr/lib/apache/libphp4.so into server: libmysqlclient.so.14: cannot open shared object file: No such file or directory

Seems strange, as ive not altered anything since apache was running last.
 
Comment out that line for now to get apache running again. Looking like you need to fix your php.
 
Ive rebuilt php and apache 2.0.59 and still getting errors.

Cannot load /usr/lib/apache/libphp4.so into server: libssl.so.0.9.8: cannot open shared object file: No such file or directory
 
Ok just issued:

ldd /usr/lib/apache/libphp4.so

and got the following output:

Code:
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x00f68000)
        libzzip-0.so.10 => /usr/local/lib/libzzip-0.so.10 (0x00111000)
        libmhash.so.2 => /usr/local/lib/libmhash.so.2 (0x00f98000)
        libmcrypt.so.4 => /usr/local/lib/libmcrypt.so.4 (0x00116000)
        libpng.so.0 => /usr/local/lib/libpng.so.0 (0x00146000)
        libssl.so.4 => /lib/libssl.so.4 (0x002a0000)
        libcrypto.so.4 => /lib/libcrypto.so.4 (0x0017c000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x00269000)
        libm.so.6 => /lib/tls/libm.so.6 (0x00eb0000)
        libdl.so.2 => /lib/libdl.so.2 (0x0027c000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x00280000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x002d4000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x002e8000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x0034d000)
        libcom_err.so.2 => /lib/libcom_err.so.2 (0x00296000)
        libcurl.so.4 => /usr/local/lib/libcurl.so.4 (0x0036e000)
        libz.so.1 => /usr/local/lib/libz.so.1 (0x003a2000)
        libc.so.6 => /lib/tls/libc.so.6 (0x0079d000)
        /lib/ld-linux.so.2 (0x008f4000)
[B]        libssl.so.0.9.8 => not found
        libcrypto.so.0.9.8 => not found[/B]



How would i add those back in?
 
The first thing I would do would be to hunt for any ssl libs that you *do* have.
1) First, update your locate command so you have the current files:
Code:
updatedb

2) Then search for what you do have:
Code:
locate libssl.so
locate libcrypto.so

3) if you find that you have the files you're looking for, but with a different version, then you can try linking to the other version. Example, if "locate libssl.so" retuns:

/lib/libssl.so.1.2.3

and if php wants libssl.so.0.9.8, then you can type
Code:
ln -s libssl.so.1.2.3 /lib/libssl.so.0.9.8
which will create the 0.9.8 file linked to the 1.2.3 file.

4) Alternatively, if that just genrates runtime linking errors.. then delete the link you created, and install/upgrade ssl, eg:
Code:
yum -y install openssl

5) and of course, you might need to recompile php/apache after making any changes in order to properly compile/link the libraries.

John
 
my webalizer country section show 100% unresolved, how to fix it? thanks

My webalizer country section show 100% unresolved, how to fix it? thanks:)

DA version: 1.29.6
Webalizer: 2.01
 
If you are the server admin, locate this line "HostnameLookups Off" in your httpd.conf file and change it to "HostnameLookups On" then the next time webalizer runs, it should start resolving the ip addresses to names. Unfortunately this will not look up names on IP Addresses for reports that have already run. Only reports that run from this point forward.

*Note* This could leed to load issues on the server. You may want to keep an eye on this for a while.
 
Back
Top