[BlueOnyx:22556] Re: Error in Site List

2018-12-14 Thread Michael Aronoff
OK, the update fixed the PHP error. To expand on the site list however. I have attached a screenshot that shows a listing from the Site List. The tree sites shown are all set to run the server default PHP via DSO + mod_ruid2. However they all show different PHP versions. It would be nice if there

[BlueOnyx:22555] Re: Error in Site List

2018-12-14 Thread Michael Stauber
Hi Michael, > In the main site list I still have some sites that show PHP 5.6+ even > though I changed the server default to 7.2. It seems that to get that to > change I have to manually go into each site, set it to another version > using FPM/FastCGI and then set it back to PHP (DSO) + mod_ruid2

[BlueOnyx:22554] Re: Error in Site List

2018-12-14 Thread Michael Aronoff
I am not sure if it helps but along the same lines I have noticed a few screwy things with how the GUI reports what PHP version the vsites use. In the main site list I still have some sites that show PHP 5.6+ even though I changed the server default to 7.2. It seems that to get that to change

[BlueOnyx:22553] Re: Error in Site List

2018-12-14 Thread Greg Kuhnert
Need more data to be conclusive, but looking at my 5209R box… The highlighted line is line 213. So something to do with custom PHP’s. Any chances in this area recently? // Expose the used PHP version: $php_suffix = ""; if (isset($vsite

[BlueOnyx:22552] Re: Error in Site List

2018-12-14 Thread Michael Stauber
Hi Michael, > When I go to the site page I get the following error (many times). > > A PHP Error was encountered > Severity: Notice > Message: Undefined index: 7.2.8 > Filename: controllers/vsiteList.php > > Line Number: 213 I just checked. There is something screwy. The code there is trying to

[BlueOnyx:22551] Error in Site List

2018-12-14 Thread Michael Aronoff
When I go to the site page I get the following error (many times). A PHP Error was encountered Severity: Notice Message: Undefined index: 7.2.8 Filename: controllers/vsiteList.php Line Number: 213 Any Idea how to fix this? __ M Aronoff Out -

[BlueOnyx:22550] Re: since some days warning in server status without detail warnings

2018-12-14 Thread Michael Stauber
Hi Dirk, > hmm, looks like in the GUI. Everything N or G but overall state R Ok, so the overall state is not getting reset. Not sure why. > Some Suggestions? Let's try this: Go to "Active Monitor" / "Settings" and disabled monitoring of all components but Apache. Save the changes. Click the but

[BlueOnyx:22549] Re: since some days warning in server status without detail warnings

2018-12-14 Thread Dirk Estenfeld
Hello Michael, hmm, looks like in the GUI. Everything N or G but overall state R Dec 14 17:30:02 mikev5 cced(smd)[31207]: client 0:[0:31206]: SET 30 . Remote lastChange = 1544805002 currentState = N currentMessage = "" Dec 14 17:30:02 mikev5 cced(smd)[31207]: client 0:[0:31206]: SET 30 . SNMP l

[BlueOnyx:22548] Whitelisting IPs in DFix

2018-12-14 Thread Richard Morgan :: Morgan Web
Hi We use a monitoring service to check the server is accessible from outside our network (NodePing). Sometimes their IPs are blocked in iptables but a rule called 'dfixblock'. I've tried adding whitelist rules but the dfixblock group gets re-inserted near the start. Does dfix have an IP w

[BlueOnyx:22547] Re: since some days warning in server status without detail warnings

2018-12-14 Thread Michael Stauber
Hi Dirk, > since some days the system status icon for some servers is red. However if I > open the detail page everything is blue. No warnings. > Also a recheck bring noch changes, The status icon is still red and in > detail view there are no warnings. > > What can I do to check why system status

[BlueOnyx:22546] since some days warning in server status without detail warnings

2018-12-14 Thread Dirk Estenfeld
Hello, since some days the system status icon for some servers is red. However if I open the detail page everything is blue. No warnings. Also a recheck bring noch changes, The status icon is still red and in detail view there are no warnings. Do this have something to do with CentOS 7.6 which s