Endpoint receives data but doesn't appear in console

So we’re doing some testing and getting some odd results. Typically when an active endpoint is removed from the database via console, when that endpoint sends its next post it will recreate a database entry.

I removed a PC from the database but it is not recreating it this time. Checking the logs, it receives and posts data just as normal, but there is no recreated entry. We resolve this by simply gutting the client and registry entries, re install, and it works. But can anyone explain the reasoning behind why it would receive\send data but not actually show in the console at all?

Thanks

I have noticed the same thing.

If I stop the client service, delete the __BESData folder under the client install, and restart the client the system reports to the console again.

Bug?

Have you checked for it under the master operator account? I wonder if it might fail to subscribe to operators…

1 Like

Yes. MO was not able to find device in Console.

We’ve experienced this issue in cases where the relay had 0MB free on the data partition. The clients still download actions and run them but reports never make it back to the server.

I assume you’ve checked the relay status?

1 Like

No, I didn’t check the Relay status, I’ll check it on Monday after I delete a ‘test’ box.
But I don’t think it’s going to be the issue. My Relays use a Relay “cache limit” that is less than the total free disk space. The Relays are not “Shared” so nothing else should be consuming substantial amounts of disk space.

I’ll check the Relays and post again tomorrow.

1 Like

The relays in my environment have plenty of free space.

1 Like

This does seem like a bug.

Any developments and recurrences?

What versions of BigFix clients / relays?


CC: @AlanM

Are you sure that the reports are reaching the DB? Have you checked the FillDB log?