The information shown on the web was correct.
Although that had come after restarting
lcg-bdii
Then a simple reboot caused the system to be incompletely seen
from the monitoring tools. Job submission seems to fail and
no processor information is shown.
After the reboot (and indeed after every reboot) the
lcg-bdii has to be restarted by hand for the system to function
correctly.
I should mention that we did a 2_3_1 --> 2_4_0 upgrade rather
than a fresh install using the apt-get instructions in the
LCG Rollout "Upgrading by Hand" documentation.
In order to check we did run locally
ldapsearch -x -H ldap://helmsley.dur.scotgrid.ac.uk:2170 -b
Mds-vo-name=Durham,o=Grid
which gives full information that on the face of it looks correct.
From our UI we have submitted jobs, and they work.
We logged into Mark Nelson's account in RAL and did the ldapsearch
from there to make sure that there were no firewall issues and that
gave the results previously seen.
The output of
ldapsearch -LLL -x -H ldap://helmsley.dur.scotgrid.ac.uk:2135 -b
"mds-vo-name=Durham,o=grid"
No such object (32)
Any ideas, suggestions ....?
The upgrade path seems to be hazardous. All the fresh installs of
2_4_0 seem
to work more or less out of the box, but the upgrade is
very much flawed. We already had to do a full fresh install on
our monbox because of conflicting tomcat issues and corrupted
server.xml file.
Lydia
--------------------------------------------------------
Dr E L Heck
Department of Physics | Tel.: + 44 191 - 334 3628
University of Durham | Fax.: + 44 191 - 334 3645
Durham, DH1 3LE |
U.K. | e-mail: [log in to unmask]
--------------------------------------------------------
|