Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[greycat]

I keep getting "Internal error" pages (that's the title) with content like

[128a457d] 2013-04-17 20:31:54: Fatal exception of type MWException

The whole wiki is unusable for me at the moment.  Yet I don't see any other threads about it yet.  Is this something that's just happening for me?

[Torrasque666]

just tried so.....
yes.

[greycat]

Very bizarre.  I do not experience the problem when I'm at home -- just when I'm at work.  So it's not tied to my wiki account.  Both systems are Linux with Firefox (slightly different versions), so it's not Firefox-specific.  A bit of googling of the error message seems to point to configuration issues that are triggered by language preferences.  My (working) home browser is set to ask for [en-us] first and [en] second.  I tried adding [en-gb] for kicks, but that worked too.  Moving things around (putting [en] on top) also failed to break it.

I'll have to wait until I'm back at work to try to figure out what's causing the failures there, unless there's a way to ssh into the system remotely and query the browser settings, either by reading files or by issuing firefox commands....

[greycat]

The work browser was also configured with [en-us] first and [en] second.  Same as the home browser.  So it's not that, or not that alone.

The work browser is Firefox ESR 17.0.3.

Then I tried with Lynx (2.8.7dev.9) from another computer altogether, and I got another internal error (this one on the Recent Changes page):

   MediaWiki internal error.
   Exception caught inside exception handler.
   Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php
   to show detailed debugging information.

Weirder and weirder.  Now Firefox wants me to restart for an update, and I'm not sure how that even works, so... saving text.

OK, now the work browser is Firefox ESR 17.0.5 and still generates the same errors.

-------------
I installed Lynx on my desktop machine and I was able to load the wiki with it.  Then I wondered how I was able to load the wiki (or any page at all) with it, since it wasn't configured to use my squid proxy which has special whitelist permission to go through the workplace transparent proxy without supplying Microsoft Active Directory login credentials.

So I exported the http_proxy environment variable to point to my squid proxy, and then Lynx on the desktop machine got the same internal errors that Firefox and Lynx-on-the-other-machine are getting.

For grins, I restarted the squid proxy, but Lynx and Firefox both get the same error after the restart.

[greycat]

The problem is also reproducible with wget, which allows me to show the results both with and without the squid proxy.

Here's the failure, going through the proxy:

Code: [Select]

wooledg@wooledg:~$ wget -O /dev/null --debug http://dwarffortresswiki.org/
DEBUG output created by Wget 1.13.4 on linux-gnu.

URI encoding = `UTF-8'
URI encoding = `UTF-8'
--2013-04-18 09:45:34--  http://dwarffortresswiki.org/
Resolving imadev.eeg.ccf.org (imadev.eeg.ccf.org)... 10.76.173.78
Caching imadev.eeg.ccf.org => 10.76.173.78
Connecting to imadev.eeg.ccf.org (imadev.eeg.ccf.org)|10.76.173.78|:3128... connected.
Created socket 5.
Releasing 0x0000000000bbe790 (new refcount 1).

---request begin---
GET http://dwarffortresswiki.org/ HTTP/1.1
User-Agent: Wget/1.13.4 (linux-gnu)
Accept: */*
Host: dwarffortresswiki.org
Connection: Close
Proxy-Connection: Keep-Alive

---request end---
Proxy request sent, awaiting response...
---response begin---
HTTP/1.0 500 Internal Server Error
Server: cloudflare-nginx
Date: Thu, 18 Apr 2013 13:43:35 GMT
Content-Type: text/html; charset=utf-8
X-Content-Type-Options: nosniff
Vary: Accept-Encoding
CF-RAY: 611c8ed7ecd0167
Age: 119
Content-Length: 1005
X-Cache: HIT from imadev
Via: 1.0 ccwsa2.cc.ad.cchs.net:80 (Cisco-IronPort-WSA/7.5.0-833), 1.0 imadev:3128 (squid/2.7.STABLE9)
Connection: close

---response end---
500 Internal Server Error
URI content encoding = `utf-8'
Closed fd 5
2013-04-18 09:45:34 ERROR 500: Internal Server Error.

And here's the successful case, bypassing the squid proxy (but I cannot bypass the transparent proxy):

Code: [Select]

wooledg@wooledg:~$ (unset http_proxy; wget -O /dev/null --debug http://dwarffortresswiki.org/)
DEBUG output created by Wget 1.13.4 on linux-gnu.

URI encoding = `UTF-8'
--2013-04-18 09:47:47--  http://dwarffortresswiki.org/
Resolving dwarffortresswiki.org (dwarffortresswiki.org)... 108.162.198.207, 108.162.199.207, 2400:cb00:2048:1::6ca2:c6cf, ...
Caching dwarffortresswiki.org => 108.162.198.207 108.162.199.207 2400:cb00:2048:1::6ca2:c6cf 2400:cb00:2048:1::6ca2:c7cf
Connecting to dwarffortresswiki.org (dwarffortresswiki.org)|108.162.198.207|:80... connected.
Created socket 5.
Releasing 0x0000000001f54740 (new refcount 1).

---request begin---
GET / HTTP/1.1
User-Agent: Wget/1.13.4 (linux-gnu)
Accept: */*
Host: dwarffortresswiki.org
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Server: cloudflare-nginx
Date: Thu, 18 Apr 2013 13:47:47 GMT
Content-Type: text/html; charset=UTF-8
X-Content-Type-Options: nosniff
Vary: Accept-Encoding, Cookie
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Cache-Control: private, must-revalidate, max-age=0
Content-Language: en
Set-Cookie: __cfduid=d8807080c93f894133e2fe08c4c2f26241366292867; expires=Mon, 23-Dec-2019 23:50:00 GMT; path=/; domain=.dwarffortresswiki.org
CF-RAY: 611cf186b370166
Transfer-Encoding: chunked
Last-Modified: Wed, 17 Apr 2013 20:46:32 UTC
Via: 1.1 ccwsa1.cc.ad.cchs.net:80 (Cisco-IronPort-WSA/7.5.0-833)
Connection: keep-alive

---response end---
200 OK
cdm: 1 2
Stored cookie dwarffortresswiki.org -1 (ANY) / <permanent> <insecure> [expiry 2019-12-23 18:50:00] __cfduid d8807080c93f894133e2fe08c4c2f26241366292867
Registered socket 5 for persistent reuse.
URI content encoding = `UTF-8'
Length: unspecified [text/html]
Saving to: `/dev/null'

    [ <=>                                   ] 42,706      --.-K/s   in 0.01s   

Last-modified header invalid -- time-stamp ignored.
2013-04-18 09:47:48 (3.43 MB/s) - `/dev/null' saved [42706]


[greycat]

Final comparison: ssh-ing to my home machine (OpenBSD 5.2), I tried to access the wiki in Lynx with the http_proxy environment variable set (pointing to another squid proxy), and I got the same internal errors.

When I unset http_proxy and tried again, it worked.

I repeated the experiment on a Linux machine on my home network.  With http_proxy set (pointing to a squid proxy), I got the internal errors.  With http_proxy unset, I still got the internal errors.

The difference between the workplace setup and the home setup is: the workplace has a transparent Cisco proxy, and I use a squid proxy by choice.  The home network has a transparent squid proxy on the OpenBSD firewall/router, so all port 80 HTTP requests go through it unless they originate on the OpenBSD box itself.

So, there is something very very broken between HTTP requests that go through a squid proxy, and the dwarf fortress wiki.

I don't fully understand what's happening, though.  The Firefox browser on my home computer is going through the transparent squid proxy, but it works.  So there's still some other factor involved.  I wish I knew what it was so I could tell you "Here, fix this."

[greycat]

Oh, and just so you know I'm not completely insane, other mediawiki wikis work just fine from this browser (wikipedia, kingdom of loathing, cities, and an internal workplace wiki).  It's only the Dwarf Fortress wiki that gives me these errors.

[Locriani]

What happens if you try to directly access a node server (dfweb3.dwarffortresswiki.org, for example)?

[greycat]

http://dfweb3.dwarffortresswiki.org/ works (so do dfweb1 and dfweb2).  http://dwarffortresswiki.org/ gives internal errors.

[Locriani]

Ok, I believe I know what the problem is.  Mediawiki is barfing because it can't determine what your ip address is, and I'll need to tweak the nginx configuration to fix it.  I won't have a chance to play with this until later today, though.

[greycat]

Well, thanks in advance

[greycat]

Additional info: at home, I can browse most of the wiki without problems, but a few pages give internal errors: search for namespaces, for instance.  Or any attempt to edit a page.

Using the dfweb3.* hostname solves these.

[Locriani]

Hrm, ok.  I haven't forgotten about you but I haven't had time to make the configuration changes yet, and as I'm about to hop on a flight, I don't want to change things that may or may not break the wiki until I have a chance to monitor things.  In the meantime, since the direct node workaround works for you, feel free to continue using that

My schedule is all kinds of retarded until 2 weeks from now (yay bsns), but I'll try to get in a fix before then for you.

[Locriani]

Greycat, I believe the issue is fixed.  Please let me know if I'm wrong and only managed to bungle things further. 

[greycat]

I still get the same internal errors at work.