Fedora-version of sysmonforlinux is failing (made for RHEL 8?)
@MarioHewardt 已经在做这个了。
开始于 2025年4月2日。
评估
这个 Issue 还没有评估数据。
描述
Describe the issue
We are using https://packages.microsoft.com/fedora/41/prod/ as source for among other packes, fetching sysmonforliux. This program is failing on an actual Fedora 41 Linux machine. The rpm package has actually an «.el8» postfix, hinting this was made under RHEL 8. When fetching a "rhel/9/" version - the same apply with an extension of «.el8», but this will actually run OK on a RHEL 9 machine.
Originally title:
«sysmonforlinux at packages.microsoft.com/fedora/41/prod/Packages/s/ is made for RHEL 8»
at:
https://github.com/microsoft/linux-package-repositories/issues/211
When did the issue occur?
2025-04-01 (This is NOT a «april fools day» ticket ;-)
If applicable, what package did you attempt to install, and from which repo?
sysmonforlinux from this repo:
https://packages.microsoft.com/fedora/41/prod/Packages/s/
Steps to Reproduce
- Start with a «vanilla» Fedora 41
- Log in as root
- wget https://packages.microsoft.com/fedora/41/prod/Packages/s/
- grep sysmon index.html
- wget https://packages.microsoft.com/fedora/41/prod/Packages/s/sysmonforlinux-1.3.5-0.el8.x86_64.rpm
- dnf install -y sysmonforlinux-1.3.5-0.el8.x86_64.rpm
- systemctl status sysmon.service
- systemctl restart sysmon.service
- systemctl status sysmon.service
Actual Result
~ $ ssh hostwithfedora systemctl start sysmon.service
Job for sysmon.service failed because the control process exited with error code.
See "systemctl status sysmon.service" and "journalctl -xeu sysmon.service" for details.
~ $
~ $
~ $ ssh hostwithfedora journalctl -xeu sysmon.service
Apr 01 04:28:16 hostwithfedora systemd[1]: sysmon.service: Control process exited, code=exited, status=12/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit sysmon.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 12.
Apr 01 04:28:16 hostwithfedora systemd[1]: sysmon.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit sysmon.service has entered the 'failed' state with result 'exit-code'.
Apr 01 04:28:16 hostwithfedora systemd[1]: Failed to start sysmon.service - Sysmon event logger.
░░ Subject: A start job for unit sysmon.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sysmon.service has finished with a failure.
░░
░░ The job identifier is 1192376 and the job result is failed.
Apr 01 04:28:16 hostwithfedora systemd[1]: sysmon.service: Consumed 313ms CPU time, 96.5M memory peak.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit sysmon.service completed and consumed the indicated resources.
Apr 01 04:28:26 hostwithfedora systemd[1]: sysmon.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit sysmon.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Apr 01 04:28:26 hostwithfedora systemd[1]: sysmon.service: Start request repeated too quickly.
Apr 01 04:28:26 hostwithfedora systemd[1]: sysmon.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Expected Result
The sysmon service should have started flawlessly
Screenshots
Additional context
The solution might be to compile the sysmonforlinux on a Fedora 41 platform, and build the rpm from there.
Note:
Fedora 42 is coming quite soon (04/24/2025 ?) and is already available as Beta, so please make a working sysmonforlinux for:
- RHEL 9
- Fedora 41
- Fedora 42
- also soon to be release: RHEL 10
- 主要语言
- C
- 星标
- 2.2k
- 派生
- 222
- 平均合并
- 4 小时 50 分钟
- 30 天内合并 PR
- 3
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/Sysmon-Linux 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 68/100
microsoft/Sysmon-Linux#253 ·
-
难度 3/5 1-2 天 新手友好度 72/100
microsoft/Sysmon-Linux#252 ·
-
难度 3/5 1-2 天 新手友好度 55/100
microsoft/Sysmon-Linux#247 ·
-
难度 1/5 1 小时以内 新手友好度 12/100
microsoft/Sysmon-Linux#246 · 3 条评论 ·
-
Sysmon service executable remains `(deleted)` after restart, causing repeated needrestart restarts and systemd start-limit-hit可能重新可做 @MarioHewardt 于 31 天前认领,目前没有进行中的 PR。 未关闭
microsoft/Sysmon-Linux#244 · 已指派 1 人 ·
查看 microsoft/Sysmon-Linux 的全部 Issue
相似的 Issue
-
enhancement good first issue help wanted
难度 2/5 1-3 小时 新手友好度 82/100
-
bug multiplayer status: planned
难度 2/5 1-3 小时 新手友好度 67/100
ChupathingyCE/chupathingyce#851 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 73/100
HigherOrderCO/Bend#2104 ·
-
research-radar
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
good first issue help wanted program
难度 2/5 1-3 小时 新手友好度 83/100
hffgzktbcc-blip/ounce-core#297 ·
维护者通常 1 天内回复