Skip to main content

munin apache server-status

When you want to monitor Apache with Munin, you have to let Munin node access the extended server status.

The server status is available on http://server/server-status and it has to be secured.

Firts, enble Extended Server Status.
In httpd.conf (or whatever is used by you installation)
ExtendedStatus On
Second, in the same file:

<Location /server-status>    SetHandler server-status    Order deny,allow    Deny from all    Allow from 127.0.0.1</Location>

With these settings, you should get Apache accesses graph on Munin.

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

OpenVPN without TLS

OpenVPN 2.7 will remove the functionality to run a VPN without TLS. DEPRECATION: No tls-client or tls-server option in configuration detected. OpenVPN 2.7 will remove the functionality to run a VPN without TLS. See the examples section in the manual page for examples of a similar quick setup with peer-fingerprint. Global actions Switching to TLS based is about generating certificates for clients. In order to achieve that, these are the steps: Install EasyRSA v3 on the system Initialize installed EasyRSA Generate server certificate and key Generate client certificate and key (operation to be repeated for each client to be connected) The perfect setting would be to have a separate CA machine, generate the certificates