Category: Server

I miss Max.

While it seems that I have little to show for it. I spent the entire week working on this blog. I’m really trying to detach myself from LiveJournal once and for all. Admittedly, on LiveJournal you have an easily wired audience. I will probably end up cross-posting summaries and links back here. But I think that my time with Frank the Goat is finally winding to a close.

Sadly,  even when I think that I can muster the emotional drama of a 14 year-old-girl (Will no ill-respect to my 1t cousin that I’m just beginning to get to know) I just don’t feel like posting it. Im not hungry for the responses from the 300-400 people who I don’t really follow anymore. I’m more interested in going back to the heart.

For me, I want to post what’s inside me. And if people choose to read it. They do. If they don’t… Amazingly, they don’t. Trust me, I’ve got metrics proving the latter. People are not reading my writings in droves. (I’ve always wanted to use that one.)

So, this is what I have to show for one week. An off-handed meta-post?

Well, no. I have spent the last week using the LiveJournal importer from my WordPress install. This is (IN THEORY) a nifty tool that brings down your posts, your comments received and puts them into your stand alone blog. I point out “in Theory” because it took me the better part of a week to figure out how to use it without throttling my server, spamming the internet, and finding the bugs in the code. (Which mind you… I haven’t found.)

Most of this week has involved me deciphering Object-Oriented PHP code. A talent that would have come in handy perhaps BEFORE my interview with the company that might have used me as an OOPHP dev. I basically found where the problem was over a few days. This involved me learning more about the language, figuring out how you debug ‘live PHP’, and shoving in a Kluge fix to get the thing to finally pass through. (If I get really bored and find myself to have time, I will talk in detail about the technical hoo-hah that I went through.)

So, here we are, a week later and only one new post of which you my faithful reader are….um… is…um….reading. However, on top of that, my recent post on being a caregiver for someone in chronic pain picked up two more comments. I also added 2915 old posts and some 12,480 comments from LiveJournal. Now admittedly, about 450 are currently pending approval because they were left as screened. Some had private info, some were screened due to the nature of the post. And so on.

One of the other problems was that I’d spent the last year pushing my aggregated daily twitters into a lone post on LJ. Those 230 posts need to be given their own post-category. The reason for that is to get them off the main page when on comes to the blog. (I’ve at least gotten the most recent 20 or so to vanish.)

Then there’s all the remaining stuff to do. I want to have my twitters auto post to this blog. I want to have summaries post to LJ with a link back here for commenting.

All this amazing work without a whole lot of content to wrap the work around. Wow, I could make an entire post on that theme. (rolls eyes)

But for now, it’s time for me to attempt to get sleep before 2 am.. or I suppose 1 am since the clocks are going to freak this weekend. More on what’s on/in my head soon.

Til then. Umm…

Witty Sign Off Line.

(With all due respect. Please forgive the 15 second preceding commercial)

So, Friday started with me flooding the Internet with unwanted spam. As of yet I have not worked up the cojones to attempt to turn on that faucet again.

While I do offer Internet services this comes at a price. I maintain a business-calibre level of data throughput. My ISP has an average priced package for this. It is “Average” in my opinion insofar as considering the cost of service compared with the speed of the connection compared with the quality of service and support. Actually, putting it down that way may make me have to reconsider my rating.

Part of this package includes a strip of static IP addresses. Most people with Internet get dynamic addresses. What this means is that you have whatever address you are allocated and that’s fine. The reason for Static is because you need a permanent address that people can get to. This is why you can get to Google or Yahoo, but people can’t necessarily find you when you’re on a chat client.

One of the problems that I’ve been suffering is slow download speed and intermittent download “drop-out.” This sounds horrid for my customers, but their download is my upload. My upload has always worked as good if not better than advertised. This download issue has basically been presenting itself as getting 40-60% the download speed I’m paying for.

I had a tech come out early last week. He was running late. No one called to tell me. This was a bit of an annoyance. I do run my business out of my house; so it’s not like my IT department is meeting with the CEO randomly. It does however mean that 3pm – 5pm cuts into my toddler’s dinner when you show up an hour late to start. (Without calling)

45 minutes later. The line looks okay but the speed problem must be internal. “Shrug” says the tech and shuffles off. On Friday another tech shows up to swap out my DSL modem. Normally this will only create about 10 minutes of downtime. He says it might be 15 if the tech in the home office in Kentucky doesn’t do his job quickly.

Actually, the tech in Kentucky does the job in 5 minutes. Of course now my internal network has to be reset. This of course is my bailiwick so I send the tech on his way. Now, the nifty part of this is that my publically served sites are on external static IP addresses. Anything on my internal network shouldn’t affect them.

This is about the time my wife tells me that the internal network has failed. I explain that I have to reset it. Thirty minutes later it’s not working. Internally, I have a DNS server. The internal network is effectively one of my static addresses served via secure WiFi via NAT. For some reason, the WiFi Network has stopped talking to the DNS server altogether. I can ping the server. I can even do NSLOOKUP on the server. I just can’t get the network to do the resolving.

This situation also inconveniences my wife who’s trying to get information and files from our server for her web site and for an art project she’s trying to muster the energy to do for a colleague. The network is frustrating her and in turn really p*£&ing me off! I’m getting short of patience because I just don’t know why things aren’t working.

This disaster proceeds to burn the better part of 3 hours. I reset all the WiFi devices at least 10 times. I reboot the server (3 minute down times) at least 3 times. I finally change all the internal IP addresses and in doing so, make a bizarre mistake. I let the main WiFi unit choose it’s own address. DNS starts moving. But there’s a problem. Now the web server won’t come back up. Ah, there’s a conflict. The WiFi has decided it WANTS one of my served domains. (My wife’s gallery and blog)… Fine… I give her domain the old WiFi Address. Web Server is coming up. DNS is working. Another hour shot to hell.

