Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Error in the log "Failed to convert IP Address"

Updated: 16 Mar 2012 | 5 comments
Milan_T's picture
+2 2 Votes
Login to vote
This issue has been solved. See solution.

During Troubleshooting of SSIM I got this Error from one of the windows server :

" Cannot convert IP address to numeric value. java.lang.IllegalArgumentException: Invalid format of ::ffff:XXX.XXX.XXX.XXX IP address "

I need Solution ASPC.

Comments

Laurent_c's picture
26
Feb
2012
1 Vote +1
Login to vote

Could you give more

Could you give more information ?

Windows machine version you are collecting from ?

Version and name of the Collector ? (Have you run Liveupdate)

Extract from debug log with raw event enabled ? (you can enable raw event in sensor properties)

Avkash K's picture
26
Feb
2012
0 Votes 0
Login to vote

Hi,   Please check the Actual

Hi,

 

Please check the Actual event logs under system.

Does your IP Address field under logs contains data other than normal IP Address format.

 

I have seen some case where some windows boxes start writing unwanted data under IP Address fields, causing this issue.

It will be helpful if you can provide the details asked by Laurent.

Regards,

Avkash K

Milan_T's picture
09
Mar
2012
0 Votes 0
Login to vote

Some details about this issue.

Windows 2008 server.

Version of collector is 4.3

that's it.I can't share more information on this.

TatyanaS's picture
02
Mar
2012
1 Vote +1
Login to vote

There is no collectors with

There is no collectors with version 4.7. I suppose you use SSIM 4.7, but what is the collector's version?

Having that information, I can only say that the the product sends events with IPv6 addresses, but it looks like the collector doesn't support them.

To help you with the issue we need more info - the name of collector at least.

 

-Tatyana

Milan_T's picture
16
Mar
2012
0 Votes 0
Login to vote

this is normal error

I found that this is normal error logs resumed after re-integrating the same server with SSIM.