We are trying to get besclient logs from endpoint to BigFix server by using archive manager. Archive manager is uploading from endpoint when I check the besclient logs on endpoint. But I did not get those files on BigFix server.
Can someone help to identify the issue.
-Venkatraj Jirra
How are you looking for the logs?
The files get hosted on the main server in the BESRelay\UploadManagerData\BufferDir\sha1\xy#####
xy are the last 2 digits of the computer id, the second set of ##### is the computer id.
@fermt We have verified the bes client logs on endpoint. where it has picked the mentioned files for upload.
Files are not available on mentioned sha1 folder.
It could be that the files on the client are too large for the Archive Manager to upload. There’s a setting on the root BES server to extend the archive manager upload cache. You’ll want to review the following articles in the BigFix KB.
Hi All,
I know it’s a old link. But we are trying to use archive manager the same way to retrieve the log file from a server. And it works.The problem is,
When the actions get posted simultaneously for the same target, we miss one log file as it is getting replaced.
every time we post an action to a server( say A), it replaces the old log file present in sha1/ComputerID/ folder.
any help on this might be very useful.
Thanks in Advance!
You’ve revived several old threads with this question which will make it difficult foe you to get a proper response.
But I think you already know the answer. You will need to create a unique archive manager set for each set of logs you want to preserve.
Allow me to be a sophomore here.
I’m using BES file that has actions to perform and archive manager command to retrieve the outputs of those through REST API.
Should I write a separate command for it[ unique archive manager] in my BES file?
If by doing so, it will leave the /sha1 folder to permanently have that log file. am I right?
and will it[creating unique AM] have any effects on overall performance of Bigfix?
You’re right. But this is the closest thread I’ve found “relevant” to my need. pun intended
Yes, I suppose you would need to do all that. Archive Manager really isn’t intended to be used this way, so you are hitting edge cases.
Another method that I prefer to use (assuming the log / output files are small enough) is to create an Analysis to read the log content and report it back, then delete or deactivate the analysis when I’m finished.