Moving to #Freebsd ?

I am thinking of moving my main server to FreeBSD. My main goal is to learn the OS. I have gotten so use to Debian and It seems like it is no longer a challenge to me. At least I think with #FreeBSD, I do not have to worry so much with upgrading. Right now, since I track Debian Unstable, I have to constantly update when I am in there. Also I also have to update the kernel. All of this I know are avoidable. I could just go with Debian stable and I could just choose to use the distro kernel and not have to worry with compiling the kernel.

Anyway, I think this would be a huge undertaking. I probably would have to plan this in stages. For one, how do I migrate without significant downtime???


Howto Fix text messages when switching from an iPhone to an Android phone

If you are not getting any text messages from your contacts after switching to Android, you have to remove your number from Apple’s servers.

First, put the old sim in your iPhone and disable iMessage.
Next, go to this webpage.
Follow the instructions and you should be good to go.
HTH. đŸ™‚

Freeswitch init via SystemD on Debian Unstable

I ran into an issue when I upgraded my Debian unstable box to systemd. I have FreeSWITCH on this box and the systemd initiation is not working.

Dec 14 18:05:44 mail systemd[1]: freeswitch.service: Start operation timed out. Terminating.
Dec 14 18:05:48 mail systemd[1]: Failed to start freeswitch.
Dec 14 18:05:48 mail systemd[1]: freeswitch.service: Unit entered failed state.
Dec 14 18:05:48 mail systemd[1]: freeswitch.service: Failed with result 'timeout'.
Dec 14 18:05:48 mail systemd[1]: freeswitch.service: Service hold-off time over, scheduling restart.
Dec 14 18:05:48 mail systemd[1]: Stopped freeswitch.
Dec 14 18:05:48 mail systemd[1]: Starting freeswitch...
Dec 14 18:05:50 mail systemd[1]: freeswitch.service: PID file /run/freeswitch/ not readable (yet?) after start: No such file or directory

After much research and trial and error, I finally found the solution. I had to change the PIDFile statement of the freeswitch.service file.


; service
ExecStart=/usr/local/freeswitch/bin/freeswitch -u freeswitch -g freeswitch -ncwait $DAEMON_OPTS

;ExecStart=/usr/local/freeswitch/bin/freeswitch -u freeswitch -g freeswitch -ncwait -nonat -rp
; exec


Systemd in Debian

I notice that my raid array is not starting up properly after I boot a new kernel, 4.3. I figured out that I could manually assemble the array with the command below. However, I want to automate the process.

mdadm --assemble --verbose /dev/md127 /dev/sdb1 /dev/sdc1

The solution is making the necessary changes in mdadm.conf file so that the system can see the array following a reboot. Here is my mdadm.conf file.

# Please refer to mdadm.conf(5) for information about this file.

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
#DEVICE partitions
DEVICE /dev/sd[bcdjkl]1

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system

# instruct the monitoring daemon where to send mail alerts

# definitions of existing MD arrays
ARRAY /dev/md127 metadata=0.90 UUID=a42d6399:f6d2b49c:924717a0:72ea5865 devices=/dev/sdb1,/dev/sdc1

# This file was auto-generated on Mon, 16 Jul 2012 06:37:54 -0400
# by mkconf 3.1.4-1+8efb9d1+squeeze1

Howto replace a bad hard drive on Software RAID

On my server, I have a drive on software raid  mirroring. This array stores all my data for this blog. A couple of weeks ago I got a degraded array message. When I try to reboot the server, I heard a clicking noise on one of the mirrored drive. These are the steps I did to replace the drive.

  1. fdisk -l
  2. fdisk partition the new hard drive
  3. add the new drive

mdadm --manage /dev/mdX --add /dev/sdX