Hi Marcel,
If this is your xrootd configuration file (I meant the “Now, it is”) then nothing will work. It doesn’t except have all.export so it will export /tmp. Can you put your old configuration files back (with an “fi” at the end)?
Can you also put your old /etc/sysconfig/xrootd back? Then run on every nodes:
service xrootd setup
service xroot start
service cmsd start
regards,
Wei Yang | [log in to unmask] | 650-926-3338(O)
On Oct 28, 2014, at 2:11 PM, Marcel Kuriyama <[log in to unmask]> wrote:
> The configuration files was changed by the xrootd installation, as I have written on this post:
> #152
>
> Basically my xrootd-clusterd.cfg was
> all.export /data/xrootdfs
> set xrdr=lipnode01
> all.manager $(xrdr):1213
> cms.allow host *
> if $(xrdr)
> all.role manager
> xrd.port 1094
> else
> all.role server
> oss.localroot /data/files
>
> Now, it is:
> all.role manager
> all.manager lipnode01 3121
> frm.xfr.copycmd /bin/cp /dev/null $PFN
> all.adminpath /var/spool/xrootd
> all.pidpath /var/run/xrootd
>
> As this example:
> https://github.com/xrootd/xrootd/blob/stable-4.0.x/packaging/common/xrootd-clustered.cfg
>
> And, my /etc/sysconfig/xrootd was
> CMSD_DEFAULT_OPTIONS="-l /var/log/xrootd/cmsd.log -c /etc/xrootd/xrootd-clustered.cfg -k 7"
>
> And was changed to:
> CMSD_DEFAULT_OPTIONS="-l /var/log/xrootd/cmsd.log -c /etc/xrootd/xrootd-clustered.cfg -k fifo"
>
> —
> Reply to this email directly or view it on GitHub.
>
—
Reply to this email directly or view it on GitHub.
{"@context":"http://schema.org","@type":"EmailMessage","description":"View this Issue on GitHub","action":{"@type":"ViewAction","url":"https://github.com/xrootd/xrootd/issues/154#issuecomment-60833232","name":"View Issue"}}
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
