2014 Update - Operations Screen Color Scheme

[mberkley]

On the Operations screen the color scheme has changed making it nearly impossible to read alerts.

We thought it was just our installation, but the same issue is happening on your own Demo XI page.
Example:


White on White Text & White on Yellow text difficult. We have this screen on our 84" video wall, and we need to be able to read it. Is there a CSS file that can be modified to correct this?

[slansing]

Thank you for reporting this, I'm going to file a request to get it changed, at least the white on yellow text.

[mberkley]

I've tried different variations of editing the PHP to no avail.
Does someone have some insight how I could modify the CSS to show hyperlinks as Black on the yellow (and more importantly white) backgrounds?

Here is the CSS from the PHP file:

.warning {
background: yellow;
background: -moz-linear-gradient(top center, yellow 50%, #edef00 50%);
color: black;
text-shadow: -1px -1px 0 #feff5f;
}
.critical td,
.ok td,
.warning td {
}
.warning td{
border-bottom: 1px solid #bdbf00;
border-right: 1px solid #bdbf00;
}
.ok td{
border-bottom: 1px solid #016f00;
border-right: 1px solid #016f00;
}

.date {
white-space: nowrap;

}

[mberkley]

NOT GOOD

That update completely rendered our NagiosXI useless. All we have are blank screens. We can still log into the core, but nothing else.
We followed your directions. We uploaded the .zip file. Was there an alternative method of doing this?

Is there any way to undo immediately?

We need to monitor our infrastructure.

[tmcdonald]

Scott is working on this as we speak and we will update you ASAP. Post was deleted to keep anyone else from downloading.

[scottwilkerson]

run

Code: Select all

rm -rf /usr/local/nagiosxi/html/includes/components/opscreen

Sorry about that

Attached is a tested component without the php error....

Truly sorry about that.

[tmcdonald]

Tested working by both myself and sreinhardt. Should be good to go.

[mberkley]

run

Code: Select all

rm -rf /usr/local/nagiosxi/includes/components/opscreen

This method did not work for us, so we simply renamed the folder and we were out of impact. We are testing the new component now.

[mberkley]

Tested working by both myself and sreinhardt. Should be good to go.

Phew.....

New component worked as intended.

Thank Yooouuu. Had us all nervous here for a few moments.

Great response time.

[snapon_admin]

I'm having this same error (saw the updated component and got excited so I installed it as well). The removal method did not seem to work for me and we're still having issues getting in. I can't even seem to log into the CLI atm...thoughts?

Edit. Quick look at top shows that the CPU is completely topped out atm.

Code: Select all

top - 16:15:23 up 35 min,  1 user,  load average: 694.64, 685.83, 606.31
Tasks: 1042 total,  48 running, 984 sleeping,   0 stopped,  10 zombie
Cpu(s): 87.5%us,  0.2%sy,  0.0%ni, 12.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   8061012k total,  1883568k used,  6177444k free,    55192k buffers
Swap:   262136k total,        0k used,   262136k free,   296044k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 2204 nagios    20   0 10248 1304  660 R 99.7  0.0 160103,58 nagios
 2209 nagios    20   0 10260 1312  660 R 99.7  0.0 110071,48 nagios
 2213 nagios    20   0 10404 1384  660 R 99.7  0.0  25016,34 nagios
 2203 nagios    20   0 10408 1408  660 R 99.4  0.0  80052,22 nagios
 2206 nagios    20   0 10404 1408  660 R 97.8  0.0 105068,33 nagios
14534 root      20   0  120m  36m 3096 S  1.6  0.5  5124095h mrtg
14451 root      20   0 15704 2004  944 R  0.7  0.0   0:00.33 top
14155 nagios    20   0  219m  21m 7428 S  0.3  0.3 300194:20 php
    1 root      20   0 19356 1592 1264 S  0.0  0.0  8911547h init