Ladeay Absent Member.
Absent Member.
582 views

ESM Service Restarting


Hi All,

I just installed the Arcsight ESM 5.2 software on a solaris box but after checking the logs i realize that it gives the following error:

port 1777 already in use, using port 32000 instaed

JVM exited while starting the application.

There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.

<-- wrapper stopped

Does anybody know what caused it and how I can rectify this?

Thank you so much.

Lolade

Labels (1)
0 Likes
Reply
14 Replies
Acclaimed Contributor.. Volker Michels Acclaimed Contributor..
Acclaimed Contributor..

Re: ESM Service Restarting

Hello Lolade,

the error you mentioned is not the reason why the wrapper stopped, this is more or less normal.

Please check the server.std.log and server.log for the real reason, normally it tells you what the issue is.

Volker

0 Likes
Reply
Ladeay Absent Member.
Absent Member.

Re: ESM Service Restarting

Hi Volker,

Can I send you the logs? Pleaseeeeeee incase I'm missing something

0 Likes
Reply
or@we-can.co.il1 Absent Member.
Absent Member.

Re: ESM Service Restarting

Hello,

The problem is probably memory related, upload the logs and i'll have look

0 Likes
Reply
Acclaimed Contributor.. Volker Michels Acclaimed Contributor..
Acclaimed Contributor..

Re: ESM Service Restarting

Hello Lolade,

of course you can but maybe you want to find out yourself

Login to the manager and check that no ArcSight process is running with "ps -ef |grep arc" otherwise kill the running processes.

Start the manager with the startup script and "tail -f" the server.std.log and follwo what is happening there. You will see things like database connection initilalized successfully etc. and I bet you will find the issue.

Volker

0 Likes
Reply
Acclaimed Contributor.. Volker Michels Acclaimed Contributor..
Acclaimed Contributor..

Re: ESM Service Restarting

... a "top" from the server might be also usefull, of course.

0 Likes
Reply
Ladeay Absent Member.
Absent Member.

Re: ESM Service Restarting

Hi Volker/Cohen

Thanks for your replies. I looked at the log on found out what the problem was, the db version check was "error" and i had to disable the check in the server.properties file. Will have to find a way to downgrade it to the supported version.

Thanks Again!!!!!!!

0 Likes
Reply
Acclaimed Contributor.. Volker Michels Acclaimed Contributor..
Acclaimed Contributor..

Re: ESM Service Restarting

Hello,

we had the same issue and had also to downgrade our db version.

Volker

0 Likes
Reply
Ladeay Absent Member.
Absent Member.

Re: ESM Service Restarting

Ohk.

I have to advise the client to downgrade. Thanks a lot Volker. I do appreciate your help

0 Likes
Reply
or@we-can.co.il1 Absent Member.
Absent Member.

Re: ESM Service Restarting

Hi,

So your problem is communication between the Manager and DB?

If so, there is a known issue that the DB rejects connections because of the 'sqlnet.ora' in the database.

If you'll upload the logs I can have look and see if that's the case.


0 Likes
Reply
Ladeay Absent Member.
Absent Member.

Re: ESM Service Restarting

Hi Cohen,

Do I upload the manager logs alone?

0 Likes
Reply
Highlighted
or@we-can.co.il1 Absent Member.
Absent Member.

Re: ESM Service Restarting

server.log and server.std.log

0 Likes
Reply
Acclaimed Contributor.. Volker Michels Acclaimed Contributor..
Acclaimed Contributor..

Re: ESM Service Restarting

Hello,

why do you need the logs?

The startup shows the issue, the db version is not right thus they have tgo downgrade the db to the supported version.

Volker

0 Likes
Reply
or@we-can.co.il1 Absent Member.
Absent Member.

Re: ESM Service Restarting

According to the described above the DB version check results is 'error', not a different version.

The question is which error is that and that is why the logs are needed.

0 Likes
Reply
Acclaimed Contributor.. Volker Michels Acclaimed Contributor..
Acclaimed Contributor..

Re: ESM Service Restarting

Hi Volker/Cohen

Thanks for your replies. I looked at the log on found out what the problem was, the db version check was "error" and i had to disable the check in the server.properties file. Will have to find a way to downgrade it to the supported version.

Thanks Again!!!!!!!

The error was db version check

0 Likes
Reply
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.