1) Check Bluetooth Service.

systemctl status bluetooth.service

bluetooth.service – Bluetooth Manager
Loaded: loaded (/lib/systemd/system/bluetooth.service)
Active: inactive (dead)
CGroup: name=systemd:/system/bluetooth.service

It shows my bluetooth is inactive (dead).

2) Activate Bluetooth Service.

First priority is to enable the service to be run on every startup, to do this use following command.

systemctl enable bluetooth.service

ln -s ‘/lib/systemd/system/bluetooth.service’ ‘/etc/systemd/system/dbus-org.bluez.service’
ln -s ‘/lib/systemd/system/bluetooth.service’ ‘/etc/systemd/system/bluetooth.target.wants/bluetooth.service’

Secondly you need to run the service to have bluetooth working on running system.

systemctl start bluetooth.service

Here you go, all bluetooth devices will be visible and can connected to your newly installed/updated Fedora 15.

Confused about systemctl command, please look fedora documentation.

[root@server1 ~]# mysql -u root -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 179
Server version: 5.0.77 Source distribution

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the buffer.

mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: 192.168.0.1
Master_User: mysqladmin
Master_Port: 3306
Connect_Retry: 5
Master_Log_File: mysql-bin.000019
Read_Master_Log_Pos: 18816335
Relay_Log_File: mysqld-relay-bin.000153
Relay_Log_Pos: 593
Relay_Master_Log_File: mysql-bin.000019
Slave_IO_Running: No
Slave_SQL_Running: No
Replicate_Do_DB: test1
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave.
Skip_Counter: 0
Exec_Master_Log_Pos: 18337925
Relay_Log_Space: 479619
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: NULL
1 row in set (0.00 sec)

ERROR:
No query specified

1) Get Log Filename and Position from Master.

To fix this we need two values from MySQL Master Server. i.e Master Log File Name and Master Log Position. To achieve this run following command on MySQL Master Server.

mysql> show master status\G;
*************************** 1. row ***************************
File: mysql-bin.000020
Position: 5387330
Binlog_Do_DB: test1,test2
Binlog_Ignore_DB:
1 row in set (0.00 sec)

ERROR:
No query specified

2) Fix Slave Server

To fix slave, first you need to stop slave on it and then run change master command with require values and start slave again to start working.

mysql> slave stop
-> ;
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> change master to master_log_file=”mysql-bin.000020″, master_log_pos=5382560;
Query OK, 0 rows affected (0.03 sec)

mysql> start slave;
Query OK, 0 rows affected (0.00 sec)

To check whether slave is OK or not, run slave status command on Slave Server.

mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.1.252
Master_User: mysqladmin
Master_Port: 3306
Connect_Retry: 5
Master_Log_File: mysql-bin.000020
Read_Master_Log_Pos: 5459989
Relay_Log_File: mysqld-relay-bin.000002
Relay_Log_Pos: 77672
Relay_Master_Log_File: mysql-bin.000020
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB: test1
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 5459989
Relay_Log_Space: 77672
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 0
1 row in set (0.00 sec)

ERROR:
No query specified

and you can see that there is no Last error and Seconds_Behind_Master value is 0 indicates we are totally sync with Master.

1) Install RPMFusion Repositories

rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
rpm -ivh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

2) Install Broadcom Wireless Card Driver

yum install broadcom-wl kmod-wl

reboot the system to get modules get loaded. But when you try to scan using NetworkManager or wlaassistant, it show’s no wireless access point found. Even they are visible on computer desk available next to you.

3) Fixing Access Points not showing.

Its a quick and dirty fix from fedora forums.

vi /boot/grub/grub.conf

edit your available kernel lines and append intel_iommu=off in the end for kernel parameters.

kernel /vmlinuz-2.6.33.5-112.fc13.x86_64 ro root=/dev/mapper/vg_server1-LogVol01 rd_LVM_LV=vg_server1/LogVol01 rd_LVM_LV=vg_server1/LogVol00 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet

