Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collector does not always complete #52

Closed
McBartok opened this issue Jun 14, 2023 · 2 comments
Closed

Collector does not always complete #52

McBartok opened this issue Jun 14, 2023 · 2 comments

Comments

@McBartok
Copy link

When running SharpHound it does not always complete. Perhaps something in the formatting of the object or similar prevents the collector from completing, not sure where to continue debugging as the iIssue will persist across multiple runs, but then go away after a day or two. The below is a short snipper from the logs of how its gets stuck.

2023-06-13T11:14:21.1899097+02:00|INFORMATION|Status: 40641 objects finished (+0 2.383217)/s -- Using 197 MB RAM
2023-06-13T11:14:51.2089165+02:00|INFORMATION|Status: 40641 objects finished (+0 2.379032)/s -- Using 197 MB RAM
2023-06-13T11:15:21.2265545+02:00|INFORMATION|Status: 40641 objects finished (+0 2.374861)/s -- Using 197 MB RAM
2023-06-13T11:15:51.2484637+02:00|INFORMATION|Status: 40641 objects finished (+0 2.370705)/s -- Using 197 MB RAM
2023-06-13T11:16:21.2634082+02:00|INFORMATION|Status: 40641 objects finished (+0 2.366564)/s -- Using 197 MB RAM
2023-06-13T11:16:51.2739820+02:00|INFORMATION|Status: 40641 objects finished (+0 2.362437)/s -- Using 197 MB RAM
2023-06-13T11:17:21.2826521+02:00|INFORMATION|Status: 40641 objects finished (+0 2.358324)/s -- Using 197 MB RAM
2023-06-13T11:17:51.3035011+02:00|INFORMATION|Status: 40641 objects finished (+0 2.354226)/s -- Using 197 MB RAM
2023-06-13T11:18:21.3104761+02:00|INFORMATION|Status: 40641 objects finished (+0 2.350142)/s -- Using 197 MB RAM
2023-06-13T11:18:51.3152642+02:00|INFORMATION|Status: 40641 objects finished (+0 2.346072)/s -- Using 197 MB RAM
2023-06-13T11:19:21.3350742+02:00|INFORMATION|Status: 40641 objects finished (+0 2.341881)/s -- Using 197 MB RAM
2023-06-13T11:19:51.3454471+02:00|INFORMATION|Status: 40641 objects finished (+0 2.337839)/s -- Using 197 MB RAM
2023-06-13T11:20:21.3646640+02:00|INFORMATION|Status: 40641 objects finished (+0 2.333812)/s -- Using 197 MB RAM
2023-06-13T11:20:51.3725154+02:00|INFORMATION|Status: 40641 objects finished (+0 2.329798)/s -- Using 197 MB RAM
2023-06-13T11:21:21.3881302+02:00|INFORMATION|Status: 40641 objects finished (+0 2.325798)/s -- Using 197 MB RAM
2023-06-13T11:21:51.4066873+02:00|INFORMATION|Status: 40641 objects finished (+0 2.321812)/s -- Using 197 MB RAM
@rvazarkar
Copy link
Contributor

This is usually the collector stuck on some gargantuan object for a while, every time I've seen this behavior it does eventually complete but it can take ages. I'm not really entirely sure what causes these crazy processing times, so I'm not sure what the best way to fix this is. If you can narrow this down to a particular object causing this, that would be helpful, and we can investigate if theres ways to maybe add a failsafe or something

@StephenHinck
Copy link

Closing issue as no additional information has been provided. Please feel free to re-open if you have anything additional to help us troubleshoot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants