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

PacketSniffer: Incomplete trace in case of a SIGTERM #575

Open
FaHaGit opened this issue Mar 5, 2024 · 0 comments
Open

PacketSniffer: Incomplete trace in case of a SIGTERM #575

FaHaGit opened this issue Mar 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@FaHaGit
Copy link
Contributor

FaHaGit commented Mar 5, 2024

Environment:
everest-core:
3e5c467

Test Sequence:

  • Start a trace
  • Restart everest while a high-level communication session is running

Expected Behavior:
In case of a SIGTERM the modul should stop recording immediately and write the pcap file completely. There should be no error message in the log of EVerest.

Observed Behavior:

Currently the traces are incomplete in case of a unexpected EVerest restart trough a SIGTERM. This is quite annoying when trying to analyze an unexpected restart of EVerest

Additional note:

Furthermore, an error message seems to appear in the log after every v2g charging session

Feb 01 10:03:11 tarragon manager[2951]: 2024-02-01 10:03:11.640330 [ERRO] packet_sniffer: void module::PacketSniffer::capture(const string&, const string&) :: Error reading packets from interface: eth1, error:

@FaHaGit FaHaGit added the bug Something isn't working label Mar 5, 2024
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

No branches or pull requests

1 participant