check what is the log level set to here. can you rerun the job with debug mode enabled ?
whats there in trace.txt and result.xml
hope this will help you
Hi Blas ,
We are running in the debug mode only
<!-- root category ========================================= -->
<category name="root" priority="info"/>
<category name="rscd" priority="debug" appender="D:/BMC/BladeLogic/RSCD/rscd.log" debugappender="stderr"/>
<!-- category name="keystroke" priority="info1" appender="D:/BMC/BladeLogic/RSCD/keystroke.log"/-->
<category name="rscdsvc" priority="info" appender="D:/BMC/BladeLogic/RSCD/rscdsvc.log" debugappender="stderr"/>
dont you find anything related to this in rscd log ?
Also enabling debug mode for the job in question.
Am seeing the below RSCD.log from the target server :
08/06/14 11:13:59.934 INFO rscd - INCAO3302 5183 -1/-1 (Not_available): (Not_available): FIPS Enabled
08/06/14 11:13:59.935 INFO rscd - INCAO3302 5183 -1/-1 (Not_available): (Not_available): Agent version is 8.3.02.332
08/06/14 11:13:59.935 INFO rscd - INCAO3302 5183 -1/-1 (Not_available): (Not_available): Platform Details: x86_64;INCAO3302;2.6.32-358.2.1.el6.x86_64;Lin
ux;#1 SMP Wed Feb 20 12:17:37 EST 2013;x86_64
08/06/14 11:21:43.301 INFO rscd - INCAO3302 5231 -1/-1 (Not_available): (Not_available): FIPS already enabled
08/06/14 11:23:14.880 INFO rscd - INCAO3302 5232 -1/-1 (Not_available): (Not_available): FIPS already enabled
08/06/14 11:23:22.746 INFO rscd - INCAO3302 5234 -1/-1 (Not_available): (Not_available): FIPS already enabled
08/06/14 11:23:23.607 INFO1 rscd - 126.96.36.199 5234 99/99 (BLAdmins:email@example.com): CM: > [PatchAnalysis] Deleting //10.240.214.7//
BLpatchcheck2.exe is not used in RHEL Patch Analysis.
Set the DEBUG_MODE_ENABLED property o True for the job and execute it against the failing target.
Collect the Job Run Log,and the debug files that the Job Run Log mentions.
Send them to Support via a new Support Issue
a couple notes:
since 8.2 you can run 'agentctl toggle' to enable/disable debug logging w/o having to edit the log4crc.txt file.
for linux, the analysis will copy over the catalog metadata and some other files to ??STAGING_DIR??/LinuxCatalog_xxx and then run blyum using the files in that directory. if that directory is still present you can look at the various log files in that directory and see what the errors are, or try to manually re-run blyum like:
cd to the LinuxCatalog dir on the target in bash
<rscd install>/bin/blyum -C -c yum.conf update
i think DEBUG_MODE_ENABLED property not defined in the server,
how we have to define the propert during the scanning of the server.
Am getting the below error
CRITICAL:yum.cli:Config Error: Error accessing file for config file:///opt/bmc/b ladelogic/NSH/bin/yum.conf
after running the command you gave
Jim is asking for set DEBUG_MODE_ENABLED to true against the patch analysis job not against server. Just execute the patch analysis job against failing target(s).
Right click on the job and select property and then select DEBUG_MODE_ENABLED from the drop-down list and set it to true.
or select the job and go to properties tab. under extended one there must find DEBUG_MODE_ENABLED property. just set that to true.
Hi Bals / Jim
Thanks for the response. i have ran the job in the DEBUG_MODE_ENABLED = True
but still remains the same condition. Please find the analysis log from the folder location
D:\BMC\BladeLogic\NSH\tmp\debug\application_server\RHEL Security Patch Analysis-DC.BDC6.CV.082\Thu Aug 07 05-20-18 EDT 2014\10.240.201.68
Debug Flag: ON
Analysis Options:List - update
Initialize: cleaning up previous result files
clean up complete
Running YUM from /var/tmp/stage/LinuxCatalog_28585_10.240.201.68...
YUM Command: includelist=`cat rpm-includes.lst| tr -d '
' | tr '
' ' '` && for i in 0 1 2 3 4 5 :; do echo n; done | blyum -c ./yum.conf -C update $includelist > "/var/tmp/stage/LinuxCatalog_28585_10.240.201.68/yum_analysis.res" 2> "/var/tmp/stage/LinuxCatalog_28585_10.240.201.68/yum.err.log"
YUM dry run done!
Generating rpm information...
RPM information generated.
Getting installed RPMs count....
Record Analysis logs in logfile: /var/tmp/stage/LinuxCatalog_28585_10.240.201.68/analysis_log.log
Still i cant scan the server 10.240.201.68
Is there a ??STAGING_DIR??/LinuxCatalog_blah directory on the target ? if so, what is the name ? what are the contents ?
right - running the job w/ the debug enabled was not going to fix anything, it was going to expose additional logging to investigate the problem.
so on the target is there a /var/tmp/stage/LinuxCatalog_28585_10.240.201.68/ directory ?
can you zip it up and attach it ?