Hi Oliver,
In fact we specifically have a warning about using /tmp as the admin
directory in the documentation:
https://xrootd.slac.stanford.edu/doc/dev53/xrd_config.htm#_Toc60181749
Additionally, certain features are turned off when the admin path is
located in /tmp (e.g. checkpointing). The only real solution is to not
use /tmp. The only reason it defaults to /tmp is because that's the only
place that's common to all possible sites not because it's the place that
should be used (in fact, it really shouldn't be placed there).
It's pretty easy to locate it elsewhere and there are a number of ways
to accomplish this (see the documentation above).
Andy
On Wed, 1 Sep 2021, Oliver Freyermuth wrote:
> Not sure if this is a "bug" or just an annoyance, or what is the best way to go about it:
> I observed our TPC transfers today failing in case X.509 delegation was required. The cause was:
> ```
> 210901 08:19:47 393183 ofs_TPC: Unable to create credentials file ***@***.***#17.creds; no such file or directory
> ```
> which in turn was caused by `/tmp/grid/.ofs/.tpccreds` not existing anymore after some days without transfers using X.509 delegation.
>
> Checking the code, it seems the directory is only created once, and then assumed to stay. Sadly, `tmpfiles` cleaners such as `systemd-tmpfilesd`or `tmpreaper` regularly pass by nowadays to prune such directories when not used for a while. And since XRootD is running very stable, it runs for many days in a row for us ;-).
>
> I think there are several ways this could be handled:
> * Warn in the documentation about it, and delegate choice of a different directory to the user.
> * Add a `systemd-tmpfilesd` exception and ship it with the `rpm` packages (might also be necessary to do this for `tmpreaper` and other such things).
> * Always recreate directories in the adminpath in case they go missing at runtime.
>
> I'm not sure what is the best way, and maybe you have an even better idea ;-).
>
> --
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1502
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1502#issuecomment-910844864",
"url": "https://github.com/xrootd/xrootd/issues/1502#issuecomment-910844864",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1