Log collector error from columbus

%3CLINGO-SUB%20id%3D%22lingo-sub-1160704%22%20slang%3D%22en-US%22%3ELog%20collector%20error%20from%20columbus%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1160704%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20seen%20the%20following%20error%20with%20columbus%20in%20the%20log%20collector%20Docker%20container%3F%26nbsp%3B%20If%20so%20how%20can%20this%20be%20corrected%3F%3C%2FP%3E%3CP%3E2020-02-07%2021%3A07%3A10.778%20ERROR%20c.a.columbus.runners.MainRunner%20KeepAliveLogTask%20-%20Failed%20reporting%20collector%20status.%20report%3A%20%7BsleepStartTime%3D0%2C%20state%3D0%2C%20freeSpaceMB%3D244094%2C%20freeSpacePercentage%3D94%7D%3CBR%20%2F%3Ejava.lang.RuntimeException%3A%20Failed%20issuing%20HTTP%20request%20to%20'%3CA%20href%3D%22https%3A%2F%2Fconsole.adallom.com%3A443%2Fapi%2Fv1%2Fdiscovery%2Freport_status%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fconsole.adallom.com%3A443%2Fapi%2Fv1%2Fdiscovery%2Freport_status%2F%3C%2FA%3E'%20with%20status%20code%20301%20(Moved%20Permanently)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%26nbsp%3B%3C%2FP%3E%3CP%3E~Michael%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1160704%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECloud%20App%20Security%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Collector%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1239444%22%20slang%3D%22en-US%22%3ERe%3A%20Log%20collector%20error%20from%20columbus%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1239444%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324973%22%20target%3D%22_blank%22%3E%40mlmcadams%3C%2FA%3E%26nbsp%3BHi!%20Could%20you%20try%20these%20two%20options%20%26amp%3B%20see%20if%20they%20work%20for%20you%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%3E%0A%3CUL%3E%0A%3CLI%20value%3D%222%22%3EThe%20error%20code%20301%20at%20the%20end%20references%20permanent%20URL%20redirection%2C%20meaning%20current%20links%20or%20records%20using%20the%20URL%20that%20the%20response%20is%20received%20for%20should%20be%20updated.%3C%2FLI%3E%0A%3CLI%20value%3D%221%22%3ECheck%20log%20collector%20version%20make%20sure%20it%20TLS%201.2%2B%2C%20you%20can%20check%20by%20running%20the%20following%20command%20prompt%3A%3CBR%20%2F%3Edocker%20exec%20-it%20%3CLOGCOLLECTORNAME%3E%20ls%20-l%20%2Fetc%2Fadallom%2Fcomponents%2Fcolumbus%2Fcolumbus.jar%3C%2FLOGCOLLECTORNAME%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Highlighted
Senior Member

Anyone seen the following error with columbus in the log collector Docker container?  If so how can this be corrected?

2020-02-07 21:07:10.778 ERROR c.a.columbus.runners.MainRunner KeepAliveLogTask - Failed reporting collector status. report: {sleepStartTime=0, state=0, freeSpaceMB=244094, freeSpacePercentage=94}
java.lang.RuntimeException: Failed issuing HTTP request to 'https://console.adallom.com:443/api/v1/discovery/report_status/' with status code 301 (Moved Permanently)

 

Thanks 

~Michael

1 Reply
Highlighted

@mlmcadams Hi! Could you try these two options & see if they work for you?

 

  • The error code 301 at the end references permanent URL redirection, meaning current links or records using the URL that the response is received for should be updated.
  • Check log collector version make sure it TLS 1.2+, you can check by running the following command prompt:
    docker exec -it <LogCollectorName> ls -l /etc/adallom/components/columbus/columbus.jar