Month: September 2013

Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp

by

The other day we faced an issue with the memory and the exact error was can be described as below:

[Mon Sep 30 10:00:29 2013] [error] [client 117.196.128.34] (12)Cannot allocate memory: couldn’t create child process: /opt/suphp/sbin/suphp for /home/unier/public_html/index.php
[Mon Sep 30 10:00:29 2013] [error] [client 117.196.128.34] File does not exist: /home/unier/public_html/500.shtml

On the first look, we should check the Apache conf for any memory limits set  in the Apache configuration file.  You can check this using the below command

# grep RLimitMEM /usr/local/apache/conf/httpd.conf

If you are seeing any result like the below one,  try disabling or removing the line in the httpd.conf file, and restarting Apache.

Read more

Mail bouncing from Microsoft’s Exchange email service in Plesk

by

Mails from microsoft exchange email services are failed in plesk (qmail). Upon investigation we found that the grey list filter in plesk 10 is blocking server that are on “dsl|pool|broadband|hsd” address ranges. In this case it would be Microsofts cloud anti-spam service that is on “pool” addresses.

Some Microsofts cloud anti-spam servers are;

co9outboundpool.messaging.microsoft.com
db8outboundpool.messaging.microsoft.com
db9outboundpool.messaging.microsoft.com
am1outboundpool.messaging.microsoft.com

Log entries are like this

Read more

R1Soft CDP Error While restoring : Connection refused

by

Moslty this is caused due to buagent not running. Even if we tried to restart buagent,it will not start and status will be showing “buagent (no pid file) not running”

Check /var/log/messages to see whether kernel module is missing or not. If it is showing any missing kernel modules, you can install kernel modules by simply running  r1soft-cki in the command prompt

# /etc/init.d/buagent restart

# /etc/init.d/buagent status
/etc/init.d/buagent status: buagent (no pid file) not running

Read more

Cannot start Postfix – Postfix integrity check failed Error

by
Here is what you can do when you are unable to start Postfix and you are getting Postfix integrity check failed Error. 
Here is the scenario:
 

Postfix was not running and an attempt to restart Postfix was failing with the following error in maillog.

mail postfix/postfix-script: fatal: Postfix integrity check failed!
mail postfix/postfix-script: fatal: the Postfix mail system is not running

We have tried several number of solutions and after a bit of research, we found the following command works and running that resolved the issue.

Read more

ntVersionCheck : New release v1.1.0

by

cPanel plugin for finding the outdated applications in the server. Currently the plugin is configured for wordpress and joomla installations.

Features

  • Find all outdated wordpress and joomla applications in the cPanel Server
  • Display the wordpress and joomla versions with color difference for visibility
  • News, Announce the latest news related with application vulnerabilities and plugin updates
  • The installations are grouped by user and reseller wise
  • One click update available for future releases

    Read more

SecurityException in Application.cpp:175: Calling user is not webserver user / SuPHP / cPanel

by

We were ended-up in this message after running EasyApache on one of our cPanel servers with mod_suphp. If we set the PHP handler to DSO, PHP applications were working fine; but when we try to switch the handler to SuPHP it started showing the above error message with 500 error code.

The actual cause for this error is given in the messsage in fact, which is “Calling user is not webserver user”. As per the security standards of SuPHP, the user invoking SuPHP must be defined in suphp.conf file and should match the user invoking it. So for a cPanel server, it should be call by the HTTP user which is “nobody”. In our case it was set to “apache” even there is no active “apache” user on a cPanel server. I met this error on a latest cPanel build; so I guess this is a bug with their latest EA3. To correct the issue, I set the value of “webserver_user” to “nobody” in /opt/suphp/etc/suphp.conf and restarted apache service.

Read more