Monday, August 14, 2017

Food Review: Oat Chocolate Chip Cookies No egg No butter

Monday, August 14, 2017 0 Comments
Feeling depressed and dejected that my job applications are being rejected, and my follow up emails are bring ignored, and my Linkedin messages are not being replied to, I decided to seek some comfort, in some comfort food of course!!!

Come hither, these babies tasted so darn good

I hacked the recipe from here

Of course I made a few adjustments to what I have sitting in my pantry

It tasted good and I was happy

I added chopped up white chocolate while the cookies were cooling down. I just pressed down the chucks into the cookies; which added more craggies to it and made it look even better




Couldn't help myself nibbling into one cookie, damn hoe was beckoning to be eaten (sorry the language)

And here's my version of the recipe


My hacks:

bourbon flavored vanilla essence

granulated sugar instead of brown sugar

sunflower oil instead of coconut oil

2 cups of instant Quaker oats

Friday, August 11, 2017

UNIX : Changing swap value on HP-UX and AIX

Friday, August 11, 2017 0 Comments
I don't like messing with a prod server's swap value unless there is a direct request from a customer

Here's how you do it on HP-UX and AIX. I trust you have your CR raised

HP-UX

The default value for swappiness is 60. You can alter it temporarily (until you next reboot) by typing as root

echo 50 > /proc/sys/vm/swappiness

If you want to alter the swap value change permanently then you need to change the vm.swappiness parameter in the /etc/sysctl.conf file

Step 1: check what is the current value for swap

sudo cat /proc/sys/vm/swappiness

(It should give a number 60 here)

Step 2: change to a lower number

sudo sysctl -w vm.swappiness=5

Step 3: check again

sudo cat /proc/sys/vm/swappiness

(Now, it should give a number 5 here)

Step 4: append the line vm.swappiness=5 in file /etc/sysctl.conf using vi editor

AIX

Things are easier on AIX with the use of smitty. I used AIX version 5.3

1. Check the current paging and swapspace value

# lsps -a

# pstat -s

2. Run smitty and make changes on the fly

# smit pgsp-----to increase/decrease paging

3. Check paging and swapspace value again

# lsps -a

# pstat -s

4. To add paging space

# smit lvm---paging space---add

or

#smit mkps

UNIX: Solving Stale PP Error after VIO2 shutdown in AIX

Friday, August 11, 2017 0 Comments
I had a customer that had 2 VIOs setup for their LPARs. When VIO2 was shutdown/powered back on, as expected the rootvg on the server showed "stale partition" or "stale PP" error

To remediate this problem the rootvg on client server needs to be varyon, but then we also have a second problem where the sysdump is holding onto the rootvg; thus disabling us to perform varyon

So in order to do a VG varyon, we need to release rootvg from the clutches of sysdump

I trust you have raised a CR for this task

1. The first step is to make note of the sysdump location

@stepper:/# sysdumpdev
primary              /dev/lg_dumplv
secondary            /dev/lg_dumplvII
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    TRUE
dump compression     ON

2.  Change the sysdumpdev to a temporary "null" device

@stepper:/# sysdumpdev -p /dev/sysdumpnull
primary              /dev/sysdumpnull
secondary            /dev/lg_dumplvII
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    TRUE

dump compression     ON

@stepper:/#  sysdumpdev -s /dev/sysdumpnull
primary              /dev/sysdumpnull
secondary            /dev/sysdumpnull
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    TRUE

dump compression     ON


3. Perform the varyon

# varyonvg rootvg

4.  Sync rootvg

# syncvg -v rootvg

(NOTE: will probably give error "Unable to synchronize logical volume")

5. Check the vg and make sure all PV are active

# lsvg -p rootvg

6. Set the sysdumpdev back to their original values (from step 1)

# sysdumpdev -p /dev/hd7

# sysdumpdev -s /dev/hd71

7. Check that everything is ok now

# lsvg rootvg

Food Review: Laphroaig

