[BlueOnyx:25891] Re: Monitorix: 404 page not found

2023-01-03 Thread oldcabin webmaster
The commands fixed the issue. I see stats! Thx On Tue, Jan 3, 2023, 4:52 PM Michael Stauber wrote: > Hi Tim, > > > 5210R > > > > Clicking the monitorx in usage info i get 404 page not found > > I ran systemctl status goaccess > > And it looks to be running > > > > Any ideas? > > Try this please:

[BlueOnyx:25890] Re: Monitorix: 404 page not found

2023-01-03 Thread Michael Stauber
Hi Tim, 5210R Clicking the monitorx in usage info i get 404 page not found I ran systemctl status goaccess And it looks to be running Any ideas? Try this please: yum clean all yum update /usr/sausalito/sbin/cced.init restart systemctl restart admserv Not all of this might be necessary, but

[BlueOnyx:25889] Monitorix: 404 page not found

2023-01-03 Thread oldcabin webmaster
5210R Clicking the monitorx in usage info i get 404 page not found I ran systemctl status goaccess And it looks to be running Any ideas? Thanks --Tim On Tue, Jan 3, 2023, 3:00 PM Michael Stauber wrote: > Hi Colin, > > > That is my problem. :-/ > > > > [root@5210r ~]# systemctl status goa

[BlueOnyx:25888] Re: The GoAccess daemon is currently not running

2023-01-03 Thread JW Ronken
Hi Michael Both working fine now! Many thanks for the quick fix! Happy New Year! Janwillem On Tue, 3 Jan 2023 at 21:02, Michael Stauber wrote: > Hi Janwillem, > > A "yum clean all" and "yum update" should fix both issues, as I just > published a fix. > > The fact that one box wasn't showing the

[BlueOnyx:25887] Re: 5210R GoAccess issues - fixed

2023-01-03 Thread Colin Jack
Hi Michael, > I just published YUM updates for 5210R that should fix this. So please > try the usual procedure and it should fix it: Yup - all good! > Sorry! Hehehe ... no worries. Well done! With best regards Colin ___ Blueonyx mailing list Blu

[BlueOnyx:25886] Re: The GoAccess daemon is currently not running

2023-01-03 Thread Michael Stauber
Hi Martin, I have also problems with firewalld since 2 or 3 days, no idea if this is connected to each other. What problems are these and what is the version of the Firewalld package shown under "Installed Software"? -- With best regards Michael Stauber

[BlueOnyx:25885] Re: The GoAccess daemon is currently not running

2023-01-03 Thread Michael Stauber
Hi Janwillem, Server 1: has the Usage Information Services item under system status and Monitorix works OK but GoAccess has the same error. Server2: doesn’t have the Usage Information Service item under system status. However it has the Monitorix menu item under Usage Information but it show

[BlueOnyx:25884] Re: 5210R GoAccess issues - fixed

2023-01-03 Thread Michael Stauber
Hi Colin, That is my problem. :-/ [root@5210r ~]# systemctl status goaccess Unit goaccess.service could not be found. [root@5210r ~]# Monitorix is running fine. I just checked and I indeed had made a mistake. The 5210R SVN tree for base-sitestats had the Systemd Unit file for goaccess, but

[BlueOnyx:25883] Re: The GoAccess daemon is currently not running

2023-01-03 Thread JW Ronken
More or less the same issue on two 5210’s: Server 1: has the Usage Information Services item under system status and Monitorix works OK but GoAccess has the same error. Server2: doesn’t have the Usage Information Service item under system status. However it has the Monitorix menu item under Usage

[BlueOnyx:25882] Re: [EXTERNAL] The GoAccess daemon is currently not running

2023-01-03 Thread Ceelie, Arie (VodafoneZiggo)
Yep, same here. Got this on january 1st ( no idea if they are running yet though): * One or more Usage Information Services are currently not running and should be restarted. - The GoAccess daemon is currently not running and should be restarted. - The Monitorix daemon is currently not running a

[BlueOnyx:25881] Re: The GoAccess daemon is currently not running

2023-01-03 Thread Martin Schepers
Hi, > Am 03.01.2023 um 21:10 schrieb Colin Jack : > > Unit goaccess.service could not be found. Same here. I have also problems with firewalld since 2 or 3 days, no idea if this is connected to each other. Martin ___ Blueonyx mailing list Blueonyx@ma

[BlueOnyx:25880] Re: The GoAccess daemon is currently not running

2023-01-03 Thread Colin Jack
Hi Michael, > GoAccess and Monitorix has just been backported form 5211R to 5210R. Yeah saw that from your posting > They bring this two new daemons aboard: That is my problem. :-/ [root@5210r ~]# systemctl status goaccess Unit goaccess.service could not be found. [root@5210r ~]#  Monitorix i

[BlueOnyx:25879] Re: The GoAccess daemon is currently not running

2023-01-03 Thread Michael Stauber
Hi Colin, All my 5210R servers are showing a status error:  The GoAccess daemon is currently not running and should be restarted. I cannot see anything in /usr/lib/systemd/system for GoAccess. Is anybody else seeing this? What am I missing? GoAccess and Monitorix has just been backported fo

[BlueOnyx:25878] The GoAccess daemon is currently not running

2023-01-03 Thread Colin Jack
All my 5210R servers are showing a status error:  The GoAccess daemon is currently not running and should be restarted. I cannot see anything in /usr/lib/systemd/system for GoAccess. Is anybody else seeing this? What am I missing? Thanks Colin ___ B