Project

General

Profile

Actions

Bug #4288

closed

inetd is missed by check_mk

Added by Holger Hampel almost 10 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
check_mk
Target version:
-
Start date:
01/25/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.2.x
Affected Plus Version:
Affected Architecture:

Description

When installing or configuring the package I get in the system log:

php-fpm74859: /rc.start_packages: The command '/etc/rc.d/inetd restart' returned exit code '127', the output was '/etc/rc.d/inetd: not found'

There's no open socket on configured port.

As far as I know from Linux, the check_mk-agent is started by (x)inetd. In 2.1 it was working.

Actions #1

Updated by Holger Hampel almost 10 years ago

inetd is running - but the standard start script is missing.

Also the check_mk config goes to /etc/inetd.conf - the running process uses /var/etc/inetd.conf.

inetd seems to be started by /etc/inc/filter.inc and there is also a hard coded "-a 127.0.0.1"

Actions #2

Updated by Kill Bill about 9 years ago

This is completely broken on pfSense 2.2.x. Please, test with files from here: https://github.com/doktornotor/pfsense-packages/tree/patch-14/config/checkmk-agent

You will need to replace files manually under /usr/local/pkg, select interface(s), optionally define allowed hosts and save settings. After that, /usr/local/bin/check_mk_agent should be added to /var/etc/inetd.conf, a line added to /etc/services and there's a NAT rule redirecting connections on enabled interfaces to the configured port on localhost.

Kindly report back how that works.

Actions #3

Updated by Kill Bill about 9 years ago

Merged, please test with 0.1.6 and report back. I have no good way to test this, but it cannot be really more broken than it already was. :D

Actions #4

Updated by Chris Buechler about 9 years ago

  • Category set to check_mk
  • Status changed from New to Feedback
  • Affected Version changed from 2.2 to 2.2.x
Actions #5

Updated by Kill Bill about 9 years ago

Ok, managed to get one user (out of the two in total who use this :P) to test it on the forum - looks like it works.

https://forum.pfsense.org/index.php?topic=101759.0

Actions #6

Updated by Chris Buechler about 9 years ago

  • Status changed from Feedback to Resolved

thanks!

Actions #7

Updated by Ph. T about 9 years ago

I still have the following issuse, which seems not to be resolved jet:
- The automatic generated NAT Port-Forwarding-Rule does not work. (NAT-Settings: [x] Disable Outbound NAT rule generation (No Outbound NAT rules))
A manually added port-forwarding-rule works fine (e.g. DEST outside-IP 6556 -> 127.0.0.1 6556).
Sidenote:
- Installing the package with IPv6 only connection will not work as git.mathias.kettner.de seems to have only IPv4.
(Error: check_mk-agent binary file not found. You can manually download it ....)

Actions #8

Updated by Kill Bill about 9 years ago

When you choose to manage NAT manually, then yeah, you need to manage it manually. Fail to see how you imagine to get this resolved in the package.

Actions

Also available in: Atom PDF