Skip to content

Error processing fallback_error.log #166

@pucherot

Description

@pucherot

When running npm with a custom user:

enviroment:
  - PUID=1000
  - PGID=1000

Warn occur when processing the nginx.conf file, and this warn is logged at fallback_error.log:

2023/10/02 19:47:29 [warn] 158#158: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:4

goaccess attempts to process these warns as access errors, but the format of the line is not as expected.

The goaccess container log shows:

2023-10-11T10:09:10.044154270Z ==338== GoAccess - version 1.7.2 - Sep  9 2023 16:25:50
2023-10-11T10:09:10.044172641Z ==338== Config file: /goaccess-config/error/goaccess.conf
2023-10-11T10:09:10.044186567Z ==338== https://goaccess.io - <hello@goaccess.io>
2023-10-11T10:09:10.044200400Z ==338== Released under the MIT License.
2023-10-11T10:09:10.044213918Z ==338==
2023-10-11T10:09:10.044250900Z ==338== FILE: /opt/log/fallback_error.log
2023-10-11T10:09:10.044265067Z ==338== Parsed 10 lines producing the following errors:
2023-10-11T10:09:10.044278770Z ==338==
2023-10-11T10:09:10.044292381Z ==338== IPv4/6 is required.
2023-10-11T10:09:10.044328770Z ==338== IPv4/6 is required.
2023-10-11T10:09:10.044344196Z ==338== IPv4/6 is required.
2023-10-11T10:09:10.044357733Z ==338== IPv4/6 is required.
2023-10-11T10:09:10.044418011Z ==338== IPv4/6 is required.
2023-10-11T10:09:10.044437696Z ==338== IPv4/6 is required.
2023-10-11T10:09:10.044451474Z ==338== IPv4/6 is required.
2023-10-11T10:09:10.044465048Z ==338== IPv4/6 is required.
2023-10-11T10:09:10.044503974Z ==338== IPv4/6 is required.
2023-10-11T10:09:10.044518845Z ==338== IPv4/6 is required.

I think goaccess should filter fallback_error.log files

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions