Message to self: to have all data from servage retrieved directly to the new server this following command can be used. You need SSH on your new server.
lftp -u ‘[username],[password]’ ftp.servage.net -e “mirror /path /destination/path new server”
This command needs to be entered in a ssh session. As we speak this command is already downloading my data for about 12 hours now ..
Due to some issues I have now a new server for all my websites. Slowly I am copying all data and databases. For you, this site visitor, it means more speed, quicker loading of pages. So be happy ;-)
I’ve 4 databases running for this site (banner, trac, forum, weblog) .. and all data was quickly transferred. Not much I had to do to have all things running .. DNS updated .. Whoalla ..
if you read this, your DNS is updated and the site is running from the new server .. I will have to test the mail .. but we will see how that is working ;-)
Finally all my domains under 1 roof ..
I’ve moved all my domains from Gandi.net and other registrars to a ‘dutch’ home and I have total control over my own DNS by using DNSTOOLS.NL ..
22 domains where most of them are running over my DSL line and this server .. Greatest and kewlest domain I have is aroundtheworld.net .. ;-)
I’ve written earlier a simple howto for users with a CH3SNAS to work with NFS. UNFS is a user space implementation of the NFSv3 protocol. This is working flawlessly on the CH3SNAS with various Linux PC’s I am running (CentOS, Debian, Linux Embedded device etc.. )
but for a VMware implementation I need the READDIRPLUS procedure which is not available in UNFS. So I need to run Kernel-NFS on the CH3SNAS
Fonz fun_plug is providing Kernel NFS (enabled in the CH3SNAS) and UNFS. Installation is easy and almost fool proof.
The issue is following: on all my linux boxes (CentOS, Debian etc.. ) I get following message:
mount: mount to NFS server ‘192.168.1.60’ failed: timed out (retrying).
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting
All mount points on 192.168.1.60:
192.168.1.100:/mnt/HD_a2
and even syslogd gives on the NFS server (CH3SNAS):
Jun 12 18:33:07 DEVELOPMENT daemon.notice mountd[1868]: authenticated mount request from 192.168.1.100:615 for /mnt/HD_a2 (/mnt/HD_a2)
I am totally not understanding why I get time-outs. I do not have a firewall, I do not use iptables. Today I tried in another environment the same: always the error:
mount: mount to NFS server ‘192.168.1.60’ failed: timed out (retrying).
suddenly here at home after about 20 minutes trying to mount the NFS share, the NFS server has been mounted on my local system. But when umounting and mounting again I have again same situation. In my work environment it was totally not possible (standard Debian setup and a CentOS configuration) to have the NFS share mounted. Although it is similar setup ..
So although al tools tells me that everything is correct: I am not getting any mount :-(
Is there anyone with enough NFS knowledge who can tell me why the NFS share is not mounted?
This morning a memory issue caused the server to crash
This afternoon I have updated PHP 4 to PHP5, this makes the server more flexible for certain scripts.
Noticed that the ftp script for the backup still was messing up my cron, but I was able to kill those sessions.
My backup FTP script is NOT GOOD.. it exhausted my memory ?? on the webserver caushing the server to ‘crash’ / not react for 4 hours, even connecting my monitor to the server: I could type my username, but login: nope ..
So message to self: how the hell can I FTP 40GB of data via a shell script without exhausting my memory .. <sigh> …
rebooting (fingers always crossed) and after 5 minutes the server was up again
en ineens kregen we geen mail meer binnen..
Mar 25 21:01:34 wb sendmail[23631]: ruleset=check_relay, arg1=[192.168.1.63], arg2=127.0.0.2, relay=[192.168.1.63], reject=554 5.7.1 Rejected 192.168.1.63found in relays.ordb.org
blijkt dus al geruime tijd de relays.ordb.org niet meer te bestaan en sinds vandaag lijkt het erop dat alle e-mail wat hier binnenkwam tegengehouden werd door bovenstaande. De dnl optie binnen sendmail.cf verwijderd en met m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf de files weer aangemaakt
sendmail restarted en hop .. probleem opgelost .. was even wat gezoek, maar het duurde gelukkig niet lang.
rpm -qa | grep kernel
(decide what you want to get rid of)
yum remove kernel name
reboot
Today I’ve installed an old BK500MI UPS from APC to keep the server running when there is a short period of time no power. Initial test shows me that a PC running Windows XP can still be online for 15 minutes. Fits perfect my needs.
Updated sendmail.mc. After the big CentOS update the sendmail.mc in use was replaced by a new version. Now adding again Spam features. Add these features after the delay_checks
dnl FEATURE(delay_checks)dnl
FEATURE(`dnsbl’,`dnsbl.njabl.org’,`”550 Mail from ” $&{client_addr} “rejected – see http://njabl.org/”‘)dnl
dnl # FEATURE(`dnsbl’,`dnsbl.sorbs.net’,`”554 Rejected ” $&{client_addr}” found in dnsbl.sorbs.net”‘)dnl
FEATURE(`dnsbl’,`relays.ordb.org’,`”554 Rejected ” $&{client_addr} “found in relays.ordb.org”‘)dnl
FEATURE(`dnsbl’, `bl.spamcop.net’, `”550 – Email blocked by SpamCop see: http://spamcop.net/bl.shtml?”$&{client_addr}’)dnl
FEATURE(`dnsbl’,`sbl-xbl.spamhaus.org’,`554 Rejected – see http://www.spamhaus.org/’)dnl