March 2007

BitTraffic - FreeBSD 6.2-RELEASE-p2 - UPGRADE COMPLETE!

Dear BitTraffic Customers,

We apologize for the issues related to FreeBSD 6.1. We have now upgraded all systems to FreeBSD 6.2-RELEASE-p2 the latest stable kernel available. Its been running excellent. We apologize for our decision to use 6.1 without having further testing and preperation. The issues that we had were uncommon and were related to IRCd’s only. They were not well known and the issue was not easy for our techs to troubleshoot, and was not even well known by OS guru’s around the world. The new kernel has patched the issues associated with the IRCd problems. We appreciate that you all have been able to bare with us through these kernel issues.

Thank you for understanding,

Announcements

Permalink

hercules.bittraffic.com - FreeBSD 6.2-RELEASE-p2

Dear BitTraffic Clients,

At approximately midnight MST hercules.bittraffic.com running the kernel FreeBSD 6.2-RC1-p1 crashed proving unstable and unreliable. At that time we attempted to upgrade the kernel using standard procedure that was successfully used on both stamina.bittraffic.com, and zeus.bittraffic.com. We upgraded the kernel to FreeBSD 6.2-RELEASE-p2 and failed. After the final configuration changes were made and the system was restarted it failed to boot. We then submit a ticket to the datacenter regarding the issue. Further investigation revealed the kernel problem. The kernel was replaced and updated with a working FreeBSD 6.2-RELEASE-p2. This update was critical the same as the first attempt with p1 and refers to the same issues. The system hercules.bittraffic.com should now be stablilized with the newest available stable release. We greatly apologize for the disturbances and are confident that the issues are resolved. If you have any questions or concerns please do not hesitate to contact us.

Thank you,

Announcements

Permalink

Critical Update

We have found a critical system issue that needs patched immdiately http://www.vulnscan.org/UnrealIrcd/faq/#105 this patch is the reason for several issues we have had with ossec security software and possibly even the sensative crontabs. We are currently running FreeBSD 6.1 and we have to upgrade to FreeBSD 6.2. This upgrade should take no longer then 30 minutes per machine to completely finish. It entails updating the system kernel and rebooting each machine twice in a row. This upgrade will fix the recent TCP connectivity issues we have encountered. This will also fix the STAT L process locking. We will start this update now by working on athena.bittraffic.com. We will send an additional email for each system just before its taken offline. We expect that all machines should be updated within 24-48 hours. Again each system should take no longer then 30 minutes to upgrade. Connectivity will only be lost during the reboots. We greatly apologize for any inconvenience. These upgrades will ensure quality and stability. It would be better to take care of these issues now and achieve longer uptimes sooner. We have taken tremendous leaps into the future and have invested heavily in high quality bandwidth solutions. Please take our word that you will be more then pleased with services to come. Please bare with us.

Update - The first upgrade to athena.bittraffic.com was successful and took less then 15 minutes. We will now perform this upgrade on hercules.bittraffic.com. We apologize for not offering more advanced warning. This is a critcal update and must be done. stamina.bittraffic.com will be upgraded at 7:30 MST ( same time tomorrow ). If you encounter issues or need support please do not hesitate to contact us.

Announcements

Permalink

Crontab Update

We are proud to announce that we have reached a resolution for the recent crontab abuse. Also the reason for hercules.bittraffic.com’s recent reboot. Crontab usage is now only permitted by root system admins. If you wish to have a crontab setup for some piticular software please submit a ticket via http://support.bittraffic.com and we will setup crontabs as requested. This is a security measure taken to ensure system uptime and stability. Existing crontabs were not removed if they were set correctly. Invalid crontabs were removed. Please contact us if you have any questions regarding crontabs.

Announcements

Permalink