-
Notifications
You must be signed in to change notification settings - Fork 100
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
Stuck on Queued #218
Comments
Hi @ralghamdi sorry for the delay in replying. When you run TRAM locally, you need to run this command in a separate tab:
That will run a background job that processes the reports. Please note that the BERT model is a bit slow when running on CPU (a few minutes per report) but the background process will display something in the logs when it starts processing a report. |
Hello @mehaase. But when you run the tram pipeline run --model bert --run-forever & in the new terminal, the files show the Error status. |
Hi @hAnguyen1517. Are you running this locally? Did you download the BERT model? Step 9 in these instructions: https://github.com/center-for-threat-informed-defense/tram/wiki/Developers#developer-setup |
Hello @mehaase . Thank you so much for taking the time to respond to my question. Yes, I am running tram locally using VS Code. I downloaded the BERT model and completed everything in step 9 as well. But it still won't work, and we are having issues loading and processing in the queue; I wonder if others are having the same issues. |
Can you please check that the following files exist in your installation and are approximately correct file size?
|
I have installed TRAM locally, and have uploaded three different reports to be analyzed. It has been almost 2 hours for the newest one of them and they all still have the status of Queued as shown below:
I've been monitoring logs of the container with no indication of progress or errors.
The text was updated successfully, but these errors were encountered: