Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I see you're based in Jossburg. I'm in Lanseria at the mo, but I'll be headed back to Durbs just as soon as I can...
Anyway, back on Topic...
The /var/log/apache2/access.log doesn't show much:
server:~# tail /var/log/apache2/access.log
18.104.22.168 - - [08/Dec/2009:11:49:33 +0200] "GET /inenergy/?q=admin/reports HTTP/1.1" 200 4356 "http://inenergy.org/inenergy/?q=admin/content/node/overview" "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/22.214.171.124 Safari/532.0"
126.96.36.199 - - [08/Dec/2009:11:49:37 +0200] "GET /inenergy/sites/default/files/logo.jpg HTTP/1.1" 304 - "http://inenergy.org/inenergy/?q=admin/reports" "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/188.8.131.52 Safari/532.0"
184.108.40.206 - - [08/Dec/2009:11:49:37 +0200] "GET /inenergy/sites/default/files/favicon.ico HTTP/1.1" 304 - "http://inenergy.org/inenergy/?q=admin/reports" "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/220.127.116.11 Safari/532.0"
18.104.22.168 - - [08/Dec/2009:11:49:42 +0200] "GET /inenergy/?q=admin/reports/status HTTP/1.1" 200 5116 "http://inenergy.org/inenergy/?q=admin/reports" "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/22.214.171.124 Safari/532.0"
This is the Drupal Error:
HTTP request status Fails
Your system or network configuration does not allow Drupal to access web pages, resulting in reduced functionality. This could be due to your webserver configuration or PHP settings, and should be resolved in order to download information about available updates, fetch aggregator feeds, sign in via OpenID, or use other network-dependent services.
I think it's do do with a complicated security model by which Drupal puts out http calls via php which I have a feeling my router doesn't accept. (I could be wrong in this).
Cool, nice to chat to an SA mate, This seems to be a networking issue based on the name resolution.
Went you make the connection from outside, the D-Link does the correct thing, it forwards the packet to the drupal system on the inside, the system on the inside however trieds to make its own http connection to itself, (inenergy.org) this resolves to the external IP on the D-Link, the packet is sent out to the D-Link which then fails to send the packet back to the drupal host.
The work around is to create a mapping for inenergy.org to the internal ip address on the machine running drupal. You can use /etc/hosts for that.
Such that when drupal requests for inenergy.org it will resolve to itself.
No that should not affect it, from the logs you posted, a redirection is being made to inenergy.org. Maybe that is not what is generating the error, is there anything different in the logs ?
If you cannot see anything then maybe you can go low level to debug it by using tcpdump to see which requests are being made.
Sorry, I had a meeting I had to dash off to attend. And, as you know, in Jossburg you have to leave at least an hour in hand because the chances are good that several traffic lights are out between you and your destination.
Anyway, it appears that the 2 issues I had were interconnected.
The Router's DHCP had overwritten my /etc/resolv.conf and replaced the opendns nameservers with it's own:
I had appended the opendns nameservers onto the file:
echo "nameserver 126.96.36.199">>/etc/resolv.conf
echo "nameserver 188.8.131.52">>/etc/resolv.conf