Over the last few days I’ve noticed that my web server has been a little unreliable. As usual there’s nothing obvious in the logs to recommend just what the cause might be. I’ve made some changes via ISPConfig and it’s possible that I may have set up something wrong! as GoogleBot has complained that it can’t reach the robots.txt file (this is in the root of the web server and is visible to me) So there’s a gremlin hiding here somewhere!
This is also effecting my mail server, So the occasional mail is bouncing (inwards) I just hope that this isn’t the beginning of a failing SQL table…
Yesterday (30th November) I rebuilt this server due to a slight problem/mistake that I caused when attempting to install ISPConfig3 on a server that had already been configured with a working environment. Notice how I said ‘working’ because after completing the install of ISPConfig3 this is where things got rather complicated rather quickly! I’ve not had much experience with ISPConfig but I was keen to see how it works and to see if it would make setting up email & web services. Well after 2 actual rebuilds I believe that I’ve managed to achieve what I set out for.
After the ‘First’ install (ISPConfig) It totally broke the server! All Web address resulted in 500 errors! Postfix was complaining about SASL Authentication I knew that I was either going to spend a lot of time trying to sort out the mess or just cheat and start a fresh. So after about 10 seconds, I said to myself… “SCREW THIS” let’s just backup what I need and start fresh (something that is clearly stated for ISPConfig!)
Skip forward to mid morning, and things were going well until I enabled squeeze backports, then ran a system update thinking that gives me the advantage of updated software that’s not included with Debian Stable. Oh boy what a “HUGE” mistake that was! My fresh install was now pretty much in the same condition as it was when I broke it!
So again, do I even attempt to work out just how things went so horribly wrong? Oh no screw that! Enter rebuild #2. So one would expect by now that I should have a slight better idea on what/whatnot to do! Yeah OK I’m learning! but in all fairness this server is all about learning. I’m not qualified in this field of work, for me it’s just a hobby.
So there’s going to be broken links until I restore some content (wiki, statusnet, forum) as I’ll be working on that in the coming days… 🙂
I’ve uploaded to the latest nightly (as of writing) and it appears that page links are broken. Posts are fine so will have to await for tomorrow’s build to see if this is fixed, or I’ll need to file a bug report (if not reported already)
So one doesn’t use nightly builds unless you expect some breakage 🙂
Well on Tuesday (5th June) I finally got my mitts on the Galaxy Nexus (i9250) This now brings about retirement of my HTC Desire (A8183) this was my launching into the world that is Android! and once my contract was up I knew that I wanted the development phone from this point forward.
Ice Cream Sandwich is a nice layout from that I’m used to with earlier versions of Android 2.1 – 2.3 and as I’ve used Cyanogenmod for about the last 18 months I prefer the native android look and feel over the stock version of HTC Sense that originally came with the Desire. The Nexus had a slightly modified release of ICS 4.02 (Telstra customised with Australian English) that I replace with the current (at the time of writing) 4.04 development build of Yakju and I’ve added SuperSU (root)
One of the main issues with the HTC Desire was its lack of storage space (a total of 148Mb with stock Hboot) but now with the Nexus that’s no an issue as it has a comfortable 13Gb to play with. The only part that I didn’t realise was the lack of an SDcard slot, but I don’t see that I’ll need to add more storage to it anyway.
With the lack of any hardware buttons this gives a nice smooth appearance but I was at a small loss as I tended to use the optical pointer, so I’ve found myself floundering a little if I need to change the cursor or place but I soon learnt that by holding you finger down on the screen you get an arrow that you can the move about any text. This will take a little getting used to but I suppose I was a little spoilt with that feature on the Desire!
So after only having the nexus for 3 days I’m very happy with it! You can expect more posts about my journey with the Nexus as I discover new things. At this point I’m sticking with Jakju, but I will no doubt experiment with other custom roms in the future… 🙂
I know that by writing this entry is going to jinx the outcome, but this Saturday (June 2nd) I will be getting a new mobile phone. I’ve been using a HTC Desire since August 2010 and it’s time to update to a newr handset. My phone of choice is the Samsung Galaxy Nexus! Now although this phone isn’t the latest an greatest handset, for me it is more important that I can customise the phone to my liking without any barriers that are imposed on most android phones (locked bootloader)
Now I’m sure that I’ll be posting many items about the nexus as I explore the possibilities that are available. So watch this space! 🙂
For some time now I’ve been using Arch Linux for my desktop pc. For those who have no idea what that is/means then go back to your coffee/tea and come back in 5 minutes! No seriously, Arch is just a distribution of Linux aimed at being minimalistic so you build your desktop to what you want. Arch is a bleeding edge distribution that pretty much has the latest software that’s generally available. Now this is great for the person who prefers to have a constant stream of updates (aka rolling distribution) However some prefer a slightly slower release that hopefully has a higher level of stability. This is where Arch can bite you (big time) if you don’t pay close attention to the pending updates, as was the case for me about a month or so ago. The ln board graphics chip is a dreaded ATI (my first time for this chip type) as previously I’ve had Nvidia cards. Anyway there was the April ATI update awaiting and not giving it the attention that I normally would I allowed it to be applied. At this point all looked like a normal update until I rebooted (included a kenel update) and this is when my trouble began!
Being rather optimistic, I figured that within a day or three there would be a patch to fix the segmentation fault I was now getting from xorg-server. Now my Minecraft server resides on this pc so I needed to keep that running so I opted to use my Eee PC for what I believed to be a temporary period until a fix came through. So today I decided to tackle the problem with the intention of getting the existing software to behave as it should. After a few hours of no result it was getting to the point where a re installation would be the better solution rather than going around in circles (as I was)
15 minutes later and “Bingo!” was back in business. All that was required now was to restore the data backup and install a few programmes.
I suppose if there’s a moral to the story it’s be aware that the bleeding edge will at times give you grief! 😀
Ok so if you recognise the critter in this image then your half way to understanding what I’m talking about! Port 70 is traditionally reserved for the Gopher protocol. What is Gopher? Well it’s a slim text only layout that pre dates the internet as we know it as (aka HTML)
Gopher started life back in 1991 and lost popularity in the mid 1990’s in favour to HTML (port 80) Just recently I have rediscovered Gopher and so have a group of friends (identi.ca, StatusNet)
I’m hosting a Gopher service using Pygopherd. This has the advantage of serving both Gopher & HTML simultaneously. This means that you can point your browser at vk7hse.org:70 and view using HTML then if you have the Overbite plugin installed for your browser you can then switch to Gopher.
Take a look, follow the links and enjoy the world of Gopher!