Says Paul Libbrecht:
>> My system's very small - approx 20 users and very little content at present.
>> It's
>> for a small collaborative research group which may grew to ~100 members. I
>> expect quite a few largish attachments and have already configured filesystem
>> attachments.
> Sounds qui
> My system's very small - approx 20 users and very little content at present.
> It's for a small collaborative research group which may grew to ~100 members.
> I expect quite a few largish attachments and have already configured
> filesystem attachments.
Sounds quite reasonable.
Limited memory
her members, who
probably did some exploring and perhaps triggered something painful.
From: Paul Libbrecht [p...@hoplahup.net]
Sent: 02 November 2014 22:21
To: XWiki Users
Subject: Re: [xwiki-users] Monitoring an Xwiki stack
Btw,
I am not sure you could s
Vincent wrote:
> BTW if you have setup some tools and have had successes
> with them to monitor xwiki instances, it would be great if
> you could add some doc about them at
> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Monitoring
>
Thanks for the pointers. These sound like useful tools,
BTW if you have setup some tools and have had successes with them to monitor
xwiki instances, it would be great if you could add some doc about them at
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Monitoring
Thanks!
-Vincent
On 2 Nov 2014 at 12:20:34, vinc...@massol.net
(vinc...@massol
Btw,
I am not sure you could say the XWiki installs are that "pesky".
However, depending on the user base, it may really need quite some tuning.
For example, if your xwiki manipulates complex documents the document cache may
be too big for the memory, and that you only reach with some time (it c
Hi Bryn,
There are some information that I’ve put at
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Monitoring to monitor XWiki
instances.
JavaMelody is quite great for that but it won’t send you alerts.
Make sure to check the tools at the end in the Others section too. There’s the
xinit
Bryn,
without JMX, straight and simple console output and thread-dump based… that's
what the monitor-sample tool was doing, it has a potential to answer the
back-end of that (e.g. DB-queries). In particular, it is the only one that can
express the query being hanging and this is exactly what wa
n a lot of mention of JMX for Tomcat monitoring, but I've shied away
from it since I wanted to start simple, but perhaps there is no simple ... ;-(
From: Paul Libbrecht [p...@hoplahup.net]
Sent: 01 November 2014 09:41
To: XWiki Users
Subject: Re: [xw
Hello all,
Here's my experience at monitoring XWikis.
With i2geo.net and with my private XWiki, I use a zabbix server.
This php-based monitoring tool is quite easy to configure for http monitoring
and with a few more steps you get a mail notification when, e.g., a timeout
occurs in connections.
I's also find any suggestions very helpful, I've had that happen a few times
and outside of monitoring CPU and RAM, I've found logging to be difficult to
use and configure, and even when I get it configured it's not very helpful.
> On Oct 31, 2014, at 1:57 PM, Bryn Jeffries
> wrote:
>
> Hav
Having made my XWiki site available to other users, I was concerned to find
that the site became unusable at one point with client connections eventually
timing out. I had no way to diagnose the problem, but eventually I managed to
make a (slow) SSH connection to the server and restarted Tomcat,
12 matches
Mail list logo