Hello All,
I am getting the following error when trying to add a new linux server to
be monitored.
The error occurs while going through the node wizard.
warning/TlsStream: OpenSSL error: error:14094410:SSL
routines:SSL3_READ_BYTES:sslv3 alert handshake failure
critical/cli: Peer did not present
Hi,
I had the same problem yesterday.
Your client is newer version than the master server, you have to upgrade
the master. I haven't found another solution.
On Wed, Dec 16, 2015 at 12:47 PM Bertalan Voros
wrote:
> Hello All,
>
> I am getting the following error when trying to add a new linux ser
OK, had this suspicion.
Cannot upgrade the server just yet unfortunately.
On Wed, 16 Dec 2015 at 11:56 Martin Stiborský
wrote:
> Hi,
> I had the same problem yesterday.
> Your client is newer version than the master server, you have to upgrade
> the master. I haven't found another solution.
>
>
Hi,
I am using icinga2 but the checkbox for the Feature Commands are NOT checkable.
Not sure what is the cause.
Could someone help? Thanks.
Regards,
Kevin
___
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/list
Am 16.12.2015 um 19:29 schrieb Siwei Zhang:
Hi,
I am using icinga2 but the checkbox for the Feature Commands are NOT
checkable.
Guess you are talking about Icinga Web 2 here.
Not sure what is the cause.
Could someone help? Thanks.
Check if your user has the appropriate permissions to i
Am 16.12.2015 um 12:58 schrieb Bertalan Voros:
OK, had this suspicion.
Cannot upgrade the server just yet unfortunately.
Server and Clients must remain the same major version, especially since
2.4 required API related changes, rendering an old 2.3.x master not to
properly process events from ne
Am 15.12.2015 um 11:52 schrieb Christian Moreno Moreno:
Hi,
we are testing the new API and I have some questions, maybe someone
can help me:
Question 1:
- If I created one host in /etc/icinga2/zones.d/zoneX/* and later I do
one update via API, then the file from /etc/icinga2/zones.d/zoneX/*
ist
Am 15.12.2015 um 02:44 schrieb Madhusmita Gochhait:
Hello All ,
I have a 2 node active-active setup for icinga , with a vip address
which points to these nodes .
For Ex :
icinga1 : icinga-cluster-3.englab.juniper.net
icinga2 :icinga-cluster-5.englab.juniper.net
VIP: icinga-cluster-6.englab.j
Am 14.12.2015 um 13:36 schrieb Jorge Ferrando:
Hello
When we were using nagios the hosts and services shown on the web
interface where those that had the logged in user as a contact.
That's fairly ugly as it requires to (ab)use contacts for notifications
also for web auth.
Is it possible to
Am 24.11.2015 um 12:25 schrieb Daniel Guillermo Bareiro:
Hi,
Hi, Michael. Thanks for your reply.
---
root@icinga2:~# /etc/init.d/icinga2 checkconfig
(...)
information/ConfigItem: Committing config items
critical/config
Am 13.12.2015 um 10:00 schrieb Madhusmita Gochhait:
Hi ,
I am stuck with a issue , where pnp4nagios graph are not getting
displayed .It says "could not load image"
Screenshot?
I see rrd files getting updated frequently with no issues . Cannot
find anything in the logs also . I have pnp4na
Am 11.12.2015 um 13:47 schrieb Jorge Ferrando:
Hi there
Is there any runtime macro to use in the commands that contains the
Icinga server IP address?
No, but what's wrong with using Linux commands >:-)
You might open a feature request, since we already resolve dns with
NodeName if not set by
Am 11.12.2015 um 13:10 schrieb Renato Pinheiro:
Hello,
I have one server with icinga2 + classic ui, and before update for
icinga2 my server
Which update from x to y?
that was icinga show the comments of old schedules
downtimes in Alert History.
Please add a screenshot, I cannot follow.
Ki
Am 08.12.2015 um 07:51 schrieb Ronny Becker:
Hello,
I am searching for a config example to disable all child checks (Host
and Services) if a service is not in "OK" state.
for example:
NET -> Router1 -> Internet -> Router2 -> Switches -> Hosts
Router2 has a ping service. If the rtt is >200ms, th
Hi Michael,
Thanks for your help.
I am not sure how to set the permission for that.
Could you help as well?
Regards,
Siwei
___
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
Michael,
We use HAPROXY and configuration are pasted below for your reference.
Here is the curl command which crashes one of the Icinga api server node - curl
-k -s -u icingaadmin:icinga
'https://192.168.67.4:5665/v1/objects/hostgroup?cascade=1' -H "accept:
application/json" -X DELETE
Regardin
Changed subject line
On 12/16/15, 8:42 PM, "Madhusmita Gochhait" wrote:
>Michael,
>
>We use HAPROXY and configuration are pasted below for your reference.
>Here is the curl command which crashes one of the Icinga api server node -
>curl -k -s -u icingaadmin:icinga
>'https://192.168.67.4:5
Hi,
please do *not* reply to mailing list digests, but the original thread. Ensures
that the reader's mail client may serve the history as thread tree and it is
easier to follow.
> Am 17.12.2015 um 05:43 schrieb Madhusmita Gochhait :
>
> Michael,
>
> We use HAPROXY and configuration are pasted
Am 16.12.2015 um 21:38 schrieb Siwei Zhang
mailto:siwzh...@teslamotors.com>>:
Hi Michael,
Thanks for your help.
I am not sure how to set the permission for that.
Could you help as well?
I'd read the docs and find out about permissions :-)
https://github.com/Icinga/icingaweb2/blob/master/doc/
19 matches
Mail list logo
