View Issue Details

IDProjectCategoryView StatusLast Update
0008032Talerexchangepublic2024-03-07 19:47
Reportersebasjm Assigned ToChristian Grothoff Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeveritytrivialReproducibilityhave not tried
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.9.4Fixed in Version0.9.4 
Summary0008032: repeated information when loggin into journalctl
DescriptionI see repeated info when checking logs using journal, example

journalctl --user -n 10 -u taler-exchange-httpd -f

Jan 02 16:29:13 T480s taler-exchange-httpd[255542]: 2024-01-02T16:29:13.861177-0300 taler-exchange-httpd-255542(378S0QKJNHYQ274MYN7XY3SS6G) INFO Setting /keys 'Expires' header to 'Mon, 01 Jan 2024 00:00:00 GMT' (rekey frequency is 84 days)
Jan 02 16:29:13 T480s taler-exchange-httpd[255542]: 2024-01-02T16:29:13.861568-0300 taler-exchange-httpd-255542(378S0QKJNHYQ274MYN7XY3SS6G) INFO Setting /keys 'Expires' header to 'Mon, 01 Jan 2024 00:00:00 GMT' (rekey frequency is 84 days)
Jan 02 16:29:13 T480s taler-exchange-httpd[255542]: 2024-01-02T16:29:13.861734-0300 taler-exchange-httpd-255542(378S0QKJNHYQ274MYN7XY3SS6G) INFO Creating /keys at cherry pick date vie dic 29 10:49:20 2023


this means that journal is also saving
 * timedate
 * process name (or unit name)
 * PID
 * channel (info, debug)

maybe we can have some config flag to prevent process to send info that is going to be provided by journal? reducing log size and junk
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

sebasjm

2024-01-02 20:20

developer   ~0020816

i know that there is a workaround using `-o cat`, the issue is tracked to reduce log traffic

Christian Grothoff

2024-01-08 15:29

manager   ~0020827

Fix committed to master branch.

Christian Grothoff

2024-01-08 15:30

manager   ~0020828

Technically fixed in GNUnet 42fb665c0..ad90694ec.

Issue History

Date ModifiedUsernameFieldChange
2024-01-02 20:19sebasjmNew Issue
2024-01-02 20:19sebasjmStatusnew => assigned
2024-01-02 20:19sebasjmAssigned To => Christian Grothoff
2024-01-02 20:20sebasjmNote Added: 0020816
2024-01-02 22:49Christian GrothoffSeverityminor => trivial
2024-01-02 22:49Christian GrothoffStatusassigned => acknowledged
2024-01-08 15:29Christian Grothoff
2024-01-08 15:29Christian GrothoffNote Added: 0020827
2024-01-08 15:29Christian GrothoffStatusacknowledged => informing
2024-01-08 15:29Christian GrothoffResolutionopen => fixed
2024-01-08 15:30Christian GrothoffFixed in Version => 0.9.4
2024-01-08 15:30Christian GrothoffTarget Versionpost-1.0 => 0.9.4
2024-01-08 15:30Christian GrothoffNote Added: 0020828
2024-03-07 19:47Christian GrothoffStatusinforming => closed