Stuff…

I know I will forget.

Stuff… header image 1

Ubuntu apt-get Cannot initiate the connection to 80:80 (0.0.0.80). – connect (22: Invalid argument)

January 4th, 2012 · Comments Off

Was using a fresh install of Ubuntu 11.10 (oneiric) and continually received the following errors when trying to apt-get update:

Cannot initiate the connection to 80:80 (0.0.0.80). – connect (22: Invalid argument)
W: Failed to fetch http://au.archive.ubuntu.com/ubuntu/dists/oneiric-updates/universe/binary-i386/Packages Cannot initiate the connection to 80:80 (0.0.0.80). – connect (22: Invalid argument)
etc…

During OS installation a proxy server was specified, but, appears was causing an issue.  Edited /etc/apt/apt.conf and disabling (commented out) the following line:

Acquire::http::Proxy “10.1.1.10:80″;

Once disabled, apt-get update started working without errors.

Comments OffTags: Linux · Operating System

Show disk usage excluding some directory structures

December 14th, 2011 · Comments Off

Wanted to do a quick “du -sh” on only the directories in / (‘root’) and NOT any of the mounted partitions.  This one liner worked nicely:

cd /
ls -la / | awk ‘{ print $9 }’ | egrep -v ‘boot|part1|var|\.’ | xargs du -sh

Comments OffTags: Coding · Linux · One Liners · Operating System

Linux routing a packet back out the interface the previous packet was received on

July 5th, 2011 · No Comments

Had a situation where there were two interfaces on a machine and one with the default gateway.  Some traffic was coming in view the backend NIC but the return traffic was going back out via the default gateway.

These two URLs were interesting for this:

→ No CommentsTags: Linux · Operating System

What is the deal with the facebook.com whois output?

June 28th, 2011 · No Comments

Was trying to find facebook contact information (phone number) on and around their site, but, this proved pretty much impossible.  I hoping they had some numbers in the whois output of their domains and the whois output looked a little strange.

I have seen this before with another domain and wondered how it’s done. (Sub domains are matched apparently, thanks Q):

Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

Server Name: FACEBOOK.COM.ZZZZZ.GET.LAID.AT.WWW.SWINGINGCOMMUNITY.COM
IP Address: 69.41.185.229
Registrar: TUCOWS.COM CO.
Whois Server: whois.tucows.com
Referral URL: http://domainhelp.opensrs.net

Server Name: FACEBOOK.COM.MORE.INFO.AT.WWW.BEYONDWHOIS.COM
IP Address: 203.36.226.2
Registrar: TUCOWS.COM CO.
Whois Server: whois.tucows.com
Referral URL: http://domainhelp.opensrs.net

Server Name: FACEBOOK.COM.KNOWS.THAT.THE.BEST.WEB.HOSTING.IS.NASHHOST.NET
IP Address: 78.47.16.44
Registrar: INTERNET INVEST, LTD. DBA IMENA.UA
Whois Server: whois.imena.ua
Referral URL: http://www.imena.ua

Server Name: FACEBOOK.COM.GET.ONE.MILLION.DOLLARS.AT.WWW.UNIMUNDI.COM
IP Address: 209.126.190.70
Registrar: DIRECTI INTERNET SOLUTIONS PVT. LTD. D/B/A PUBLICDOMAINREGISTRY.COM
Whois Server: whois.PublicDomainRegistry.com
Referral URL: http://www.PublicDomainRegistry.com

Domain Name: FACEBOOK.COM
Registrar: MARKMONITOR INC.
Whois Server: whois.markmonitor.com
Referral URL: http://www.markmonitor.com
Name Server: NS1.FACEBOOK.COM
Name Server: NS2.FACEBOOK.COM
Name Server: NS3.FACEBOOK.COM
Name Server: NS4.FACEBOOK.COM
Name Server: NS5.FACEBOOK.COM
Status: clientDeleteProhibited
Status: clientTransferProhibited
Status: clientUpdateProhibited
Status: serverDeleteProhibited
Status: serverTransferProhibited
Status: serverUpdateProhibited
Updated Date: 16-mar-2011
Creation Date: 29-mar-1997
Expiration Date: 30-mar-2020

>>> Last update of whois database: Tue, 28 Jun 2011 07:29:48 UTC <<<
NOTICE: The expiration date displayed in this record is the date the
registrar’s sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant’s agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar’s Whois database to
view the registrar’s reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services’ (“VeriSign”) Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

MarkMonitor is the Global Leader in Enterprise Brand Protection.

Domain Management
MarkMonitor Brand Protectionâ
¢
AntiFraud Solutions
Corporate Consulting Services

Visit MarkMonitor at www.markmonitor.com
Contact us at 1 800 745 9229
In Europe, at +44 (0) 20 7840 1300

The Data in MarkMonitor.com’s WHOIS database is provided by MarkMonitor.com
for information purposes, and to assist persons in obtaining information
about or related to a domain name registration record.  MarkMonitor.com
does not guarantee its accuracy.  By submitting a WHOIS query, you agree
that you will use this Data only for lawful purposes and that, under no
circumstances will you use this Data to: (1) allow, enable, or otherwise
support the transmission of mass unsolicited, commercial advertising or
solicitations via e-mail (spam); or  (2) enable high volume, automated,
electronic processes that apply to MarkMonitor.com (or its systems).
MarkMonitor.com reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by this policy.

Registrant:
Domain Administrator
Facebook, Inc.
1601 S. California Ave
Palo Alto CA 94304
US
domain@fb.com +1.6505434800 Fax: +1.6505434800

Domain Name: facebook.com

Registrar Name: Markmonitor.com
Registrar Whois: whois.markmonitor.com
Registrar Homepage: http://www.markmonitor.com

Administrative Contact:
Domain Administrator
Facebook, Inc.
1601 S. California Ave
Palo Alto CA 94304
US
domain@fb.com +1.6505434800 Fax: +1.6505434800
Technical Contact, Zone Contact:
Domain Administrator
Facebook, Inc.
1601 S. California Ave
Palo Alto CA 94304
US
domain@fb.com +1.6505434800 Fax: +1.6505434800

Created on…………..: 1997-03-28.
Expires on…………..: 2020-03-29.
Record last updated on..: 2011-05-30.

Domain servers in listed order:

ns4.facebook.com
ns2.facebook.com
ns1.facebook.com
ns5.facebook.com
ns3.facebook.com

MarkMonitor is the Global Leader in Enterprise Brand Protection.

Domain Management
MarkMonitor Brand Protectionâ
¢
AntiFraud Solutions
Corporate Consulting Services

Visit MarkMonitor at www.markmonitor.com
Contact us at 1 800 745 9229
In Europe, at +44 (0) 20 7840 1300

→ No CommentsTags: Networking

Upgraded PHP to 5.3 caused error in horde, phpbb3 and wordpress

April 26th, 2011 · No Comments

A client upgraded his PHP install using the Atomic Turtle packages from 5.2.x to 5.3.6 and started to get error messages on some of his sites, and, in the error_log file for the site.  They looked like this:

[Tue Apr 26 14:01:37 2011] [error] [client x.x.x.x] PHP Warning:  strftime() [<a href='function.strftime'>function.strftime</a>]: It is not safe to rely on the system’s timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning
, you most likely misspelled the timezone identifier. We selected ‘Europe/London’ for ‘BST/1.0/DST’ instead in /var/www/html/webmail/config/prefs.php on line 328

[Tue Apr 26 14:01:37 2011] [error] [client x.x.x.x] PHP Fatal error:  Uncaught exception ‘Exception’ with message ‘DateTime::__construct() [<a href='datetime.--construct'>datetime.--construct</a>]: It is not safe to rely on the system’s timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case
you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier.
We selected ‘Europe/London’ for ‘BST/1.0/DST’ instead’ in /var/www/html/webmail/lib/Horde/Date.php:537\nStack trace:\n#0 /
var/www/html/webmail/lib/Horde/Date.php(537): DateTime->__construct()\n#1 /var/www/html/webmail/lib/Horde/Date.php(588): Horde_Date->format(‘Y-m-d H:i:s’)\n#2 /var/www/html/webmail/lib/Horde/Alarm/sql.php(143): Horde_Date->sqlDateTime()\n#3 /var/www/html/webmail/lib/Horde/Alarm.php(275): Horde_Alarm_sql->_list(false, Object(Horde_Date))\n#4 /var/www/html/webmail/lib/Horde/Alarm.php(301): Horde_Alarm->listAlarms(false, NULL, true, true)\n#5 /var/www/html/webmail/lib/Horde/Notification.php(209 in /var/www/html/webmail/lib/Horde/Date.php on line 537

Simply setting date.timezone = “Europe/London” in the /etc/php.ini file and restarting the webserver resolved the problems.

URL:

→ No CommentsTags: Coding · Linux · Operating System