Cron Hunts don't run in HEAD about grr HOT 8 CLOSED

I am able to create/run cron hunts on HEAD, but I have slightly different issues. (MySQL, separate processes for each role)

1. On a host under Manage Launched Flows any flow that was launched by the Cron Hunt has a blank "Results" tab.
2. On Cron Job Viewer when clicking on a flow I get a popup with flow data, but on the Cron Hunt it shows each flow it has created, but each one expands into a sub list of all the flows, which expand into a list of all flows, which expands.... turtles all the way down.
3. I was able to verify that the Cron Hunt is getting data back by viewing the flows in the Hunt Manager by toggling display of automatic flows and clicking on the results tab there.

from grr.

Hi Darren,
This log trace looks fine to me. I cant see the screenshot but essentially the cron manager has to start a hunt via the SUID flow CreateGenericHuntFlow. It needs to do this because it has to make sure the original creator is propagated though the audit logs. This looks fine the hunt is created.

Pidydx, the blank results tab is expected too - when a flow is run under a hunt it passes its results to the parent rather than keeping it itself (this makes sense otherwise we end up with multiple copies of the same results for all child flows).

I am not sure about the UI bug you describe I will have a look.

Thanks
Michael.

from grr.

Michael,
Yeah, I chatted with Greg about this a bit and it sounds like it is just some unclear UX stuff rather than anything under the hood going wrong. Thanks!

Sean

from grr.

I experienced the UI problem:

Go to cronjob viewer, click flows tab, expand any of the flows. It seems to duplicate the flow in the table every time it pops the modal to show the flow details. If you keep expanding you keep getting new identical flow entries in the table. If you refresh the pane they all disappear.

I couldn't reproduce hunts being created but getting stuck in the paused state. However I ran on a dev internal db without approvals in place, maybe that makes a difference. In my case the hunt got created, was visible after clicking the robot icon, got scheduled on clients, and reported results.

@darrenbilby your hunt didn't get created at all? My worker output looks the same.

@chris maybe run your worker in --verbose mode to look for some more clues.

from grr.

This is what I see in the hunt manager after clicking the "show automated hunts" button. It's creating a new hunt every hour but the hunt doesn't appear to start. If I manually click start on a hunt it runs just fine but obviously that is not desirable for something that is intended to be automated. I'll try to get some verbose worker logs and see if that adds any clues.

from grr.

Just to make sure. We have fixed this issue recently so are you running the
latest grr git head or the last stable server build?
Am 10.11.2014 22:08 schrieb "Christopher Anderson" <[email protected]

:

This is what I see in the hunt manager after clicking the "show automated
hunts" button. It's creating a new hunt every hour but the hunt doesn't
appear to start. If I manually click start on a hunt it runs just fine but
obviously that is not desirable for something that is intended to be
automated. I'll try to get some verbose worker logs and see if that adds
any clues.

[image: screen shot 2014-11-10 at 1 04 37 pm]
https://cloud.githubusercontent.com/assets/5566454/4983737/4f212fbc-691d-11e4-92fd-4d8a5c51e713.png

—
Reply to this email directly or view it on GitHub
#48 (comment).

from grr.

I'm a few commits back. I haven't had a chance to test with the latest server build yet. I should be able to on Monday.

from grr.

I pushed a fix for this a while ago so this should work now. Please reopen if the problems persist...

from grr.