Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Other: Agent logs does not logs timestamp for Fatal error in log

Tushar Sharma User

There is no corresponding timestamps  when F_* error logged into log, so we don't known when its happened 

Timestamps is important for analysis and monitoring.

2023-02-27T07:09:19-05:00: hvragentlistener -d: Warning: W_JC0500: Process encountered termination signal.
2023-02-27T07:09:32-05:00: hvragentlistener -d: Listening on port 7003.
hvrhubserver[w306|ch_nyt_test_poc]: hvrhubserver[w306|ch_nyt_test_poc]: F_JG219A: TLS read error: Protocol violating EOF. This could be a network problem or a fatal error in the child coprocess
F_JC0531: The previous error occurred through a proxy hijack child.F_JG219A: TLS read error: Protocol violating EOF. This could be a network problem or a fatal error in the child coprocess
F_JC0531: The previous error occurred through a proxy hijack child.

hvrhubserver[w306|ch_nyt_test_poc]: hvrhubserver[w306|ch_nyt_test_poc]: F_JG0550: TLS shutdown error: I/O error occurred: Success.F_JG0550: TLS shutdown error: I/O error occurred: Success.

hvrhubserver[w307|ch_nyt_test_poc]: F_JG219A: TLS read error: Protocol violating EOF. This could be a network problem or a fatal error in the child coprocess
F_JC0531: The previous error occurred through a proxy hijack child.
hvrhubserver[w307|ch_nyt_test_poc]: F_JG0550: TLS shutdown error: I/O error occurred: Success.
hvrhubserver[w305|ch_nyt_test_poc]: F_JG219A: TLS read error: Protocol violating EOF. This could be a network problem or a fatal error in the child coprocess
F_JC0531: The previous error occurred through a proxy hijack child.
hvrhubserver[w305|ch_nyt_test_poc]: F_JG0550: TLS shutdown error: I/O error occurred: Success.
hvrhubserver[w328|ch_nyt_test_poc]: F_JG219A: TLS read error: Protocol violating EOF. This could be a network problem or a fatal error in the child coprocess
F_JC0531: The previous error occurred through a proxy hijack child.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Mark Van de Wiel User

    Hi Tushar,

    Thank you for highlighting this issue.

    This quarter we have a project to improve logging for cases like these. We plan to address this issue by the end of January 2024 (our fiscal quarter).

    Your ticket reference is T-583375.

    Thanks again,
    Mark.