Friday, August 11, 2017 0 Comments
I usually don't talk about drinks here but this one was worthy of an entry simply because I have never drank anything so damn tantalizing

Goes very well when paired with red meats-it's smooth and smoky at the same time

It is meant to be drunk slowly and in sips over a course of a good night with BFFs

Oh yeah

Food Review: Instant Jalebi No Yeast No Besan

Friday, August 11, 2017 0 Comments
I saw this recipe on Youtube from this MasterChef India and she made it look so easy I just had to try it

My sugar syrup was off so I had to stir for way too long just to burn off the excess water so I can get a thick single strand stage, but still, in the end the jalebi turned out really well. Crispy, dripping in sugar and melt in your mouth orange fatsos. Yummy!

Damn just look at these hoes, will you? Do they not tantalize your senses?


They look wiggly because I didn't use a nozzle in my piping bag

The link to full recipe here

Hacks

I mixed ghee with cooking oil to deep fry the jalebis

Orange coloring in gel instead of powder

Added saffron strands and rose essence in batter

Tuesday, August 8, 2017

UNIX: Problems and Solutions to Running Nickel on HP-UX

Tuesday, August 08, 2017 0 Comments
Back then whenever a server crashed, one of the first things I used to do was to run nickel script to collect all kind of system logs so us engineers can start investigation. Nickel stands for Network related Information Collector, Keeper and Elaborator.

It is free, sometimes located in the HP-UX machine itself, or maybe in your sharepoint. Download and save it into the server and run the sh script

But what I am going to show here is the problems that usually arise with nickel (imagine running a stress test for a heart patient) and the solution

Tested on older versions of HP-UX

I trust you have the necessary tools and permissions to run nickel

Transferring nickel file from Windows to UNIX via ftp

1. Unzip latest nickel.zip in PC (Windows)

2. If /opt/contrib/bin does not exist on client server then create a directory path 

     # mkdir -p /opt/contrib/bin

3. FTP nickel from Windows PC to HP-UX server in "BINARY" mode, into /opt/contrib/bin

4. In the HP-UX server, go into the said directory

     # cd /opt/contrib/bin 

5. Change permission of the file

     # chmod 555 nickel 

6. Run nickel script

     # ./nickel 

7. A file: nickel.yourhostname.tar.gz will be created.

8. FTP in "BINARY" mode, nickel.yourhostname.tar.gz to Windows PC

The reason I am stressing about FTPing in Binary mode is because by default most FTP software uses ASCII mode and this is generally corrupt the tarball file, hence the Binary mode to transfer

====================================================================
What to do if nickel script appears to hung while running (i.e running for 30 mins is one of it)
====================================================================

Well, if nickel is not giving any output, then it may have hung while running. I have had this many times, not a reason to worry or panic. Here's what I used to do

Solution 1

1. Exit nickel session with Ctrl + C

2. Issue following commands

     # /sbin/init.d/diagnostic stop
     # /sbin/init.d/diagnostic start

3. Run Nickel again

     # cd /opt/contrib/bin
     # ./nickel

Solution 2

This is a solution to yet another problem that may arise after attempting Solution 1 where nickel again hangs ar *stm*

1. Telnet another session to the said server

2. Run the following commands

     # ps -ef | grep nickel
     # kill -9
     # kill -9

   Repeat above step if necessary

Solution 3

Because nickel is not perfect or God sent...

Possible causes for error "There is not enough memory available now" while running nickel

1. Server was too busy at that time

2. While the script does # cat  of big *.log files or when it is collecting network log netfmt

3. You may may have noticed some logs collected in nickel appear blank (in this case the process is not completed, hence the blank logs)

4. OLD STM , the query for STM info is slow, believe me

Solution to memory shortage error:

1. Backup & nullify the logs (if it is too big) and re-run nickel

     # >

2. Check the memory utilization of servers by running the following commands

     # top

     # glance -m

3. Run the nickel when the server is free

*I was using a very old version of nickel from 2007/2008