Bug 295864 - sysutils/goaccess: failed to start goaccess
Summary: sysutils/goaccess: failed to start goaccess
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Adam Weinberger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-06-05 04:56 UTC by Matt Anton
Modified: 2026-06-08 10:49 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (adamw)


Attachments
goaccess.in patch (1.64 KB, patch)
2026-06-05 04:56 UTC, Matt Anton
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Anton 2026-06-05 04:56:21 UTC
Created attachment 271502 [details]
goaccess.in patch

Hello,

An error was thrown when starting up goaccess:

# service goaccess start
Starting goaccess.

GoAccess - version 1.10.2 - Jun  5 2026 05:45:07
Config file: /usr/local/etc/goaccess/goaccess.conf

Fatal error has occurred
Error occurred at: src/goaccess.c - initializer - 1714
No input data was provided nor was there data to restore.

/usr/local/etc/rc.d/goaccess: WARNING: failed to start goaccess

Had to rewrite the /usr/local/etc/rc.d/goaccess to be able to (re)start/stop the service.
Comment 1 Adam Weinberger freebsd_committer freebsd_triage 2026-06-05 15:38:54 UTC
Why submit a patch that:

- Hardcodes paths (never allowed)
- Makes numerous NOOP changes to variables (ex. $name -> ${name})
- Makes numerous NOOP changes to strings (ex. NO -> "NO")
- Does NOOP shuffling of CLI arguments
- Removes guards

This is a 60-line patch to add one argument to one command.
Comment 2 Matt Anton 2026-06-08 10:49:20 UTC
Hello Adam,
Thank you for checking this so switfly.

I understand that naming the attachment as such was not relevant, my bad.

As I haven't write any rc.d, I submitted a working one that avoid the error I'm facing in hope someone can fix the observed issue with the rc.d provided by this port.

Best regards