The domain switchbl8.nl now runs on a PC/server again. I replaced the motherboard, processor and memory, and ditched the old 9GB SCSI disk in favor of a 60GB SSD from Adata. Also, the system now runs Ubuntu 12.04 LTS x64, no longer the unmaintained 7.04 (in 32-bits).
The gallery is not back yet, gotta find out how to reimport/recreate the original structure, but as you can see, the weblog is up and running.
I just installed Jetpack from WordPress. Let’s see how that goes…
Dear Sayontan Sinha, I just donated because I think your theme for WordPress is awesome.
The Synology has a WordPress module, which works great and it is a recent version (not the latest). But you are bound to having your weblog in the folder “/wordpress”, and my weblog resides in “/blog” for ages now. I couldn’t find how to change it by modifying PHP files, wp_options entries and just renaming the folder. So….
# mkdir blog
# cd blog
# unzip /tmp/wordpress-3.4.1.zip
# mv wordpress/* ./
# rmdir wordpress
And point your browser to the URL “synology-ip-adres/blog” and do the install.
I used the database credentials created by the Synology WordPress module, and vanilla-WordPress then says: Hey, already installed. Via the Admin panel you upgrade your database, and you’re good to go. Now disable the Synology WordPress module. I haven’t uninstalled it, since I don’t know whether it will actually delete the database too.
I bought a Synology DS212j to be the replacement of the server. Great machine for very little money, but the transition is not as smooth as I hoped. My mail (domain switchbl8.nl) now runs via the Synology, not via this server anymore. Next is this blog, then the gallery. And the rest is just for fun, so to hell with it 😉
The reboots are still there. Sometimes the system is up for less then a minute, sometimes for more than 2 days. I now disconnected the SATA drives, so that means some stuff (e.g. my gallery) on the server is not available since that resides on the SATA drive. If the system stays up now, it means the extra SATA controller is broken. I hope so, since that’s an easy and cheap replacement.
I just replaced the CPU cooler in the server, along with its (broken) mounting bracket. The old one was the stock AMD cooler, on a plastic bracket that came with the motherboard. One of the plastic hooks was broken a long time ago, so the cooler was in place, but only just.
I now installed a Cooler Master Hyper 212 EVO so hopefully the reboots are gone now. In the BIOS the CPU temperature dropped from previously 57 degrees (C) to now somewhere around 34-35 degrees. Much better.
The server reboots did not stop. Just 20 minutes ago, while checking logs and other possibly strange behaviour, the server just rebooted as I was typing the next “pg /var/log/…..” command. I entered the BIOS, to see if the system itself was healthy. CPU temperature went up from 57 to 61 in a couple of seconds whilst the system was doing nothing.
AHA!
I unplugged the system, opened the case, and voila………DUST!
With the vacuum cleaner I sucked out the DUST as gently (lowest power) but as thorough as possible, so hopefully things go better from now on.
For some reason the server has been rebooting a couple of times per day since June, 5th. Not sure why, can’t find any strange things happening on the system. Hope it stays up now.
Yesterday I switched from ADSL to cable internet, upgrading the line from 6/1Mbit (max 20 means 6 where I live) to 60/6Mbit. Unfortunately I don’t have a fixed IP address anymore, but there are ways to work around this. I choose DynDNS Free to take care of that problem. Easy peasy!
When you can read this, it means it works 😉
One thing I have to do later is upgrade my router, since I now basically have a 20/6Mbit connection now because my router only has a 100Mbit LAN port, and the internet modem then caps the connection. Not sure why, but a speedtest revealed that.