change to

kernel /vmlinuz-2.6.33.5-112.fc13.x86_64 ro root=/dev/mapper/vg_server1-LogVol01 rd_LVM_LV=vg_server1/LogVol01 rd_LVM_LV=vg_server1/LogVol00 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet intel_iommu=off

save the file and reboot the system again to get kernel to load following kernel parameter and bravo you can see the Access Points

vi /etc/pam.d/gdm

find following line

auth       required    pam_succeed_if.so user != root quiet

comment out by placing # at beginning to disable this check

#auth       required    pam_succeed_if.so user != root quiet

save and close the file.

vi /etc/pam.d/gdm.password

find following line

auth       required    pam_succeed_if.so user != root quiet

comment out by placing # at beginning to disable this check

#auth       required    pam_succeed_if.so user != root quiet

save and close the file. Now logout from terminal or GUI and relogin with root from GUI.

1) Install Pre-Requisite i686 Packages.

Pre-requisite contain pulse audio because of to use call in/out.

yum -y install libXv.i686 libXScrnSaver.i686 qt.i686 qt-x11.i686 pulseaudio-libs.i686 pulseaudio-libs-glib2.i686 alsa-plugins-pulseaudio.i686

2) Download Skype i586 (fedora10+)

wget http://download.skype.com/linux/skype-2.1.0.81-fc10.i586.rpm

3) Install Skype

rpm -ivh skype-2.1.0.81-fc10.i586.rpm

Run it from Applicaition or command line and bravo its running

Please comment for any questions.

1 ) Update RPM Package

First rpm package has to be upgraded.

yum update rpm

2) Update full system

Then you need to upgrade full system to have updated Fedora 12 packages

yum update

clean the yum cache after upgrade.

yum clean all

and reboot the system.

reboot

3) Upgrade to Fedora 13 using preupgrade

First you need to install preupgrade (it can be already install but for sure run following install command)

yum install preupgrade

When installation completes run preupgrade-cli to get list of releases you can update to, you should get Fedora 13 (Goddard) in the list.

preupgrade-cli
Loaded plugins: blacklist, whiteout
No plugin match for: rpm-warm-cache
No plugin match for: remove-with-leaves
No plugin match for: auto-update-debuginfo
No plugin match for: presto
Loaded plugins: refresh-packagekit
please give a release to try to pre-upgrade to
valid entries include:
“Fedora 13 (Goddard)”
“Rawhide”

In above output i have Fedora 13 (Goddard) available for upgrade. Now run preupgrade-cli with Fedora 13 to start upgrade process.

preupgrade-cli “Fedora 13 (Goddard)”

When it finish, reboot your system

reboot

The upgrade will be happen during reboot, so be patient and wait until it get updated and then rebooted.

After reboot you will have Fedora 13 and enjoy the new features.

vi /usr/share/doc/kernel-doc-2.6.18/Documentation/networking/bonding.txt

The Linux bonding driver provides a method for aggregating multiple network interfaces into a single logical “bonded” interface. The behavior of the bonded interfaces depends upon the mode; generally speaking, modes provide either hot standby or load balancing services. Additionally, link integrity monitoring may be performed.

We have multiple bonding implementation using two or three ethernet card but with single bonding interface and it can be found on internet. Using multiple bonding interfaces are rear and all of them using different method to implement it because the documentation method isn’t working now. The document says to load multiple bonding modules for multiple bonding interfaces but using -o option within options in /etc/modprobe.conf and its not support by RHEL 5 and later releases. Therefore we will use BONDING_OPTS options in network scripts of bonding interfaces.

As we are implementing one of the biggest Oracle RAC implementation, we need load balancing with fault tolerance of network to access the storage without any point of failure. Therefore we are using bonding mode 2 (balance-xor), This mode provides load balancing and fault tolerance.

