Ftp ошибка 552

At Bobcares, we provide 24/7 expert support, monitoring and preventive maintenance to all our customers.

And as part of our service, we sometimes have to fix numerous issues coming from various client, all in a day.

‘552 Transfer aborted, Disk quota exceeded‘ is one such issue that we often resolve for our clients.

What does “552 Transfer aborted, Disk quota exceeded” mean?

What if while uploading your file, you see that you’ve already used up all your allocated space?

Or, what if you have space available, but the file is so large that if uploaded, it would exceed your disk space quota?

In such cases, FTP server sends you the ‘552 Transfer aborted, Disk quota exceeded‘ message. This means that you have either reached or exceeded your disk space quota.

What causes “552 Transfer aborted, Disk quota exceeded” error?

When customers contact us with this issue, we look for the various reasons that could be using up all the disk space.

And in our experience, the 5 most common causes for space hogs have been :

1. Backups

Many a times, customers have to restore backup archives to get a file. And we have seen that there’s usually a tendency to forget about removing the full archive.

There have been instances where we’ve deleted uncompressed archives which had been occupying over 70% of the space.

And then, we’ve come across situations where VPS owners store backup on the same disk. In such cases, these backup archives and uncompressed files take up a huge amount of disk space.

So, we delete these files to resolve the issue. And as a preventive measure, we set up disk space alerts and fix space issues before they lead to service failure.

2. Old application backups and database dumps

We have seen that web users sometimes store old copies of web apps in their document root.

Also, website developers usually take a backup before they upgrade an app. And we’ve seen that in some accounts, there maybe several months worth of database dumps that take as much as 50% of the disk space.

In such situations we clear these backups  to reclaim the space.

3. Unused media files

When we check for probable causes for the space limitation, we sometimes run into a lot of unused media files stored by the site.

These are usually several versions of the same video, audio or image file. Media files as such take a lot of space. These are files which are never accessed for months or even years.

Deleting them frees up the space for other uses.

4. Spams

Sometimes a user may be flooded with hundreds of unsolicited email or spams a day.

A single spam may not take up a large space. But, once they start accumulating, their combined consumption may reach hundreds of MBs or GBs of space.

We have seen that this is usually the case for customers who opt to use the Spam quarantine feature but sometimes forget about the spams. In such situations, we recommend automatic deletion of spam mails.

We also set up mail directory expiry settings. With this option, clients can review the spam mails if they want. And any spam that’s older than 30 days gets deleted automatically.

5. Trash

Most often deleted files end up in ‘Trash’ folders. In such cases, the deleted file’s disk space is still in use.

So, when we check and find that the ‘Trash’ folder contents are the major space users, we purge the ‘Trash’ folder to free up the disk space.

Conclusion

‘552 Transfer aborted, Disk quota exceeded‘ is a common warning message for the disk quota limitation. Today we have seen the 5 common causes for this problem and how our Support Engineers fix it at Bobcares.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP® Home (All Versions)
• CuteFTP Pro® (All Versions)

SYMPTOMS

When attempting to upload a file to the remote FTP site, a 552 error code is encountered, resulting in an error message similar to the following example:

COMMAND:> STOR yourfile.ext

STATUS:> Connecting FTP data socket… 192.168.0.1:21…

150 Opening ASCII mode data connection for yourfile.ext
552

Transfer aborted. Disk quota exceeded.

ERROR:> Exceeded storage allocation.

CAUSE

This error is not caused by CuteFTP.  The 552 error code is coming directly from the remote FTP server.  There is not enough disk space available to you on the remote FTP server.  The most common cause for this error is that the limited disk space allocated for your individual FTP account is already in use. 

This error may also appear when disk space appears to be available but the file being uploaded is large enough so that if it were uploaded, it would cause your disk space quota to be exceeded.

RESOLUTION

More disk space is needed.  You can increase the space available by deleting unnecessary files from the remote server or by making arrangements with your Web hosting provider or FTP account administrator for additional disk space.

I have this code for uploading images on my FTP Server:

FtpWebRequest ftp = (FtpWebRequest)FtpWebRequest.Create("ftp://domain.com/" + "393174" + ".jpg");
                ftp.Credentials = new NetworkCredential("user@domain.com", "password");

                ftp.KeepAlive = true;
                ftp.UseBinary = true;
                ftp.Method = WebRequestMethods.Ftp.UploadFile;

                FileStream fs = File.OpenRead(@"location" + "393174" + ".jpg");
                byte[] buffer = new byte[fs.Length];
                fs.Read(buffer, 0, buffer.Length);
                fs.Close();

                Stream ftpstream = ftp.GetRequestStream();
                ftpstream.Write(buffer, 0, buffer.Length);
                ftpstream.Close();

