Jump to content


TCH-James

Member Since 14 Mar 2007
Offline Last Active Feb 07 2008 12:22 AM

Topics I've Started

Route & Network Issues This Morning

16 January 2008 - 03:43 AM

Greetings TCH Family,

This morning one of the routers feeding our building began dropping the connection to XO and bringing it back online. Due to this repeated flapping of the link, our routes were dampened temporarily. This means that other routers on the internet stopped talking to us for a short period of time until it was stabilized. The XO connection was brought down completely and our network is now running on Level(3) and Cogent.

The root cause of this was a failing line card in an older router. The connection to XO will be moved over to the newer router and brought back online. There should be no further issues by bringing the connection back online, but we regain transit with XO at that time.

If you have any specific issues with your account, please open a ticket with the help desk.

Level(3) Network Maintenance

20 December 2007 - 08:58 PM

Greetings TCH Family,

We have been informed that there will be maintenance performed on two DWDM ring nodes which provide our facility with Level(3) transit. The maintenance window is set to begin at 2:00AM EST December 22nd and ending 3:00AM EST December 22nd.

There will be a brief interruption in reachability to Level(3) connected networks during this window. The interruption is not expected to last more than 30 seconds while our system reroutes this traffic and only traffic destined to or originating from Level(3) connected networks will be affected. For a period of approximately 30 minutes Level(3) connected networks will be routed through our two other peers, XO and Cogent. The maintenance being performed is meant to improve reliability of traffic on this circuit.

Movabletype Missing Mt-config.cgi

19 December 2007 - 02:12 AM

With some newer environments, MT seems to become confused in finding it's own location. The following error is quite common:
Got an error: Error opening file '/mt-config.cgi': No such file or directory

This issue seems to crop up due to the way that MT tries to configure it's path. A one stop fix for this is to hardcode the path so that MT know how to find it's configuration files. This fix will ensure that all functions continue to work afterwards

Edit lib/MT/Bootstrap.pm. The first section is where we will add the fix:

sub BEGIN {
	my ($dir, $orig_dir);
	require File::Spec;
	if (!($dir = $ENV{MT_HOME})) {

after the "sub BEGIN" statement, insert the hard coded path:
sub BEGIN {
	$ENV{'MT_HOME'} = '/home/<username>/public_html/mt';  <-- this line should be added
	my ($dir, $orig_dir);
	require File::Spec;
	if (!($dir = $ENV{MT_HOME})) {

You may have to adjust the previous line if your MT path resides elsewhere, such as /home/<username>/public_html/cgi-bin/mt.

If you're uncomfortable editing this file or would like some assistance, please open a ticket with the help desk and we'll be happy to help.

Apache2 Announcement

19 December 2007 - 01:30 AM

Greetings TCH Family,

We have been evaluating the roll out of Apache 2.2 on TotalChoice servers. At the present time, we do not have a roll out date as we are still finishing up testing with various software and php modules.

Apache2 will provide TCH customers benefits in performance and security while still providing the reliability that everyone expects from Apache 1. Along with Apache2, we will be enabling new features such as MySQL PDO and SOAP that have been the most requested features thus far. During the rollout we will also be updating servers to the latest PHP5 revision which is mainly a security release.

As we finish up testing I wanted to solicit feedback from any customers looking to utilize features specific to the latest version of Apache2 or the new modules. Good, bad or indifferent to Apache2 I'd like to hear your opinion.

Network Blip This Afternoon

28 November 2007 - 04:48 PM

Greetings TCH Family,

This afternoon we experienced a short blip in the network which lasted about 5 minutes. This blip was caused by a delay in our failover system. There were some residual issues for a short time afterwards between our servers and our name lookup servers which exist on separate networks in the same facility. This may have caused a bit of lag as this was being fixed.

All servers are back online and operating at full capacity. If you experience any issues with your account, please open a ticket with the help desk.