Month: February 2014


I’ve been lucky enough to be sent some Obihai hardware, so you will see a few posts from me about my experiences with setting it up and what not. I’ve been sent an Obi202 and ObiLine which I should start to tinker with from the weekend.

Unfortunately they arrived today, however they are waiting at the local PO, which means I wont be able to collect them until Saturday morning.

So you’ll be seeing some posts from me about the hardware and my experience. Looking forward to it to be honest, as it looks pretty impressive on paper. If anyone is already using it, drop me a comment, as I wouldn’t mind doing some test calls via the Obitalk number that is provided when you setup an account.

Noontec N5 Gigalink Firmware info

As discussed in one of my previous posts here. I own a Noontec N5 Gigalink single drive NAS. It’s not the greatest thing around, but for what it does do well (basic file sharing) it does the job. I don’t use any other features of the unit, just simply the file sharing side of it.

I wish I never upgraded the firmware, as the one that it shipped with had a much more basic UI for administration, however the newer firmwares you find may be TerraMaster branded, which I honestly don’t like. Although TerraMaster make a unit based off the N5, I just like it to remain Noontec branding.

I found that the firmware available at the page here, is a recent Noontec branded one. So I have installed it and will be using it for now. It is version as per below;


NOTE: The direct link above to Noontec site may disappear over time. Should it do so, I have zipped up a copy and made it available from my site below; (From:

DB2 Archive log backup failing

Had a client/server who was unable to do any DB2 Archive log backup. Attempts to run it would fail and when I looked into the logs the failure was seen against the key log lines below. I’ve named the log file and component where this log exists.


2100 2944 02/16 11:40:11 111111 Servant [---- SCHEDULED BACKUP REQUEST ----], taskid [15821] Clnt[aaaaa003] AppType[DB2 on Unix][62] BkpSet[AA1] SubClnt[AA1_Archive_logs] BkpLevel[Full][1]


13720 26b4 02/16 11:40:16 111111 SrvDb2Agent::AgentAttach() - 1: dataAgentAttach-> HostName=aaaaa003.bbbbb.ccc*aaaaa003*8400*8402 start...
13720 26b4 02/16 11:40:16 111111 ** CVSession::attach(ulPortArg):
	- RemoteHost=aaaaa003.bbbbb.ccc.
	- RemoteProcess=todo.
	- AuthenticateClient failed. Error=9000026.

13720 26b4 02/16 11:40:16 111111 SrvDb2Agent::AgentAttach() - 0: dataAgentAttach() failed: m_cvsOA.getLastError: Err Number=9000026 sLastErr=[CVSession::authenticateClient]:Remote system [aaaaa003.bbbbb.ccc]. Failed authentication returned from server..
13720 26b4 02/16 11:40:16 111111 SrvDb2Agent::RunClient() - 0: AgentAttach() failed.
13720 26b4 02/16 11:40:16 111111 SrvDb2Agent::ExitHere() - 1: JobObjectInitialize(111111) started...

Failed authentication messages could indicate that like the message says, the network password used by the Commserve and Client to communicate is different, thus the communication fails. i.e. Client could have a network password stored on it’s configuration that doesn’t match the one for this client stored in the Commserve database.


Something might be wrong with the communication between the Commserve and the Client (in either direction).

So I would recommend checking out that the communication is fine and that the Commserve is resolving the client correctly and accessing the correct IP address for the client.

If this all checks out fine, and communication from Client to CS is fine (in both directions). You might have to force a network password reset/sync. The easiest way I find to do this is to do a LOCAL uninstall on the problem client (to ensure that the backup history for client is retained in the Commserve) and perform a reinstall on the client using the Simpana DVD3 media. Ensuring to install again using the same details the client is displayed as in the Commserve. During the reinstall the network password is put in sync again.

In the case of the client here, we had to reinstall it. Post the reinstall the client and backup attempts worked fine. ¬†This would affect all Simpana iDA’s on the client too, thus impact all backups for the client.

Cache Database is failing at client side

Recently came across the following failure condition against a Unix client during backups via Commvault Simpana. Not something I have seen recently however, as you will see from below, the reason for this is quite simple once you understand why.

Exact error reported in Simpana Console for the job;

Error Code: [10:15]
Description: [Cache Database is failing at client side.]

Picture below shows the error too;


Check the client’s properties and confirm if it has the following options enabled. Per the screen capture below, we want to confirm under the Client Side Deduplication tab if the “Enable Client Side Disk Cache” tick box is ticked.


If this option is ticked, as shown above, it will use a max cache-database size of 4096MB (4 Gigabytes), which is created in the same location as the client jobResults folder.

Guess what happens if your client doesn’t have enough disk space for this cache-database? If your guessing the error we got during this backup attempt? You’d be absolutely correct.

This client in question only had about 2G of diskspace available per the output below;

hostname:/opt/simpana/Log_Files]bdf /opt
Filesystem          kbytes    used   avail %used Mounted on
/dev/vg00/lvol3    20971520 18749152 2205632   89% /

Which meant backup attempts against this client when this option is enabled and set to 4096MB max cache-database size caused the error per the start of the post.

Solution here, increase space on the volume where jobResults is hosted, turn off Client Side Disk Cache, reduce Client Side Disk Cache, or move jobResults to a volume with more space. You just need to pick the option that suits you.

Site modifications and updates

I’ve attempted to have blog references to my site on Planet Linux Australia’s feed updated, but these haven’t been done in some time, so rather than leave the feed linking to a broken/deconfigured site, I have created the subdomain again and forwarded it’s requests to my blog that run’s on the TLD for these days.

Hello to those on Planet Linux Australia who will now once again see my posts.

Haven’t done much Linux hacking since I got rid of the Raspberry Pi’s I was using to play around with various things. I still want to learn to code in Objective C and Python more, so will start to tackle those soon. Thanks to a post from Craige McWhirter, I think I have found a new Python book I should buy.

Learning Python from O’Reilly, will be next book on my purchase list. However my Obective C one is still sitting on my desk and I haven’t actually started it as yet.

In addition, I have imported content from another domain I owned, which I am not going to renew. It’s content has been merged into the main site here, and I will continue to post that type of content here as needed. For reference domain is/was “

A washed car always leads to rain

Spent a good amount time lastnight washing the cars, and this usually results in the use of the car next day involving lots of rain. Sure enough my trip to Wyong today involved driving in lots of rain on the way up and back.

Car is now dirty, guess I will be cleaning it again probably tomorrow, as it certainly needs it again now.

The rain we drove through was very heavy and the visibility was reduced greatly during the trip.

Broke my corded Jigsaw

The other day I was using my corded Jigsaw which I got free from neighbour a while ago. Unfortunately it broke, so it looks like I need to buy another.

Not the best timing, but I was going to eventually replace it with a Makita cordless one anyways, guess I will have to buy one sooner now, since I don’t have a working one now and still have some jobs I am completing with it.

Going to buy this one here. (Model: BJV180Z)

Hackpad – a site to watch

I remember seeing someone on twitter mention Hackpad and I meant to sign up and look at it further. Got side tracked, never happened.

Saw it mentioned again today and signed up. So glad I did, as I was in the middle of researching for setting up a private wiki for a lot of stuff I like to keep track off. Some of the content will merge into other sources as it gets to a point where it can be shared to wider audiences. I’ve used these wiki’s below in the past;

  • MediaWiki
  • Confluence
  • Dokuwiki

However, each has its pros and cons. I won’t go into detail on pros and cons for each, as they might be different to different people.

So glad I checked out Hackpad, as it suits what I need perfectly, and I can see you can do exports into html, markdown and plaintext. See the graphic below to see what I mean. When you select html, it sends you an email with the download link.



Unfortunately my content cannot be seen by the public, as it’s a private site. I recommend if your interested in playing around with Hackpad. You should go sign up.

Makita 18v LXT Li-Ion Cordless Hammer Drill Driver BHP458

The new Makita 18v LXT Li-Ion Cordless Hammer Drill Driver (BHP458) I ordered yesterday arrived. I ordered it as a kit from Sydney Tools, as I needed a charger and batteries for some other skins I purchased on the weekend, so this made a good deal to get those items.

My kit I ordered is here.

I charged up both batteries, and used the drill just briefly and was complete impressed by the torque that it produces when used in driver mode. Very impressive. The dual LED lights are nice and bright too, think this will be one of my new favorite tools for a while.

Will be sure to post more feedback after I use it a bit more.