Stuck with Pure-ftpd wildcard operation fails? We can help you.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Today, let’s take a look at how our Support Team help a customer  deal with this error.

How to resolve Pure-ftpd wildcard operation fails?

Usually, after updating from pure-ftpd 1.0.22 to 1.0.43, wildcard operations may fail.

Wildcard operations center around directory listings, but not always because some client operations such as a multiple get (mget) will do directory listings behind the scenes.

Typically, error might look as shown below:

ftp> ls *
229 Extended Passive mode OK (|||30087|)
150 Accepted data connection
226-Out of memory during globbing of *
226-(This probably means “Permission denied”)
226-Options: -a -l
226 0 matches total
ftp>

Between pure-ftpd 1.0.22 and 1.0.43, the globbing code was sync with OpenBSD-current.

That code had a memory buffer of 64K.

The result was that pure-ftpd could not handle as many wildcard results as previously allowed.

There are various options to resolve this:

Today, let us see the steps followed by our Support Techs to resolve it.

1. Firstly, customers with SLES 11 SP4 LTSS contracts can update their pure-ftpd package to version 1.0.43-30.5 or higher.

That update version increases the default size of a memory buffer from 64K to 512K.

In most cases, merely updating the package will be enough, and no configuration change would need.

For more extreme cases, the size of that buffer has also been made configurable.

Then, can controll as a 3rd value on the -L parameter, also known as the “LimitRecursion” setting in /etc/pure-ftpd/pure-ftpd.conf.

For example, in pure-ftpd.conf, the following line would allow up to 10000 directory entry results, traversal of up to 8 subdirectories deep, and a buffer size of 1024K.

LimitRecursion 10000 8 1024

Note that the size of each of these variables is independent of the other, meaning that the first value may allow for 10000 files, but even so there may not be enough memory buffer to handle that many.

Please insure that BOTH values are appropriate for your needs.

2. Customers without an LTSS contract have these options:

a. Revert to a 1.0.22 version of pure-ftpd.

This can be done within yast2 –> software management.

Search on “pure-ftpd”. Once found and selected, use the “Versions” tab to select the previous version which is desired.

The click “accept”. Packages can optionally be locked to prevent them from being updated in the future.

The command for this would be: zypper al pure-ftpd

b. Directory sizes can be kept smaller to avoid the issue.

c. Naming conventions or wildcard specifications can made more diverse to decrease the number of files which would match the particular wildcard specifications.

[Need a solution to another query? We are just a click away.]

Conclusion

Today, we saw steps followed by our Support Engineers in order to resolve Pure-ftpd wildcard operation fails.