Skip to main content

enterprise ready cent os - the install

This weekend, I decided to blow away fedora core 3 and install something supposed to be more stable and enterprise ready. Part of the reason was also to do with another disk reshuffle and I've been finding an excuse to swap my creative live drive with my cdrom. the SDPIF cable was blocking the tray from opening properly. So why not just do a new distro upgrade as well.

Being familiar with redhat, I didn't think it would be that much of a challenge. Well, needless to say there were a couple of hickups. The first one being I had the install DVD and my machine didn't have the DVD rom. So off I went to download the 4 cd's.

After the installation, it refused to boot failing at the boot loader. I decided to stick to defaults and use the suggested LVM with root and swap. I modified the LVM to include a bigger mount for /home. As I was going to change my distro if things go sour.

After the machine booted sucessfully with the recommended disk partitions, I stuck in my backup harddrive and it didn't seem to boot properly. Anyway, by that time I was too tired and decided to reboot for the heck of it and go to sleep.

The next morning to my suprise, I saw the login screen of centos waiting for me. In glee, I decided to log in only to realise that it was unnaturally slow and it popped an error saying that it can't find itself in its host that will cause gnome to act weird.

I couldn't even start a terminal, but somehow the machine came back to life when i used system-config-network to disable the eth0.

Great, now I got a terminal. I decided to modify the hosts file and resolve.conf. I even decided to specify the IRQ for each network card so as I dont confuse it. The config all looked fine, but my network was still broken and I couldn't even ping my gateway. Hmm, broken network card?

So I rummaged though my spare parts and found another 3com network card. I pulled the machine apart again. After the card was changed, the machine didn't even boot to bios. Argh. Ok, I swapped the previous card back. Made in Ireland vs made in Singapore.

Whoo Hoo, it booted and network works for some strange reason. Maybe all it needed was a reboot.

Anyway, what do you do first after you install centos?

Download and install xmms-mp3 from

http://mirror.optusnet.com.au/dag/redhat/el4/en/i386/dag/RPMS/xmms-mp3-1.2.10-11.1.2.el4.rf.i386.rpm

Yes, the compiled binaries for RHEL 4 works for Centos 4.3 as well. Yay, joy. my machine now plays my mp3s.

Another one down and tons more to go.

Comments

Popular posts from this blog

Multiple Broadlink RM mini 3 integration using MQTT

Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this. https://lprhodes.github.io/slate/

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone https://github.com/eschava/broadlink-mqtt

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'
4. Start the python script and check that it started and detected all the RM devices.
Check the log file to see what the IP / MAC addresses are. DEBUG Connected to RM2 Broadlink device at …

Fibaro HCL Virtual Device Slider

How to setup Fibaro home center lite (HCL) slider for virtual devices.

As the Fibaro HCL does not support LUA. The question was how to update the number value of the slider to send to the HTTP string. Thanks to this site which is a really good reference https://www.vesternet.com/resources/application-notes/apnt-88/

The 2 use cases here are;

Sonos HTTP API Volume

To allow for volume control for all Sonos devices, add a virtual device with the IP address for SONOS HTTP API and specify the default port to 5005. Create Slider and put the following text into the string.

GET /volume/_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A


Domotiz Virtual Devices

GET /json.htm?type=command&param=switchlight&idx=XX&switchcmd=Set%20Level&level=_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Replace XX with the device ID.

Restart Fibaro HCL when it stops working automatically

It seems that the Fibaro HCL seems to hang every now and then. Instead of trying to restart it regularly, which doesn't really work, as it's almost impossible to predict when this will happen.

This method checks that the HCL is actually running and in the event it stops working, trigger a script that will restart it.


1. Get a non Fibaro controlled power plug and scripts to control it.

I used a wifi smart plug, TP-link HS100 and downloaded the scripts from

https://blog.georgovassilis.com/2016/05/07/controlling-the-tp-link-hs100-wi-fi-smart-plug/

2. Create a bash script to restart the Fibaro, e.g. restart_fibaro.sh

#!/bin/bash

ip_addr=
scripts=

$scripts/tplink-smartplug.py -t $ip_addr -c off
sleep 10
$scripts/tplink-smartplug.py -t $ip_addr -c on


3. Create a test global variable in the Fibaro HCL

Go to the variables panel and create a test variable, e.g. Test


4. Add a cron entry to test that the Fibaro API is still working and restart if it's not.

The cron script is scheduled ev…