open-sys-services

This is dedicated to the linux users, system admins, open source enthusiastic, techs whoever is looking for solution, tricks & concept etc. Reader will apply concept or execute command at their own risk. Owner of these article is not responsible for any impact, damages or errors.

Solution

Root cause Analysis

During docker build on a machine which is behind proxy server can encounter this issue. Requests do not go through running Docker engine but go directly. hence, you need to mention proxy in Dockerfile and unset later.

Second issue may happen that upstream server is not available. This is very rare. You can view with below command to see current repositories

Wednesday, February 10, 2016

Problem : Puppet was consuming 96% CPU while it ran as a daemon or ran as "puppet agent -t".Environment: RHEL 6Solution : Make sureapplication puppet module is tested with out any error and unwanted issue.Root Cause Analysis:

3. While I was tracking filename of corresponding file descriptor, I found /home/qpadm/temp was opened that had size 101GB.
4. read() call was continuously trying to read data from this file and read size was 4096 Bytes in every call. Trace looked below:

In above trace, you see file /home/qpadm/temp is opened in read mode as FD(file descriptor) is 4 and same FD is passed to read() call that returns 4096 Bytes incrementally. It supposed to take long time to read 101GB file[:) would never be finished using huge read calls those would have neen performed by kernel]. That's why CPU spiked to 60-80% consumed by puppet agent.

We need to check why above file is there and what is the usage of it and why it has large size.

This one is I think main culprit.

Another thing I noticed is either ovo was reinstalled or being migrated to newer version. In relation to this, I found following calls :

You can check that the keytab contains the appropriate encryption key by attempting to use it to obtain a ticket-granting ticket. This can be done using the kinit command:
#kinit -k -t /etc/nsupdateuser.keytab nsupdate@example.com # here nsupdate is username exiting in AD. this has privileges to update dns records on win DNS.
#klist <#will show if ticket is created or not