Was sad to hear in the news today that Harold Ramis has died. Still not that old either. Will always remember him from Ghostbusters.
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  Clnt[aaaaa003] AppType[DB2 on Unix] BkpSet[AA1] SubClnt[AA1_Archive_logs] BkpLevel[Full]
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.
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.
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 heimic.net 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 “libobk.so“
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.
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)
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.
I’ve had a driver and impact drill set from Makita for a year now. It was an 18v combo kit that my wife got me as a Christmas gift. It’s been a very good set, however it is the generation prior to the LXT models available now.
I would typically buy PC bits with any extra money I get from time to time for working various extra work outside the normal year. While I still have been considering the purchase of PC hardware, I thought it might be a good idea to buy some new Makita 18v gear. It just so happens I noticed some price drops, so I thought why not.
Picked up the following items today, and plan on buying an additional item this week, as I need some 18v LXT 3.0Ah batteries and charger to suit.
As I mentioned above, was going to buy a rapid charger and 2 batteries, however decided to buy the kit below which includes the batteries I need and the rapid charger, but also gives me a hammer drill in the LXT range, which I somewhat need, as I don’t have one already from my existing kit I own.
At which point I will be buying probably another individual battery to give me 3 total and some additional 18v LXT Li-Ion tools. As I really want to get a jigsaw, circular saw, multitool.
You might not seen any more posts from me in regards to the Raspberry Pi, as I sold off my two units I had. I had fun with them and managed to do a number of things with them. In the end I just felt I didn’t have anything more I could do with them, so I decided to sell them on to someone who wanted the excitement to tinker.
My wife and I decided to take our oldest son to Wet n Wild – Sydney as a treat. Considering this week was his first day at prep school.
He was very excited, and when we arrived yesterday afternoon his excitement at the time was evident once he saw the place. We had a good time and managed to make the most of the special price for twilight after 3pm. Mind you it got pretty cool once that sun went down about 8pm. All in all it wasn’t bad.
The queues were of course fairly long for the attractions and the food/drink prices are a bit of a joke.