Hi,
Our team managed to solve the problem: it was a combination of missing
submit_filter.pl on gCE (somehow it disappeared after the reconfiguration,
probably due to the human error), erroneous ssh_known_hosts (gCE key has
changed, and was not updated since old key was present), and the most
important issue being the change of <VO>prd<number> and <VO>sgm<number> pool
accounts to prd<VO><number> and sgm>VO><number> form, which was not reflected
in AllowedUsers in sshd_config. After all this was fixed, the problem is gone,
so we will finish the downtime for gCE and hope for the best :)
Thanks to all who answered for useful suggestions!
Best regards, Antun
PS: Maarten, dropping gCE support altogether on our site was the next step I
considered if we fail to revive it; seems it survived this time :)
-----
Antun Balaz
Research Assistant
E-mail: [log in to unmask]
Web: http://scl.phy.bg.ac.yu/
Phone: +381 11 3713152
Fax: +381 11 3162190
Scientific Computing Laboratory
Institute of Physics, Belgrade, Serbia
-----
---------- Original Message -----------
From: Maarten Litmaath <[log in to unmask]>
To: [log in to unmask]
Sent: Wed, 11 Jul 2007 17:24:54 +0200
Subject: Re: [LCG-ROLLOUT] Problems with gCE after latest updates
> Antun Balaz wrote:
>
> > Hi,
> >
> > After applying all the latest updates yesterday on all nodes, and
> > reconfiguring them, we are experiencing significant problems with gCE, and
> > just with this node.
>
> Hi Antun,
> how important is it to get the current gLite CE still to work?
>
> The "true" gLite CE, a.k.a. "glexec" CE (*) has made good progress
> in certification, so we may want to stop bothering with debugging
> the current, clunky approximation...
>
> (*) Not to be confused with potential use of glexec by pilot jobs.
------- End of Original Message -------
|