<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-8543517995066619584</atom:id><lastBuildDate>Fri, 08 Jan 2010 02:46:01 +0000</lastBuildDate><title>Open Source Solutions.....</title><description>Do contact on nilesh_patil82@yahoo.com</description><link>http://bigunix.blogspot.com/</link><managingEditor>noreply@blogger.com (ynilesh)</managingEditor><generator>Blogger</generator><openSearch:totalResults>45</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-2351726162392397145</guid><pubDate>Mon, 26 Oct 2009 12:58:00 +0000</pubDate><atom:updated>2009-10-26T22:38:13.099-07:00</atom:updated><title>Invalid command 'php_flag', perhaps misspelled or defined by a module not included in the server configuration</title><description>Install php package and it will resolve the issue.&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;yum install php&lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-2351726162392397145?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/10/invalid-command-phpflag-perhaps.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-3555625489229385024</guid><pubDate>Wed, 16 Sep 2009 12:30:00 +0000</pubDate><atom:updated>2009-09-16T05:48:36.069-07:00</atom:updated><title>how to configure APC pdu using minicom.</title><description>&lt;span style="font-weight:bold;"&gt;Prerequisite:&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;    PDU installation with proper network and console connection.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Configuration:&lt;br /&gt;  1. Run minicom -s -c on&lt;br /&gt;    -s - Setup. It has different option to setup your console. It edits /etc/minirc.dfl which is default to store configuration.&lt;br /&gt;    -c It usage color's on console.&lt;br /&gt;&lt;br /&gt;    Note: you can even run only "minicom -s"&lt;br /&gt;&lt;br /&gt;    Your screen should be like this,&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;            ┌─────[configuration]───-──┐&lt;br /&gt;            │ Filenames and paths               │&lt;br /&gt;            │ File transfer protocols             │&lt;br /&gt;            │ Serial port setup                     │&lt;br /&gt;            │ Modem and dialing                 │&lt;br /&gt;            │ Screen and keyboard              │&lt;br /&gt;            │ Save setup as dfl                    │&lt;br /&gt;            │ Save setup as..                      │&lt;br /&gt;            │ Exit                                        │&lt;br /&gt;            │ Exit from Minicom                   │&lt;br /&gt;            └──────────────────-─┘&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;  2. Select serial port setup option to select connect to correct serial device. I have terminated serial console cable from PDU to my Linux box so my device was /dev/ttyS0&lt;br /&gt;&lt;br /&gt; It may differ depend on OS.&lt;br /&gt;&lt;br /&gt; &lt;blockquote&gt;   ┌────────────────────────────────────┐&lt;br /&gt;    │ A -    Serial Device      : /dev/ttyS0                                 │&lt;br /&gt;    │ B - Lockfile Location     : /var/lock                                    │&lt;br /&gt;    │ C -   Callin Program      :                                                  │&lt;br /&gt;    │ D -  Callout Program      :                                                │&lt;br /&gt;    │ E -    Bps/Par/Bits       : 9600 8N1                                   │&lt;br /&gt;    │ F - Hardware Flow Control : No                                     │&lt;br /&gt;    │ G - Software Flow Control : No                                      │&lt;br /&gt;    │                                                                                        │&lt;br /&gt;    │    Change which setting?                                               │&lt;br /&gt;    └────────────────────────────────────┘&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt; 3. I had to set Hardware Flow Control to No as it was Yes by default.&lt;br /&gt;&lt;br /&gt; 4. Choose Save setup as dfl to save the configuration. By default it save configuration in /etc/minirc.dfl. Here is my minirc.dfl.&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;    # Machine-generated file - use "minicom -s" to change parameters.&lt;br /&gt;     pr port             /dev/ttyS0&lt;br /&gt;     pu baudrate         9600&lt;br /&gt;     pu bits             8&lt;br /&gt;     pu parity           N&lt;br /&gt;     pu stopbits         1&lt;br /&gt;     pu rtscts           No&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt; 5. Once you save and exit from the setup. It intitialize the serial console and gives you access to PDU. The next screen would be something like this,&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;Welcome to minicom 2.1&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n&lt;br /&gt;Compiled on Jul 26 2006, 06:38:09.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Press CTRL-A Z for help on special keys&lt;br /&gt;                                                                                                                                                          &lt;br /&gt;User Name : apc                                                                           &lt;br /&gt;Password  : ***&lt;br /&gt;&lt;br /&gt;&lt;/blockquote&gt; &lt;br /&gt;&lt;br /&gt; 6. Default username and password for apc PDU's are apc/apc.&lt;br /&gt; &lt;br /&gt;&lt;blockquote&gt;American Power Conversion               Network Management Card AOS      v3.7.0&lt;br /&gt;(c) Copyright 2008 All Rights Reserved  Rack PDU APP                     v3.7.0&lt;br /&gt;----------------------------------------------------------------------------------------------------------&lt;br /&gt;Name      : Engineering Rack PDU                      Date : 29.03.2000&lt;br /&gt;Contact   : Nilesh Patil                              Time : 19:23:22&lt;br /&gt;Location  : Server Room 1                             User : Administrator&lt;br /&gt;Up Time   : 0 Days 5 Hours 0 Minutes                  Stat : P+ N+ A+&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Switched Rack PDU: Communication Established&lt;br /&gt;&lt;br /&gt;------- Control Console -------------------------------------------------------&lt;br /&gt;&lt;br /&gt;     1- Device Manager&lt;br /&gt;     2- Network&lt;br /&gt;     3- System&lt;br /&gt;     4- Logout&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;     &lt;ESC&gt;- Main Menu, &lt;ENTER&gt;- Refresh, &lt;CTRL-L&gt;- Event Log&lt;br /&gt;&gt;&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt; 7. Select 2-Network option to configure network. You can define network settings like ip, netmask, gateway etc.&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;     ------- Network ---------------------------------------------------------------&lt;br /&gt;&lt;br /&gt;     1- TCP/IP&lt;br /&gt;     2- DNS&lt;br /&gt;     3- Ping Utility&lt;br /&gt;     4- FTP Server&lt;br /&gt;     5- Telnet/SSH&lt;br /&gt;     6- Web/SSL/TLS&lt;br /&gt;     7- Email&lt;br /&gt;     8- SNMP&lt;br /&gt;     9- Syslog&lt;br /&gt;    10- ISX Protocol&lt;br /&gt;&lt;br /&gt;     &lt;ESC&gt;- Back, &lt;ENTER&gt;- Refresh, &lt;CTRL-L&gt;- Event Log&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt; 8. Likewise you can configure your PDU as per your need.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-3555625489229385024?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/09/how-to-configure-apc-pdu-using-minicom.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-193527909762984089</guid><pubDate>Wed, 26 Aug 2009 11:21:00 +0000</pubDate><atom:updated>2009-08-26T04:30:19.861-07:00</atom:updated><title>How to setup rsync</title><description>If you want to run rsync as a daemon make sure following thing.&lt;br /&gt; - rsync is not hashed in &lt;span style="font-style:italic;"&gt;/etc/services&lt;/span&gt;&lt;br /&gt;&lt;br /&gt; - I have created following script to start rsync daemon which uses &lt;span style="font-style:italic;"&gt;/etc/rsyncd.conf&lt;/span&gt; file&lt;br /&gt;&lt;br /&gt;  ######### Creating start/stop script ..... &lt;span style="font-style:italic;"&gt;/etc/init.d/rc.d/rsyncd&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt; #!/bin/sh&lt;br /&gt; # Rsyncd This shell script takes care of starting and stopping the rsync daemon&lt;br /&gt; # description: Rsync is an awesome replication tool.&lt;br /&gt;&lt;br /&gt; # Source function library.&lt;br /&gt; . /etc/rc.d/init.d/functions&lt;br /&gt; &lt;br /&gt; [ -f /usr/bin/rsync ] || exit 0&lt;br /&gt; &lt;br /&gt; case "$1" in&lt;br /&gt; start)&lt;br /&gt; action "Starting rsyncd: " /usr/bin/rsync --daemon&lt;br /&gt; ;;&lt;br /&gt; stop)&lt;br /&gt; action "Stopping rsyncd: " killall rsync&lt;br /&gt; ;;&lt;br /&gt; *)&lt;br /&gt; echo "Usage: rsyncd {start|stop}"&lt;br /&gt; exit 1&lt;br /&gt; esac&lt;br /&gt; exit 0&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;########## &lt;br /&gt;&lt;br /&gt;######### Create /etc/rsyncd.conf file&lt;br /&gt;&lt;br /&gt; &lt;span style="font-style:italic;"&gt;### Rsync Configurations ###&lt;br /&gt; uid = nobody&lt;br /&gt; gid = nobody&lt;br /&gt; use chroot = no&lt;br /&gt; max connections = 10&lt;br /&gt; syslog facility = local5&lt;br /&gt; pid file = /var/run/rsyncd.pid&lt;br /&gt; motd file = /etc/rsyncd.motd&lt;br /&gt; lock file = /var/run/rsync.lock&lt;br /&gt;  &lt;br /&gt; [daily_backup]&lt;br /&gt;         path = /backup/&lt;br /&gt;         auth users = backup&lt;br /&gt;         comment = Main backup directory.&lt;br /&gt; ####    secrets file = /etc/rsyncd.secrets&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;IMP NOTE: &lt;br /&gt; We should take care of trailing "/" while specifying the source directory for data copying. &lt;br /&gt; for example, &lt;br /&gt;  &lt;br /&gt; &lt;span style="font-style:italic;"&gt;rsync -avz -e ssh remoteuser@remotehost:/remoterdir/data/for/copy/   /local/data/dir&lt;/span&gt;&lt;br /&gt; &lt;br /&gt; Above example means that /local/data/dir must be available to to receive data from /remoterdir/data/for/copy/, otherwise rsync will simply download all the files into the path given as destination.&lt;br /&gt;&lt;br /&gt; &lt;span style="font-style:italic;"&gt;rsync -avz -e ssh remoteuser@remotehost:/remoterdir/data/for/copy   /local/data/dir&lt;/span&gt;&lt;br /&gt; in this case "copy" directory will be created first under /local/data/dir directory and data will be populated from remote host.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;I have created script to copy data remotely.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;#!/bin/bash&lt;br /&gt;# Script to copy data on remote machine.&lt;br /&gt;&lt;br /&gt;RSYNC=/usr/bin/rsync&lt;br /&gt;RSSH=/usr/bin/ssh&lt;br /&gt;RUSER=backup&lt;br /&gt;RHOST=backup.remote.host.com&lt;br /&gt;RDATABASE=/backup/Database&lt;br /&gt;RDIR=/backup/Directory/&lt;br /&gt;&lt;br /&gt;$RSYNC -avz -e $RSSH /backup/daily/ $RUSER@$RHOST:$RDATABASE/MySQL/&lt;br /&gt;$RSYNC -avz -e $RSHH /var/www/html/ $RUSER@$RHOST:$RDIR&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Please generate password less keys to copy data remotely without interruption. Use "ssh-keygen"&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-193527909762984089?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/08/how-to-setup-rsync.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-4656566264480373405</guid><pubDate>Mon, 24 Aug 2009 12:05:00 +0000</pubDate><atom:updated>2009-08-24T06:04:38.357-07:00</atom:updated><title>Postgresql backup and restore.</title><description>First method using pg_dump and second one is file system level backup.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Dump level Backup:&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;pg_dump dbname &gt; outfile&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Options available with pg_dump,&lt;br /&gt;-h &lt;span style="font-style:italic;"&gt;hostname&lt;/span&gt;. Default is &lt;span style="font-style:italic;"&gt;localhost&lt;/span&gt; or whatever is set in PGHOST variable.&lt;br /&gt;-p &lt;span style="font-style:italic;"&gt;which port&lt;/span&gt;. PGPORT env. &lt;br /&gt;-U username. default is logged in user name. PGUSER env.&lt;br /&gt;outfile - name of the target file&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Note:&lt;/span&gt; &lt;br /&gt;pg_dump does not block other operations on the database while it is working. (Exceptions are those operations that need to operate with an exclusive lock, such as VACUUM FULL.)&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Restore:&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;psql dbname &lt; infile&lt;/span&gt;&lt;br /&gt;infile - infile is what you used as outfile for the pg_dump command.&lt;br /&gt;&lt;br /&gt;It is suggested to run analyze on each db to obtain the useful statistics. Run,&lt;br /&gt;&lt;span style="font-style:italic;"&gt;vacuumdb -a -z to VACUUM ANALYZE all databases; &lt;/span&gt;&lt;br /&gt;&lt;br /&gt;pg_dump and psql can also use to dump a database directly from one server to another; &lt;br /&gt;for example:&lt;br /&gt;&lt;span style="font-style:italic;"&gt;pg_dump -h host1 dbname | psql -h host2 dbname&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;2. &lt;span style="font-weight:bold;"&gt;File system level backup&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;tar -cf backup.tar /usr/local/pgsql/data&lt;/span&gt;&lt;br /&gt;- Servers must be shutdown before taking backup.&lt;br /&gt;- To restore database, we have to restore full database, can not do partial restore of tables or etc.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-4656566264480373405?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/08/postgresql-backup-and-restore.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-9108741931262542947</guid><pubDate>Wed, 12 Aug 2009 08:05:00 +0000</pubDate><atom:updated>2009-08-12T01:18:03.026-07:00</atom:updated><title>Open GUI application via ssh</title><description>ssh -p 2222 -l nilesh -X -v {remote.host.ip.or.hostname}&lt;br /&gt;&lt;br /&gt;  -p 2222  In case your server runs a non-standard TCP port.  &lt;br /&gt;           (If yours runs on the default port (TCP port 22), there is no need to add this option.)&lt;br /&gt;&lt;br /&gt;  -l nilesh is only required if you do not have matching usernames on remote host.&lt;br /&gt;&lt;br /&gt;  -X allows X forwarding.  Use -x can be used to disable X11 forwarding&lt;br /&gt;&lt;br /&gt;  -v is verbose.  This lets you watch what is going on.&lt;br /&gt;&lt;br /&gt;Run your application once it is done. &lt;br /&gt;I was about to run virt-manager GUI application, which ran successfully :)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-9108741931262542947?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/08/open-gui-application-via-ssh.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-8862528475451281952</guid><pubDate>Wed, 12 Aug 2009 07:45:00 +0000</pubDate><atom:updated>2009-08-12T01:00:16.985-07:00</atom:updated><title>Virtualization: Xen Installation</title><description>&lt;span style="font-weight:bold;"&gt;How Xen works?&lt;/span&gt;&lt;br /&gt;   Xen hypervisor is run on top of the hardware which is the virtual machine monitor. Guest operating systems are run on top of this hypervisor, thus all guest operating systems are secondary to the hardware and contacts the hardware through the hypervisor. The first thing for grub would be to load the hypervisor. Look at the /boot/grub/grub.conf which loads the &lt;span style="font-weight:bold;"&gt;&lt;span style="font-weight:bold;"&gt;xen.gz-2.6.18-128.4.1.el5&lt;/span&gt;&lt;/span&gt; which is the hypervisor.&lt;br /&gt;&lt;br /&gt;    Hypervisor loads the &lt;span style="font-weight:bold;"&gt;Dom-0&lt;/span&gt; kernel and initrd image and starts the main system. Dom-0 itself is a guest operating system with additional privileges to manage other guest operating systems and is started with system start up. &lt;br /&gt;&lt;br /&gt;Following rpms should be installed for Xen virtualization,&lt;br /&gt; - kernel-xen ---&gt; Dom-0 and Dom-U kernels.&lt;br /&gt; - xen ----------&gt; Xen hypervisor and other management tools.&lt;br /&gt; - libvirt ------&gt; Libraries required to manage domains which is used as a backend for virtmanager. http://libvirt.org&lt;br /&gt; - virt-manager ----&gt; GUI interface to manage guests&lt;br /&gt;&lt;br /&gt;Once installation of above RPM's are done, System should be rebooted using the new XEN kernel.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-8862528475451281952?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/08/virtualization-xen-installation.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-4929760865627377246</guid><pubDate>Wed, 12 Aug 2009 05:09:00 +0000</pubDate><atom:updated>2009-08-11T22:10:43.036-07:00</atom:updated><title>Hidden ports on Linux.</title><description>A nice blog post about the hidden ports on linux. &lt;br /&gt;http://www.ossec.net/dcid/?p=87&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-4929760865627377246?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/08/hidden-ports-on-linux.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-3129945104512460868</guid><pubDate>Fri, 31 Jul 2009 06:52:00 +0000</pubDate><atom:updated>2009-07-30T23:58:55.163-07:00</atom:updated><title>**FATAL_ERROR** No password for admin user - please re-run ntop in non-daemon mode fir st</title><description>When you install ntop, daemon does not start automatically. It returns above error when you try to start it. &lt;br /&gt;&lt;br /&gt;You need to set password to start ntop in daemon mode. &lt;br /&gt;&lt;span style="font-style:italic;"&gt;"ntop -A"&lt;/span&gt; or &lt;span style="font-style:italic;"&gt;ntop --set-passwd&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;It asks for password, set it. &lt;br /&gt;Then start the service. &lt;br /&gt;&lt;span style="font-style:italic;"&gt;/etc/init.d/ntop start&lt;/span&gt; &lt;br /&gt;&lt;br /&gt;You are now ready to view your network statitics :).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-3129945104512460868?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/fatalerror-no-password-for-admin-user.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-6900311211712209509</guid><pubDate>Thu, 30 Jul 2009 11:22:00 +0000</pubDate><atom:updated>2009-07-30T04:28:09.030-07:00</atom:updated><title>checking for intltool &gt;= 0.35.0... ./configure: line 16914: intltool-update: command not found</title><description>Error:&lt;br /&gt;checking for intltool &gt;= 0.35.0... ./configure: line 16914: intltool-update: command not found&lt;br /&gt;configure: error: Your intltool is too old.  You need intltool 0.35.0 or later.&lt;br /&gt;&lt;br /&gt;Solution: &lt;br /&gt;1. Install package, intltool-0.35.0-2.i386&lt;br /&gt;2. It will fail for following dependency if XML Parser not installed. &lt;br /&gt;error: Failed dependencies:&lt;br /&gt;        perl-XML-Parser is needed by intltool-0.35.0-2.i386&lt;br /&gt;3. Also Download and install perl-XML-Parser package&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-6900311211712209509?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/checking-for-intltool-0350-configure.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-7746534080312738490</guid><pubDate>Thu, 30 Jul 2009 10:52:00 +0000</pubDate><atom:updated>2009-07-30T03:59:51.957-07:00</atom:updated><title>Error! You need to have libevent 1.4.X or better.</title><description>You need to install libevent-devel package. Please find the respective package for your OS and install it. Also check whether you have already install libevent.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-7746534080312738490?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/error-you-need-to-have-libevent-14x-or.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-6762352309718726537</guid><pubDate>Wed, 29 Jul 2009 11:25:00 +0000</pubDate><atom:updated>2009-07-29T05:25:36.824-07:00</atom:updated><title>How to monitor bandwidht using MRTG and Nagios</title><description>Assuming that you have enough knowledge of Unix system and Nagios monitoring. If you dont know how to configure nagios please follow this &lt;a href="http://www.nagios.org/"&gt;link&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Prerequisite:&lt;/span&gt;&lt;br /&gt;- Make sure Nagios is running properly. Check &lt;span style="font-style:italic;"&gt;http://localhost/nagios&lt;/span&gt;&lt;br /&gt;- Also make sure that you have installed nagios_plugins.&lt;br /&gt;- Iptables and Selinux must be disabled. &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Install check_snmp plugin:&lt;/span&gt;&lt;br /&gt;- Make sure you have all following packages install for successful installation of snmp plugin.&lt;br /&gt;  net-snmp, net-snmp-devel, net-snmp-libs, net-snmp-utils, beecrypt-devel, &lt;br /&gt;  elfutils-devel, elfutils-devel-static, lm_sensors&lt;br /&gt; &lt;br /&gt;- To install check_snmp I download the plugin from this location. &lt;a href="http://www.monitoringexchange.org/cgi-bin/page.cgi?g=2021.html;d=1"&gt;check_snmp&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;1. Unzip the downloaded file &lt;br /&gt;   bunzip check_snmp-1.1.tar.bz2&lt;br /&gt;&lt;br /&gt;2. Untar it.&lt;br /&gt;   tar xvf check_snmp-1.1.tar&lt;br /&gt;&lt;br /&gt;3. Configure and install it. &lt;br /&gt;   ./configure &lt;br /&gt;   make&lt;br /&gt;   make install&lt;br /&gt;&lt;br /&gt;4. Once it is install successfully you can find check_snmp at /usr/local/bin location. &lt;br /&gt;&lt;br /&gt;5. Create a soft link for check_snmp. &lt;br /&gt;   ln -s /usr/local/bin/check_snmp  /usr/local/nagios/libexec/check_snmp&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt; Install MRTG: &lt;/span&gt;&lt;br /&gt;To monitor bandwidth usages of router/switch you must have mrtg installed on system. Before installation please make sure you have install gd, libpng, zlib packages.  &lt;br /&gt;&lt;br /&gt;1. Download &lt;a href="http://oss.oetiker.ch/mrtg/doc/mrtg.en.html"&gt;MRTG&lt;/a&gt;. &lt;br /&gt;&lt;br /&gt;2. Once all libraries installed required for MRTG you are all set to compile and configure MRTG. &lt;br /&gt;    gunzip -c mrtg-2.16.2.tar.gz | tar xvf -&lt;br /&gt;    cd mrtg-2.16.2&lt;br /&gt;&lt;br /&gt;3. ./configure --prefix=/usr/local/mrtg-2&lt;br /&gt;   make &lt;br /&gt;   make install&lt;br /&gt;&lt;br /&gt;4. Create /var/www/html/mrtg file to store mrtg html files. &lt;br /&gt;   mkdir /var/www/html/mrtg&lt;br /&gt;&lt;br /&gt;5. Now you need not to create mrtg configuration file. Use cfgmaker.&lt;br /&gt;    cfgmaker --global 'WorkDir: /var/www/html/mrtg' --global 'Options[_]: bits,growright' --output /etc/httpd/conf/mrtg.cfg  public@172.17.42.22&lt;br /&gt;   ( I choose default apache web location for installation of mrtg html files and apache conf directory to store mrtg.cfg.)&lt;br /&gt;   &lt;br /&gt;6. Go to respective location and make sure that above command has created respective files.&lt;br /&gt;   cd /var/www/html/mrtg; &lt;br /&gt;   ls -al /etc/httpd/conf/mrtg.cfg&lt;br /&gt;&lt;br /&gt;7. Run this command to update mrtg log file.&lt;br /&gt;   env LANG=C /usr/local/mrtg-2/bin/mrtg /home/mrtg/cfg/mrtg.cfg&lt;br /&gt;&lt;br /&gt;8. create a script to update the mrtg log file which will fetch data regularly and display in graph as well as on nagios. &lt;br /&gt;   vi /usr/local/mrtg-2/bin/monitor_mrtg.sh&lt;br /&gt;   &lt;br /&gt;9. Put following lines in it and save.&lt;br /&gt;   #!/bin/sh&lt;br /&gt;   env LANG=C /usr/local/mrtg-2/bin/mrtg /home/mrtg/cfg/mrtg.cfg&lt;br /&gt;   (When you run it first time it returns you few errors/warnings. Ignore it.)   &lt;br /&gt;   &lt;br /&gt;   chmod 755 mrtgbw.sh             ; Make script executable.&lt;br /&gt;&lt;br /&gt;10. Set cron to run above script every 5 minute. &lt;br /&gt;    crontab -e &lt;br /&gt;   &lt;br /&gt;11. Modify and save,&lt;br /&gt;    */5  *  *  *  *  /usr/local/mrtg-2/bin/monitor_mrtg.sh&lt;br /&gt;&lt;br /&gt;12. Restart cron service.&lt;br /&gt;    /etc/init.d/crond restart&lt;br /&gt;&lt;br /&gt;13. Confirm that it is been configured. &lt;br /&gt;    &lt;span style="font-style:italic;"&gt;http://localhost/mrtg/{name of html file}&lt;/span&gt;&lt;br /&gt;   &lt;br /&gt;    Actually when you run mrtg command it searches for respective router community collects all data from router. Accordingly it creates log file. Like in my case it has found port 2 running on router and hence created file 172.17.42.22_2.log, 172.17.42.22_2.html. So I can access my graph through this link,&lt;br /&gt;     &lt;span style="font-style:italic;"&gt;http://localhost/mrtg/172.17.42.22_2.html&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Procedure to monitor Bandwidth Usages in Nagios: &lt;/span&gt;&lt;br /&gt;1. Default installation directory of nagios is /usr/local/nagios/. &lt;br /&gt;&lt;br /&gt;2. Open switch.cfg file &lt;br /&gt;   vi /usr/local/nagios/etc/objects/switch.cfg&lt;br /&gt;&lt;br /&gt;3. Make changes according to your router specifications. Like,&lt;br /&gt;   define host{&lt;br /&gt;        use             generic-switch   &lt;br /&gt;        host_name       Router_1         &lt;br /&gt;        alias           Router 1 &lt;br /&gt;        address         172.17.42.22     &lt;br /&gt;        hostgroups      switches&lt;br /&gt;        }&lt;br /&gt;4. You can also set PING, Uptime, Ports Link Status etc.&lt;br /&gt;   define service{&lt;br /&gt;        use                     generic-service ; Inherit values from a template&lt;br /&gt;        host_name               Router_1        ; The name of the host the service is associated with&lt;br /&gt;        service_description     PING            ; The service description&lt;br /&gt;        check_command           check_ping!200.0,20%!600.0,60%  ; The command used to monitor the service&lt;br /&gt;        normal_check_interval   5               ; Check the service every 5 minutes under normal conditions&lt;br /&gt;        retry_check_interval    1               ; Re-check the service every minute until its final/hard state is determined&lt;br /&gt;        }&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;        use                     generic-service ; Inherit values from a template&lt;br /&gt;        host_name               Router_1&lt;br /&gt;        service_description     Uptime&lt;br /&gt;        check_command           check_snmp!-C public -o sysUpTime.0 -H 172.17.42.22&lt;br /&gt;        }&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;        use                     generic-service ; Inherit values from a template&lt;br /&gt;        host_name               Router_1&lt;br /&gt;        service_description     Port 2 Link Status&lt;br /&gt;        check_command           check_snmp!-C public -o ifOperStatus.2 -r 1 -H 172.17.42.22&lt;br /&gt;        }&lt;br /&gt;&lt;br /&gt;define service{&lt;br /&gt;        use                     generic-service ; Inherit values from a template&lt;br /&gt;        host_name               Router_1&lt;br /&gt;        service_description     Port 2 Bandwidth Usage&lt;br /&gt;        check_command           check_local_mrtgtraf!/var/www/html/mrtg/172.17.42.22_2.log!AVG!1000000,1000000!5000000,5000000&lt;br /&gt;!10&lt;br /&gt;        }&lt;br /&gt;  &lt;br /&gt;5. Verify the configuration of nagios &lt;br /&gt;   /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg&lt;br /&gt;&lt;br /&gt;6. Restart nagios service.&lt;br /&gt;   /etc/init.d/nagios restart&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-6762352309718726537?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/how-to-monitor-bandwidht-using-mrtg-and.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-4932423566082840171</guid><pubDate>Tue, 21 Jul 2009 12:15:00 +0000</pubDate><atom:updated>2009-07-22T02:02:18.030-07:00</atom:updated><title>Solaris: Disk Management</title><description>- A disk under the Solaris OE can be divided into eight slices that are labeled Slice 0 through Slice 7.&lt;br /&gt; - In reality Slice 2 represents the entire disk because "/" is the first(0) slice and swap is second(1).&lt;br /&gt;&lt;br /&gt;Dist Slice Naming Convention, Controller number, Target number, Disk number, Slice number. &lt;br /&gt; - Controller number, which control communications between system and disk unit. &lt;br /&gt; - Target number is a unique hardware address of disk, tape, CDROM etc.&lt;br /&gt; - Disk number is a logical unit number.&lt;br /&gt; - Slice number is partition number on disk.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-4932423566082840171?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/solaris-disk-management.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-3318763202090347054</guid><pubDate>Tue, 21 Jul 2009 11:30:00 +0000</pubDate><atom:updated>2009-07-21T05:15:37.662-07:00</atom:updated><title>Solaris: Key points in File System</title><description>&lt;span style="font-weight:bold;"&gt;Inode&lt;/span&gt;&lt;br /&gt; In general inode contains two parts. First, inodes contains information about file, including owners, permissions, size etc. Second inode contains pointers to data blocks associated with files.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Different file types&lt;/span&gt; &lt;br /&gt; Regular files    &lt;br /&gt; Directories&lt;br /&gt; Device files contains block device and character device.&lt;br /&gt; Symbolic links&lt;br /&gt; Socket files&lt;br /&gt;&lt;br /&gt; - Data block associated with directory contains lists of all files and associated inodes.&lt;br /&gt; - Symbolic links can point to regular files, directories, other symbolic links and device files. &lt;br /&gt; - A data block of symbolic link contains the path of original file. &lt;br /&gt; - A long listing of a device file shows two numbers, separated by a comma where major number denotes specific device driver required to access the device and minor device denotes the specific unit of the device driver control.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-3318763202090347054?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/solaris-key-points-in-file-system.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-2411670647707293731</guid><pubDate>Thu, 16 Jul 2009 05:01:00 +0000</pubDate><atom:updated>2009-07-16T01:38:28.216-07:00</atom:updated><title>Red Hat : Global File System</title><description>- native file system.&lt;br /&gt;- Interfaces directly with Linux kernel file system interface (VFS Player).&lt;br /&gt;- Can be implemented on Standalone System.&lt;br /&gt;- Can be a part of cluster configuration.&lt;br /&gt;- GFS can be created on LVM logical volume.&lt;br /&gt;- GFS is based on 64 bit architecture, can accommodate 8 EB file system.&lt;br /&gt;- Red Hat GFS nodes can be configured and managed with Red Hat Cluster Suite configuration and management tools.&lt;br /&gt;- LVM logical volumes in a Red Hat Cluster Suite are managed by CLVM, which is cluster wide implementation of LVM (&lt;span style="font-weight:bold;"&gt;clvmd&lt;/span&gt; daemon).&lt;br /&gt;- daemon allow all nodes in cluster to share the volume.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-2411670647707293731?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/redhat-global-file-system.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-57390670910369660</guid><pubDate>Tue, 07 Jul 2009 10:21:00 +0000</pubDate><atom:updated>2009-07-08T21:07:48.531-07:00</atom:updated><title>OTRS: How to set the Generic Agent?</title><description>Taken from, lists.otrs.org.&lt;br /&gt;&lt;br /&gt;So you need to create as many jobs as you have agents.&lt;br /&gt;The idea behind GenericAgent is very simple: search for tickets using the&lt;br /&gt;values in sections shaded grey and set new values in tickets in sections&lt;br /&gt;shaded black. You should have all your ticket types, queues, agents,&lt;br /&gt;customers defined before you start making a GenericAgent job.&lt;br /&gt;&lt;br /&gt;For example, we are building a job to assign Hardware problems to Mark&lt;br /&gt;Twain.&lt;br /&gt;&lt;br /&gt;In Admin, go to Generic Agent. Type in the job name Hardware_to_Twain and&lt;br /&gt;click Add. A new job form appears. Study it a little. There are sections&lt;br /&gt;with title shaded gray. The values you put into these sections' fields are&lt;br /&gt;used to select the tickets for processing by the job. You select Agent/Owner&lt;br /&gt;= root at localhost. You select ticket state = new. You select Ticket lock =&lt;br /&gt;unlock, you select ticket type = Hardware problem. How do you plan to deal&lt;br /&gt;with email tickets btw? They will not get tycket type set correctly.&lt;br /&gt;&lt;br /&gt;Now we move to sections with titles shaded black. That's where we program&lt;br /&gt;new values for ticket fields:&lt;br /&gt;You select new Agent = Mark Twain. You select the new Queue = Hardware, New&lt;br /&gt;ticket lock = lock.&lt;br /&gt;You may add a note to leave trace of what has been done for your customer.&lt;br /&gt;(It's reflected in the history for the agents anyway).&lt;br /&gt;Check Send no notifications flag .&lt;br /&gt;&lt;br /&gt;Go back to the beginning and think of the schedule for the job. How often it&lt;br /&gt;should run?&lt;br /&gt;&lt;br /&gt;AS soon as you save the job - you're done. If there are problems with the&lt;br /&gt;job - look in the System Log.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-57390670910369660?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/otrs-how-to-set-generic-agent.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-2244077208089063445</guid><pubDate>Tue, 07 Jul 2009 08:35:00 +0000</pubDate><atom:updated>2009-07-07T01:44:39.801-07:00</atom:updated><title>OTRS: How survey module works?</title><description>There are no steps given anywhere about how survey module works. &lt;br /&gt;Here are the steps given,&lt;br /&gt;1. Download and install Survey module &lt;br /&gt;2. Login as OTRS Admin i.e. root@localhost by default. &lt;br /&gt;3. Navigate to SysConfig setting under "Misc" section.&lt;br /&gt;4. Search for Survey, then go to Core -&gt; Survey::SendPeriod. &lt;br /&gt;5. Change this value to 0, to send mail always whenever agent close the ticket. &lt;br /&gt;6. Also created survey should have status as "Master". This is the setting when you create the survey.&lt;br /&gt;&lt;br /&gt;This is where you can find more details, this post is translation from German.&lt;br /&gt;http://translate.google.com/translate?hl=en&amp;sl=de&amp;u=http://wiki.otrs-forum.de/index.php%3Ftitle%3DSurvey&amp;ei=3VWxSdOZCozMmQeRxJjfBQ&amp;sa=X&amp;oi=translate&amp;resnum=8&amp;ct=result&amp;prev=/search%3Fq%3DSurvey::SendPeriod%26hl%3Den%26client%3Dsafari%26rls%3Den-us%26sa%3DG&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-2244077208089063445?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/otrs-how-survey-module-works.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-8778198683891593717</guid><pubDate>Mon, 06 Jul 2009 06:45:00 +0000</pubDate><atom:updated>2009-07-07T00:28:32.834-07:00</atom:updated><title>Ganglia Installation errors and solutions.</title><description>&lt;span style="font-weight:bold;"&gt;Error:&lt;/span&gt;&lt;br /&gt;Checking for apr&lt;br /&gt;checking for apr-1-config... no&lt;br /&gt;configure: error: apr-1-config binary not found in path&lt;br /&gt;make: *** No targets specified and no makefile found.  Stop.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Resolution:&lt;/span&gt;&lt;br /&gt;Install respective version of apr-devel. for me it was apr-devel-1.2.7-11.i386.rpm&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Error:&lt;/span&gt;&lt;br /&gt;Checking for confuse&lt;br /&gt;checking for cfg_parse in -lconfuse... no&lt;br /&gt;Trying harder including gettext&lt;br /&gt;checking for cfg_parse in -lconfuse... no&lt;br /&gt;Trying harder including iconv&lt;br /&gt;checking for cfg_parse in -lconfuse... no&lt;br /&gt;libconfuse not found&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Resolution:&lt;/span&gt;&lt;br /&gt;Install &lt;span style="font-style:italic;"&gt;"libconfuse"&lt;/span&gt; and &lt;span style="font-style:italic;"&gt;"libconfuse-devel"&lt;/span&gt; packages. &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Error:&lt;/span&gt;&lt;br /&gt;mod_python.c error: Python.h: No such file or directory&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Resolution:&lt;/span&gt;&lt;br /&gt;Install &lt;span style="font-style:italic;"&gt;"python-devel"&lt;/span&gt; package if not installed.&lt;br /&gt;&lt;br /&gt;- nilesh&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-8778198683891593717?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/checking-for-apr-checking-for-apr-1.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-5052819578959080966</guid><pubDate>Wed, 01 Jul 2009 07:26:00 +0000</pubDate><atom:updated>2009-07-01T00:34:49.274-07:00</atom:updated><title>Nagios: How to suppress notifications when host goes down.</title><description>There are two ways to avoid extra notifications of services when host goes down.&lt;br /&gt;&lt;br /&gt;1. Configure ping (use &lt;span style="font-style:italic;"&gt;check-host-alive&lt;/span&gt;) as the host check, when the host is unreachable, the notifications for the services will not be sent. &lt;br /&gt;&lt;br /&gt;2. Can have service dependency configuration file like this,&lt;br /&gt;   define servicedependency {&lt;br /&gt;     hostgroup_name                  all_servers&lt;br /&gt;     service_description             ping check&lt;br /&gt;     dependent_hostgroup_name        all_servers&lt;br /&gt;     dependent_service_description   *&lt;br /&gt;     execution_failure_criteria      w,c&lt;br /&gt;     notification_failure_criteria   w,u,c&lt;br /&gt;   }&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-5052819578959080966?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/07/nagios-how-to-suppress-notifications.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-5630991938413351721</guid><pubDate>Wed, 01 Jul 2009 05:58:00 +0000</pubDate><atom:updated>2009-06-30T23:13:49.051-07:00</atom:updated><title>Nagios: How to monitor a website</title><description>check_http supports arguments like hostname, hostaddress, URI etc. &lt;br /&gt;you can have,&lt;br /&gt;   check_http -H $ARG1 -I $ARG2 -u $ARG3&lt;br /&gt;where,&lt;br /&gt;$ARG1 - hostname&lt;br /&gt;$ARG2 - hostaddress&lt;br /&gt;$ARG3 - URI - www.yourwebsite.com&lt;br /&gt;&lt;br /&gt;Also check &lt;span style="font-style:italic;"&gt;"check_http --help"&lt;/span&gt; for more details.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-5630991938413351721?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/06/nagios-how-to-monitor-website.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-8006364402457991376</guid><pubDate>Wed, 01 Jul 2009 05:58:00 +0000</pubDate><atom:updated>2009-06-30T22:58:48.153-07:00</atom:updated><title>Nagios: Adding Cisco enterprise MIBs</title><description>(Taken from nagios user list)&lt;br /&gt;&lt;br /&gt;- Default directory for snmp mibs are /usr/share/snmp/mibs/ if you have libsnmp-base package installed.&lt;br /&gt;&lt;br /&gt;- to verify that the mibs are working, you can use a mib browser such as mbrowse (apt-get install mbrowse).&lt;br /&gt;&lt;br /&gt;- not all OIDs in a MIB are supported for all IOS versions.  Cisco usually has a link for each IOS version and what MIBs are supported.&lt;br /&gt;&lt;br /&gt;- once the mib is verified and working, use the check_snmp check_command&lt;br /&gt;in your .cfg files of the routers and switches you want to monitor.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-8006364402457991376?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/06/nagios-adding-cisco-enterprise-mibs.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-4146076913086297820</guid><pubDate>Wed, 01 Jul 2009 05:57:00 +0000</pubDate><atom:updated>2009-06-30T22:58:02.143-07:00</atom:updated><title>Nagios: Default parameter with check_total_procs</title><description>We define service like this,&lt;br /&gt;&lt;span style="font-style:italic;"&gt;&lt;br /&gt;define service{&lt;br /&gt;service_description   Total_Processes&lt;br /&gt;check_command         check_nrpe!check_total_procs&lt;br /&gt;…&lt;br /&gt;}&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;By default this check is an execution of check_procs with only the warning and critical thresholds, so it counts all processes running on your machine.&lt;br /&gt;&lt;br /&gt;The thresholds are configured in the nrpe.cfg on the remote machine.&lt;br /&gt;&lt;br /&gt;- Nilesh&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-4146076913086297820?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/06/nagios-default-parameter-with.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-6116603655081298608</guid><pubDate>Wed, 01 Jul 2009 05:52:00 +0000</pubDate><atom:updated>2009-06-30T22:57:11.371-07:00</atom:updated><title>Install and Configure Nagios Plugins &amp; NRPE on Solaris 10</title><description>I came across lots of issues to do this installation so here is a step by step installation of Nagios Plugins and NRPE on Solaris 10.&lt;br /&gt;&lt;br /&gt;Add “nagios” user as &lt;span style="font-style:italic;"&gt;“/usr/local/nagios”&lt;/span&gt; as home directory.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# useradd -c “Nagios User” -d /usr/local/nagios -m nagios&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Change ownership of directory to nagios&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# chown nagios:nagios /usr/local/nagios/&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;download nagios-plugins and nrpe from net. I have download them from sourceforge.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# mkdir /nagios; cd /nagios&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;wget http://sourceforge.net/project/downloading.php?group_id=29880&amp;filename=nagios-plugins-1.4.13.tar.gz&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;wget http://sourceforge.net/project/downloading.php?group_id=26589&amp;filename=nrpe-2.12.tar.gz&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;Now extract them&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# gunzip nagios-plugins-1.4.13.tar.gz; gunzip nrpe-2.12.tar.gz&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# tar xvf nagios-plugins-1.4.13.tar.gz; tar xvf nrpe-2.12.tar.gz&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Before compiling I had to set PATH to find gcc binary,&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# export PATH=$PATH:/usr/sfw/sbin:/usr/sfw/bin:/usr/ccs/bin&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# cd nagios-plugins-1.4.13;&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# ./configure –without-mysql (I did want to install with mysql support)&lt;br /&gt;# make; make install&lt;br /&gt;# chown -R nagios:nagios /usr/local/nagios/libexec&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;Install NRPE with SSL library support otherwise you will get error while compilation like this,&lt;br /&gt;&lt;br /&gt;“checking for SSL headers… configure: error: Cannot find ssl headers”&lt;br /&gt;&lt;br /&gt;If you run &lt;span style="font-style:italic;"&gt;“dmesg” &lt;/span&gt;or if you check system messages you can see this error.&lt;br /&gt;&lt;br /&gt;May 28 19:08:26 solaris10.remotehost.com inetd[24233]: [ID 702911 daemon.error] Failed to set credentials for the inetd_start method of instance svc:/network/nrpe/tcp:default (chdir: No such file or directory)&lt;br /&gt;May 28 19:15:27 solaris10.remotehost.com inetd[24241]: [ID 702911 daemon.error] Failed to set credentials for the inetd_start method of instance svc:/network/nrpe/tcp:default (chdir: No such file or directory)&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# cd nrpe-2.12; ./configure –with-ssl=/usr/sfw/ –with-ssl-lib=/usr/sfw/lib/ –with-ssl-inc=/usr/sfw/include&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;Still if you compilation fails please apply these faqs/solutions given in nagios faqs.&lt;br /&gt;&lt;br /&gt;http://www.nagios.org/faqs/index.php?section_id=4&amp;expand=false&amp;showdesc=true&lt;br /&gt;&lt;br /&gt;In my case I had to make changes in src/nrpe.c for encryption. Do make all, make install to create respective binaries.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# make all; make install; make install-daemon-config;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Once that is done, modify nrpe.cfg with approprite settings. Add following line at the end of /etc/services&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;nrpe                    5666/tcp                         # NRPE&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Also add this line to /etc/inetd.conf and convert it into SMF and enable service with -e option. Also checkout whether it went online.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;nrpe stream tcp nowait nagios /usr/sfw/sbin/tcpd /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -i&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# inetconv;   inetconv -e&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# svcs | grep nrpe&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Check if 5666 port is open and in LISTEN mode.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# netstat -a | grep nrpe&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;Make sure that your /etc/hosts.allow and /etc/hosts.deny does not block your nagios server. Here are the entries&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;hosts.allow: nrpe: 127.0.0.1, 172.17.38.11&lt;br /&gt;&lt;br /&gt;hosts.deny: nrpe: ALL&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;Final command, make sure that nrpe returns correct output.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;# /usr/local/nagios/libexec/check_nrpe -H localhost&lt;br /&gt;NRPE v2.12&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-6116603655081298608?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/06/install-and-configure-nagios-plugins.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-8061338099479513422</guid><pubDate>Mon, 29 Jun 2009 13:30:00 +0000</pubDate><atom:updated>2009-06-30T22:46:46.327-07:00</atom:updated><title>Open Audit</title><description>There is no documentation available for this Open Source Tool. These all points written while going through open-audit documentation.&lt;br /&gt;&lt;br /&gt;What it Open Audit?&lt;br /&gt; - It audits hardware and software it discovers on the your computer.&lt;br /&gt; - Use's MySQL database to store all discovered data.&lt;br /&gt; - PHP used to display information stored in MySQL database.&lt;br /&gt; - Apache to make it available through web interface. &lt;br /&gt;&lt;br /&gt;What is audit.vbs?&lt;br /&gt; - audit.vbs reads data from Microsoft's Windows Management Interface (WMI) and posts its findings to the server.&lt;br /&gt; - OA collects the data using audit.vbs script and write directly to web server through POST method.&lt;br /&gt;&lt;br /&gt;Schedule an audit?&lt;br /&gt; - use "at" command to schedule an audit.&lt;br /&gt; - audit domain everyday at some specific time, (can also use windows schedule task)&lt;br /&gt;   &lt;span style="font-style:italic;"&gt;at 18:00 /interactive /every:M,T,W,Th,F,S,Su "C:\Program Files\xampp\htdocs\scripts\audit_mydomain.bat"&lt;/span&gt;&lt;br /&gt; - audit_mydomain.bat contains something like....&lt;br /&gt;   &lt;span style="font-style:italic;"&gt;@echo off&lt;br /&gt;   rem audit local domain pcs&lt;br /&gt;   cscript audit.vbs&lt;br /&gt;   cscript nmap.vbs&lt;br /&gt;  :end&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-8061338099479513422?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/06/open-audit.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-8060877287391939841</guid><pubDate>Fri, 26 Jun 2009 07:05:00 +0000</pubDate><atom:updated>2009-06-29T06:30:30.888-07:00</atom:updated><title>OTRS Issues - Phase I</title><description>Putting it from list.otrs.org for my own information. &lt;br /&gt;-----------------------------------------------------&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Problem: &lt;/span&gt;How to Clean up the database.?&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Solution&lt;/span&gt;&lt;br /&gt; - You can use the Generic Agent to remove all or some ticket based on criteria.&lt;br /&gt; - With a bulk change you could set all or some tickets to state 'removed' for instance, and than run GA on it.&lt;br /&gt; - Deleting customers/agents is harder, like for some other data types. You could do it in the database (phpmyadmin), or you can do like I do, recycle. Make them invalid, rename them to INVALID... en reuse (rename) when needed.&lt;br /&gt;--------------------------------------------------------------------------------------&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Problem :&lt;/span&gt; How to setup LDAP Authentication?&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Solution: &lt;/span&gt;&lt;br /&gt;  #Enable LDAP authentication for Customers / Users&lt;br /&gt;  $Self-&gt;{'Customer::AuthModule'} = 'Kernel::System::CustomerAuth::LDAP';&lt;br /&gt;  $Self-&gt;{'Customer::AuthModule::LDAP::Host'} = 'xx.xxx.xx.xx';&lt;br /&gt;  $Self-&gt;{'Customer::AuthModule::LDAP::BaseDN'} = &lt;br /&gt;'ou=user,ou=dublin,dc=int,dc=domain,dc=com';&lt;br /&gt;  $Self-&gt;{'Customer::AuthModule::LDAP::UID'} = 'sAMAccountName';&lt;br /&gt;&lt;br /&gt;#The following is valid but would only be necessary if the&lt;br /&gt;#anonymous user do NOT have permission to read from the LDAP tree&lt;br /&gt;# $Self-&gt;{'Customer::AuthModule::LDAP::SearchUserDN'} = 'otrsldap';&lt;br /&gt;# $Self-&gt;{'Customer::AuthModule::LDAP::SearchUserPw'} = 'password';&lt;br /&gt;  $Self-&gt;{'Customer::AuthModule::LDAP::SearchUserDN'} = 'MyDomain\otrsldap';&lt;br /&gt;  $Self-&gt;{'Customer::AuthModule::LDAP::SearchUserPw'} = 'password';&lt;br /&gt;&lt;br /&gt;#CustomerUser&lt;br /&gt;#(customer user database backend and settings)&lt;br /&gt;    $Self-&gt;{CustomerUser} = {&lt;br /&gt;      Module =&gt; 'Kernel::System::CustomerUser::LDAP',&lt;br /&gt;      Params =&gt; {&lt;br /&gt;      Host =&gt; 'xx.xxx.xx.xx',&lt;br /&gt;      BaseDN =&gt; 'ou=user,ou=dublin,dc=int,dc=domain,dc=com',&lt;br /&gt;      SSCOPE =&gt; 'sub',&lt;br /&gt;      UserDN =&gt;'otrsldap',&lt;br /&gt;      UserPw =&gt; 'password',&lt;br /&gt;    },&lt;br /&gt;&lt;br /&gt;# customer unique id&lt;br /&gt;    CustomerKey =&gt; 'sAMAccountName',&lt;br /&gt;    # customer #&lt;br /&gt;    CustomerID =&gt; 'mail',&lt;br /&gt;    CustomerUserListFields =&gt; ['sAMAccountName', 'cn', 'mail'],&lt;br /&gt;    CustomerUserSearchFields =&gt; ['sAMAccountName', 'cn', 'mail'],&lt;br /&gt;    CustomerUserSearchPrefix =&gt; '',&lt;br /&gt;    CustomerUserSearchSuffix =&gt; '*',&lt;br /&gt;    CustomerUserSearchListLimit =&gt; 250,&lt;br /&gt;    CustomerUserPostMasterSearchFields =&gt; ['mail'],&lt;br /&gt;    CustomerUserNameFields =&gt; ['givenname', 'sn'],&lt;br /&gt;    Map =&gt; [&lt;br /&gt;      # note: Login, Email and CustomerID needed!&lt;br /&gt;      # var, frontend, storage, shown, required, storage-type&lt;br /&gt;      #[ 'UserSalutation', 'Title', 'title', 1, 0, 'var' ],&lt;br /&gt;      [ 'UserFirstname', 'Firstname', 'givenname', 1, 1, 'var' ],&lt;br /&gt;      [ 'UserLastname', 'Lastname', 'sn', 1, 1, 'var' ],&lt;br /&gt;      [ 'UserLogin', 'Login', 'sAMAccountName', 1, 1, 'var' ],&lt;br /&gt;      [ 'UserEmail', 'Email', 'mail', 1, 1, 'var' ],&lt;br /&gt;      [ 'UserCustomerID', 'CustomerID', 'mail', 0, 1, 'var' ],&lt;br /&gt;      #[ 'UserPhone', 'Phone', 'telephonenumber', 1, 0, 'var' ],&lt;br /&gt;      #[ 'UserAddress', 'Address', 'postaladdress', 1, 0, 'var' ],&lt;br /&gt;      #[ 'UserComment', 'Comment', 'description', 1, 0, 'var' ],&lt;br /&gt;    ],&lt;br /&gt;  };&lt;br /&gt; &lt;br /&gt;#Add the following lines when only users are allowed to login if they &lt;br /&gt;reside in the spicified security group&lt;br /&gt;#Remove these lines if you want to provide login to all users specified in &lt;br /&gt;the User Base DN&lt;br /&gt;#example: $Self-&gt;{'Customer::AuthModule::LDAP::BaseDN'} = 'ou=BaseOU, &lt;br /&gt;dc=example, dc=com';&lt;br /&gt;  $Self-&gt;{'Customer::AuthModule::LDAP::GroupDN'} = &lt;br /&gt;'CN=OTRS_Users,OU=Security Groups,OU=Dublin,DC=int,DC=domain,DC=com';&lt;br /&gt;  $Self-&gt;{'Customer::AuthModule::LDAP::AccessAttr'} = 'member';&lt;br /&gt;  $Self-&gt;{'Customer::AuthModule::LDAP::UserAttr'} = 'DN'&lt;br /&gt;--------------------------------------------------------------------------------------&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Problem:&lt;/span&gt; &lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Solution:&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Few important points about OTRS:&lt;br /&gt;--------------------------------&lt;br /&gt;- The queue view only displays unlocked tickets by default.&lt;br /&gt;- There is a line that says "Tickets shown..... All Tickets xx"  The xx is a link which should display all tickets locked and unlocked which are in your "My Queues".&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-8060877287391939841?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/06/otrs-issues-phase-i.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-8543517995066619584.post-2545078870184070693</guid><pubDate>Mon, 16 Mar 2009 19:08:00 +0000</pubDate><atom:updated>2009-03-16T12:16:37.904-07:00</atom:updated><title>Innodb Error 'Can't create table 'mysql.ibbackup_binlog_marker'</title><description>&lt;span style="font-weight:bold;"&gt;Problem: &lt;/span&gt;&lt;br /&gt;090316 11:57:32 [ERROR] Slave SQL: Error 'Can't create table 'mysql.ibbackup_binlog_marker' (errno: -1)' on query. Default database: 'mysql'. Query: 'CREATE TABLE ibbackup_binlog_marker(a INT) TYPE=INNODB', Error_code: 1005&lt;br /&gt;090316 11:57:32 [Warning] Slave: The syntax 'TYPE=storage_engine' is deprecated and will be removed in MySQL 5.2. Please use 'ENGINE=storage_engine' instead Error_code: 1287&lt;br /&gt;090316 11:57:32 [Warning] Slave: Can't create table 'mysql.ibbackup_binlog_marker' (errno: -1) &lt;br /&gt;Error_code: 1005&lt;br /&gt;090316 11:57:32 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'testing-bin.000009' position 321&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Answer:&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;mysql&gt; CREATE TABLE ibbackup_binlog_marker2(a INT) TYPE=INNODB;&lt;br /&gt;Query OK, 0 rows affected, 1 warning (0.02 sec)&lt;br /&gt;&lt;br /&gt;bash# cd /var/mysql/data/&lt;br /&gt;bash# mv mysql/ibbackup_binlog_marker{2,}.frm&lt;br /&gt;bash# mysqladmin flush-tables&lt;br /&gt;&lt;br /&gt;mysql&gt; SET SQL_LOG_BIN = 0;&lt;br /&gt;Query OK, 0 rows affected (0.00 sec)&lt;br /&gt;&lt;br /&gt;mysql&gt; DROP TABLE IF EXISTS ibbackup_binlog_marker;&lt;br /&gt;Query OK, 0 rows affected (0.12 sec)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8543517995066619584-2545078870184070693?l=bigunix.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://bigunix.blogspot.com/2009/03/innodb-error-cant-create-table.html</link><author>noreply@blogger.com (ynilesh)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item></channel></rss>