Open-Xchange - User contributions [en]

https://wiki.open-xchange.com/wiki/api.php?action=feedcontributions&feedformat=atom&user=Felix.Marx Open-Xchange - User contributions [en] 2026-06-30T19:12:07Z User contributions MediaWiki 1.39.7 https://wiki.open-xchange.com/wiki/index.php?title=AppSuite:Grizzly&diff=21078 AppSuite:Grizzly 2015-12-09T08:58:46Z

<p>Felix.Marx: /* Apache configuration */</p> <hr /> <div><div class="title">Grizzly</div><br /> <br /> __TOC__<br /> <br /> = Grizzly based backend =<br /> Up to OX App Suite we were limited to AJP based communication between the HTTP server and the OX backend server. Starting with the release 7.0.1 of OX App Suite, we offer a second HTTP based connector for the communication between the HTTP server and the backend. This new connector is based on Oracle's '''[http://grizzly.java.net Project Grizzly]''' - a [http://en.wikipedia.org/wiki/New_I/O NIO] and Web framework. AJP is deprecated with 7.4 and will be discontinued with 7.6.0.<br /> <br /> =Packages=<br /> Next, we'll show some information on the packages needed to install a Grizzly based backend, give you some in depth information about the package dependencies of '''open-xchange''' on '''open-xchange-grizzly'''. <br /> <br /> ==HttpService as packaging dependency==<br /> The open-xchange package depends on a virtual package called '''open-xchange-httpservice'''. This service is provided by the '''open-xchange-grizzly''' package.<br /> <br /> <div style="clear: both"></div><br /> <br /> {{InstallPlugin|pluginname=open-xchange-grizzly| toplevel=products | sopath=appsuite/stable/backend|version=App Suite}}<br /> <br /> =Cluster setup=<br /> [[File:GrizzlOXClusterSetup.png|left|alt=The default cluster setup.]]<br /> This picture shows our default cluster setup. It consists of a proxying balancer (in our case Apache) and a cluster of multiple OX App Suite backends. The balancer receives HTTP and/or HTTPS requests. It then decides which requests should be handled by itself and which should be forwarded, so they can be handled by one of the OX App Suite backends. That's where the HTTP connector is used. <br /> <div style="clear: both"></div><br /> <br /> ==Configuration==<br /> As requests pass the balancer first, we'll start with a look at how to configure the balancer before configuring the Grizzly-based OX App Suite backends.<br /> <br /> ===Apache configuration===<br /> <br /> {{Template:ApacheOXModsDebian|connector=http}}<br /> <br /> If you are using Apache 2.4, you will also need to enable the mod_lbmethod_byrequests<br /> <br /> $ a2enmod lbmethod_byrequests<br /> <br /> If you used AJP before, you have to delete /etc/apache2/conf.d/proxy_ajp.conf.<br /> <br /> {{Template:ApacheAppSuiteConf|connector=http|connectorConf=/etc/apache2/conf.d/proxy_http.conf|apacheconf=/etc/apache2/sites-enabled/000-default|docroot=/var/www/|loadmodule=|easProxyName=eas_oxcluster|syncProxyName=oxcluster_sync}}<br /> <br /> ====X-FORWARDED-PROTO Header====<br /> <br /> [[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the OX backends. To let the backends know about the protocol that is used to communicate with the Apache server we have to set a special header in the ssl virtual hosts configurations in Apache to forward this information. The de facto standard for this is the X-Forwarded-Proto header.<br /> <br /> To add it to your Apache configuration you have to open the default ssl vhost, for Debian systems do:<br /> $ vim /etc/apache2/sites-enabled/default-ssl<br /> <br /> For RHEL and CentOS, do:<br /> $ vim/etc/httpd/conf.d/ssl.conf<br /> <br /> <br /> and add <br /> RequestHeader set X-Forwarded-Proto "https"<br /> <br /> to each of the virtual hosts used to communicate with the OX App Suite backends.<br /> <br /> ===Grizzly configuration===<br /> <br /> ====Available configuration files====<br /> <br /> ====/opt/open-xchange/etc/server.properties====<br /> This extract of the server.properties shows the properties that can be applied to the grizzly backend.<br /> <pre><br /> ...<br /> # DEFAULT ENCODING FOR INCOMING HTTP REQUESTS<br /> # This value MUST be equal to web server's default encoding<br /> DefaultEncoding=UTF-8<br /> ...<br /> # The host for the connector's http network listener. Set to "*" if you<br /> # want to listen on all available interfaces.<br /> #Default value: 127.0.0.1, bind to localhost only.<br /> com.openexchange.connector.networkListenerHost=*<br /> <br /> # The default port for the connector's http network listener.<br /> # Default value: 8009.<br /> com.openexchange.connector.networkListenerPort=8009<br /> <br /> # Specify the max. number of allowed request parameters for the connector http<br /> # Default value: 30<br /> com.openexchange.connector.maxRequestParameters: 30<br /> <br /> # To enable proper load balancing and request routing from {client1, client2 ..<br /> # .} --> balancer --> {backend1, backend2 ...} we have to append a backend route<br /> # to the JSESSIONID cookies separated by a '.'. It's important that this backend<br /> # route is unique for every single backend behind the load balancer.<br /> # The string has to be a sequence of characters excluding semi-colon, comma and<br /> # white space so the JSESSIONID cookie stays in accordance with the cookie<br /> # specification after we append the backendroute to it.<br /> # Default value: OX0 <br /> com.openexchange.server.backendRoute=OX1<br /> <br /> # Decides if we should consider X-Forward-Headers that reach the backend.<br /> # Those can be spoofed by clients so we have to make sure to consider the headers only if the proxy/proxies reliably override those<br /> # headers for incoming requests.<br /> # Default value: false<br /> com.openexchange.server.considerXForwards = false<br /> <br /> # The name of the protocolHeader used to identify the originating IP address of<br /> # a client connecting to a web server through an HTTP proxy or load balancer.<br /> # This is needed for grizzly based setups that make use of http proxying.<br /> # If the header isn't found the first proxy in front of grizzly will be used<br /> # as originating IP/remote address.<br /> # Default value: X-Forwarded-For<br /> com.openexchange.server.forHeader=X-Forwarded-For<br /> <br /> # A list of know proxies in front of our httpserver/balancer as comma separated IPs e.g: 192.168.1.50, 192.168.1.51<br /> com.openexchange.server.knownProxies = <br /> ...<br /> </pre><br /> <br /> ====/opt/open-xchange/etc/grizzly.properties====<br /> Next we'll look at the parts of the grizzly.properties that configures the grizzly backend.<br /> <pre><br /> # Grizzly.properties<br /> #<br /> # This file configures the grizzly server contained in the package<br /> # open-xchange-grizzly. In your OX setup grizzly is located behind the<br /> # load-balancer and accepts incoming client requests. Communication with the<br /> # load balancer is done via http, e.g via Apache's mod_proxy_http.<br /> <br /> <br /> ### Push technology<br /> ################################################################################<br /> <br /> # Comet is an umbrella term used to describe a technique allowing web browser to<br /> # receive almost real time updates from the server. The two most common<br /> # approaches are long polling and streaming. Long polling differs from streaming<br /> # in that each update from the server ultimately results in another follow up<br /> # request from the client.<br /> # Default value: true<br /> com.openexchange.http.grizzly.hasCometEnabled=true<br /> <br /> # Bi-directional, full-duplex communications channels over a single TCP<br /> # connection.<br /> # Default value: false<br /> com.openexchange.http.grizzly.hasWebSocketsEnabled=true<br /> <br /> <br /> ### JMX<br /> ################################################################################<br /> <br /> # Do you want to enable grizzly monitoring via JMX? Default value: true.<br /> com.openexchange.http.grizzly.hasJMXEnabled=true<br /> </pre><br /> <br /> ====/opt/open-xchange/etc/requestwatcher.properties====<br /> And finally the properties to configure the requestwatchers of the http backend<br /> <pre><br /> # Requestwatcher.properties<br /> #<br /> # This file configures the requestwatchers contained in the packages<br /> # open-xchange-grizzly. The requestwatcher keeps track of<br /> # incoming requests and periodically checks the age of the currently processing<br /> # requests. If a request exceeds the configured maximum age, infos about the<br /> # request and its processing thread are logged either into the configured<br /> # logfiles or syslog depending on your configuration. <br /> <br /> <br /> # Enable/disable the requestwatcher.<br /> # Default value: true (enabled).<br /> com.openexchange.requestwatcher.isEnabled: true<br /> <br /> # Define the requestwatcher's frequency in milliseconds.<br /> # Default value: 30000.<br /> com.openexchange.requestwatcher.frequency: 30000<br /> <br /> # Define the maximum allowed age of requests in milliseconds.<br /> # Default value: 60000. <br /> com.openexchange.requestwatcher.maxRequestAge: 60000<br /> </pre><br /> <br /> ==Multiple Proxies in front of the cluster==<br /> [[File:GrizzlOXClusterMultipleProxySetup.png|left|935px|alt=The default cluster with multiple proxies setup.]]<br /> <div style="clear: both"></div><br /> <br /> ===X-FORWARDED-FOR Header===<br /> <br /> Wikipedia[http://en.wikipedia.org/wiki/X-Forwarded-For] describes the X-Forwarded-For Header as: <br /> <br /> The '''X-Forwarded-For''' ('''XFF''') HTTP header field is a ''de facto'' standard for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer. This is an HTTP request header which was introduced by the [[Squid (software)|Squid]] caching proxy server's developers. An effort has been started at IETF for standardizing the '''Forwarded''' HTTP header.<br /> <br /> In this context, the caching servers are most often those of large ISPs who either encourage or force their users to use proxy servers for access to the World Wide Web, something which is often done to reduce external bandwidth through caching. In some cases, these proxy servers are transparent proxies, and the user may be unaware that they are using them.<br /> <br /> Without the use of XFF or another similar technique, any connection through the proxy would reveal only the originating IP address of the proxy server, effectively turning the proxy server into an anonymizing service, thus making the detection and prevention of abusive accesses significantly harder than if the originating IP address was available. The usefulness of XFF depends on the proxy server truthfully reporting the original host's IP address; for this reason, effective use of XFF requires knowledge of which proxies are trustworthy, for instance by looking them up in a whitelist of servers whose maintainers can be trusted.<br /> <br /> ====Format====<br /> The general format of the field is:<br /> <br /> : <tt>X-Forwarded-For: client, proxy1, proxy2</tt><br /> <br /> where the value is a comma+space separated list of IP addresses, the left-most being the original client, and each successive proxy that passed the request adding the IP address where it received the request from. In this example, the request passed through proxy1, proxy2, and then proxy3 (not shown in the header). proxy3 appears as remote address of the request.<br /> <br /> The given information should be used with care since it is easy to forge an X-Forwarded-For field. The last IP address is always the IP address that connects to the last proxy, which means it is the most reliable source of information. X-Forwarded-For data can be used in a forward or reverse proxy scenario.<br /> <br /> Just logging the X-Forwarded-For field is not always enough: The last proxy IP address in a chain is not contained within the X-Forwarded-For field, it is in the actual IP header. A web server should log BOTH the request's source IP address and the X-Forwarded-For field information for completeness.<br /> <br /> ===Getting the remote IP===<br /> If you want the backends in the GrizzlOX-Cluster to use '''Client''''s(95.223.182.44) instead of '''Balancer''''s IP as remote address for e.g reporting the LogProperty '''com.openexchange.grizzly.remoteAddress''' for faulty requests in the Open-Xchange logs, you have to change these parameters from their default values seen in /opt/open-xchange/etc/server.properties to:<br /> <br /> # Decides if we should consider X-Forward-Headers that reach the backend.<br /> # Those can be spoofed by clients so we have to make sure to consider the headers only if the proxy/proxies reliably override those<br /> # headers for incoming requests.<br /> # Default value: false<br /> com.openexchange.server.considerXForwards = '''true'''<br /> <br /> # The name of the protocolHeader used to identify the originating IP address of<br /> # a client connecting to a web server through an HTTP proxy or load balancer.<br /> # This is needed for grizzly based setups that make use of http proxying.<br /> # If the header isn't found the first proxy in front of grizzly will be used<br /> # as originating IP/remote address.<br /> # Default value: X-Forwarded-For<br /> com.openexchange.server.forHeader='''X-Forwarded-For'''<br /> <br /> # A list of know proxies in front of our httpserver/balancer as comma separated IPs e.g: 192.168.1.50, 192.168.1.51<br /> com.openexchange.server.knownProxies = '''192.168.1.50, 192.168.1.51'''<br /> <br /> After you have changed the the configuration you have to restart the backend server via<br /> <br /> $ /etc/init.d/open-xchange restart<br /> <br /> The remote IP is detected in the following way: All configured known proxies are removed from the list of IPs listed in the X-FORWARDED-FOR header, beginning frome the right side of the list. The rightmost leftover IP is then seen as our new remote address as it represents the first IP not known to us.<br /> <br /> =Servlet Filters=<br /> <br /> From version 7.6.1 on you are able to register your own servlet filters when using a Grizzly powered OX backend.<br /> <br /> This is realized via a '''ServletFilterTracker''' that tracks services of type javax.servlet.Filter and updates the registered ServletHandlers so that the filters are applied to new incoming requests/outgoing responses.<br /> <br /> ==Filter Service Properties==<br /> Your filter service may be registered with additional <code>com.openexchange.servlet.Constants.FILTER_PATHS</code> and <code>org.osgi.framework.Constants.SERVICE_RANKING</code> properties. <br /> <br /> ===<code>filter.paths</code>===<br /> This property may consist of path expressions including wildcards. The path property should be provided as:<br /> <br /> # A single String for a single path<br /> # An array of Strings<br /> # A Collection of of Objects that provides the path via invocation of toString()<br /> <br /> If the filter.path property is missing/null the filter will be used for every incoming request.<br /> <br /> The form of a path must be one of:<br /> <br /> # '''*''' : This filter will be applied to all request<br /> # The path starts with '''/''' and ends with the '''/*''' wildcard but doesn't equal '''/*''' e.g. '''/a/b/*''' : This filter will be used for requests to all URLs starting with /a/b e.g /a/b/c, /a/b/c/d and so on<br /> # The path starts with '''/''' but doesn't end with the '''/*''' wildcard : This filter will only be used for requests that match this path exactly<br /> <br /> ===<code>service.ranking</code>===<br /> The filters you register are combined into a filterchain and ordered by this service ranking that has to be specified as an integer value. Incoming Requests will then be processed by the filterchain. If multiple filters have the same service ranking their order within the filterchain is as follows:<br /> <br /> # filters that match all paths e.g. were registered without a path or with the '''/*''' wildcard<br /> # filters that match a prefix of a path e.g. filters that are registered for '''/a/b/*''' should be used for requests to '''/a/b/c''', too<br /> # filters that match a path e.g. filters that are registered for '''/a/b''' should be used only for requests to '''/a/b'''<br /> <br /> It's recommended to use unique ranking values for each servlet filter to achieve a reliable filterchain setup.<br /> <br /> ==Example==<br /> <br /> <nowiki><br /> public class ServletFilterActivator extends HousekeepingActivator {<br /> <br /> @Override<br /> protected Class[] getNeededServices() {<br /> // It is important to await the HttpService before filter registration takes place!<br /> return new Class[] { HttpService.class };<br /> }<br /> <br /> @Override<br /> protected void startBundle() throws Exception {<br /> Filter yourFilter = new Filter() {<br /> <br /> @Override<br /> public void destroy() {<br /> // Nothing to do<br /> }<br /> <br /> @Override<br /> public void doFilter(ServletRequest request, ServletResponse response, FilterChain filterChain)<br /> throws IOException, ServletException {<br /> String world = request.getParameter("hello");<br /> filterChain.doFilter(request, response);<br /> }<br /> <br /> @Override<br /> public void init(FilterConfig config) throws ServletException {<br /> // Nothing to do<br /> }<br /> };<br /> <br /> Dictionary&lt;String, Object&gt; serviceProperties = new Hashtable&lt;String, Object&gt;(2);<br /> serviceProperties.put(Constants.SERVICE_RANKING, Integer.valueOf(0));<br /> serviceProperties.put(FILTER_PATHS, "*");<br /> <br /> registerService(Filter.class, yourFilter, serviceProperties);<br /> }</nowiki><br /> <br /> [[Category: AppSuite]]<br /> [[Category: Administrator]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=OX_munin_scripts&diff=18258 OX munin scripts 2014-08-11T10:21:19Z

<p>Felix.Marx: /* open-xchange-munin-scripts-jolokia */</p> <hr /> <div>= How to install Munin scripts for Open-Xchange=<br /> <br /> == Support for Jolokia ==<br /> <br /> By Version 7.4.0, Munin Scripts do support [[Jolokia]] as a bridge to get their information.<br /> This has been done to get less overhead and speak with the corresponding JMX-beans directly.<br /> <br /> == Prerequisites ==<br /> <br /> Munin node and munin master must be installed and configured prior using the Munin scripts package for Open-Xchange. The installation for this core components differs on various Linux distributions. For details, please visit:<br /> <br /> http://munin-monitoring.org/<br /> <br /> especially:<br /> <br /> http://munin-monitoring.org/wiki/LinuxInstallation<br /> <br /> === open-xchange-munin-scripts ===<br /> {{InstallPlugin|pluginname=open-xchange-munin-scripts|toplevel=products|sopath=appsuite/stable/backend|version=App Suite}}<br /> <br /> === open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin-scripts for Jolokia need an additional perl modules json and lwp, which are set inside the depenecies. Those should be installed automaticly.<br /> <br /> If not, please install the following modules:<br /> <br /> Debian: libwww-perl, libjson-perl<br /> <br /> rpm: perl-JSON, perl-libwww-perl<br /> <br /> == Configuring munin-node scripts for Open-Xchange ==<br /> <br /> The configuration of the scripts is done automatically. <br /> <br /> Note: The database pool monitoring script will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. That can be verified by e.g.:<br /> <br /> # showruntimestats -x | grep "DB Pool"<br /> com.openexchange.pooling:name=DB Pool 4,NumWaiting = 0<br /> com.openexchange.pooling:name=DB Pool 4,PoolSize = 3<br /> com.openexchange.pooling:name=DB Pool 4,NumBrokenConnections = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumActive = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumIdle = 3<br /> com.openexchange.pooling:name=DB Pool 4,AvgUseTime = 4.948<br /> com.openexchange.pooling:name=DB Pool 4,MaxUseTime = 16777<br /> com.openexchange.pooling:name=DB Pool 4,MinUseTime = 0<br /> <br /> === Configuring for open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin Scripts for Jolokia do have some additional settings for [[jolokia]].<br /> <br /> <code>vim /etc/munin/plugin-conf.d/ox</code><br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | env.oxJolokiaUrl<br /> | http://localhost:8009/monitoring/jolokia<br /> | base url for jolokia. this can differ, when using ajp. Possible ajp url could be http://apacheaddress/internal/ox1/monitoring/jolokia<br /> |-<br /> | env.oxJolokiaUser<br /> | "changeMe!Now"<br /> | <nowiki>User used for authentication with HTTP Basic Authentication.</nowiki><br /> |-<br /> | env.oxJolokiaPassword<br /> | "s3cr3t!toBeChanged"<br /> | <nowiki>Password used for authentification,</nowiki><br /> |}<br /> <br /> WARNING: If <code> env.oxJolokiaUser </code> is not changed from its default value <code> changeMe!Now </code>, monitoring will not work as the user <code> changeMe!Now </code> is set to stop monitoring inside the munin scripts.<br /> <br /> Both, <code> env.oxJolokiaUser </code> and <code> env.oxJolokiaPassword </code> need to be set to the same value as set inside <code>jolokia.properties</code><br /> <br /> = Supplementary notes for distributed munin clients =<br /> <br /> == Munin node ==<br /> The default munin node configuration only allows connections from localhost, which means that munin master has to run on the same host. If there already is a munin master running, that master IP has to be added to the file <code>/etc/munin/munin-node.conf</code> on each node:<br /> <br /> # A list of addresses that are allowed to connect. This must be a<br /> # regular expression, since Net::Server does not understand CIDR-style<br /> # network notation unless the perl module Net::CIDR is installed. You<br /> # may repeat the allow line as many times as you'd like<br /> <br /> allow ^127\.0\.0\.1$<br /> <br /> == Munin master ==<br /> <br /> Make sure the munin and apache packages are installed. If only localhost is going to be monitored, the default configuration is sufficient. Other munin nodes can be added in the <code>/etc/munin/munin.conf</code> file:<br /> <br /> # a simple host tree<br /> [localhost.localdomain]<br /> address 127.0.0.1<br /> use_node_name yes<br /> <br /> By default, the munin monitoring web page is only reached from localhost, other hosts or networks can be added in <code>/etc/apache2/conf.d/munin</code>:<br /> <br /> Allow from localhost 127.0.0.0/8 ::1 # the default setting<br /> Allow from 10.99.0.0/8 # added network<br /> <br /> The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>. <br /> <br /> <br /> <br /> [[Category: OX6]]<br /> [[Category: Administrator]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=OX_munin_scripts&diff=18257 OX munin scripts 2014-08-11T10:19:45Z

<p>Felix.Marx: /* Configuring for open-xchange-munin-scripts-jolokia */</p> <hr /> <div>= How to install Munin scripts for Open-Xchange=<br /> <br /> == Support for Jolokia ==<br /> <br /> By Version 7.4.0, Munin Scripts do support [[Jolokia]] as a bridge to get their information.<br /> This has been done to get less overhead and speak with the corresponding JMX-beans directly.<br /> <br /> == Prerequisites ==<br /> <br /> Munin node and munin master must be installed and configured prior using the Munin scripts package for Open-Xchange. The installation for this core components differs on various Linux distributions. For details, please visit:<br /> <br /> http://munin-monitoring.org/<br /> <br /> especially:<br /> <br /> http://munin-monitoring.org/wiki/LinuxInstallation<br /> <br /> === open-xchange-munin-scripts ===<br /> {{InstallPlugin|pluginname=open-xchange-munin-scripts|toplevel=products|sopath=appsuite/stable/backend|version=App Suite}}<br /> <br /> === open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin-scripts for Jolokia need an additional CPAN module.<br /> <br /> <br /> jmx4perl (and its dependencies) can be easily installed with cpan if you have Perl installed:<br /> You also need to have make installed.<br /> <br /> Debian:<br /> <br /> sudo apt-get install make<br /> <br /> $ perl -MCPAN -e shell<br /> <br /> Terminal does not support AddHistory.<br /> cpan shell -- CPAN exploration and modules installation (v1.9205)<br /> ReadLine support available (maybe install Bundle::CPAN or Bundle::CPANxxl?)<br /> <br /> cpan[1]> install JMX::Jmx4Perl<br /> <br /> ...<br /> ...<br /> jmx4perl<br /> ========<br /> jmx4perl is a command line utility for accessing Jolokia agents<br /> (www.jolokia.org). It can be used for script based exploration <br /> and easy inspection of the JMX space.<br /> Install 'jmx4perl' ? (y/n) [y ]<br /> ....<br /> <br /> == Configuring munin-node scripts for Open-Xchange ==<br /> <br /> The configuration of the scripts is done automatically. <br /> <br /> Note: The database pool monitoring script will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. That can be verified by e.g.:<br /> <br /> # showruntimestats -x | grep "DB Pool"<br /> com.openexchange.pooling:name=DB Pool 4,NumWaiting = 0<br /> com.openexchange.pooling:name=DB Pool 4,PoolSize = 3<br /> com.openexchange.pooling:name=DB Pool 4,NumBrokenConnections = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumActive = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumIdle = 3<br /> com.openexchange.pooling:name=DB Pool 4,AvgUseTime = 4.948<br /> com.openexchange.pooling:name=DB Pool 4,MaxUseTime = 16777<br /> com.openexchange.pooling:name=DB Pool 4,MinUseTime = 0<br /> <br /> === Configuring for open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin Scripts for Jolokia do have some additional settings for [[jolokia]].<br /> <br /> <code>vim /etc/munin/plugin-conf.d/ox</code><br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | env.oxJolokiaUrl<br /> | http://localhost:8009/monitoring/jolokia<br /> | base url for jolokia. this can differ, when using ajp. Possible ajp url could be http://apacheaddress/internal/ox1/monitoring/jolokia<br /> |-<br /> | env.oxJolokiaUser<br /> | "changeMe!Now"<br /> | <nowiki>User used for authentication with HTTP Basic Authentication.</nowiki><br /> |-<br /> | env.oxJolokiaPassword<br /> | "s3cr3t!toBeChanged"<br /> | <nowiki>Password used for authentification,</nowiki><br /> |}<br /> <br /> WARNING: If <code> env.oxJolokiaUser </code> is not changed from its default value <code> changeMe!Now </code>, monitoring will not work as the user <code> changeMe!Now </code> is set to stop monitoring inside the munin scripts.<br /> <br /> Both, <code> env.oxJolokiaUser </code> and <code> env.oxJolokiaPassword </code> need to be set to the same value as set inside <code>jolokia.properties</code><br /> <br /> = Supplementary notes for distributed munin clients =<br /> <br /> == Munin node ==<br /> The default munin node configuration only allows connections from localhost, which means that munin master has to run on the same host. If there already is a munin master running, that master IP has to be added to the file <code>/etc/munin/munin-node.conf</code> on each node:<br /> <br /> # A list of addresses that are allowed to connect. This must be a<br /> # regular expression, since Net::Server does not understand CIDR-style<br /> # network notation unless the perl module Net::CIDR is installed. You<br /> # may repeat the allow line as many times as you'd like<br /> <br /> allow ^127\.0\.0\.1$<br /> <br /> == Munin master ==<br /> <br /> Make sure the munin and apache packages are installed. If only localhost is going to be monitored, the default configuration is sufficient. Other munin nodes can be added in the <code>/etc/munin/munin.conf</code> file:<br /> <br /> # a simple host tree<br /> [localhost.localdomain]<br /> address 127.0.0.1<br /> use_node_name yes<br /> <br /> By default, the munin monitoring web page is only reached from localhost, other hosts or networks can be added in <code>/etc/apache2/conf.d/munin</code>:<br /> <br /> Allow from localhost 127.0.0.0/8 ::1 # the default setting<br /> Allow from 10.99.0.0/8 # added network<br /> <br /> The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>. <br /> <br /> <br /> <br /> [[Category: OX6]]<br /> [[Category: Administrator]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=OX_munin_scripts&diff=17216 OX munin scripts 2014-03-07T11:13:39Z

<p>Felix.Marx: /* open-xchange-munin-scripts-jolokia */</p> <hr /> <div>= How to install Munin scripts for Open-Xchange=<br /> <br /> == Support for Jolokia ==<br /> <br /> By Version 7.4.0, Munin Scripts do support [[Jolokia]] as a bridge to get their information.<br /> This has been done to get less overhead and speak with the corresponding JMX-beans directly.<br /> <br /> == Prerequisites ==<br /> <br /> Munin node and munin master must be installed and configured prior using the Munin scripts package for Open-Xchange. The installation for this core components differs on various linux distributions. For details, please visit:<br /> <br /> http://munin-monitoring.org/<br /> <br /> especially:<br /> <br /> http://munin-monitoring.org/wiki/LinuxInstallation<br /> <br /> === open-xchange-munin-scripts ===<br /> {{InstallPlugin|pluginname=open-xchange-munin-scripts|sopath=unsupported/repo|reponame=oxmunin}}<br /> <br /> === open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin-scripts for Jolokia need an additional CPAN module.<br /> <br /> <br /> jmx4perl (and its dependencies) can be easily installed with cpan if you have Perl installed:<br /> You also need to have make installed.<br /> <br /> Debian:<br /> <br /> sudo apt-get install make<br /> <br /> $ perl -MCPAN -e shell<br /> <br /> Terminal does not support AddHistory.<br /> cpan shell -- CPAN exploration and modules installation (v1.9205)<br /> ReadLine support available (maybe install Bundle::CPAN or Bundle::CPANxxl?)<br /> <br /> cpan[1]> install JMX::Jmx4Perl<br /> <br /> ...<br /> ...<br /> jmx4perl<br /> ========<br /> jmx4perl is a command line utility for accessing Jolokia agents<br /> (www.jolokia.org). It can be used for script based exploration <br /> and easy inspection of the JMX space.<br /> Install 'jmx4perl' ? (y/n) [y ]<br /> ....<br /> <br /> == Configuring munin-node scripts for Open-Xchange ==<br /> <br /> The configuration of the scripts is done automatically. <br /> <br /> Note: The database pool monitoring script will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. That can be verified by e.g.:<br /> <br /> # showruntimestats -x | grep "DB Pool"<br /> com.openexchange.pooling:name=DB Pool 4,NumWaiting = 0<br /> com.openexchange.pooling:name=DB Pool 4,PoolSize = 3<br /> com.openexchange.pooling:name=DB Pool 4,NumBrokenConnections = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumActive = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumIdle = 3<br /> com.openexchange.pooling:name=DB Pool 4,AvgUseTime = 4.948<br /> com.openexchange.pooling:name=DB Pool 4,MaxUseTime = 16777<br /> com.openexchange.pooling:name=DB Pool 4,MinUseTime = 0<br /> <br /> === Configuring for open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin Scripts for Jolokia do have some additional settings for [[jolokia]].<br /> <br /> <code>vim /etc/munin/plugin-conf.d/ox</code><br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | env.oxJolokiaUrl<br /> | http://localhost:8009/monitoring/jolokia<br /> | base url for jolokia. this can differ, when using ajp. Possible ajp url could be http://apacheaddress/internal/ox1/monitoring/jolokia<br /> |-<br /> | env.oxJolokiaUser<br /> | ""<br /> | <nowiki>User used for authentication with HTTP Basic Authentication.</nowiki><br /> |-<br /> | env.oxJolokiaPassword<br /> | ""<br /> | <nowiki>Password used for authentification,</nowiki><br /> |}<br /> <br /> Both, <code> env.oxJolokiaUser </code> and <code> env.oxJolokiaPassword </code> need to be set to the same value as set inside <code>jolokia.properties</code><br /> <br /> = Supplementary notes for distributed munin clients =<br /> <br /> == Munin node ==<br /> The default munin node configuration only allows connections from localhost, which means that munin master has to run on the same host. If there already is a munin master running, that master IP has to be added to the file <code>/etc/munin/munin-node.conf</code> on each node:<br /> <br /> # A list of addresses that are allowed to connect. This must be a<br /> # regular expression, since Net::Server does not understand CIDR-style<br /> # network notation unless the perl module Net::CIDR is installed. You<br /> # may repeat the allow line as many times as you'd like<br /> <br /> allow ^127\.0\.0\.1$<br /> <br /> == Munin master ==<br /> <br /> Make sure the munin and apache packages are installed. If only localhost is going to be monitored, the default configuration is sufficient. Other munin nodes can be added in the <code>/etc/munin/munin.conf</code> file:<br /> <br /> # a simple host tree<br /> [localhost.localdomain]<br /> address 127.0.0.1<br /> use_node_name yes<br /> <br /> By default, the munin monitoring web page is only reached from localhost, other hosts or networks can be added in <code>/etc/apache2/conf.d/munin</code>:<br /> <br /> Allow from localhost 127.0.0.0/8 ::1 # the default setting<br /> Allow from 10.99.0.0/8 # added network<br /> <br /> The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>. <br /> <br /> <br /> <br /> [[Category: OX6]]<br /> [[Category: Administrator]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=OX_munin_scripts&diff=16915 OX munin scripts 2014-01-29T13:17:35Z

<p>Felix.Marx: /* open-xchange-munin-scripts-jolokia */</p> <hr /> <div>= How to install Munin scripts for Open-Xchange=<br /> <br /> == Support for Jolokia ==<br /> <br /> By Version 7.4.0, Munin Scripts do support [[Jolokia]] as a bridge to get their information.<br /> This has been done to get less overhead and speak with the corresponding JMX-beans directly.<br /> <br /> == Prerequisites ==<br /> <br /> Munin node and munin master must be installed and configured prior using the Munin scripts package for Open-Xchange. The installation for this core components differs on various linux distributions. For details, please visit:<br /> <br /> http://munin-monitoring.org/<br /> <br /> especially:<br /> <br /> http://munin-monitoring.org/wiki/LinuxInstallation<br /> <br /> === open-xchange-munin-scripts ===<br /> {{InstallPlugin|pluginname=open-xchange-munin-scripts|sopath=unsupported/repo|reponame=oxmunin}}<br /> <br /> === open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin-scripts for Jolokia need an additional CPAN module.<br /> <br /> <br /> jmx4perl (and its dependencies) can be easily installed with cpan if you have Perl installed:<br /> <br /> $ perl -MCPAN -e shell<br /> Terminal does not support AddHistory.<br /> cpan shell -- CPAN exploration and modules installation (v1.9205)<br /> ReadLine support available (maybe install Bundle::CPAN or Bundle::CPANxxl?)<br /> cpan[1]> install JMX::Jmx4Perl<br /> ...<br /> ...<br /> jmx4perl<br /> ========<br /> jmx4perl is a command line utility for accessing Jolokia agents<br /> (www.jolokia.org). It can be used for script based exploration <br /> and easy inspection of the JMX space.<br /> Install 'jmx4perl' ? (y/n) [y ]<br /> ....<br /> <br /> == Configuring munin-node scripts for Open-Xchange ==<br /> <br /> The configuration of the scripts is done automatically. <br /> <br /> Note: The database pool monitoring script will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. That can be verified by e.g.:<br /> <br /> # showruntimestats -x | grep "DB Pool"<br /> com.openexchange.pooling:name=DB Pool 4,NumWaiting = 0<br /> com.openexchange.pooling:name=DB Pool 4,PoolSize = 3<br /> com.openexchange.pooling:name=DB Pool 4,NumBrokenConnections = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumActive = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumIdle = 3<br /> com.openexchange.pooling:name=DB Pool 4,AvgUseTime = 4.948<br /> com.openexchange.pooling:name=DB Pool 4,MaxUseTime = 16777<br /> com.openexchange.pooling:name=DB Pool 4,MinUseTime = 0<br /> <br /> === Configuring for open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin Scripts for Jolokia do have some additional settings for [[jolokia]].<br /> <br /> <code>vim /etc/munin/plugin-conf.d/ox</code><br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | env.oxJolokiaUrl<br /> | http://localhost:8009/monitoring/jolokia<br /> | base url for jolokia. this can differ, when using ajp. Possible ajp url could be http://apacheaddress/internal/ox1/monitoring/jolokia<br /> |-<br /> | env.oxJolokiaUser<br /> | ""<br /> | <nowiki>User used for authentication with HTTP Basic Authentication.</nowiki><br /> |-<br /> | env.oxJolokiaPassword<br /> | ""<br /> | <nowiki>Password used for authentification,</nowiki><br /> |}<br /> <br /> Both, <code> env.oxJolokiaUser </code> and <code> env.oxJolokiaPassword </code> need to be set to the same value as set inside <code>jolokia.properties</code><br /> <br /> = Supplementary notes for distributed munin clients =<br /> <br /> == Munin node ==<br /> The default munin node configuration only allows connections from localhost, which means that munin master has to run on the same host. If there already is a munin master running, that master IP has to be added to the file <code>/etc/munin/munin-node.conf</code> on each node:<br /> <br /> # A list of addresses that are allowed to connect. This must be a<br /> # regular expression, since Net::Server does not understand CIDR-style<br /> # network notation unless the perl module Net::CIDR is installed. You<br /> # may repeat the allow line as many times as you'd like<br /> <br /> allow ^127\.0\.0\.1$<br /> <br /> == Munin master ==<br /> <br /> Make sure the munin and apache packages are installed. If only localhost is going to be monitored, the default configuration is sufficient. Other munin nodes can be added in the <code>/etc/munin/munin.conf</code> file:<br /> <br /> # a simple host tree<br /> [localhost.localdomain]<br /> address 127.0.0.1<br /> use_node_name yes<br /> <br /> By default, the munin monitoring web page is only reached from localhost, other hosts or networks can be added in <code>/etc/apache2/conf.d/munin</code>:<br /> <br /> Allow from localhost 127.0.0.0/8 ::1 # the default setting<br /> Allow from 10.99.0.0/8 # added network<br /> <br /> The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>. <br /> <br /> <br /> <br /> [[Category: OX6]]<br /> [[Category: Administrator]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=Jolokia&diff=16363 Jolokia 2013-11-07T15:36:39Z

<p>Felix.Marx: /* Jolokia with Grizzly */</p> <hr /> <div><div class="title">Jolokia</div><br /> <br /> '''Summary:''' This article tells you to use Jolokia, a JMX bridge, that is available vom AppSuite v7.4.0 on.<br /> <br /> __TOC__<br /> <br /> = How to interact with Jolokia for Open-Xchange=<br /> <br /> Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.<br /> <br /> By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties<br /> <br /> Additional information can be found at http://www.jolokia.org/ .<br /> <br /> == jolokia.properties ==<br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | com.openexchange.jolokia.start<br /> | false<br /> | start switch for jolokia<br /> |-<br /> | com.openexchange.jolokia.servlet.name<br /> | /monitoring/jolokia<br /> | <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki><br /> |-<br /> | com.openexchange.jolokia.user<br /> | <br /> | <nowiki>User used for authentication with HTTP Basic Authentication. If not given, Jolokia will not start!</nowiki><br /> |-<br /> | com.openexchange.jolokia.password<br /> | <br /> | <nowiki>Password used for authentification, if not set "secret" is used.</nowiki><br /> |-<br /> | com.openexchange.jolokia.restrict.to.localhost<br /> | true<br /> | <nowiki>This setting will restrict jolokia access to localhost. It is completly ignored when a jolokia-access.xml is present</nowiki><br /> |}<br /> <br /> Keep in mind that Jolokia will not start unless you set <code> com.openexchange.jolokia.start = true </code> , <code> com.openexchange.jolokia.user = yourUser</code> and to <code> com.openexchange.jolokia.password = yourPassword</code>.<br /> <br /> When using Munin-Scripts with Jolokia, this user and password also need to be changed.<br /> <br /> == Running Jolokia ==<br /> <br /> As Jolokia represents a JMX-Interface it is highly recommended '''not''' to forward it to the internet!<br /> <br /> This is by default set through the use of <code>com.openexchange.jolokia.restrict.to.localhost = true</code> and can be changed by either setting it to <code>false</code> or providing a <code>jolokia-access.xml</code> inside <code>/opt/open-xchange/etc/</code><br /> <br /> For further information how to setup this file, http://www.jolokia.org/reference/html/security.html is a good start as all those settings are usable.<br /> <br /> === Jolokia with Grizzly ===<br /> <br /> When using Grizzly and munin scripts on the same machine, you can connect to jolokia directly with the servers address, e.g.: <code>http://localhost:8009/monitoring/jolokia</code>.<br /> When connecting through another machine, a best practise is to use the same forwarding as described below.<br /> <br /> === Jolokia with AJP ===<br /> <br /> When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.<br /> <br /> An Apache proxy_ajp.conf could look like this:<br /> <code><br /> <Location /internal><br /> # restrict access to internal<br /> Order Deny,Allow<br /> Deny from all<br /> Allow from 127.0.0.1<br /> # you might add more ip addresses / networks here <br /> # if the apache is not on the same machine as the OX-server <br /> # Allow from 192.168 10 172.16<br /> </Location><br /> ...<br /> <Proxy /internal/ox1/monitoring><br /> ProxyPass ajp://oxhost1:8009/monitoring<br /> </Proxy><br /> ...<br /> </code><br /> <br /> Jolokia on oxhost1 is accessable by <code>http://apacheaddress/internal/ox1/monitoring/jolokia</code>.<br /> <br /> [[Category:AppSuite]]<br /> [[Category:Server]]<br /> [[Category:Administrator]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=OX_munin_scripts&diff=15650 OX munin scripts 2013-09-09T10:10:24Z

<p>Felix.Marx: /* Configuring for open-xchange-munin-scripts-jolokia */</p> <hr /> <div>= How to install Munin scripts for Open-Xchange=<br /> <br /> == Support for Jolokia ==<br /> <br /> By Version 7.4.0, Munin Scripts do support [[Jolokia]] as a bridge to get their information.<br /> This has been done to get less overhead and speak with the correspondending JMX-beans directly.<br /> <br /> When 7.4.0 is released, all installation restrictions and informations will be written here,<br /> as those scripts will be released as a new package.<br /> <br /> == Prerequisites ==<br /> <br /> Munin node and munin master must be installed and configured prior using the Munin scripts package for Open-Xchange. The installation for this core components differs on various linux distributions. For details, please visit:<br /> <br /> http://munin-monitoring.org/<br /> <br /> especially:<br /> <br /> http://munin-monitoring.org/wiki/LinuxInstallation<br /> <br /> === open-xchange-munin-scripts ===<br /> {{InstallPlugin|pluginname=open-xchange-munin-scripts|sopath=unsupported/repo|reponame=oxmunin}}<br /> <br /> === open-xchange-munin-scripts-jolokia ===<br /> <br /> <br /> == Configuring munin-node scripts for Open-Xchange ==<br /> <br /> The configuration of the scripts is done automatically. <br /> <br /> Note: The database pool monitoring script will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. That can be verified by e.g.:<br /> <br /> # showruntimestats -x | grep "DB Pool"<br /> com.openexchange.pooling:name=DB Pool 4,NumWaiting = 0<br /> com.openexchange.pooling:name=DB Pool 4,PoolSize = 3<br /> com.openexchange.pooling:name=DB Pool 4,NumBrokenConnections = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumActive = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumIdle = 3<br /> com.openexchange.pooling:name=DB Pool 4,AvgUseTime = 4.948<br /> com.openexchange.pooling:name=DB Pool 4,MaxUseTime = 16777<br /> com.openexchange.pooling:name=DB Pool 4,MinUseTime = 0<br /> <br /> === Configuring for open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin Scripts for Jolokia do have some additional settings for [[jolokia]].<br /> <br /> <code>vim /etc/munin/plugin-conf.d/ox</code><br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | env.oxJolokiaUrl<br /> | http://localhost:8009/monitoring/jolokia<br /> | base url for jolokia. this can differ, when using ajp. Possible ajp url could be http://apacheaddress/internal/ox1/monitoring/jolokia<br /> |-<br /> | env.oxJolokiaUser<br /> | ""<br /> | <nowiki>User used for authentication with HTTP Basic Authentication.</nowiki><br /> |-<br /> | env.oxJolokiaPassword<br /> | ""<br /> | <nowiki>Password used for authentification,</nowiki><br /> |}<br /> <br /> Both, <code> env.oxJolokiaUser </code> and <code> env.oxJolokiaPassword </code> need to be set to the same value as set inside <code>jolokia.properties</code><br /> <br /> = Supplementary notes for distributed munin clients =<br /> <br /> == Munin node ==<br /> The default munin node configuration only allows connections from localhost, which means that munin master has to run on the same host. If there already is a munin master running, that master IP has to be added to the file <code>/etc/munin/munin-node.conf</code> on each node:<br /> <br /> # A list of addresses that are allowed to connect. This must be a<br /> # regular expression, since Net::Server does not understand CIDR-style<br /> # network notation unless the perl module Net::CIDR is installed. You<br /> # may repeat the allow line as many times as you'd like<br /> <br /> allow ^127\.0\.0\.1$<br /> <br /> == Munin master ==<br /> <br /> Make sure the munin and apache packages are installed. If only localhost is going to be monitored, the default configuration is sufficient. Other munin nodes can be added in the <code>/etc/munin/munin.conf</code> file:<br /> <br /> # a simple host tree<br /> [localhost.localdomain]<br /> address 127.0.0.1<br /> use_node_name yes<br /> <br /> By default, the munin monitoring web page is only reached from localhost, other hosts or networks can be added in <code>/etc/apache2/conf.d/munin</code>:<br /> <br /> Allow from localhost 127.0.0.0/8 ::1 # the default setting<br /> Allow from 10.99.0.0/8 # added network<br /> <br /> The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>. <br /> <br /> <br /> <br /> [[Category: OX6]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=OX_munin_scripts&diff=15649 OX munin scripts 2013-09-09T10:09:06Z

<p>Felix.Marx: /* Configuring for open-xchange-munin-scripts-jolokia */</p> <hr /> <div>= How to install Munin scripts for Open-Xchange=<br /> <br /> == Support for Jolokia ==<br /> <br /> By Version 7.4.0, Munin Scripts do support [[Jolokia]] as a bridge to get their information.<br /> This has been done to get less overhead and speak with the correspondending JMX-beans directly.<br /> <br /> When 7.4.0 is released, all installation restrictions and informations will be written here,<br /> as those scripts will be released as a new package.<br /> <br /> == Prerequisites ==<br /> <br /> Munin node and munin master must be installed and configured prior using the Munin scripts package for Open-Xchange. The installation for this core components differs on various linux distributions. For details, please visit:<br /> <br /> http://munin-monitoring.org/<br /> <br /> especially:<br /> <br /> http://munin-monitoring.org/wiki/LinuxInstallation<br /> <br /> === open-xchange-munin-scripts ===<br /> {{InstallPlugin|pluginname=open-xchange-munin-scripts|sopath=unsupported/repo|reponame=oxmunin}}<br /> <br /> === open-xchange-munin-scripts-jolokia ===<br /> <br /> <br /> == Configuring munin-node scripts for Open-Xchange ==<br /> <br /> The configuration of the scripts is done automatically. <br /> <br /> Note: The database pool monitoring script will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. That can be verified by e.g.:<br /> <br /> # showruntimestats -x | grep "DB Pool"<br /> com.openexchange.pooling:name=DB Pool 4,NumWaiting = 0<br /> com.openexchange.pooling:name=DB Pool 4,PoolSize = 3<br /> com.openexchange.pooling:name=DB Pool 4,NumBrokenConnections = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumActive = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumIdle = 3<br /> com.openexchange.pooling:name=DB Pool 4,AvgUseTime = 4.948<br /> com.openexchange.pooling:name=DB Pool 4,MaxUseTime = 16777<br /> com.openexchange.pooling:name=DB Pool 4,MinUseTime = 0<br /> <br /> === Configuring for open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin Scripts for Jolokia do have some additional settings when using ajp or different user settings for [[jolokia]].<br /> <br /> <code>vim /etc/munin/plugin-conf.d/ox</code><br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | env.oxJolokiaUrl<br /> | http://localhost:8009/monitoring/jolokia<br /> | base url for jolokia. this can differ, when using ajp. Possible ajp url could be http://apacheaddress/internal/ox1/monitoring/jolokia<br /> |-<br /> | env.oxJolokiaUser<br /> | ""<br /> | <nowiki>User used for authentication with HTTP Basic Authentication.</nowiki><br /> |-<br /> | env.oxJolokiaPassword<br /> | ""<br /> | <nowiki>Password used for authentification,</nowiki><br /> |}<br /> <br /> Both, <code> env.oxJolokiaUser </code> and <code> env.oxJolokiaPassword </code> need to be set to the same value as set inside <code>jolokia.properties</code><br /> <br /> = Supplementary notes for distributed munin clients =<br /> <br /> == Munin node ==<br /> The default munin node configuration only allows connections from localhost, which means that munin master has to run on the same host. If there already is a munin master running, that master IP has to be added to the file <code>/etc/munin/munin-node.conf</code> on each node:<br /> <br /> # A list of addresses that are allowed to connect. This must be a<br /> # regular expression, since Net::Server does not understand CIDR-style<br /> # network notation unless the perl module Net::CIDR is installed. You<br /> # may repeat the allow line as many times as you'd like<br /> <br /> allow ^127\.0\.0\.1$<br /> <br /> == Munin master ==<br /> <br /> Make sure the munin and apache packages are installed. If only localhost is going to be monitored, the default configuration is sufficient. Other munin nodes can be added in the <code>/etc/munin/munin.conf</code> file:<br /> <br /> # a simple host tree<br /> [localhost.localdomain]<br /> address 127.0.0.1<br /> use_node_name yes<br /> <br /> By default, the munin monitoring web page is only reached from localhost, other hosts or networks can be added in <code>/etc/apache2/conf.d/munin</code>:<br /> <br /> Allow from localhost 127.0.0.0/8 ::1 # the default setting<br /> Allow from 10.99.0.0/8 # added network<br /> <br /> The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>. <br /> <br /> <br /> <br /> [[Category: OX6]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=Jolokia&diff=15648 Jolokia 2013-09-09T10:07:16Z

<p>Felix.Marx: /* jolokia.properties */</p> <hr /> <div>= How to interact with Jolokia for Open-Xchange=<br /> <br /> Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.<br /> <br /> By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties<br /> <br /> Additional information can be found at http://www.jolokia.org/ .<br /> <br /> == jolokia.properties ==<br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | com.openexchange.jolokia.start<br /> | false<br /> | start switch for jolokia<br /> |-<br /> | com.openexchange.jolokia.servlet.name<br /> | /monitoring/jolokia<br /> | <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki><br /> |-<br /> | com.openexchange.jolokia.user<br /> | <br /> | <nowiki>User used for authentication with HTTP Basic Authentication. If not given, no authentication is used.</nowiki><br /> |-<br /> | com.openexchange.jolokia.password<br /> | <br /> | <nowiki>Password used for authentification, if not set "secret" is used. Only needed if com.openexchange.jolokia.user is used</nowiki><br /> |-<br /> | com.openexchange.jolokia.restrict.to.localhost<br /> | true<br /> | <nowiki>This setting will restrict jolokia access to localhost. It is completly ignored when a jolokia-access.xml is present</nowiki><br /> |}<br /> <br /> Keep in mind that Jolokia will not start, unless you set <code> com.openexchange.jolokia.start = true </code> , <code> com.openexchange.jolokia.user = "yourUser"</code> and to <code> com.openexchange.jolokia.password = "yourPassword"</code>.<br /> <br /> When using Munin-Scripts with Jolokia, this user and password also need to be changed.<br /> <br /> == Things to mention about Jolokia ==<br /> <br /> As Jolokia represents a JMX-Interface it is highly recommended to not forward it to the internet!<br /> This is by default set through the use of <code>com.openexchange.jolokia.restrict.to.localhost = true</code> and can be changed by either setting it to <code>false</code> or providing a <code>jolokia-access.xml</code> inside <code>/opt/open-xchange/etc/</code><br /> <br /> for further information how to setup this file, http://www.jolokia.org/reference/html/security.html is a good start as all those settings are usable.<br /> <br /> === Jolokia with Grizzly ===<br /> <br /> When using Grizzly, you can connect to jolokia directly with the servers address, e.g.: http://oxserver1:8009/monitoring/jolokia<br /> <br /> === Jolokia with AJP ===<br /> <br /> When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.<br /> <br /> An Apache proxy_ajp.conf could look like this:<br /> <code><br /> <Location /internal><br /> # restrict access to internal<br /> Order Deny,Allow<br /> Deny from all<br /> Allow from 127.0.0.1<br /> # you might add more ip addresses / networks here <br /> # if the apache is not on the same machine as the OX-server <br /> # Allow from 192.168 10 172.16<br /> </Location><br /> ...<br /> <Proxy /internal/ox1/monitoring><br /> ProxyPass ajp://oxhost1:8009/monitoring<br /> </Proxy><br /> ...<br /> </code><br /> <br /> Jolokia on oxhost1 is accessable by http://apacheaddress/internal/ox1/monitoring/jolokia .</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=Jolokia&diff=15647 Jolokia 2013-09-09T09:42:34Z

<p>Felix.Marx: /* jolokia.properties */</p> <hr /> <div>= How to interact with Jolokia for Open-Xchange=<br /> <br /> Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.<br /> <br /> By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties<br /> <br /> Additional information can be found at http://www.jolokia.org/ .<br /> <br /> == jolokia.properties ==<br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | com.openexchange.jolokia.start<br /> | false<br /> | start switch for jolokia<br /> |-<br /> | com.openexchange.jolokia.servlet.name<br /> | /monitoring/jolokia<br /> | <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki><br /> |-<br /> | com.openexchange.jolokia.user<br /> | <br /> | <nowiki>User used for authentication with HTTP Basic Authentication. If not given, no authentication is used.</nowiki><br /> |-<br /> | com.openexchange.jolokia.password<br /> | <br /> | <nowiki>Password used for authentification, if not set "secret" is used. Only needed if com.openexchange.jolokia.user is used</nowiki><br /> |-<br /> | com.openexchange.jolokia.restrict.to.localhost<br /> | true<br /> | <nowiki>This setting will restrict jolokia access to localhost. It is completly ignored when a jolokia-access.xml is present</nowiki><br /> |}<br /> <br /> == Things to mention about Jolokia ==<br /> <br /> As Jolokia represents a JMX-Interface it is highly recommended to not forward it to the internet!<br /> This is by default set through the use of <code>com.openexchange.jolokia.restrict.to.localhost = true</code> and can be changed by either setting it to <code>false</code> or providing a <code>jolokia-access.xml</code> inside <code>/opt/open-xchange/etc/</code><br /> <br /> for further information how to setup this file, http://www.jolokia.org/reference/html/security.html is a good start as all those settings are usable.<br /> <br /> === Jolokia with Grizzly ===<br /> <br /> When using Grizzly, you can connect to jolokia directly with the servers address, e.g.: http://oxserver1:8009/monitoring/jolokia<br /> <br /> === Jolokia with AJP ===<br /> <br /> When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.<br /> <br /> An Apache proxy_ajp.conf could look like this:<br /> <code><br /> <Location /internal><br /> # restrict access to internal<br /> Order Deny,Allow<br /> Deny from all<br /> Allow from 127.0.0.1<br /> # you might add more ip addresses / networks here <br /> # if the apache is not on the same machine as the OX-server <br /> # Allow from 192.168 10 172.16<br /> </Location><br /> ...<br /> <Proxy /internal/ox1/monitoring><br /> ProxyPass ajp://oxhost1:8009/monitoring<br /> </Proxy><br /> ...<br /> </code><br /> <br /> Jolokia on oxhost1 is accessable by http://apacheaddress/internal/ox1/monitoring/jolokia .</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=Jolokia&diff=15641 Jolokia 2013-09-06T07:31:34Z

<p>Felix.Marx: </p> <hr /> <div>= How to interact with Jolokia for Open-Xchange=<br /> <br /> Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.<br /> <br /> By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties<br /> <br /> Additional information can be found at http://www.jolokia.org/ .<br /> <br /> == jolokia.properties ==<br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | com.openexchange.jolokia.start<br /> | false<br /> | start switch for jolokia<br /> |-<br /> | com.openexchange.jolokia.servlet.name<br /> | /monitoring/jolokia<br /> | <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki><br /> |-<br /> | com.openexchange.jolokia.user<br /> | oxadmin<br /> | <nowiki>User used for authentication with HTTP Basic Authentication. If not given, no authentication is used.</nowiki><br /> |-<br /> | com.openexchange.jolokia.password<br /> | secret<br /> | <nowiki>Password used for authentification, if not set "secret" is used. Only needed if com.openexchange.jolokia.user is used</nowiki><br /> |-<br /> | com.openexchange.jolokia.restrict.to.localhost<br /> | true<br /> | <nowiki>This setting will restrict jolokia access to localhost. It is completly ignored when a jolokia-access.xml is present</nowiki><br /> |}<br /> <br /> == Things to mention about Jolokia ==<br /> <br /> As Jolokia represents a JMX-Interface it is highly recommended to not forward it to the internet!<br /> This is by default set through the use of <code>com.openexchange.jolokia.restrict.to.localhost = true</code> and can be changed by either setting it to <code>false</code> or providing a <code>jolokia-access.xml</code> inside <code>/opt/open-xchange/etc/</code><br /> <br /> for further information how to setup this file, http://www.jolokia.org/reference/html/security.html is a good start as all those settings are usable.<br /> <br /> === Jolokia with Grizzly ===<br /> <br /> When using Grizzly, you can connect to jolokia directly with the servers address, e.g.: http://oxserver1:8009/monitoring/jolokia<br /> <br /> === Jolokia with AJP ===<br /> <br /> When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.<br /> <br /> An Apache proxy_ajp.conf could look like this:<br /> <code><br /> <Location /internal><br /> # restrict access to internal<br /> Order Deny,Allow<br /> Deny from all<br /> Allow from 127.0.0.1<br /> # you might add more ip addresses / networks here <br /> # if the apache is not on the same machine as the OX-server <br /> # Allow from 192.168 10 172.16<br /> </Location><br /> ...<br /> <Proxy /internal/ox1/monitoring><br /> ProxyPass ajp://oxhost1:8009/monitoring<br /> </Proxy><br /> ...<br /> </code><br /> <br /> Jolokia on oxhost1 is accessable by http://apacheaddress/internal/ox1/monitoring/jolokia .</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=Jolokia&diff=15640 Jolokia 2013-09-06T07:23:45Z

<p>Felix.Marx: /* jolokia.properties */</p> <hr /> <div>= How to interact with Jolokia for Open-Xchange=<br /> <br /> Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.<br /> <br /> By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties<br /> <br /> Additional information can be found at http://www.jolokia.org/ .<br /> <br /> == jolokia.properties ==<br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | com.openexchange.jolokia.start<br /> | false<br /> | start switch for jolokia<br /> |-<br /> | com.openexchange.jolokia.servlet.name<br /> | /monitoring/jolokia<br /> | <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki><br /> |-<br /> | com.openexchange.jolokia.user<br /> | oxadmin<br /> | <nowiki>User used for authentication with HTTP Basic Authentication. If not given, no authentication is used.</nowiki><br /> |-<br /> | com.openexchange.jolokia.password<br /> | secret<br /> | <nowiki>Password used for authentification, if not set "secret" is used. Only needed if com.openexchange.jolokia.user is used</nowiki><br /> |-<br /> | com.openexchange.jolokia.restrict.to.localhost<br /> | true<br /> | <nowiki>This setting will restrict jolokia access to localhost. It is completly ignored when a jolokia-access.xml is present</nowiki><br /> |}<br /> <br /> == Things to mention about Jolokia ==<br /> <br /> As Jolokia represents a JMX-Interface it is highly recommended to not forward it to the internet!<br /> <br /> === Jolokia with Grizzly ===<br /> <br /> When using Grizzly, you can connect to jolokia directly with the servers address, e.g.: http://oxserver1:8009/monitoring/jolokia<br /> <br /> === Jolokia with AJP ===<br /> <br /> When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.<br /> <br /> An Apache proxy_ajp.conf could look like this:<br /> <code><br /> <Location /internal><br /> # restrict access to internal<br /> Order Deny,Allow<br /> Deny from all<br /> Allow from 127.0.0.1<br /> # you might add more ip addresses / networks here <br /> # if the apache is not on the same machine as the OX-server <br /> # Allow from 192.168 10 172.16<br /> </Location><br /> ...<br /> <Proxy /internal/ox1/monitoring><br /> ProxyPass ajp://oxhost1:8009/monitoring<br /> </Proxy><br /> ...<br /> </code><br /> <br /> Jolokia on oxhost1 is accessable by http://apacheaddress/internal/ox1/monitoring/jolokia .</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=Jolokia&diff=15567 Jolokia 2013-08-30T11:21:42Z

<p>Felix.Marx: /* Jolokia with Grizzly */</p> <hr /> <div>= How to interact with Jolokia for Open-Xchange=<br /> <br /> Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.<br /> <br /> By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties<br /> <br /> Additional information can be found at http://www.jolokia.org/ .<br /> <br /> == jolokia.properties ==<br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | com.openexchange.jolokia.start<br /> | false<br /> | start switch for jolokia<br /> |-<br /> | com.openexchange.jolokia.servlet.name<br /> | /monitoring/jolokia<br /> | <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki><br /> |-<br /> | com.openexchange.jolokia.user<br /> | oxadmin<br /> | <nowiki>User used for authentication with HTTP Basic Authentication. If not given, no authentication is used.</nowiki><br /> |-<br /> | com.openexchange.jolokia.password<br /> | secret<br /> | <nowiki>Password used for authentification, if not set "secret" is used. Only needed if com.openexchange.jolokia.user is used</nowiki><br /> |}<br /> <br /> == Things to mention about Jolokia ==<br /> <br /> As Jolokia represents a JMX-Interface it is highly recommended to not forward it to the internet!<br /> <br /> === Jolokia with Grizzly ===<br /> <br /> When using Grizzly, you can connect to jolokia directly with the servers address, e.g.: http://oxserver1:8009/monitoring/jolokia<br /> <br /> === Jolokia with AJP ===<br /> <br /> When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.<br /> <br /> An Apache proxy_ajp.conf could look like this:<br /> <code><br /> <Location /internal><br /> # restrict access to internal<br /> Order Deny,Allow<br /> Deny from all<br /> Allow from 127.0.0.1<br /> # you might add more ip addresses / networks here <br /> # if the apache is not on the same machine as the OX-server <br /> # Allow from 192.168 10 172.16<br /> </Location><br /> ...<br /> <Proxy /internal/ox1/monitoring><br /> ProxyPass ajp://oxhost1:8009/monitoring<br /> </Proxy><br /> ...<br /> </code><br /> <br /> Jolokia on oxhost1 is accessable by http://apacheaddress/internal/ox1/monitoring/jolokia .</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=OX_munin_scripts&diff=15163 OX munin scripts 2013-08-02T09:35:45Z

<p>Felix.Marx: /* How to install Munin scripts for Open-Xchange */</p> <hr /> <div>= How to install Munin scripts for Open-Xchange=<br /> <br /> == Support for Jolokia ==<br /> <br /> By Version 7.4.0, Munin Scripts do support [[Jolokia]] as a bridge to get their information.<br /> This has been done to get less overhead and speak with the correspondending JMX-beans directly.<br /> <br /> When 7.4.0 is released, all installation restrictions and informations will be written here,<br /> as those scripts will be released as a new package.<br /> <br /> == Prerequisites ==<br /> <br /> Munin node and munin master must be installed and configured prior using the Munin scripts package for Open-Xchange. The installation for this core components differs on various linux distributions. For details, please visit:<br /> <br /> http://munin-monitoring.org/<br /> <br /> especially:<br /> <br /> http://munin-monitoring.org/wiki/LinuxInstallation<br /> <br /> === open-xchange-munin-scripts ===<br /> {{InstallPlugin|pluginname=open-xchange-munin-scripts|sopath=unsupported/repo|reponame=oxmunin}}<br /> <br /> === open-xchange-munin-scripts-jolokia ===<br /> <br /> <br /> == Configuring munin-node scripts for Open-Xchange ==<br /> <br /> The configuration of the scripts is done automatically. <br /> <br /> Note: The database pool monitoring script will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. That can be verified by e.g.:<br /> <br /> # showruntimestats -x | grep "DB Pool"<br /> com.openexchange.pooling:name=DB Pool 4,NumWaiting = 0<br /> com.openexchange.pooling:name=DB Pool 4,PoolSize = 3<br /> com.openexchange.pooling:name=DB Pool 4,NumBrokenConnections = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumActive = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumIdle = 3<br /> com.openexchange.pooling:name=DB Pool 4,AvgUseTime = 4.948<br /> com.openexchange.pooling:name=DB Pool 4,MaxUseTime = 16777<br /> com.openexchange.pooling:name=DB Pool 4,MinUseTime = 0<br /> <br /> === Configuring for open-xchange-munin-scripts-jolokia ===<br /> <br /> Munin Scripts for Jolokia do have some additional settings when using ajp or different user settings for [[jolokia]].<br /> <br /> <code>vim /etc/munin/plugin-conf.d/ox</code><br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | env.oxJolokiaUrl<br /> | http://localhost:8009/monitoring/jolokia<br /> | base url for jolokia. this can differ, when using ajp. Possible ajp url could be http://apacheaddress/internal/ox1/monitoring/jolokia<br /> |-<br /> | env.oxJolokiaUser<br /> | oxadmin<br /> | <nowiki>User used for authentication with HTTP Basic Authentication.</nowiki><br /> |-<br /> | env.oxJolokiaPassword<br /> | secret<br /> | <nowiki>Password used for authentification,</nowiki><br /> |}<br /> <br /> = Supplementary notes for distributed munin clients =<br /> <br /> == Munin node ==<br /> The default munin node configuration only allows connections from localhost, which means that munin master has to run on the same host. If there already is a munin master running, that master IP has to be added to the file <code>/etc/munin/munin-node.conf</code> on each node:<br /> <br /> # A list of addresses that are allowed to connect. This must be a<br /> # regular expression, since Net::Server does not understand CIDR-style<br /> # network notation unless the perl module Net::CIDR is installed. You<br /> # may repeat the allow line as many times as you'd like<br /> <br /> allow ^127\.0\.0\.1$<br /> <br /> == Munin master ==<br /> <br /> Make sure the munin and apache packages are installed. If only localhost is going to be monitored, the default configuration is sufficient. Other munin nodes can be added in the <code>/etc/munin/munin.conf</code> file:<br /> <br /> # a simple host tree<br /> [localhost.localdomain]<br /> address 127.0.0.1<br /> use_node_name yes<br /> <br /> By default, the munin monitoring web page is only reached from localhost, other hosts or networks can be added in <code>/etc/apache2/conf.d/munin</code>:<br /> <br /> Allow from localhost 127.0.0.0/8 ::1 # the default setting<br /> Allow from 10.99.0.0/8 # added network<br /> <br /> The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>. <br /> <br /> <br /> <br /> [[Category: OX6]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=Jolokia&diff=15162 Jolokia 2013-08-02T09:19:02Z

<p>Felix.Marx: /* Jolokia with Grizzly */</p> <hr /> <div>= How to interact with Jolokia for Open-Xchange=<br /> <br /> Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.<br /> <br /> By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties<br /> <br /> Additional information can be found at http://www.jolokia.org/ .<br /> <br /> == jolokia.properties ==<br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | com.openexchange.jolokia.start<br /> | false<br /> | start switch for jolokia<br /> |-<br /> | com.openexchange.jolokia.servlet.name<br /> | /monitoring/jolokia<br /> | <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki><br /> |-<br /> | com.openexchange.jolokia.user<br /> | oxadmin<br /> | <nowiki>User used for authentication with HTTP Basic Authentication. If not given, no authentication is used.</nowiki><br /> |-<br /> | com.openexchange.jolokia.password<br /> | secret<br /> | <nowiki>Password used for authentification, if not set "secret" is used. Only needed if com.openexchange.jolokia.user is used</nowiki><br /> |}<br /> <br /> == Things to mention about Jolokia ==<br /> <br /> As Jolokia represents a JMX-Interface it is highly recommended to not forward it to the internet!<br /> <br /> === Jolokia with Grizzly ===<br /> <br /> When using Grizzly, you can connect to jolokia directly with the servers address, e.g.: http://oxserver1.8009/monitoring/jolokia<br /> <br /> === Jolokia with AJP ===<br /> <br /> When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.<br /> <br /> An Apache proxy_ajp.conf could look like this:<br /> <code><br /> <Location /internal><br /> # restrict access to internal<br /> Order Deny,Allow<br /> Deny from all<br /> Allow from 127.0.0.1<br /> # you might add more ip addresses / networks here <br /> # if the apache is not on the same machine as the OX-server <br /> # Allow from 192.168 10 172.16<br /> </Location><br /> ...<br /> <Proxy /internal/ox1/monitoring><br /> ProxyPass ajp://oxhost1:8009/monitoring<br /> </Proxy><br /> ...<br /> </code><br /> <br /> Jolokia on oxhost1 is accessable by http://apacheaddress/internal/ox1/monitoring/jolokia .</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=Jolokia&diff=15161 Jolokia 2013-08-02T09:18:44Z

<p>Felix.Marx: Created page with "= How to interact with Jolokia for Open-Xchange= Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP. By Version 7.4.0 ongoing, it is located inside Open-Xcha..."</p> <hr /> <div>= How to interact with Jolokia for Open-Xchange=<br /> <br /> Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.<br /> <br /> By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties<br /> <br /> Additional information can be found at http://www.jolokia.org/ .<br /> <br /> == jolokia.properties ==<br /> {|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'<br /> ! scope="col" width="30%" | Key<br /> ! scope="col" width="20%" | Default value<br /> ! scope="col" width="35%" | Comment<br /> |-<br /> | com.openexchange.jolokia.start<br /> | false<br /> | start switch for jolokia<br /> |-<br /> | com.openexchange.jolokia.servlet.name<br /> | /monitoring/jolokia<br /> | <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki><br /> |-<br /> | com.openexchange.jolokia.user<br /> | oxadmin<br /> | <nowiki>User used for authentication with HTTP Basic Authentication. If not given, no authentication is used.</nowiki><br /> |-<br /> | com.openexchange.jolokia.password<br /> | secret<br /> | <nowiki>Password used for authentification, if not set "secret" is used. Only needed if com.openexchange.jolokia.user is used</nowiki><br /> |}<br /> <br /> == Things to mention about Jolokia ==<br /> <br /> As Jolokia represents a JMX-Interface it is highly recommended to not forward it to the internet!<br /> <br /> === Jolokia with Grizzly ===<br /> <br /> When using Grizzly, you can connect to jolokia directly with the servers address, e.g.: http://oxserver1.8009/monitoring/jolokia<br /> <br /> When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.<br /> <br /> An Apache proxy_ajp.conf could look like this:<br /> <code><br /> <Location /internal><br /> # restrict access to internal<br /> Order Deny,Allow<br /> Deny from all<br /> Allow from 127.0.0.1<br /> # you might add more ip addresses / networks here <br /> # if the apache is not on the same machine as the OX-server <br /> # Allow from 192.168 10 172.16<br /> </Location><br /> ...<br /> <Proxy /internal/ox1/monitoring><br /> ProxyPass ajp://oxhost1:8009/monitoring<br /> </Proxy><br /> ...<br /> </code><br /> <br /> Jolokia on oxhost1 is accessable by http://apacheaddress/internal/ox1/monitoring/jolokia .</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=OX_munin_scripts&diff=15160 OX munin scripts 2013-08-02T07:10:35Z

<p>Felix.Marx: /* Support for Jolokia */</p> <hr /> <div>= How to install Munin scripts for Open-Xchange=<br /> <br /> == Support for Jolokia ==<br /> <br /> By Version 7.4.0, Munin Scripts do support Jolokia as a bridge to get their information.<br /> This has been done to get less overhead and speak with the correspondending JMX-beans directly.<br /> <br /> When 7.4.0 is released, all installation restrictions and informations will be written here,<br /> as those scripts will be released as a new package.<br /> <br /> == Prerequisites ==<br /> <br /> Munin node and munin master must be installed and configured prior using the Munin scripts package for Open-Xchange. The installation for this core components differs on various linux distributions. For details, please visit:<br /> <br /> http://munin-monitoring.org/<br /> <br /> especially:<br /> <br /> http://munin-monitoring.org/wiki/LinuxInstallation<br /> <br /> {{InstallPlugin|pluginname=open-xchange-munin-scripts|sopath=unsupported/repo|reponame=oxmunin}}<br /> <br /> == Configuring munin-node scripts for Open-Xchange ==<br /> <br /> The configuration of the scripts is done automatically. <br /> <br /> Note: The database pool monitoring script will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. That can be verified by e.g.:<br /> <br /> # showruntimestats -x | grep "DB Pool"<br /> com.openexchange.pooling:name=DB Pool 4,NumWaiting = 0<br /> com.openexchange.pooling:name=DB Pool 4,PoolSize = 3<br /> com.openexchange.pooling:name=DB Pool 4,NumBrokenConnections = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumActive = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumIdle = 3<br /> com.openexchange.pooling:name=DB Pool 4,AvgUseTime = 4.948<br /> com.openexchange.pooling:name=DB Pool 4,MaxUseTime = 16777<br /> com.openexchange.pooling:name=DB Pool 4,MinUseTime = 0<br /> <br /> = Supplementary notes for distributed munin clients =<br /> <br /> == Munin node ==<br /> The default munin node configuration only allows connections from localhost, which means that munin master has to run on the same host. If there already is a munin master running, that master IP has to be added to the file <code>/etc/munin/munin-node.conf</code> on each node:<br /> <br /> # A list of addresses that are allowed to connect. This must be a<br /> # regular expression, since Net::Server does not understand CIDR-style<br /> # network notation unless the perl module Net::CIDR is installed. You<br /> # may repeat the allow line as many times as you'd like<br /> <br /> allow ^127\.0\.0\.1$<br /> <br /> == Munin master ==<br /> <br /> Make sure the munin and apache packages are installed. If only localhost is going to be monitored, the default configuration is sufficient. Other munin nodes can be added in the <code>/etc/munin/munin.conf</code> file:<br /> <br /> # a simple host tree<br /> [localhost.localdomain]<br /> address 127.0.0.1<br /> use_node_name yes<br /> <br /> By default, the munin monitoring web page is only reached from localhost, other hosts or networks can be added in <code>/etc/apache2/conf.d/munin</code>:<br /> <br /> Allow from localhost 127.0.0.0/8 ::1 # the default setting<br /> Allow from 10.99.0.0/8 # added network<br /> <br /> The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>. <br /> <br /> <br /> <br /> [[Category: OX6]]</div>

Felix.Marx https://wiki.open-xchange.com/wiki/index.php?title=OX_munin_scripts&diff=15159 OX munin scripts 2013-08-02T07:02:43Z

<p>Felix.Marx: /* How to install Munin scripts for Open-Xchange */</p> <hr /> <div>= How to install Munin scripts for Open-Xchange=<br /> <br /> == Support for Jolokia ==<br /> <br /> By Version 7.4.0, Munin Scripts do support Jolokia as a bridge to get their information.<br /> This has been done to get less overhead and speak with the correspondending JMX-beans directly.<br /> <br /> When 7.4.0 is released, all installation restrictions and informations will be written here.<br /> <br /> == Prerequisites ==<br /> <br /> Munin node and munin master must be installed and configured prior using the Munin scripts package for Open-Xchange. The installation for this core components differs on various linux distributions. For details, please visit:<br /> <br /> http://munin-monitoring.org/<br /> <br /> especially:<br /> <br /> http://munin-monitoring.org/wiki/LinuxInstallation<br /> <br /> {{InstallPlugin|pluginname=open-xchange-munin-scripts|sopath=unsupported/repo|reponame=oxmunin}}<br /> <br /> == Configuring munin-node scripts for Open-Xchange ==<br /> <br /> The configuration of the scripts is done automatically. <br /> <br /> Note: The database pool monitoring script will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. That can be verified by e.g.:<br /> <br /> # showruntimestats -x | grep "DB Pool"<br /> com.openexchange.pooling:name=DB Pool 4,NumWaiting = 0<br /> com.openexchange.pooling:name=DB Pool 4,PoolSize = 3<br /> com.openexchange.pooling:name=DB Pool 4,NumBrokenConnections = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumActive = 0<br /> com.openexchange.pooling:name=DB Pool 4,NumIdle = 3<br /> com.openexchange.pooling:name=DB Pool 4,AvgUseTime = 4.948<br /> com.openexchange.pooling:name=DB Pool 4,MaxUseTime = 16777<br /> com.openexchange.pooling:name=DB Pool 4,MinUseTime = 0<br /> <br /> = Supplementary notes for distributed munin clients =<br /> <br /> == Munin node ==<br /> The default munin node configuration only allows connections from localhost, which means that munin master has to run on the same host. If there already is a munin master running, that master IP has to be added to the file <code>/etc/munin/munin-node.conf</code> on each node:<br /> <br /> # A list of addresses that are allowed to connect. This must be a<br /> # regular expression, since Net::Server does not understand CIDR-style<br /> # network notation unless the perl module Net::CIDR is installed. You<br /> # may repeat the allow line as many times as you'd like<br /> <br /> allow ^127\.0\.0\.1$<br /> <br /> == Munin master ==<br /> <br /> Make sure the munin and apache packages are installed. If only localhost is going to be monitored, the default configuration is sufficient. Other munin nodes can be added in the <code>/etc/munin/munin.conf</code> file:<br /> <br /> # a simple host tree<br /> [localhost.localdomain]<br /> address 127.0.0.1<br /> use_node_name yes<br /> <br /> By default, the munin monitoring web page is only reached from localhost, other hosts or networks can be added in <code>/etc/apache2/conf.d/munin</code>:<br /> <br /> Allow from localhost 127.0.0.0/8 ::1 # the default setting<br /> Allow from 10.99.0.0/8 # added network<br /> <br /> The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>. <br /> <br /> <br /> <br /> [[Category: OX6]]</div>

Felix.Marx