Month: April 2013

Pedego Electric Bike

Recently while on holidays, I had the chance to hire our a Pedego Electric Bike. I must say I really liked it, was tempted to honestly buy one, but probably not the best idea.

My wife liked it too, until she had tumble. Shes is alright, just got a few scratches and sore.

2013-04-24 14.36.34

Beautiful sunrise

While on holidays, I managed to get up early one morning and get a glimpse of the sunrise over the ocean while staying in Queensland on the Gold Coast. Below is a photo as captured by a GoPro Hero3 Silver just sitting on a fence.

2013-04-23 18.32.29

Simpana 9 Oracle or File System SnapProtect Failure via NetApp

Had an interesting condition in the last few days and really thought I would share, as it seemed like something really simple that could be checked by anyone.

Likewise, this could affect Oracle and/or File System SnapProtect jobs via NetApp.

Error: 62:2145

Description: The client machine initiator address is not visible on the file server. Please check the SAN or iSCSI connectivity between the file server and the client.

Upon reviewing this one, I identified the following conditions;

[ClOraAgent.log]
11502 1   04/16 18:20:07 19593 ManageONTAP::OpenConnection: Trying HTTP on port:[80]
11502 1   04/16 18:20:08 19593 ManageONTAP::OpenConnection: FileServer:[LBnNNNnn-n] Version:[NetApp Release 8.0.2P6 7-Mode: Fri Jan 27 14:48:08 PST 2012]
11502 1   04/16 18:20:09 19593 CVSnapEngineNetApp::cvso_snapDevices Check for snap clone dependences on volume:[volume_boot] on file server:[LBnNNNnn-n] returned success:[true] dependency on:[false]

First connection to the FileServer completes, however…

