ProFTP gone after daily upcp - FreeBSD5.2

[Holbrookau]

After the daily scripts/upcp a couple of days ago I saw that FTP was down. This is a partial log of the update:

Ftp Setup Script Version 5.0
This is the proftpd installer
fetch: ftp://ftp13.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp13.us.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp11.us.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp6.us.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp12.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp12.us.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp10.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp10.us.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp2.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp2.us.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp1.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp2.fr.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp.dk.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp15.us.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp1.us.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
fetch: ftp://ftp4.us.freebsd.org/pub/FreeBSD/ports/i386/packages-5.2-release/INDEX: File unavailable (e.g., file not found, no access)
Package index download failed!
Removing old ftp server (pure-ftpd)
pkg_delete: no packages match pattern(s)
Ftp Log Relocated!
<table border=0 width=100%>
<tr>
<td>Attempting to restart ftpserver</td>
<td><img src=/gears.gif></td>
</tr>
</table>
Waiting for ftpserver to restart....
.
.
.
.
.
.
.
.
.
.
finished.

<br><br>
<table width=100% border="1" cellspacing="0" cellpadding="0" bordercolorlight="#FF9900">
<tr>
<td>ftpserver status</td>
<td><font size=-1><pre></pre></font></td>
</tr>
</table>
<br>
<br>
ftpserver has failed, please contact the sysadmin.

I contacted my dedi provider who managed to get ProFTP up and working again after a few hours.
The last 2 days scripts/upcp have been ok except the package URLs are still down/incorrect - FTP has stayed up though. However, I had to reboot this morning on an unrelated matter and now FTP has failed again, seems to be the same issue.
I have contacted my host again but have heard nothing back. Can anyone shed some light on this and/or possibly give some pointers about getting FTP going again?
Thanks Holbrookau.

 

[SonServers]

Several months ago, I tried to change my FreeBSD machine from Proftp to Pureftp. The WHM tool failed, but said it was running Pureftp. It stayed this way for all that time until Tuesday. Tuesday morning, I found ftp down. I ran upcp a couple times and ftp came back up and it was finally running Pureftp.

Pureftp ran fine and well until Wednesday morning when I added a new account. Watching the add account process, it got to where it said it was synchronizing the ftp passwords and the server crashed. It rebooted, but many things were broken. It would serve web pages, but that's about it. I could not log in via SSH, no email, and WHM was down too.

The data center checked on it for me and found that all the password files were either gone or corrupted.

We had the /etc/passwd file from the daily backup, but that was it. I don't know if it would have been possible to restore all the necessary password files from just that file. Also, I had two new drives there waiting and was planning on a reinstall to FreeBSD 5.3 anyway, so I decided to have them do a reinstall rather than spend the time trying to fix something that may not have been fixable.

Anything that could have gone wrong during the reinstall did and the data center and cpanel techs were VERY helpful in helping get everything running.

I still have to wonder though what went wrong. I don't think I'll ever click that little button that says "change to Pureftp" on a FreeBSD machine again.

 

[cPanelNick]

Please open a ticket and reference this post.

 

[Holbrookau]

Sorry for not getting back sooner. I gave up chasing the problem, the server needed a clean out anyway so I had it re-imaged with FreeBSD5.3.
Apart from a named issue (see elsewhere) all is good on the later OS with cPanel10