Scans permanently 'pending.'

[thatguy031415]

I stood up the docker (had to make a couple of changes to get it to run) and kicked off a scan, but after over an hour, it still says:

2

Pending

I've not used a functional instance of Rumal before, but Thug certainly wouldn't take this long on its own. Is this a problem you've seen before, or did the docker instance fail to run properly?

[pdelsante]

Are you sure you started both the docker containers needed by Rumal (frontend and backend), by running docker compose? Sounds like you may be entirely missing the backend component.

[thatguy031415]

Yeah, I ran and

The status window currently reads:
frontend_1 | Checking if rumal-http is still alive
frontend_1 | Checking if rumal-fdaemon is still alive
frontend_1 | Checking if rumal-enrich is still alive
backend_1 | Checking if rumal_back-http is still alive
backend_1 | Checking if rumal_back-run_thug is still alive
backend_1 | Checking if rumal_back-consumer is still alive
frontend_1 | Checking if rumal-http is still alive
frontend_1 | Checking if rumal-fdaemon is still alive
frontend_1 | Checking if rumal-enrich is still alive
backend_1 | Checking if rumal_back-http is still alive
backend_1 | Checking if rumal_back-run_thug is still alive
backend_1 | Checking if rumal_back-consumer is still alive
frontend_1 | Checking if rumal-http is still alive
frontend_1 | Checking if rumal-fdaemon is still alive
frontend_1 | Checking if rumal-enrich is still alive
backend_1 | Checking if rumal_back-http is still alive
backend_1 | Checking if rumal_back-run_thug is still alive
backend_1 | Checking if rumal_back-consumer is still alive
frontend_1 | Checking if rumal-http is still alive
frontend_1 | Checking if rumal-fdaemon is still alive
frontend_1 | Checking if rumal-enrich is still alive

[thatguy031415]

I may just need to skip docker and run a full build. I was hoping to save myself some work, as this is currently just a POC for my boss, to see if he wants me to build it out for our first-line analysts.

[pdelsante]

You may simply want to run docker exec -ti backend_1 /bin/bash (while the docker compose is running) and have a look at the logs, it would probably save you some time ;-)

You can also do the same in the frontend, of course.

[Dennisparchkov]

I'm looking into it. Will get back to you with what i find

[Dennisparchkov]

Would you mind elaborating on the changes you made to make it run, and what errors you were getting when building ?

Also, the status of the scan doesn't update when the scan has finished or failed, so you will need to refresh the page. This is a know issue.

It seems weird that the scan is stuck on "pending" as we have a whole lot of logic and timeouts so that scans never stay in that state (they either go to fail or timeout).

I'v tested the docker instance and it works for me. Are you running it on Windows or Linux ?

[morriscode]

Mines stuck pending also. Ubuntu server 14

[pdelsante]

Hello @morriscode, this could be due to a problem we recently had with the unbuffer command we are using here: https://github.com/thugs-rumal/rumal_back/blob/master/main/management/commands/run_thug.py#L349

You may want to attach a shell to the backend docker instance and manually edit the file (comment or remove that line). Please let us know if this works.