Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

filebeat clashes with chkconfig under Rocky Linux 9 (redhat like distrib) #37622

Open
Neurozone opened this issue Jan 12, 2024 · 3 comments
Open
Labels
needs_team Indicates that the issue/PR needs a Team:* label

Comments

@Neurozone
Copy link

Neurozone commented Jan 12, 2024

During its install on Rocky 9, filebeat creates /etc/init.d and drops a file into it.
This is preventing chkconfig from installing correctly.
The package chkconfig expects /etc/init.d not to exist, in order to create a synlink in its place.

This happens on Rocky 9 and leaves the setup in a wrong state, which is reported as an error by 'dnf check'.

The init.d scripts should not be needed for recent Rocky/RHEL versions.

Extract from redhat kb:

The /etc/init.d directory was created in system during the installation of some third-party applications Later on when installing chkconfig package, the system attempts to create a symbolic link /etc/init.d and point to /etc/rc.d/init.d As /etc/init.d/ is already existed as a directory, the installation fails due to unable to create the symbolic link

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 12, 2024
@botelastic
Copy link

botelastic bot commented Jan 12, 2024

This issue doesn't have a Team:<team> label.

@Neurozone
Copy link
Author

Also:

cat /etc/rocky-release && dnf repoquery -l filebeat | grep init
Rocky Linux release 9.2 (Blue Onyx)
Last metadata expiration check: 1:06:50 ago on Fri Jan 12 08:12:01 2024.
/etc/init.d/filebeat
/etc/init.d/filebeat
/etc/init.d/filebeat

@SimonHoenscheid
Copy link

This still seems to be an unsolved problem. We just ran into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

No branches or pull requests

2 participants