Highlighted
Absent Member.. Absent Member..
Absent Member..
662 views

JEE Jboss by Shell Discovery

Hi all,

 

I am struggling with the JEE Jboss by Shell discovery Job.

 

I am running uCMDB 10.01 CUP6.438 (CP 12.08.1009)

 

I am able to discover the JEE TCP Ports but when I try to run the JEE Jboss by Shell discovery job the job stops with the message:

 

<< Progress message, Serverity: Warning>>
jboss: Not data collected

<<Progress message, Severity: Error>>
JBOSS: Connection failed.

 

When I look in the communication log I notice the following.

 

<EXEC start="10:12:25" duration="12">
<CMD>[CDATA&colon; perl -e '
use File::Basename;
$d = shift;
-d dirname($d) || print("Path not found\n") &amp;&amp; exit 1;
$d =~ s/\s/\\$&amp;/gs;
for $file (glob($d)){
(-l $file and not -e readlink($file)) &amp;&amp; print("Path not found\n") &amp;&amp; exit 1;
print "&lt;==&gt;\n";
@Stat = stat $file;
open FH, $file; print while(&lt;FH&gt;);close FH; print("&lt;=&gt;\n");
printf("%s &lt;=&gt;\n", basename($file));
printf("%s &lt;=&gt;\n", $file);
}' "d:\hp\UCMDB\DataFlowProbe\bin/host-slave.xml" ; echo ERROR_CODE:$?]</CMD>
<RESULT>[CDATA&colon; Path not found
ERROR_CODE:1]</RESULT>
</EXEC>

I attached the complete communication log to be complete.

 

I copied the jboss-client.jar from the target server to the probe directory (d:\hp\ucmdb\dataflowprobe\runtime\probemanager\discoveryresources\j2ee\7.x) and I added the discovery user to the correct groups.

 

What could go wrong here?

 

Kind regards,


Martijn Krop.

Tags (2)
0 Likes
5 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: JEE Jboss by Shell Discovery

Hi All,

 

Does anyone have any experience with this issue?

 

What is the best step for me to take?

 

Regards,

Martijn Krop.

0 Likes
Highlighted
Established Member..
Established Member..

Re: JEE Jboss by Shell Discovery

Martijn,

 

You have a permission issue. It appears that a large number of the simple file system based access requirements are not met. I would provide this list to your Unix admin. From my reading of your log, your user is able to connect, but once connected and the basic OS discovery is complete, the user cannot operate any JBOSS discovery. Even though it knows what system you're on, the commands fail. Since you can clearly see the Jboss instance in 'ps' and you can't access it... Permissions issue.

Really not very hard to figure out by reading the log. I've also attached the key snippet you can send to your Unix SA.

 

 

 

Erik

Spoiler

 

 

Operation

Usage description

Objects and parameters

select

Basic Login and Env
Setup

UNIX: echo $SHELL $?
UNIX: uname -a -r
UNIX: locale -a
UNIX: set ComSpec
UNIX: date +%z
Windows: ver
Windows: wmic OS Get CodeSet OS Get
OSLanguage

select

Discover files

Windows: dir <folder_path> /Q /-C /b
"<folder_path>" /b "<file_path>"
UNIX: ls -lA <folder_path>
Windows: attrib <file_path>
Windows: cd /D <file_path>
UNIX: cat <file_path>
UNIX: ps -eo user,pid,lstart,command --cols 2530
--no-headers
UNIX: perl -e
Windows: type <file_path>
Windows: cmd /V:ON /c
Windows: wmic path Win32_Process get
ParentProcessId, commandLine, creationdate,
executablepath, name, processId /value

exec

 

dir\ls
type\cat

 

		<CMD>[CDATA&colon; cat /usr/share/jbossas/docs/licenses/licenses.xml ; echo ERROR_CODE:$?]</CMD>
		<RESULT>[CDATA&colon; cat: /usr/share/jbossas/docs/licenses/licenses.xml: No such file or directory
effectualsystems.com
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: JEE Jboss by Shell Discovery

Hello Erik, 

 

Thank you very much for your reply. I asked our unix admin to temporarily give root acces to the discovery account.

 

He informed me that this user allready was a member of the Jboss admin group. Shouldn't this be enough?

 

What I also noticed is this strange path in the communication log. I assume this is a bug. What do yo think?

 

d:\hp\UCMDB\DataFlowProbe\bin/host-slave.xml" ; echo ERROR_CODE:$?]</CMD>

 

Regards,

 

Martijn Krop.

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: JEE Jboss by Shell Discovery

Today we ran this discovery using the root account and we got exactly the same results. I think this is not related to a permissions issue. 

 

Regards,

 

Martijn Krop.

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: JEE Jboss by Shell Discovery

I created a Service Request for this issue:  4648352608 (SD00761289)

 

Please continue to deliver support through this forum. It is highly appreciated. 

 

Warm regards,

 

Martijn Krop.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.