Ginka, Uptime, and the GDB.

[Angela Christine]

It seems like every time Ginka becomes unavailable due to some mysterious router problem, the GDB also become nearly unreadable.  Each and every page takes a couple minutes to load, and then is topped by a string of error messages.

Warning: file_get_contents(http://www.armageddon.org/cgi-bin/mudpub/uptime_s.cgi): failed to open stream: Connection timed out in /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php on line 344

Warning: Cannot modify header information - headers already sent by (output started at /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php:344) in /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php on line 480

Warning: Cannot modify header information - headers already sent by (output started at /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php:344) in /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php on line 482

Warning: Cannot modify header information - headers already sent by (output started at /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php:344) in /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php on line 483

I know nothing about networks, but I assume what is happening is that every time the GDB tries to load a page it asks ginka what the uptime is, and then waits until the request times out before proceeding to load the page.

Whatever the cause, the result is that the GDB is painfully, even agonizingly slow at the very time when a bunch of people are likely to check the GDB to find out what is going on.  Ok "Is the game down for you too?" may not be the most fascinating topic of conversation, but it seems very urgent to the people involved.  


Is there anyway to stop ginka's disappearing act from crippling the GDB?  Like, maybe if it couldn't reach ginka three times in a row it would just shut off the uptime feature until someone manually restarts it -- doing without the uptime until an imm reinstates it would be better than doing without the GDB untill an imm disables it (and then has to reinstate it later anyway).  Or make the uptime counter an optional feature, so that people could individually toggle it off?  Is there anything the Amos on the street can do to make his or her GDB reading experience go more smoothly?


Angela Christine

[Morgenes]

I will speak with Brixius when I get a chance to see if we can get this resolved.  Ginka has arisen and the game is back up and running.  Apologies for the downtime.

[Angela Christine]

Warning: file_get_contents(http://www.armageddon.org/cgi-bin/mudpub/uptime_s.cgi): failed to open stream: Connection timed out in /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php on line 344

Warning: Cannot modify header information - headers already sent by (output started at /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php:344) in /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php on line 480

Warning: Cannot modify header information - headers already sent by (output started at /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php:344) in /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php on line 482

Warning: Cannot modify header information - headers already sent by (output started at /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php:344) in /home/.faberge/gdb/zalanthas.org/phpBB2/includes/page_header.php on line 483

D'oh!  It's happening again!


Angela Christine