Skip to content
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

Close/reopen laptop lid - Brim shows Network error #533

Closed
philrz opened this issue Apr 1, 2020 · 4 comments · Fixed by #739
Closed

Close/reopen laptop lid - Brim shows Network error #533

philrz opened this issue Apr 1, 2020 · 4 comments · Fixed by #739
Assignees
Labels
bug Something isn't working

Comments

@philrz
Copy link
Contributor

philrz commented Apr 1, 2020

This can be considered low priority, as it does not always happen. It's hard to reproduce and may be related to the size of ingested pcaps. Here's a screenshot of one time the problem reproduced:

image

More detail from the user who originally reported it:

When this happened, the ingest process stopped and I had to open file again and start over. I found the same problem when the screen saving/automatic lock of account happened.

@philrz philrz added the bug Something isn't working label Apr 1, 2020
@siskojr
Copy link

siskojr commented Apr 2, 2020

I have tested this issue again with v0.5.4 and still happens.
I can easily reproduce now as follows.

  1. Open big pcap file.
  2. processing packets and progress bar
  3. close lid and open again.
  4. The ingest process stops and shows Network error message.

The errors I get looking at it with Developer tools are:

  1. Failed to load resource: the server responded with a status of 400 (Bad Request)
  2. Failed to load resource: net::ERR_NETWORK_IO_SUSPENDED
  3. /Applications/Brim.app/Contents/Resources/app/dist/js/services/zealot/fetcher.js:218 POST http://localhost:9867/space/wrc12x.pcap.brim/packet net::ERR_NETWORK_IO_SUSPENDED 202 (Accepted)

image

I can see how the zeek process does not show in the system after this error.

@philrz
Copy link
Contributor Author

philrz commented May 1, 2020

Scope of this has been narrowed to simply improve the error message.

@siskojr
Copy link

siskojr commented May 1, 2020

Good call.
I could reproduce if inactivity timer kicked in during an ingest.
But as a user installed the tool amphetamine ‎Amphetamine on the Mac App Store
https://apps.apple.com › app › amphetamine so that issue did not happen.

Thanks

@philrz
Copy link
Contributor Author

philrz commented May 5, 2020

Verified in Brim commit 8f8df0c talking to zqd commit 335d284. Following the original repro instructions, I closed the lid of my laptop during pcap import and it triggered the new error message.

image

Thanks @jameskerr!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants