What is the appropriate way to purge nuxeo.tmp.dir?

[Steven_Huwig1]

We recently had nuxeo.tmp.dir fill up, and from looking at the contents, it seems that removing old files is not something done by Nuxeo itself. I selectively removed large files to resolve our outage, but this seemed to result in very unstable operation. After removing the rest of nuxeo.tmp.dir and reloading some software, the instability seems to have been resolved.

What is the correct way to remove unused data from nuxeo.tmp.dir? If there is not a way for users to do this, is there a recommended minimum available space -- ours was greater than 12GB -- or a way to set the maximum size of the tmpdir?

Thanks, Steve

[Steven_Huwig1]

My nuxeo.tmp.dir is currently 69GB -- any input for avenues of research will be appreciated.

[Florent_Guillau]

How are the files named, and maybe in what subdirectory (so that we can find out where they come from)?

[Florent_Guillau]

Also, what Nuxeo version do you use?

[Steven_Huwig1]

I am using Nuxeo 5.8, though according to the list of deployed binaries in the admin page, many artifacts are 5.9.2-SNAPSHOT.

[Florent_Guillau]

The nxbincache directory is used to store a local cache of files for the S3BinaryManager. Its default maximum size should be 100 MB although this can be increased by the nuxeo.s3storage.cachesize property in nuxeo.conf (see Amazon S3 Online Storage).

There may be a bug which does not clear this cache when the server is shut down. I'll check. In the meantime this cache can be safely purged when the server is stopped.

[Steven_Huwig1]

For what it is worth, after installing from the fasttrack .deb to resolve the version mismatches I mentioned in another comment, the tmpdir is now much smaller. Perhaps the Nuxeo packaging script did this, or perhaps my issue was a result of having the wrong JARs deployed somewhere.

[Florent_Guillau]

Note that you shouldn't have artifacts of 5.9.2-SNAPSHOT if you're running a Nuxeo 5.8. Something is wrong with the bundles you have.

[Steven_Huwig1]

We have deliberately installed the following packages through the marketplace interface -- perhaps the installation process entailed installing 5.9.2-SNAPSHOT of other bundles?