For some reason I get Error (552) Exceeded storage allocation: System.Net.WebException.

I tried with new ftp account on different location but same error.
I checked FTP Quota is on Unlimited.

The remote server returned an error: (552) Exceeded storage allocation
(for current directory or data set). at
System.Net.FtpWebRequest.SyncRequestCallback(Object obj) at
System.Net.FtpWebRequest.RequestCallback(Object obj) at
System.Net.CommandStream.Dispose(Boolean disposing) at
System.IO.Stream.Close() at System.IO.Stream.Dispose() at
System.Net.ConnectionPool.Destroy(PooledStream pooledStream) at
System.Net.ConnectionPool.PutConnection(PooledStream pooledStream,
Object owningObject, Int32 creationTimeout, Boolean canReuse) at
System.Net.FtpWebRequest.FinishRequestStage(RequestStage stage) at
System.Net.FtpWebRequest.GetRequestStream() at
WindowsFormsApplication1.Form1.button1_Click(Object sender, EventArgs
e) in C:UsersDemirAppDataLocalTemporary
ProjectsWindowsFormsApplication1Form1.cs:line 38

Moderator: Project members

---

---

---

Range Purpose 1xx Positive Preliminary reply

The requested action is being initiated; expect another reply before proceeding with a new command. (The user-process sending another command before the completion reply would be in violation of protocol; but server-FTP processes should queue any commands that arrive while a preceding command is in progress.) This type of reply can be used to indicate that the command was accepted and the user-process may now pay attention to the data connections, for implementations where simultaneous monitoring is difficult. The server-FTP process may send at most, one 1xx reply per command.

2xx Positive Completion reply

The requested action has been successfully completed. A new request may be initiated.

3xx Positive Intermediate reply

The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information. The user should send another command specifying this information. This reply is used in command sequence groups.

4xx Transient Negative Completion reply

The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. The user should return to the beginning of the command sequence, if any. It is difficult to assign a meaning to «transient», particularly when two distinct sites (Server- and User-processes) have to agree on the interpretation. Each reply in the 4xx category might have a slightly different time value, but the intent is that the user-process is encouraged to try again. A rule of thumb in determining if a reply fits into the 4xx or the 5xx (Permanent Negative) category is that replies are 4xx if the commands can be repeated without any change in command form or in properties of the User or Server (e.g., the command is spelled the same with the same arguments used; the user does not change his file access or user name; the server does not put up a new implementation.)

5xx Permanent Negative Completion reply

The command was not accepted and the requested action did not take place. The User-process is discouraged from repeating the exact request (in the same sequence). Even some «permanent» error conditions can be corrected, so the human user may want to direct his User-process to reinitiate the command sequence by direct action at some point in the future (e.g., after the spelling has been changed, or the user has altered his directory status.)

6xx Protected reply

RFC 2228 introduced the concept of protected replies to increase security over FTP communications. The 6xx replies are Base64 encoded protected messages that serves as responses to secure commands. When properly decoded, these replies fall into the above categories.

