Project

General

Profile

Actions
Copy link

Feature #18

closed

HOOK-based debug output wrongly appears in the console whereas the binding/service has been started via systemd

Added by Emmanuel Jubera [SAFT] over 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Low
Assignee:
Emmanuel Jubera [SAFT]
Target version:
arz-1.0
Start date:
05/18/2022
Due date:
% Done:

0%

Estimated time:
Hardware platform:
Solidrun (aarch64)
OS Affects Version/s:
arz-1.0
OS Fix Version/s:
Labels:

Description

It would be nice to have "HOOK" logs in the system journal instead of the standard output.

[root@localhost ~]# HOOK: [req-000001:b2r/subscribe] BEGIN uid=0=0 gid=0 pid=116                                                                                                                                                             2 label=System id=System
HOOK: [req-000002:ble-sensor/ciss/POC] BEGIN uid=0=0 gid=0 pid=1162 label=System                                                                                                                                                              id=System
HOOK: [req-000001:b2r/subscribe] subscribe(b2r/B2R_CAN:2) -> 0
HOOK: [req-000001:b2r/subscribe] reply[success: 0]
HOOK: [req-000001:b2r/subscribe] END
Actions
Copy link
 #1

Updated by Yann Bodéré over 2 years ago

  • Assignee changed from Vincent Rubiolo to Marc-Antoine Riou
Actions
Copy link
 #2

Updated by Emmanuel Jubera [SAFT] over 2 years ago

  • Priority changed from Normal to Low

Priority changed from Normal to Low.

Actions
Copy link
 #3

Updated by José Bollo over 2 years ago

Is it possible to have more context? When does it happen? Is there a specific command that produces that output?

Actions
Copy link
 #4

Updated by Vincent Rubiolo over 2 years ago

Based on our discussions with Emmanuel, the issue is that once the binding is launched via the startup scripts, when a request is done on the binding side, the HOOK debug logs appear on the console and not in the systemd journal.

Actions
Copy link
 #5

Updated by Vincent Rubiolo over 2 years ago

  • Subject changed from HOOK logs to HOOK-based debug output wrongly appear in the console whereas the binding/service has been started via systemd
Actions
Copy link
 #6

Updated by Vincent Rubiolo over 2 years ago

  • Subject changed from HOOK-based debug output wrongly appear in the console whereas the binding/service has been started via systemd to HOOK-based debug output wrongly appears in the console whereas the binding/service has been started via systemd
Actions
Copy link
 #7

Updated by José Bollo about 2 years ago

Because it is launched in startup scripts, scripts should be changed to used the command systemd-cat.

Example: afb-binder .... should become systemd-cat --level-prefix=true --identifier=IDENTITY afb-binder ....

Actions
Copy link
 #8

Updated by José Bollo about 2 years ago

  • Status changed from New to Submitter feedback needed
Actions
Copy link
 #9

Updated by Emmanuel Jubera [SAFT] about 2 years ago

  • Status changed from Submitter feedback needed to Resolved

Okay, also HOOK logs appear in the system journal when a service is used to launch the application.

Actions
Copy link
 #10

Updated by Sebastien Douheret [IoT.bzh] about 2 years ago

  • OS Affects Version/s arz-1.0.0 added
Actions
Copy link
 #11

Updated by Sebastien Douheret [IoT.bzh] almost 2 years ago

  • OS Affects Version/s arz-1.0 added
  • OS Affects Version/s deleted (arz-1.0.0)
Actions
Copy link
 #12

Updated by Emmanuel Jubera [SAFT] almost 2 years ago

  • Assignee changed from Marc-Antoine Riou to Emmanuel Jubera [SAFT]
Actions
Copy link
 #13

Updated by Emmanuel Jubera [SAFT] almost 2 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF