-
Notifications
You must be signed in to change notification settings - Fork 9
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
500 - Internal Server Error #9
Comments
That error suggests that your database stopped at some point. You will probably need to restart your container (you could also try to exec into the container and only start the DB but I'm not sure if that will work).
There seem to be some problems with FACT docker in combination with the OMS plugin / ClamAV. Did it work for you at some point?
This could mean that call to the "linguist" docker container did not work. Did it produce any results at all? Could be another mounting path problem. |
I have not used ClamAV or linguist before and not sure which category they fall in. They may never have worked and I didn't notice. I am guessing ClamAV relates to the "malware scanner" tab and linguist is for the "source code analysis" tab? |
ClamAV is an open source Linux anti-malware scanner and should be used to scan the file when you run the "malware scanner" plugin linguist is a tool that is used internally for the "source code analysis" plugin for determining the (programming) language |
What I meant was: were there any results for the respective plugins? |
Since I have always only run firmware analysis (not source code) I have never looked at the source code analysis tab. I just checked an older firmware analysis and opened a script file
Anytime that I have looked at that, the page returns clean results. Example: |
The web server was running fine for days, then I added a zip of some source code (curl) to test the source code static analysis plugin. I selected all plugin checkmarks.
When I came back a few hours later, the webpage show the error:
The docker logs showed many errors like this:
for a long time leading up to a more fatal error like this:
The error seems to be related to mongodb. It looks like it stopped working at some point because I don't see port 27018 in the
netstat
output anymore.I also see messages like this in the logs
The text was updated successfully, but these errors were encountered: