8/09/2012

view confs without comments

Just to note to myself. how to generate clean configs w/out any comments


sed -e '/^$/d;/^#/d;/^;/d' /etc/php.ini > php.ini.clean

result

root@ ~ # cat /etc/php.ini |wc -l
1249
root@ ~ # cat php.ini.clean |wc -l
182


5/24/2012

{new stable release} Zabbix auto install scripts

!!!NOTE: this scripts only for education/testing/investigation purposes, use on your own risk

I've prepared 2 auto Zabbix 2.0.0  installation scripts, tested on Centos 5.8 and 6.2

https://www.dropbox.com/s/pdekmf5yi6on8o3/zabbix20_el6_install.sh << Centos 6.2
https://www.dropbox.com/s/6sdlerh4ufthys4/zabbix20_el5_install.sh << Centos 5.8

short desc
#!/bin/sh
#
# Centos 6.2 (5.8) zabbix 2 install w/ psql9.1 jabber IPv6 support
#
# known problems:
# zabbix web config not fully configured during installation
# need manually to  setup $ZBX_SERVER  and $ZBX_SERVER_NAME parameters after installation finish
# after installation rpm prepared and it is in /root/rpmbuild/RPMS/
# do not know why but in this version zabbix won't work with DB user other than root had to create role for root
#
# reboot required after installation
#
#
# software distributed under the License is distributed on an "AS IS" BASIS,  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND
# (c) Michael Veselovski support@omgsw.com
# v1: initial release 4/10/2011
# v2: 24/12/2011 new release:
# - psql 9.1 support added
# - db user should be provided during installation
# - zabbix 1.9.8 support added
# v3.1: 15/05/2012 new release
# - script complete rewitten for Centos 6.2 suppport
# - script installing Zabbix 2.0.0rc4 /psql
# v3.2: 15/05/2012 second script for Centos 5.8
# - separate script for Centos 5.8 
# v4: 23/05/2012 script for zabbix 2.0.0
# - same problems as above

5/15/2012

{new release} Zabbix auto install scripts

!!!NOTE: this scripts only for education/testing/investigation purposes, use on your own risk


I've prepared 2 auto Zabbix 2.0.0rc4 installation scripts, tested on Centos 5.8 and 6.2

https://www.dropbox.com/s/unzvemer4itptdt/zabbix2rc4_el5_install.sh
https://www.dropbox.com/s/88nudr29280xm61/zabbix2rc4_el6_install.sh

short desc
#!/bin/sh
#
# Centos 6.2 (5.8) zabbix 2rc4 install w/ psql9.1 jabber IPv6 support
#
# known problems:
# zabbix web config not fully configured during installation
# need manually to  setup $ZBX_SERVER  and $ZBX_SERVER_NAME parameters after installation finish
# after installation rpm prepared and it is in /root/rpmbuild/RPMS/
# do not know why but in this version zabbix won't work with DB user other than root had to create role for root
#
# reboot required after installation
#
#
# software distributed under the License is distributed on an "AS IS" BASIS,  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND
# (c) Michael Veselovski support@omgsw.com
# v1: initial release 4/10/2011
# v2: 24/12/2011 new release:
# - psql 9.1 support added
# - db user should be provided during installation
# - zabbix 1.9.8 support added
# v3.1: 15/05/2012 new release
# - script complete rewitten for Centos 6.2 suppport
# - script installing Zabbix 2.0.0rc4 /psql
# v3.2: 15/05/2012 second script for Centos 5.8
# - separate script for Centos 5.8

5/07/2012

How to upgrade Joomla from 1.5/1.6 to 2.5

BEFORE APPLYING ANY CHANGES YOU SHOULD CREATE A BACKUP

1) Go to http://domain/administrator => Extensions => Install/Uninstall => Upload Package File “com_jupgrade-2.5.1.zip” => Upload File & Install

2) Extensions => Plugin Manager => find “System - Mootools Upgrade” => Enabled “Yes”

3) create “jupgrade”subfolder in RootDirectory (/var/www/public_html/jupgrade), change owner to Apache user and change permissions to “777”

4) Download “http://joomlacode.org/gf/download/frsrelease/16804/73116/Joomla_2.5.3-Stable-Full_Package.zip” (download link: http://joomlacode.org/gf/project/joomla/frs/) to this directory (./jupgrade) and unpack

5) Go to http://domain/administrator => Components => Jupgrade => Parameters:
Distribution => Joomla 2.5
Skip checks => Yes
Skip Download => Yes
Skip Decompress => Yes
Enable migration debug => Yes
Enable Mootools version debug => Yes
DO NOT FORGET “Save” on the top and close this window.

6) Press “START UPGRADE”

7) After upgrade you should check all links. You may do that via “Xenu's Link Sleuth”.
This program works under Fedora, Red Hat, Ubuntu (use Wine) and Windows.
You may download it from “http://home.snafu.de/tilman/XENU.ZIP”, just unzip, install and start under Wine.
1) Go to “File => Check URL”
2) Enter “http://domain/jupgrade/”, NOT http://domain/jupgrade, DO NOT FORGET the last “/”.
(More about this program: http://home.snafu.de/tilman/xenulink.html)

8) If all looks fine - create another subfolder “my_old_joomla” in RootDirectory and move all content FROM RootDirectory to this subdirectory (from /var/www/public_html/ to /var/www/public_html/my_old_joomla) except “jupgrade” and “my_old_joomla” folders.

9) As we can see the RootDirectory is contained only two folders “jupgrade” and “my_old_joomla” you should move all content from /var/www/public_html/jupgrade to /var/www/public_html/

10) That’s all.


(c)  Yan Ternovsky

5/05/2012

Changing tables engine from MyISAM to InnoDB

1. Edit /etc/my.cnf , make sure that:
  
#skip-innodb - commented out
innodb_file_per_table = ON

2. install Percona toolkit

Visit http://www.percona.com/software/percona-toolkit/ to download the latest release of Percona Toolkit. Or, get the latest release from the command line:
 
wget percona.com/get/percona-toolkit.tar.gz

wget percona.com/get/percona-toolkit.rpm

wget percona.com/get/percona-toolkit.deb

You can also get individual tools from the latest release:
 
wget percona.com/get/TOOL 
 
Replace TOOL with the name of any tool.

3. using pt-find convert tables from MyISAM to  InnoDB

pt-find db-name --engine MyISAM --exec "ALTER TABLE %D.%N ENGINE=INNODB" --print

[how to]Windows slow download speed

in case if Windows servers show poor download performance in clouds based on Onapp software its necessary to do the following

Networking: Xen network adapter->Xen network device drivers-> Properties
Configure:  -> Properties->Advanced

In advanced properties should be set:
CheckSumOffload-> Disabled
LargeSendOffload->Disabled

and as usual reboot VPS

1/20/2012

mdadm

1. start raid

mdadm --assemble --scan

2. start raid in case if you do not have /etc/mdadm.conf (should have raid UUID)

mdadm /dev/md0 --assemble -u e6d85d3d:d20ddcfc:c7cxxxxx:6a0xxxx

3. generate /etc/mdadm.conf

 mdadm --detail --scan >> /etc/mdadm.conf

1/10/2012

[mdadm] 2 how-tos

1. how to cancel sync:

in order to cancel raid sync its necessary to left only one drive as active (we are talking about raid1):

 mdadm --fail /dev/md2 /dev/sda3
and  we will receive something like that (in my case it was md2 and /dev/sda3):

 mdadm --detail /dev/md2
/dev/md2:
        Version : 0.90
  Creation Time : Fri Feb  4 21:22:50 2011
     Raid Level : raid1
     Array Size : 1462766336 (1395.00 GiB 1497.87 GB)
  Used Dev Size : 1462766336 (1395.00 GiB 1497.87 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Tue Jan 10 18:37:27 2012
          State : clean, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0

           UUID : 71b91f85:bdd01b3f:776c2c25:004bd7b2
         Events : 0.28394

    Number   Major   Minor   RaidDevice State
       0       0        0        0      removed
       1       8       19        1      active sync   /dev/sdb3

       2       8        3        -      faulty spare   /dev/sda3
 /dev/sda3 was set as failed.

2. how to re-add failed disk into existing array and restart scan :)

  • set disk as failed (we already did that in 1st how-to )
  • remove device from array
  • mdadm --remove /dev/md2 /dev/sda3 
  • add device one more time
  • mdadm --add /dev/md2/ /dev/sda3

We can check the status of the arrays on the system with:
watch -n .1 cat /proc/mdstat
 or
mdadm --detail /dev/md0