Code Explanation 100 Series The requested action is being initiated, expect another reply before proceeding with a new command. 110 Restart marker replay . In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm where yyyy is User-process data stream marker, and mmmm server’s equivalent marker (note the spaces between markers and «=»). 120 Service ready in nnn minutes. 125 Data connection already open; transfer starting. 150 File status okay; about to open data connection. 200 Series The requested action has been successfully completed. 202 Command not implemented, superfluous at this site. 211 System status, or system help reply. 212 Directory status. 213 File status. 214 Help message. Explains how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user. 215 NAME system type. Where NAME is an official system name from the registry kept by IANA. 220 Service ready for new user. 221 Service closing control connection. Logged out if appropriate. 225 Data connection open; no transfer in progress. 226 Closing data connection. Requested file action successful (for example, file transfer or file abort). 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2). 228 Entering Long Passive Mode (long address, port). 229 Entering Extended Passive Mode (|||port|). 230 User logged in, proceed. 232 User logged in, authorized by security data exchange. 234 Server accepts the security mechanism specified by the client; no security data needs to be exchanged. 235 Server accepts the security data given by the client; no further security data needs to be exchanged. 250 Requested file action okay, completed. 257 «PATHNAME» created. 300 Series The command has been accepted, but the requested action is on hold, pending receipt of further information. 331 User name okay, need password. 332 Need account for login. 334 Server accepts the security mechanism specified by the client; some security data needs to be exchanged. 335 Server accepts the security data given by the client; more security data needs to be exchanged. 336 Username okay, need password. Challenge is «….». 350 Requested file action pending further information 400 Series The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. 421 Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down. 425 Can’t open data connection. 426 Connection closed; transfer aborted. 430 Invalid username or password 431 Need some unavailable resource to process security. 434 Requested host unavailable. 450 Requested file action not taken. 451 Requested action aborted. Local error in processing. 452 Requested action not taken. Insufficient storage space in system. File unavailable (e.g., file busy). 500 Series Syntax error, command unrecognized and the requested action did not take place. This may include errors such as command line too long. 501 Syntax error in parameters or arguments. 502 Command not implemented. 503 Bad sequence of commands. 504 Command not implemented for that parameter. 530 Not logged in. 532 Need account for storing files. 533 Command protection level denied for policy reasons. 534 Request denied for policy reasons. 535 Failed security check. 536 Data protection level not supported by security mechanism. 537 Command protection level not supported by security mechanism. 550 Requested action not taken. File unavailable (e.g., file not found, no access). 551 Requested action aborted. Page type unknown. 552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset). 553 Requested action not taken. File name not allowed. 600 Series Replies regarding confidentiality and integrity 631 Integrity protected reply. 632 Confidentiality and integrity protected reply. 633 Confidentiality protected reply. 10000 Series Common Winsock Error Codes^[2] (These are not FTP return codes) 10054 Connection reset by peer. The connection was forcibly closed by the remote host. 10060 Cannot connect to remote server. 10061 Cannot connect to remote server. The connection is actively refused by the server. 10065 No route to host / DNS cannot be resolved. 10066 Directory not empty. 10068 Too many users, server is full.

Опубликовал(а):
в: 08.11.2010

LIST OF COMMON FTP ERROR CODES

File Transfer Protocol (FTP) is a network protocol responsible for transferring file between hosts. An FTP on the other hand, is a server that serves as a central reposi tory for files that users can download and, in some cases, upload.

It can then also authenticate users based on user name and password combination but and FTP server can also be configured to allow users to connect anonymously.

FTP uses TCP/IP port 20 and 21; port 20 is for transmitting data between the FTP server and client while the port 21 is used for transmitting instructions between the FTP server and client.

FTP server return codes always have three digits and each digit has a unique meaning. The first digit denotes whether the response is good, bad or incomplete.

NOTE: Error messages are very much important to be read whenever they appear on our computer screen or any electronic device. It really helps us to understand the situation at hand.  Below are brief explanations of the most common status and error codes. The table below is provided so that you have some idea whether you can solve the issue on your own or you need to call your ISP for assistance.

ERROR CODES	MEANINGS
230	User logged in, proceed. Logged out if appropriate.
227	Entering Passive Mode (h1, h2, h3, h4, p1, p2).
250	Requested file action okay, completed.
257	“PATHNAME” created
120	Service ready in nnn minutes.
125	Data connection already open; transfer starting
350	Requested file action pending further information
331	User name okay, need password.
332	Need account for login.
213	File status.
425	Can’t open data connection
212	Directory status.
150	File status okay; about to open data connection.
200	Command okay.
202	Command not implemented, superfluous at this site.
530	Not logged in
501	Syntax error in parameters or arguments.
220	Service ready for new user.
503	Bad sequence of commands.
211	System status, or system help reply.
421	Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down.
214	Help message. On how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user.
215	NAME system type. Where NAME is an official system name from the list in the Assigned Numbers document.
532	Need account for storing files.
502	Command not implemented.
504	Command not implemented for that parameter.
550	Requested action not taken. File unavailable (e.g., file not found, no access).
225	Data connection open; no transfer in progress.
426	Connection closed; transfer aborted.
226	Closing data connection. Requested file action successful (for example, file transfer or file abort).
552	Requested file action aborted. Exceeded storage allocation (for current directory or dataset).
551	Requested action aborted. Page type unknown.
221	Service closing control connection.
553	Requested action not
450	Requested file action not taken
451	Requested action aborted. Local error in processing.
500	Syntax error, command unrecognized. This may include errors such as command line too long.
452	Requested action not taken. Insufficient storage space in system. File unavailable (e.g., file busy).