All of our servers are with 4 ethernet cards and we connect 2 ethernet interfaces (eth0 and eth1) with switch1 and 2 interfaces (eth2 and eth3) with switch2 to have multiple paths. We will create two bonding interfaces bond0 (eth0 and eth2) and bond1 (eth1, eth3). So if eth0 (from switch1) fails the bond will continue to use eth2 (from switch2) and load balance between two switches.

1) Load Bonding Driver/Module

We need to edit /etc/modprobe.conf to load bonding module into linux.

vi /etc/modprobe.conf

add following lines

alias bond0 bonding
alias bond1 bonding

2) Configure ethernet interfaces.

As we discussed we have 4 ethernet interfaces, so we need to put right configuration to team multiple cards in it to work as bond. You need to edit/add following as it is

vi /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

vi /etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1
USERCTL=no
ONBOOT=yes
MASTER=bond1
SLAVE=yes
BOOTPROTO=none

vi /etc/sysconfig/network-scripts/ifcfg-eth2

DEVICE=eth2
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

vi /etc/sysconfig/network-scripts/ifcfg-eth3

DEVICE=eth3
USERCTL=no
ONBOOT=yes
MASTER=bond1
SLAVE=yes
BOOTPROTO=none

3) Configure bonding

Create bond0 and bond1 scripts under /etc/sysconfig/network-scripts same as ethernet interfaces.

touch /etc/sysconfig/network-scripts/ifcfg-bond0
touch /etc/sysconfig/network-scripts/ifcfg-bond1

vi /etc/sysconfig/network-scripts/ifcfg-bond0

DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
BONDING_OPTS=”max_bonds=2 miimon=100 mode=2 primary=eth0″
NETMASK=255.255.255.0
IPADDR=192.168.0.1

Change IPADDR and NETMASK as per your environment.

vi /etc/sysconfig/network-scripts/ifcfg-bond1

DEVICE=bond1
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
BONDING_OPTS=”max_bonds=2 miimon=100 mode=2 primary=eth1″
NETMASK=255.255.255.0
IPADDR=192.168.0.2

Change IPADDR and NETMASK as per your environment. where

max_bonds = Specifies the number of bonding devices to create for this instance of the bonding driver

miimon = Specifies the MII link monitoring frequency in milliseconds. This determines how often the link state of each slave is inspected for link failures.

mode = Specifies one of the bonding policies, and we are using 2 as defined above

primary = A string (eth0, eth2, etc) specifying which slave is the primary device.  The specified device will always be the active slave while it is available.  Only when the primary is off-line will alternate devices be used

4) Test

Restart network init script, it will first load bonding module and then setup bond0 and bond1 interfaces.

/etc/init.d/network restart

