When connecting SOGo with MySQL, you may either use a remote or a local server.
To use a remote server, you’ll configure SOGo with such directives:
SOGoProfileURL = "mysql://sogouser:sogopass@mysqlhost:3306/sogodbname/sogo_user_profile"; To use a local MySQL server, you will need to access the mysql.socket file. And when it is secured with chroot&friends, the mysql.sock may not be where SOGo expects it. I have mine located at /var/chroot/mysql/mysql.sock. Normally, you would modify my.cnf to refer to the MySQL socket file.Continue reading...
Here’s a quick trick that allows automatic installation of WordPress on an HTTP server.
The normal process is: browse to wordpress.com, grab the archive locally, upload to your server, unzip and run the installer. Sometimes, you even have to unzip locally and then upload the whole sets of files to the server.
The automatic process can be done using Instant Install.Continue reading...
On my munin-node-1.4.5p5, I can only graph HTTP activity ; no HTTPS. There is a plugin though that enables graphing both HTTP and HTTPS.
Grab the plugin here ; Copy it in /etc/munin/plugins/ in replacement for the original Munin plugin ; Configure /etc/munin/plugin-conf.d/openbsd-packages to know about the Apache ports to monitor: (...) [apache_*] env.ssl yes env.port 80 env.ports 443 (...) Restart munin_node Wait about 5 minutes and check your new shiny HTTP/SSL graphs!Continue reading...
This article is about monitoring NetBSD with Munin, using munin-node. I already configured a running munin-server on OpenBSD ; so I could simply use it to graph my NetBSD metrics. Here’s, we’ll go through installing both node and server on NetBSD.
ATTOW, pkgsrc provides Munin v1.3.x. So I’m gonna build munin-node from pkgsrc-wip. Once this is done, proceed to installation and configuration on the node to be monitored:Continue reading...
When you host a secondary MX server and the primary SMTP is out of order for more than 5 days, you will start to loose e-mail from the MX backup. There is a (temporary) easy way to deal with this: raise the retention time of the Postfix mail queue.
Edit postfix/main.cf, add
maximal_queue_lifetime = 30d and reload Postfix. You’re done!
Keep an eye on the mail queue while the primary MX is down.Continue reading...