Category Archives: Servers

Hardware : HP Proliant DL160 chipset driver

Chipset driver for Windows Server on HP Proliant DL160 might appear as “Unknown device” in the Device Manager and listed as : ACPI\HPQ000B\0 ACPI\HPQ000B *HPQ000B The proper driver on HP Web site will be listed as : HP Proliant Management Controller Driver (Device ID: HPQ000B)

Linux : How to create a bridge interface on RHEL/CentOS

A bridge interface is actually a virtual interface handled by a config file on your Linux system. Creating a bridge is quite simple, just follow those steps and you’re all set! 1. Create the bridge interface configuration file : vi /etc/sysconfig/network-scripts/ifcfg-br0 Add the the following parameters : DEVICE=br0 TYPE=Bridge BOOTPROTO=static ONBOOT=yes STP=on IPADDR= NETMASK= GATEWAY=… Read More »

Qmail : Create a catch-all account with vpopmail

On the latest vpopmail release, there is a bug with the Web interface that prevent creating a catch all mail account for non-existent recipients. When pressing the catch-all button, a blank page is returned. Here is the steps to create the catch-all manually instead of using the WebUI. This example assume that your domain name… Read More »

Linux : How to install source rpm on RHEL/CentOS

Here is a quick tutorial regarding how to install a source RPM on RHEL/CentOS Linux. 1. Prepare the build environment and get the dependencies. Do those following command under your root home directory : yum install rpm-build redhat-rpm-config gcc make mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS} 2. Put the source rpm file at the root of your home directory… Read More »

Bind : validating : dlv.isc.org SOA: got insecure response; parent indicates it should be secure

Have you notified this error message in the logs since bind-9.8.2 update? named: validating @0x7fc170001550: dlv.isc.org SOA: got insecure response; parent indicates it should be secure named: error (insecurity proof failed) resolving ‘dlv.isc.org/DLV/IN’: 0.0.0.0#53 This is related to the new DNSSEC feature which is now enabled by default. This might indicate the DNS resolvers/forwarders you… Read More »

FreeBSD : vsftpd not configured for standalone, must be started from inetd

Getting this error message trying to start vsFTPd on FreeBSD? 500 OOPS: vsftpd: not configured for standalone, must be started from inetd Then you missed the important part shown at the end of “vsftpd.conf”! # If using vsftpd in standalone mode, uncomment the next two lines: listen=YES background=YES Just uncomment “listen=YES”, “background=YES” and start the… Read More »