I recently decided to do a fresh CentOS install on a web server with a minimal amount of sites on it because it seemed easier than attempting to upgrade everything. With a fresh install I figured I would be forced to get everything completed quicker. The server was upgraded from CentOS 5.1 to CentOS 5.3 and from ISPConfig 2.X to ISPConfig 3.X. One of the virtual host configurations was for a Nagios server that monitors a fairly large list of servers running various services from basic server items like CPU, Load, Disk Space, etc. all the way to complex PostgreSQL statistics and other custom items. There are numerous Perl scripts to monitor PostgreSQL including check_pg_connections.pl, check_pg_lock_status.pl, check_pg_max_xid.pl, check_pg_queries.pl, check_pg_time.pl, and check_pg_waiting_queries.pl. The scripts use the DBD-Pg Perl module to make a connection (remote or local) to PostgreSQL servers.
I have had a server running ISPConfig 2.x for quite some time and have been wanting to make the transition to ISPConfig 3.x as soon as I had a chance. That chance presented itself earlier this weekend and I am glad to say there were no major issues thanks to the amazing how to from Falco at HowToForge. After the installation and bringing numerous sites back online I had some outside the normal installation steps to complete. These steps included things like installing/configuring SNMP, installing/configure Nagios, etc.
All appeared well when I went to sleep meaning the servers seemed to all check out when was finished and ready to catch some sleep. Anyways when I logged on the following day to check all of the sites all was still functional besides a small DNS configuration error I had made with one sub domain which was not a big deal.
If attachments are showing up in your Microsoft Outlook inbox with a modified ending such as .doc being changed to .1324DEFANGED-doc then the issue is more than likely with your mail server instead of your email client. There is an application called MailScanner that modifies the file ending as a security measure to stop any files from being executed automatically. Below I briefly discuss modifying this setting on a Linux server using ISPConfig.
The easiest way to resolve this issue on a per user basis with an ISPConfig Linux server is to disable MailScanner for that user. MailScanner does provide numerous other security checks though so it is not recommended to disable it but if you must disable the file ending modification then modify the below files.
I recently reinstalled a CentOS 5.2 server running ISPConfig using apache for virtual web hosting. The first site I was reinstalling the RapidSSL certificate for was not working. It continued to tell me that it was a non trusted self signed certificate. Eventually I figured out the only issue was that ISPConfig was not restarting the web server thus not taking the RapidSSL cert. Once I restarted the web server manually everything worked properly. A couple things to note though are exactly how to install a SSL Certificate with ISPConfig and how to regenerate the servers self signed certificate if necessary.
Installing a SSL Certificate for a Virtual Host with ISPConfig:
- Create Site: Create the hosting account using your typical methods with ISPConfig
I saw these errors after a fresh install of CentOS 5.2 during the process of preparing the server for ISPConfig. If you try to enable quotas after getting this error then quotaon will simply explain it cannot find the files like the below.