It is now about 3 pm. I still have no clue what went wrong. I put my wife’s IP address into the server but that takes at least 30 minutes to propagate for me. I go to see if it’s propagated and I can’t hit the site. The network refuses to let me go to the server. (This is a situation we refer to as ITWTF) Then it hits me. I ping the domain’s IP address (this is effectively a “Knock knock…anyone home?”) The ping cannot go to the address. This address does not resolve.

Oh for heaven’s sake. I proceed to ping every one of my Static IPs. Of the n addresses I control. I can ping the first n/2 – 1. So, if I had for example 25, I can now reach 11. The mis-provisioned my account and dropped half of my addresses. I’ve killed the past 4 hours diagnosing a problem that one idiot tech screwed up by transposing ONE DIGIT.

The saving grace is that I prioritize my sites. The paying customers are on the lowest (smallest) IP cluster. As a result, those servers never even blinked at the networking mis-configuration. Some of my personal and favour-domains… those got knocked off for the better part of 4 hrs. I called up my ISP’s ‘elevated support center.’

I have access to the elevated support center because I have a problem that’s been open for the better part of 2 months and I mouthed off on Twitter about the problems I’d been having. When ESC (an ironic acronym) heard about the mistake and the amount of time both my wife and I lost… they were QUICK to fix it. They also offered me a token credit on the bill for the month.

Since then I have put all the IP addresses back where they are supposed to be. My internal network is still ‘renumbered’ because that wasn’t the problem and I just don’t want to put it back again yet. (Maybe later in the week) Less-Than-Humourously, the original problem still exists.

On the upside… on Saturday and Sunday despite this entire disaster happening, I picked up a new hosting customer from GoDaddy who’s been VERY happy with the level of service since joining my server.

Hopefully, I can bring in more paying hosting clients while I’m at it.

Friday, I’m in Hell.

(With all due respect)

If it’s not completely obvious, I run a hosting server. (Cue the endless attack from script kiddies and hackers) If one were to ask me what my profession is, it is Apple engineer. Granted this is without the actual employ from the great big Cupertino Company.

I started on the Apple ][ in 1979. (Not a plus, not an e, just the ][.) 48K of non-floating point, raw computing power. For those keeping count, I have been programming for 32 years. (Okay, 20 in base 16). I will not list the Apple products I have owned or used, as it would fill up a pretty long laundry list.

So currently I run a server. I have an Intel based Mac Mini running Mac OS X Server v 10.5. On this system I host about 8 different primary domains. I manage or administrate to some degree slightly over 70 domains. On top of the web hosting, there is also DNS, VNC, FTP, and a series of other acronyms. The result of this is also a fairly complex internal network that serves all the hardware in the house.

A little over a year ago I called the death knell of LiveJournal. Since then, of the nearly 580 ‘friends’ I had subscribed to: 27 of the journals have been deleted and purged. So let’s scratch that as 5%. As an example I looked at Saturday as a whole. There were 117 posts. 38 by users, 34 of those were unique users, 6 were simply posting aggregated Twitter feeds. So, let’s call that 28. That’d be about the same as the number of journals that have completely bailed, also about 5%. I’d say that LiveJournal is waning. At some point I’d love to do an in depth analysis.

But, I digress.

On most of my domains I am now running WordPress. This is a DIY blog. Now, being the social networking guru in my own mind that I believe myself to be; I have a complex network set up. I make a blog post on my WordPress Blog. WordPress generates a post to Twitter. Twitter is linked to Facebook. So anything I write in Twitter that doesn’t begin with a reply character (@) gets posted into my status. Then around 3:34 – 3:35 am (That’d be 25 or 6 to 4) all of my twitter posts (I HATE the term Tweet) are compiled into one LiveJournal post.

There. I’ve covered all the bases.

WordPress is amazingly configurable. It’s simple so you can use it as is, but you can also beat the crap out of it and change EVERYTHING. (Score one for open source). It’s also an active product. This means developers are always trying to make it better. This often includes adding new features to the system.

One feature I discovered Friday evening was the ability to import all of my posts from LiveJournal. I’m really not using LJ actively anymore. So I figured, “Cool! I’ll do that.” I threw the switch (or more correctly pressed the “Go” button) and then something went wrong. My computer (server) slowed down to the speed of molasses.

The server was giving me no indication that anything was going on or more correctly that anything was going wrong. At this point I should explain some little facts. I joined LiveJournal in October of 2001. This means my journal is about to turn 8½ years old. My journal also has nearly 3,000 entries with almost 12,700 comments. I did not take that into consideration when I said, “Go.”

Oh yes, there was one other little thing. Remember that whole Social networking interaction thing I have set up? Yeah… I managed to forget about that. My Twitter and Facebook subscribers however got the alert immediately. I managed to spam about 145 Twitter and Facebook posts in a period of 5 minutes. The up side is that I did in fact import those posts to my blog. The mechanism even backdated the posts to match, converted the ‘page cuts’ and password locked any protected posts. Of course, Facebook and Twitter noticed and turned off my cross-post relay once the inundation ceased. The inundation ceased when I managed to send a reboot command to my server.

I lost one subscriber on Twitter. I don’t know if he’s given up on my permanently or if he’ll come back now that I know what happened. I also will still be trying to import the rest… but only after safeguards are taken.

Next up, Friday afternoon… things got worse. This time… not my fault!