Search Engine: Elastic

Article ID: 4554, created on Mar 24, 2008, last review on May 11, 2014

  • Applies to:
  • Sphera


FTP/POP/SMTP connections refused on some accounts. Getting "VDS does not exist" error when trying to restart a VDS.


This problem may occur mainly at the first ServerDirector's startup after a machine's boot.

The phenomena is that due to temporary lack of resources (which is handled later on after ServerDirector's initialization) at Sphera process boot, some VDSs inetd services (FTP,POP,SMTP) are not initiated by the sphera process of ServerDirector.

This is a known bug in SD 3.5 and 3.7, which will be fixed in SD 3.7 UP1.

A workaround for this issue is as follows:

1) Verify the problem: netstat -anp | grep 'VDS IP' | grep LISTEN
 If you can't see the sphera process listening on VDS IP and ports 21, 110, 25, then the problem exists.
2) Check that the VDS doesn't exceed disk / files quota.

3) If the VDS doesn't exceed the quota, restart the ServerDirector (sphadmin).

4) Verify by netstat -anp | grep 'VDS IP' | grep LISTEN that sphera process listen on the VDS IP and the 3 ports.

5f478287f7e74fe9b07217d8131cd741 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF