Scanning cannot be completed correctly. #196
Comments
|
Thank you for contributing an issue! Welcome to the EMBA firmware analysis community! We are glad you are here and appreciate your contribution. Please keep in mind our contributing guidelines here and here. If you like EMBA you have the chance to support us by becoming a Sponsor or buying some beer here. This is an automatic message. Allow for time for the EMBA community to be able to read the issue and comment on it. |
|
Is there a firmware we can use to reproduce the issue? |
Sorry, our firmware involves company secrets and cannot be provided to you. I am trying to scan some open-source firmware to reproduce this issue. If reproduced, I will provide it to you. Before that maybe you can try using larger firmware first (according to discussions within our team, this bug are more likely to occur with firmware over 2GB). |
BenediktMKuehne
added
the
can't reproduce
|
I'll make some tests on larger FW-files, but so far I'm unable to reproduce the issue |
|
Something is not OK with large FW scans in EMBArk.
In the console also some error messages:
I am going to wait till monday morning, but even if the test runs, it is likely that the results will not be available under EMBArk. |
|
I have reproduced it through the public binary file.
`logreader.log`
`emba_logs/emba.log`
scanning was finished at
|
|
Thank you, will do some tests |
|
My scan also hangs at 46% with rootfs.ext4, I started it 3 days before. :( |
|
looks like an issue with the f50 read_in working on a fix now |
|
I was able to manually finish the report generation when this happened to me. This may depend on where it times out and where the actual failure happens, but I had the same log output as BenediktMKuehne in the above screenshot. From the Then, I ran the following in the django admin python shell: Which essentially just re-ran the call to embark/embark/uploader/boundedexecutor.py Line 107 in de065c1 embark/embark/uploader/boundedexecutor.py Lines 260 to 264 in de065c1 embark/embark/uploader/boundedexecutor.py Lines 125 to 130 in de065c1 I think (not 100% sure) the actual issue is that the connection to MySQL times out somehow. Hence the error message specifying the embark/embark/porter/importer.py Line 96 in de065c1 I'm not 100% sure of this but something is triggering the exception in |
|
I was able to fix the issue with This can be tested on a shorter cycle by setting the A quick hack is to set the To fix:I added a call to embark/embark/uploader/boundedexecutor.py Lines 91 to 101 in de065c1 After adding that call and re-running analysis on the same firmware that caused the issue, it completed correctly. I am not sure if this is the only place this fix needs to be inserted. It seems like there could be a similar gap in database accesses in the |
|
It would be great to test this with other FWs also.... |
|
All my more days long tests are not available in EMBArk. Maybe this fix solve the issue I hope. |
|
This would be a very useful improvement, because many tests run fine, but the report is inaccessible on EMBArk and you can only copy the results from the file system. |
|
Sorry for the delay, will try to fix within the next week |
|
Can anyone confirm that the issue is fixed? |
Was this fix by https://github.com/BenediktMKuehne/embark/tree/196-scanning-cannot-be-completed-correctly? I will start verification in the next few days. |
|
It's more of a workaround since the underlying issue is somewhere in mysql(/its config) |
|
I tested it,it took about 13h30mins to finish and report is accessible on EMBArk. |
|
Sorry for delay. I have tested https://sourceforge.net/projects/android-x86/files/Release%209.0/android-x86_64-9.0-r2.iso/download (sha256: F7EB8FC56F29AD5432335DC054183ACF086C539F3990F0B6E9FF58BD6DF4604E), it took about 4 day and appears to be working well and has successfully completed the task.
|
Describe the bug
Scanning has finished, but the page is still running. The progress froze and no longer updates.
Larger firmware will trigger this bug more easily.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Scanning end and show reports。
Screenshots
logreader.logincompletewhile
emba_logs/emba.logis completeDesktop (please complete the following information):
Additional context
Now I can export report from
/var/www/emba_logs/ac93bbfe-2d8c-4530-8ba2-8c2cb0320519/emba_logs/html-report/index.html, but that's not a long-term solution.The text was updated successfully, but these errors were encountered: