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

Fresh installed OMD labs stable: check_mk issues #18

Closed
arturmartins opened this issue Dec 2, 2015 · 10 comments
Closed

Fresh installed OMD labs stable: check_mk issues #18

arturmartins opened this issue Dec 2, 2015 · 10 comments

Comments

@arturmartins
Copy link

List of services started:

omd start
Starting influxdb..............OK
Starting Grafana...OK
Starting Nagflux...OK
Starting naemon...OK
Starting dedicated Apache for site testing...OK
Initializing Crontab...OK

Issue: Missing column in DB

screen shot 2015-12-02 at 2 48 40 a m

screen shot 2015-12-02 at 2 47 14 a m

Unable to visualize host/services/hostgroups/etc. Found out that this is a duplicate of #4. This is a fresh server with fresh installed OMD Version 2.10-labs-edition. #### Issue: Missing directories for naemon

screen shot 2015-12-02 at 1 52 01 a m

This makes impossible to create hosts.

Workaround:

mkdir -p /usr/local/var/log/naemon/
mkdir -p /usr/local/var/spool/checkresults
chmod 777 -R /usr/local/var
@Griesbacher
Copy link
Contributor

Both problems lies between neamon and multisite/mk, so maybe their issue trackers are the right place for such issues.

@marblerun
Copy link

The system actually creates a file .../site/tmp/naemon/naemon.cfg, which clearly states on line 2 that the file has been created by OMD. So something in the many config files then referenced below that must be incorrect.

That would also account for it not finding the logfile, as 14 naemon cfg files are referenced to the correct site specific location.

@smarmie
Copy link

smarmie commented Feb 21, 2017

Hi,
I'm having the same issue with a fresh install of omd-2.20-labs-edition=0.ubuntu16.04
However, the workaround is not working.
Thanks.

@sni
Copy link
Contributor

sni commented Feb 21, 2017

You could try the nightly builds, cmk has been updated meanwhile. Or try setting the core to nagios.

@lgwapnitsky
Copy link

Still occurring as of latest stable version

@heinzelrumpel
Copy link

I actually cannot beliefe, that this error has not been fixed and that that there is no fix resp. workarround posted somewhere. Sorry, but what makes it so difficult to include those columns into livestatus installation?

@lausser
Copy link
Contributor

lausser commented Jul 5, 2017

The easiest and quickest way to get this done is to fix it and send us a pull request.
The workaround is not to use check_mk.

@davidedg
Copy link

davidedg commented Oct 1, 2017

I really think this is deliberate - see also comment #4 (comment) - what should you use, if not cmk, for configuring the core, in omd ?
Been trying omd labs for over 2 years, always found it to be utterly broken.

@lausser
Copy link
Contributor

lausser commented Oct 1, 2017

We (at ConSol) do not use check_mk, we do not recommend using check_mk. For everybody who thinks that Nagios is not usable without check_mk:
Go to omdistro.org and turn to the left, there is an OMD maintained by MK himself. If it is free or open source, i don't know.
OMD Labs Edition on the other side, is 100% free and open source. If it would be broken, then it would not be the preferred monitoring tool for several large-scale enterprises. This allows us to make the money necessary to maintain OMD.
Configuration is done by manually editing config files, mostly using templates and hostgroups. Companies which have some sort of CMDB (and most of them have one, instead of letting check_mk doing the inventory of their IT zoo) use Coshsh

@davidedg
Copy link

davidedg commented Oct 1, 2017

Gerhard, thank you for making this clearer.
What I meant by deliberate is just this: omd-lab do contains Check_MK (often older versions), as in RAW edition, but not only it does not work, you are confirming that there's no will to make it work.
I think this might be misleading - why not leave out check_mk from the package if it's broken in the first place?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants