You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Environment:
everest-core:
3e5c467
Test Sequence:
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:
The text was updated successfully, but these errors were encountered: