On Tue, 15 May 2007, Christoph Wissing wrote:
> [log in to unmask] wrote:
>
> > On Tue, 15 May 2007, Christoph Wissing wrote:
> >
> [...]
> > > What do you mean by "Check all components of the path"?
> >
> > All leading directories must have the 'x' bit for the world,
> > and lcgdm-mapfile itself the 'r' bit for the world.
> > Obviously that is OK on your machine.
>
> All directories downto /opt/lcg/etc are 'x' for the world
>
> > Was the lfc-daemon restarted? Might the lfcmgr UID have changed?
>
> I do not know if it was done during upgrade, but I did it now by hand. Seems to have no (positive) effect.
> All old logfiles are still listed with lfcmgr:lfcmgr, so I assume that no IDs have changed during the upgrade process.
>
> Further idea are of course very welcome :-)
For me the most likely explanation still is that the daemon
cannot open the lcgdm-mapfile.
Are there complaints in /var/log/lfc/log?
Can you run this command:
lsof -p `ps -u lfcmgr | awk '/[ ]lfcdaemon/{print $1}'`
Maybe it reached the max. nr. of open files per process?
