Friday, January 30, 2015

To Enable Remote Command from Red Hat Central Management Portal

The latest version of the following packages needs to be installed:

up2date 
rhncfg 
rhncfg-actions 
rhncfg-client
 
The remote commands currently on the Pending actions queue can be applied immediately to the system by running the command from the command prompt:

# rhn_check

But schedule actions actually depends on rhnsd service (Red Hat Network Daemon) that periodically connects to Red Hat Network to check (rhn_check) for updates, notifications or to apply remote commands if it is configured. This service will check with RHN every 240 minutes (default). If you want to schedule your remote command to run every hour, please change the value in the file to:

/etc/sysconfig/rhn/rhnsd

INTERVAL=60

Please take note that changing this interval to less than 15 minutes will result to "Abuse of Service" error which means that the system is checking in with RHN more than the allowed number of times (100 check in per 24 hours).

After changing the INTERVAL, run this command:

# service rhnsd restart
 
Actually, to run remote commands, we only need to enable:

# rhn-actions-control --enable-run

but if you want to run config files, diffing package versions, mtime, etc., --enable-all
will be appropriate.

--enable-all will let you deploy remote commands

Wednesday, January 28, 2015

GHOST: glibc vulnerability (CVE-2015-0235) - How to fix the issue in Ubuntu and Red Hat

In Linux Ubuntu, the easy way to fix is update your library to the following version:


Follow the command below to update the Ubuntu library
  • $ sudo apt-get update
  • $ sudo apt-get dist-upgrade
In Linux Red Hat, the easiest way to resolved the issue is to update the glibc and nscd  packages on your system using the package release with the following errata: 


Thursday, January 8, 2015

What is working in IT in a non-IT Company vs an IT Software or Service Provider company?

After working in both conditions here are my observations:

Working for pure IT services company:

- I worked on many projects involved many technologies, latest and old.
- Less pressure during development since SDLC involved, sufficient time for
development. Even with agile also, I used to get much time to do things since we followed "agile way of estimating effort" 
- I used to get time to do things for my own learning, for example using JUnit ,MUnit, Mockito, writing unit test cases, doing POC, setting local dev environment using Virtual Box or VMware or Fusion and now, you can actually leverage the AWS for the cheapest t2.nano instance for almost $5 / month.
- I don't have to interact with customer directly unless I am in a big role.
- Challenging work environment and you will be on the go. 

Working for non-IT company as an IT support engineer:

- Working closely with customers (people who doesn't know technology well).
- Things changes so fast, even after project launch I used to get change requests to modify something instantly! 
- Very tight schedules and too much pressure.
- Once project goes live I used to get couple of weeks to one month free time.
- I am only working on one project, to support the users on technical issues etc. I am quite familiar with the system now and there is nothing to learn much. 
- Not so challenging, doing simple things within shortest time is challenging.

- Convincing users on certain things is difficult. Whenever we tell them that certain things cannot be done this way or that way, they immediately says "if you can't do it, why you need this computer system?"

Hard to pick which field you want to take:

To work in a IT Service company, is fun and you will envolve on different company, high expectation of course, don't afraid if you fail because the today's failure can make way for your tomorrow's triumph...

To work in IT support or in-house is kind of layback especially if your rule is supporting internal client. You can make your life busy if you want to. Make your own challenge but it's up to you. You can do that or just go with the flow.