Our business telephones are down at present. We get our telephone service from Comcast and Comcast is broken at the moment and can’t schedule anyone until tomorrow afternoon.
If you can’t get through on our phones, please e-mail email@example.com instead. Fortunately, I have a T1 to our co-location facility so I do have another way of getting to e-mail and our hosts.
I will be rebooting and taking machines out of service for imaging early Saturday morning on June 7th, 2014.
There will be an initial outage that affects all services when the main file server is rebooted, lasting about 15 minutes, and then after that individual machines will be taken down, imaged, and rebooted.
This is a maintenance outage for the company we use to provide DSL back haul for DSL Customers on CenturyLink circuits. This outage will affect the greater Seattle area.
Start time: 10:59 pm PDT
End time: 12:00 am PDT
Affected: Internet Transit in Seattle
Maintenance is being performed make adjustments to the core router in Seattle. This requires a reboot of the core router and customers should expect around 15 minutes of downtime.
Those of you who have NetFlix, I’d like to recommend a film there called “Terms and Conditions May Apply“. It’s a very excellent documentary regarding privacy and the lack thereof.
I am experimenting with RoundCube as a possible replacement for SquirrelMail. The reason for considering an alternative is primarily the need to provide a mail client that is responsive, that is that adapts to the display and device that it’s being used with. SquirrelMail is good for desktops but not so good for tablets and smartphones.
Just after midnight tonight I will be rebooting first the main file server which will make everything that depends upon files halt for several minutes. Then I will be rebooting other servers. This is to make recent updates to glibc take effect.
Since putting fail2ban in place, nearly all of the brute force password attacks have been out of China, a handful from Viet Nam.
The IP 188.8.131.52 has just been banned by Fail2Ban after
5 attempts against SSH.
Here are more information about 184.108.40.206:
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '220.127.116.11 - 18.104.22.168'
inetnum: 22.214.171.124 - 126.96.36.199
descr: CHINANET jiangsu province network
descr: China Telecom
descr: A12,Xin-Jie-Kou-Wai Street
descr: Beijing 100088
remarks: This object can only be updated by APNIC hostmasters.
remarks: To update this object, please contact APNIC
remarks: hostmasters and include your organisation's account
remarks: name in the subject line.
status: ALLOCATED PORTABLE
changed: firstname.lastname@example.org 20050624
role: CHINANET JIANGSU
address: 260 Zhongyang Road,Nanjing 210037
remarks: send anti-spam reports to email@example.com
remarks: send abuse reports to firstname.lastname@example.org
remarks: times in GMT+8
changed: email@example.com 20090831
changed: firstname.lastname@example.org 20090831
changed: email@example.com 20090901
changed: firstname.lastname@example.org 20111114
person: Chinanet Hostmaster
address: No.31 ,jingrong street,beijing
changed: email@example.com 20070416
changed: firstname.lastname@example.org 20140227
% This query was served by the APNIC Whois Service version 1.69.1-APNICv1r0 (WHOIS1)
This mornings maintenance activity has been concluded. All NFS relationships between servers are now back to version 4 so mandatory locking is functioning again.
I will be rebooting various servers tonight in order to switch NFS back to version 4 which now appears to be fixed in CentOS 6.5.
NFS version 4 supports mandatory locking, provides better overall performance, and can mutually co-exist with firewalls allowing for greater system security.
Clam-AV has been updated on all servers and the queues flushed so mail is no longer backed up in queue with the exception of mail destined to sites that are currently down.