how come i get this error in whm when creating a new account:

Unable to locate proftpd.conf at /scripts/wwwacct line 1312.
Account Creation Complete!!!



how do i fix it....

Hi

Seems to be a Cpanel update prob, from the forum

"To fix this and as a work around, move server back to ProFTP."


we just moved away from Proftp and its slow speed and login problems, lol.

it seems however, that this has some effect on proftpd as well (login problems). Brought to you by the infinite wisdom from CPanel. I think, however, i found why this is happening.

... but yes, to fix it (for a quick fix) switch back to proFTPd

it seems that this is a hard code error with CPanel account creation file. THIS IS NOT 100% ACCURATE, just my best guess. But it seems that when the geniouses at DarkORB updated CPanel, they hardcoded ProFTPd without leaving any room for pure-FTPd.

For example... in the account creation file...


$logdir = "domlogs";
$ncftpdconf = "/usr/local/etc/ncftpd/conf/virtual.cf";
$proftpddir = "/etc/proftpd";
$proftpdconf = find_proftpconf();
$nameddir = "/var/named";
$namedboot = "/etc/named.boot";
$namedconf = "/etc/named.conf";
$httpconf = find_httpconf();
$domainalias = "/etc/domainalias";
$sendmailcw = "/etc/sendmail.cw";
$logout = "/var/log/wwwacct";
$cpaneludir = "/var/cpanel/users";

and then that find_proftpconf then calls:

sub find_proftpconf {
my(@LOC,$loc);
@LOC = ("/etc/proftpd.conf",
"/usr/local/etc/proftpd.conf");
foreach $loc (@LOC) {
if (-e $loc) { return $loc; }
}
die "Unable to locate proftpd.conf";
return "";
}

Hence would explain the main error. The main point being that as I have the server in pureFTPd mode, it STILL is seeking for proFTPd (and NOT looking for pure-ftpd). WHEN you convert to pure-ftpd, the conversion lets you know EXACTLY what it did with proftpd:

warning: /etc/proftpd.conf saved as /etc/proftpd.conf.rpmsave

I am looking in a way to resolve this and will post if i find anything.

CPanel forums also has a post on this as well (for your reference)

http://forums.cpanel.net/read.php?TID=7266

USE AT YOUR OWN RISK

Our resolve to problem (not official): voyage to file "/scripts/wwwacct"


First, go back to PURE-FTPd.

Then, edit the following line of code

sub find_proftpconf {
my(@LOC,$loc);
@LOC = ("/etc/proftpd.conf",
"/usr/local/etc/proftpd.conf");
foreach $loc (@LOC) {
if (-e $loc) { return $loc; }
}
die "Unable to locate proftpd.conf";
return "";
}

to

sub find_proftpconf {
my(@LOC,$loc);
@LOC = ("/etc/pure-ftpd.conf",
"/usr/local/etc/proftpd.conf");
foreach $loc (@LOC) {
if (-e $loc) { return $loc; }
}
die "Unable to locate proftpd.conf";
return "";
}

And then, restart FTP Server (just for kicks).

EcpHosting is NOT responsible for any problems this may create or for any updates that DarkORB may create. We reserve the exlusive right to be wrong. However, this was tested and worked in all of our tests (as well with old accounts). All this update does is point to the pure-ftpd file. It's just a shot. It still creates all of the FTP db files in /etc/proftpd/ as it normally should, and allows WHM account creation.

Update: if you have automatic updates enabled nightly, then you will need to fix this every day.

I wonder when/if this will ever be fixed.

Originally posted by jayjay
I wonder when/if this will ever be fixed.

One would only hope.

another fix is simple:

login via SSH as root and type this in

touch /etc/proftpd.conf

error fixed

Originally posted by spinnaweb
another fix is simple:

login via SSH as root and type this in

touch /etc/proftpd.conf

error fixed
Yep! I was about to write the same thing. This worked for me also on 4 web servers.

Excellent! Glad to find a far better fix... question... does this continue to work even ***after*** an automatic cpanel update?

I'm assuming it does, but you can see my concern as this once was working and now it doesn't (after a CPanel auto-update).