ESM Service Restarting

[Ladeay]

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

[Volker Michels]

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

[Ladeay]

Hi Volker,

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

[or@we-can.co.il1]

Hello,

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

[Volker Michels]

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

[Volker Michels]

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

[Ladeay]

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!!!!!!!

[Volker Michels]

Hello,

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

Volker

[Ladeay]

Ohk.

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

[or@we-can.co.il1]

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.

[Ladeay]

Hi Cohen,

Do I upload the manager logs alone?

[or@we-can.co.il1]

server.log and server.std.log

[Volker Michels]

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

[or@we-can.co.il1]

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.

[Volker Michels]

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