/etc/init.d/network restart
Shutting down interface bond0:                             [  OK  ]
Shutting down interface bond1:                             [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface bond0:                               [  OK  ]
Bringing up interface bond1:                                [  OK  ]

Check interfaces

ifconfig

bond0     Link encap:Ethernet  HWaddr 00:24:E8:4A:F8:77
inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:27908 errors:0 dropped:0 overruns:0 frame:0
TX packets:18422 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:23044634 (21.9 MiB)  TX bytes:2218142 (2.1 MiB)

bond1     Link encap:Ethernet  HWaddr 00:24:E8:4A:F8:79
inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:70 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15611 (15.2 KiB)  TX bytes:3524 (3.4 KiB)

eth0      Link encap:Ethernet  HWaddr 00:24:E8:4A:F8:77
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:27474 errors:0 dropped:0 overruns:0 frame:0
TX packets:18422 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23013444 (21.9 MiB)  TX bytes:2218142 (2.1 MiB)
Interrupt:106 Memory:d2000000-d2012800

eth1      Link encap:Ethernet  HWaddr 00:24:E8:4A:F8:79
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:67 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15419 (15.0 KiB)  TX bytes:3524 (3.4 KiB)
Interrupt:114 Memory:d4000000-d4012800

eth2      Link encap:Ethernet  HWaddr 00:24:E8:4A:F8:77
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:434 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31190 (30.4 KiB)  TX bytes:0 (0.0 b)
Interrupt:122 Memory:d6000000-d6012800

eth3      Link encap:Ethernet  HWaddr 00:24:E8:4A:F8:79
UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:192 (192.0 b)  TX bytes:0 (0.0 b)
Interrupt:130 Memory:d8000000-d8012800

Verify bonding actually works

cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.2.4 (January 28, 2008)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth0
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:24:e8:4a:f5:cc

Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:24:e8:4a:f5:d0

cat /proc/net/bonding/bond1
Ethernet Channel Bonding Driver: v3.2.4 (January 28, 2008)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth1
Currently Active Slave: eth1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:24:e8:4a:f5:ce

Slave Interface: eth3
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:24:e8:4a:f5:d2

If you have any question please use comments.

Like in CentOS 5.3 you cannot update PHP version above 5.1.x. I have been using different repositories to update PHP to latest version but most of them break rpm one or two, which may let to unstable Server.

AtomicRocketTurtle (http://www.atomicrocketturtle.com/) company i found that regularly updating applications used in CentOS/Fedora/RHEL. You will be seeing that i will be updating PHP from version 5.1.x to 5.2.12, which is latest till this date.

1) Install AtomicRocketTurtle Repository.

Pre-requisite of atomicrocketturtle repository is yum, you should be confirm that you have yum install specially on CentOS. Some of the VPS comes without yum installation, so if your server doesnt have yum on CentOS 5.x, use following my post to install yum. http://www.sohailriaz.com/howto-install-yum-on-centos-52-vps/

To install atomicrocketturtle repository run following command.

wget -q -O – http://www.atomicorp.com/installers/atomic.sh | sh

This script will automatically detect your OS and install approperiate repository.

2) Update PHP

First check the available PHP version on atomic repository

yum list | grep atomic | grep php

Get the list of your install rpm and update following.

rpm -qa | grep php
php-cli-5.1.6-23.2.el5_3
php-5.1.6-23.2.el5_3
php-gd-5.1.6-23.2.el5_3
php-pdo-5.1.6-23.2.el5_3
php-common-5.1.6-23.2.el5_3
php-imap-5.1.6-23.2.el5_3
php-xml-5.1.6-23.2.el5_3
php-mbstring-5.1.6-23.2.el5_3
php-mysql-5.1.6-23.2.el5_3

It can be different for you, just create the list like below i used for update PHP. I used every package name as i dont want to miss any of the module it has.

yum update php php-cli php-gd php-pdo php-common php-imap php-xml php-mbstring php-mysql

at end you will see this

Updated: php.i386 0:5.2.12-3.el5.art php-cli.i386 0:5.2.12-3.el5.art php-common.i386 0:5.2.12-3.el5.art php-gd.i386 0:5.2.12-3.el5.art php-imap.i386 0:5.2.12-3.el5.art php-mbstring.i386 0:5.2.12-3.el5.art php-mysql.i386 0:5.2.12-3.el5.art php-pdo.i386 0:5.2.12-3.el5.art php-xml.i386 0:5.2.12-3.el5.art
Complete!

If you have any question please use comments.

After diagnosing it, I found up2date is running on my server, so first thing just clear that if something related to rpm is running including yum or up2date, it will lock some files to do any other rpm transaction.

I use kill command to kill the process of up2date but still the problem was same, rpm got stuck / hang and wont do anything further.

Then i issued lsof command to find which files were locked and in used by any old or dead process related to rpm

lsof | grep /var/lib/rpm/

I found /var/lib/rpm/__db* are locked by some process maybe up2date, so i need to delete them to release rpm database for further transaction.

rm -rf /var/lib/rpm/__db*

and it works, all the installation/query of rpm working absolutely fine. I hope this will help.

panic[cpu0]/thread=xxxxxxxx: page_unlock: page xxxxxxx is not locked

After searching i found that minimal required RAM for installation of Solaris 10 is 768MB and i was using 512MB. So i increase the RAM under my KVM configuration and bingo the installation starts smoothly.