Debian installs icinga2 packages versioned 2.6.0-2 and icingaweb2
packages versioned 2.4.1-1
I did read the docs from icinga.com and used them as a guide for the
install as well. I used the howtoforge because it was specific to the
Debian packaging. Debian sometimes structures their installations
differently than the upstream packagers, and puts different files in
different places, particularly compared to RH installations.
I set the max_response_time and max_execution_time to 300 as
reccommended. I added the lines to enable opcache, but I've tried
commenting those out with no change.
I will go back over the icinga.com docs and see if I can sort what I
might have missed from what's different if you're not pulling from git.
From the fact that I'm getting alerts, I infer that Debian sets up
localhost monitoring to some extent - I haven't actually configured any
hosts or alerts for it.
I infer that the basic incinga2 setup is correct, but as you say
something's off with the PHP, but it seems strange that I've had no
trouble with WordPress on the same server.
I'm going to try the debmon packages.
---
Jonathan
On 2017-12-24 15:15, Antony Stone wrote:
On Sunday 24 December 2017 at 21:59:21, Jonathan Hutchins wrote:
Thanks for the quick reply!
I'm using the docs at
https://www.howtoforge.com/tutorial/how-to-install-icinga2-on-debian-9/
Hm, dated November 16 2017, so it *should* be reasonably current...
That seems to go into incredible detail regarding Apache and MySQL.
Have you
compared the steps there with the Icinga2 docs at
https://www.icinga.com/docs/icinga2/latest/doc/02-getting-started/
and
https://www.icinga.com/docs/icingaweb2/latest/doc/02-Installation/
which focus far more on the Icinga2 parts, and only cover the bare
essentials
for Apache and MySQL?
and installing the icinga2 packages from the official Debian Stable
repository.
What version does that offer to install?
I've never set up Icinga from the official Debian repos; I've only used
debmon
to make sure I'm a bit more up to date.
I've skipped some of the steps because the server is already up and
running several web sites, including the working WordPress site. All
of
the configuration steps appear to have gone as expected. I have
created
the authentication token.
Okay, sounds good.
In /etc/apache2/conf-available/icingaweb2.conf I've added Alias lines
for "/icinga" and "/nagios" for convenience:
Alias /icingaweb2 "/usr/share/icingaweb2/public"
Alias /icinga "/usr/share/icingaweb2/public"
Alias /nagios "/usr/share/icingaweb2/public"
Well, not necessary, but it's up to you what URLs you want to use :)
I'm getting alerts about the server from icinga via email (nightly
maintenance, down when I have it off-line).
Eh?
So, you mean it's working?
And yet you haven't finished the configuration?
Or are you just saying that you've configured everything in Icinga2,
but it's
just the web interface which is not going right?
Relevant log lines only appear to be in the access.log:
eponasgrove.com:80 2605:a601:437:3c01:21f:d0ff:fe5d:4211 - -
[24/Dec/2017:14:44:32 -0600] "GET /icinga/ HTTP/1.1" 302 246 "-"
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko)
Chrome/63.0.3239.108 Safari/537.36"
So, an HTTP 302 redirect response of 246 bytes...
eponasgrove.com:80 2605:a601:437:3c01:21f:d0ff:fe5d:4211 - -
[24/Dec/2017:14:44:32 -0600] "GET /icinga/authentication/login
HTTP/1.1"
200 202 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36
(KHTML,
like Gecko) Chrome/63.0.3239.108 Safari/537.36"
...followed by an HTTP 200 OK response, of only 202 bytes!?
Methinks something's not quite right with your PHP setup.
I suggest you carefully check anything to do with PHP in the docs you
followed, and the links I posted at the top of this reply, to see if
there's
something missing.
Antony.
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
