Search · Index


Filtered by popular tag monitoring, 1 - 2 of 2 Postings (all, summary)

OpenACS Monitoring

Created by Malte Sussdorff, last modified by Gustaf Neumann 20 Apr 2017, at 06:07 PM

When running an OpenACS site a couple of packages come in handy to monitor your site and see why and where bottlenecks are located. To use them though, you need to install AOLserver with libthread support. If you are lazy as I am, just download the install script from and get started. This will make sure that you have all the necessary ingridients installed.

Then go to your systems administration at /acs-admin and install two packages:


  • xotcl-request-processor
  • monitoring

The first one gives you an overview over the system performance, while the latter allows you to scan the error.log for errors and have them send to you via e-mail.  A little bit more detail:


The monitoring package has a couple of nice things which help you monitor you website. First and foremost you can use it to get the error logs. This is HIGHLY recommended, as your users will not report errors to you. They will just complain internally and not use your site anymore. We learned this the hard way.

Once you have monitoring installed (and mounted at e.g. /monitoring) go there and edit the parameters. There you can define who should get the error reports send and how often they are send out. NOTE: They will be send out with every restart of the server, so this gives you a pretty good idea if your server has restarted.

You can also get the TOP reports (if you have a high load on the system), which is something I usually don't use, but maybe it is of importance for you.

Last but not least (for me at least) you can view which scheduled procs are running on your server and when they are executed next time. This is really helpful to understand what is going on on your site of the things you cannot see.


XoTCL Request Monitor

The request monitor (automatically mounted under /request-monitor) will give you a performance overview of your site, how many users are online, what are the average page load times ....

If you look at the overview page you will first be delighted to see that the average times are so low. This is misleading as the quick fetches to ".css" files and so on are counted into the equation as well.

More accurate is the aggregated stats view, which allows you to see which URLs are called most often on your site and how expensive they are to load. It is a good idea to have the most often called pages be *fast*.

One thing we do as well is to run the "last 100 request" page on a continuous basis in a browser window. It refreshes every 60 seconds and if you get the sorting right you can actually get a good overview of the activity on your site (e.g. we order by execution time, so we always see how long users are waiting for their pages and if this number goes up considerably, well, then we know we have to act!).




Let me say first, anyone running an OpenACS site without daemontools and keepalive should be send to a very unpleasant place. Keepalive is the only thing preventing you from being called in the middle of the night "our site is down". Why ?

Assume your database restarts for whatever the reason. AOLserver will restart immediately (if you have daemontools), but maybe the database takes longer to come up again, so you aolserver is showing "Installation Error, check your database connection" page to your users.

Or your web server has used up too much memory (for whatever the reasons) and connections are rare (e.g. if someone is trying an attack on your site). Then keepalive will see that the server is down and issue an automatic restart. And notify you about this via e-mail. If you are smart you could actually set it up in a way that, if keepalive has to restart three times within e.g. 15 minutes, then you are send an SMS and the infernal ringtone wakes you up.

Where to configure keepalive? /web/yoursite/etc/keepalive.




Monitoring Naviserver

Created by Gustaf Neumann, last modified by Gustaf Neumann 10 Oct 2015, at 02:42 PM

Munin  is a popular web-based tool to monitor several website. Munin provides a simple plugin mechanism for adding new kinds of sources, such as e.g. the NaviServer plugins  for monitoring NaviServer.

The monitoring information collected by munin can be placed at different web servers, one finds usually information about apache and friends. In general older versions of munin (before 2.0) supported only static pages, whereas newer version support as well dynamic information (with additional features such as zooming).

For static munin pages, it is the easiest to place in OpenACS sites the output directory either under the main www directory, or under the subsite admin directory (packages/acs-subsite/www/admin/).

For the cgi-setup, one has to make sure to load nscgi in the statup files of NaviServer and to point the urls to the appropriate directories. The sample setup below uses the directories of munin as provided by a standard munin setup on an Ubuntu system.

ns_section ns/server/${server}/modules
   ns_param   nscgi

ns_section "ns/server/${server}/module/nscgi"
   ns_param map  "GET /munin-cgi/munin-cgi-graph /var/www/cgi-bin/munin-cgi-graph"
   ns_param map  "GET /munin-cgi/static /etc/munin/static/"
   ns_param map  "GET /munin-cgi /var/www/cgi-bin/munin-cgi-html"

Previous Month April 2017
Sun Mon Tue Wed Thu Fri Sat
26 27 28 29 30 31 1
2 3 4 5 6 7 8
9 (3) 10 11 12 13 (11) 14 15
16 17 18 19 (28) 20 21 (3) 22
23 (3) 24 (1) 25 (1) 26 27 28 29
30 1 2 3 4 5 6

Popular tags

17 , 5.9.0 , 5.9.1 , ad_form , ADP , ajax , aolserver , asynchronous , bgdelivery , bootstrap , bugtracker , CentOS , COMET , CSP , CSRF , cvs , debian , emacs , fedora , FreeBSD , hstore , includelets , install , installation , installers , install-ns , javascript , libthread , linux , monitoring
No registered users in community xowiki
in last 30 minutes