[CVMA.log]
17401 11  04/16 18:20:23 19593 ManageONTAP::OpenConnection: Trying HTTP on port:[80]
17401 11  04/16 18:20:23 19593 ManageONTAP::OpenConnection: Failed to get HTTP system version for server [LBnNNNnn-n]. Error:[-1][Can't connect to host (err=-8).]. This could be because 1. The server is powered down. 2. The server name is not resolvable from this host 3. Error with HTTP configuration. Please rectify the above errors (if any) and try again.
17401 11  04/16 18:20:23 19593 ManageONTAP::OpenConnection: Trying SSL on port:[443]
17401 11  04/16 18:20:23 19593 ManageONTAP::OpenConnection: Failed to get HTTPS system version for server[LBnNNNnn-n]. Error:[-1][Can't connect to host (err=-8).]. This could be because 1. The server is powered down. 2. The server name is not resolvable from this host 3. Error with HTTPS configuration. Please rectify the above errors (if any) and try again.

As you can see the next attempt fails… The final attempt will be to determine if the HBA’s from the client can be seen against the FileServer. Should we also get failures again connecting to the FileServer it will fall through with the error below.

[CVMA.log]
17401 11  04/16 18:20:49 19593 CvSnapNetApp::detectHBA() - No initiators logged in. Getting all initiators.
17401 11  04/16 18:20:49 19593 CvSnapNetApp::detectHBA() - Returning initiator ID list length:[1] iSCSI:[false] LoggedIn:[false]
17401 11  04/16 18:20:49 19593 CVSnapEngineNetApp::cvso_mapSnaps Initiators on host:[libobk-client] Are not logged into file server:[LBnNNNnn-n]. Please check the SAN or iSCSI connectivity between the file server and the client.
17401 11  04/16 18:20:49 19593 ERROR:60516:Initiators on host:[libobk-client] Are not logged into file server:[LBnNNNnn-n]. Please check the SAN or iSCSI connectivity between the file server and the client.
17401 11  04/16 18:20:49 19593 CVSnapEngineNetApp::cvso_mapSnaps Printing status of clones at the end of map
17401 11  04/16 18:20:49 19593 CVSnapEngineNetApp::cvso_mapSnaps pSnapInfo->SnapDevice: [] status [11]
17401 11  04/16 18:20:49 19593 CVSnapEngineNetApp::cvso_mapSnaps iSnaps=0
17401 11  04/16 18:20:49 19593 CVMASnapHandler::mapSnaps() - From Snap Engine VolSnap:Status-[60500] Err-[60516:Initiators on host:[libobk-client] Are not logged into file server:[LBnNNNnn-n]. Please check the SAN or iSCSI connectivity between the file server and the client.]: [60500:].
17401 11  04/16 18:20:49 19593 CVMASnapHandler::mapSnaps() - Failed to map snaps. Err [60500:Error occurred in Snap Engine Error[]].
17401 11  04/16 18:20:49 19593 CVMASnapHandler::mountVolumes() - Request for mountVolumes Failed. Status [60500].
17401 11  04/16 18:20:49 #####  WORKER   [211977/0/0          ]  Failed to Mount Volume . Err [60516:Initiators on host:[libobk-client] Are not logged into file server:[LBnNNNnn-n]. Please check the SAN or iSCSI connectivity between the file server and the client.].

Things we have learnt, if communication between Client and Fileserver is impacted, it can cause the failure above. So be sure to validate that communication between the client and Fileserver is not affected.

Side note, if you wish to lock down the Simpana to use http vs https for the ManageONTAP communication you can use the registery key below;

s<arrayname>_NETAPPONTAPUSEADMINTRANSPORT

Defined under the iDataAgent branch of the simpana registry. Where the value of the key is http or https.

i.e. Example

vi /etc/CommVaultRegistry/Galaxy/Instance001/iDataAgent/.properties
Add line;

sLBnNNNnn-n_NETAPPONTAPUSEADMINTRANSPORT http

Now our communication will be http to FileServer LBnNNNnn-n, per regkey.

Installing Shepherd onto OSX Lion

I’ve been building a replacement server for my current mythtv box that is running on OS X Lion.

To install shepherd epg grabber I used the following procedure:

 

Install Active Perl form ActiveState.

http://www.activestate.com/activeperl

 
make sure you add activeperl to your .profile:
export PATH=/usr/local/ActivePerl-5.16/bin:/opt/local/bin:/opt/local/sbin:$PATH
 

install shepherd prerequisites:

sudo cpan
install XML::Parser
install XML::Twig
install XML::Writer
install Date::Manip
install LWP
install Memoize
install Storable
install HTML::Parser
install HTML::TreeBuilder
install SOAP::Lite
install CGI
install Term::ProgressBar
install PerlIO::gzip
install Compress::Zlib
install Lingua::Preferred
install Unicode::String
install Lingua::EN::Numbers::Ordinate
install Log::TraceMessages
install WWW::Mechanize
install HTML::TableExtract
install Net::SSL
install XML::LibXML

exit

 

Install perl MySQL client

ppm install DBD-mysql

 

then install HTTP Cache Transparent proxy

ppm install HTTP-cache-transparent

 

Download xmltv

http://sourceforge.net/projects/xmltv/files/

uncompress xmltv, change directories and compile

perl Makefile.PL

 

Commvault Simpana 9 Linux push deployment failure

Wanted to post about a very common Linux push deployment failure, infact I do believe this is applicable to other Unix platforms, so be sure to check this common thing against other Unix platforms.

An attempt to push Simpana 9 Linux File System iDA (and/or other iDA’s) will result in a failure like below, I’ll name the logs the information is obtained from so end readers can follow along.

[DistributeSoftware.log]

3000 ea4 04/09 19:29:18 27 CCvPatchesUpdateDBClient::InstallUnixSeed STDERR[]
3000 ea4 04/09 19:29:18 27 CCvPatchesUpdateDBClient::InstallUnixSeed STDOUT[*** UNIX SEEDING SETUP_ERROR 2042 detected and returned. ***
]

3000 9f8 04/09 19:29:28 27 ****** Now Check status of all clients ******
3000 9f8 04/09 19:29:28 27 Check status started for client [192.168.11.24][-1]
3000 9f8 04/09 19:29:58 27 Clients Failed:
3000 9f8 04/09 19:29:58 27 Client [-1] [192.168.11.24] [QINSTALL_BASE_PACKAGE_FAILED]
3000 9f8 04/09 19:29:58 27 *******************************************

3000 9f8 04/09 19:29:58 27 Job Failed.
3000 9f8 04/09 19:29:58 27 COMPLETE CALLED (JOB Status::FAIL), Job ID = 27

The most common cause for this failure is the client has a hosts file that is configured like so;

[/etc/hosts] – Bad version

127.0.0.1 localhost ldebx86-1.lab.libobk.so ldebx86-1

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Essentially your clients primary hostname and FQDN has been associated to a localhost entry. Modify the hosts file so that these hostname entries are defined against your primary interface that the machine has, as shown below;

[/etc/hosts] – Good version

127.0.0.1 localhost
192.168.11.24 ldebx86-1.lab.libobk.so ldebx86-1

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

This would have to be one of the most common issues for a push deployment.

If you attempted an interactive installation on this client when the hosts file was in the bad state, you would get the failure below during interactive install which will clearly indicate the problem.

Simpana 9.0.0 (BUILD84) Linux glibc2.11
——————————————————————————-
Physical Machine Host Name

We found one network interface available on your machine. We will associate it
with the physical machine being installed, and it will also be used by the
CommServe to connect to the physical machine. Note that you will be able to
additionally customize Datapipe Interface Pairs used for the backup data
traffic later in the Simpana Java GUI.

Please check the interface name below, and make corrections if necessary:

Physical Machine Host Name: ldebx86-1.lab.libobk.so

*** We found that /etc/hosts file associates name you provided
*** (ldebx86-1.lab.libobk.so) with loopback address.
*** Please check the /etc/hosts file and make corrections if necessary to
*** remove this association, or provide a new Host Name.

Press <ENTER> to try again …

If this post assists you, please leave comments.

Ubuntu Linux and Commvault Simpana 9 startup

As a follow up to the post yesterday about Debian Linux and Commvault Simpana 9 startup as found here.

Ubuntu Linux is also going to have the same issue. Since Ubuntu is based on Debian, it too has a runlevel 2 by default.

I installed Ubuntu 11.10 and out of the box it was on runlevel 2.

The same workaround I provided on the Debian post would be applicable here too.

EDIT:

Ubuntu 11.10 is not affected, as the installer detects the runlevel 2 correctly and sets the correct symlinks to the init scripts so that startup of Ubuntu will see the services start up fine.

Debian Linux and Commvault Simpana 9 startup

If you’ve recently installed Commvault Simpana 9 software/services onto a Debian Linux client, be sure check your runlevel and ensure that the software/services will start on the next reboot automatically.

By default simpana 9 software/services will be linked into runlevel 3 and runlevel 5, however on Debian the default runlevel is 2. (When your not running any X11 that is).

To confirm what runlevel the system runs by default you can check the inittab file and confirm an entry. Below is an example;

root@ldebx86-1:~# cat /etc/inittab | grep initdefault
id:2:initdefault:

And the same output from a CentOS 5.6 server (which is running X windows);

[root@lcosx86v56-1 ~]# cat /etc/inittab | grep initdefault
# 0 – halt (Do NOT set initdefault to this)
# 6 – reboot (Do NOT set initdefault to this)
id:5:initdefault:

From the output we can see that the top most one will default to runlevel 2 and the bottom one runlevel 5.

If you cat the inittab file you will see some comments indicating the runlevels;

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

And from CentOS 5.6 server;

# Default runlevel. The runlevels used by RHS are:
# 0 – halt (Do NOT set initdefault to this)
# 1 – Single user mode
# 2 – Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 – Full multiuser mode
# 4 – unused
# 5 – X11
# 6 – reboot (Do NOT set initdefault to this)
#

Post my Commvault Simpana 9 Linux File System iDA deployment, we go check for the Galaxy initscript being linked from the runlevel directories, and as you can see below, no script for runlevel 2, thus these services will not come up automaticaly upon reboot on this server.

root@ldebx86-1:/etc/rc3.d# ls -l *Galaxy*
lrwxrwxrwx 1 root root 16 Apr 8 19:07 S23Galaxy -> ../init.d/Galaxy
root@ldebx86-1:/etc/rc3.d# cd ..
root@ldebx86-1:/etc# cd rc2.d
root@ldebx86-1:/etc/rc2.d# ls -l *Galaxy*
ls: cannot access *Galaxy*: No such file or directory
root@ldebx86-1:/etc/rc2.d#

This can be resolved by of course creating the same symlink in the runlevel 2 directory and it will work next time as expected.

cd /etc/rc2.d
ln -s ../init.d/Galaxy S23Galaxy

Now we check again to confirm it created;

root@ldebx86-1:/etc/rc2.d# ls -l *Galaxy*
lrwxrwxrwx 1 root root 16 Apr 8 19:15 S23Galaxy -> ../init.d/Galaxy

Job done.

IBM Express-C

I was introduced by another work colleague to IBM Express-C. The reason for this introduction is that I needed a free version of DB2 which could be installed on Windows and/or Linux for a test environment. i.e. I wanted to simulate an environment where I could install the Commvault Simpana DB2 iDA to see how it’s configured, in addition perform backups and restores.

So if your in a situation like myself, I can highly recommend it.

IBM Express-C can be downloaded from here. In addition you can obtain a copy of a free e-book for it called “Getting started with Express-C” from here. The later item probably only of use if you want to develop on the database platform. Forums also exist as linked here.

Commvault Simpana 9 DB2 iDA documentation is found here.

Output of the commands below against a DB2 client are handy for troubleshooting purposes (command in bold);

  • db2level – obtain db2 revision/version information
  • db2ilist
  • db2 get instance – list current instance
  • db2 list db directory – list all DB’s in current instance (as defined in OS environment variable DB2INSTANCE)
  • db2 get dbm cfg – list all database manager configuration file values
  • db2 get db cfg for <DB> – list all DB parameters for <DB> and shows values.

Recover MySQL root password

Last week I found myself in one of those situations where a machine I setup nearly 2 years ago required some additional MySQL databases created and for the life of me I couldn’t find where I had recorded the MySQL root password.

I figured setting a new one should be possible, however I’ve never had to do it. After about literally one search on Google and a few short clicks later I had found what I needed. I ended up at the following site here.

Process looked easy enough so I scheduled an outage window, since the MySQL server in question was being used for a Confluence Wiki.

Sure enough the process worked fine, I now had set a new MySQL root password and brought the services back online.

I of course immediately added the password into my password safe, so I don’t have to do it ever again.