Ticket #5883 (closed: fixed)
Logging and properties file modification for mpi build
Reported by: | Russell Taylor | Owned by: | Russell Taylor |
---|---|---|---|
Priority: | major | Milestone: | Release 2.3 |
Component: | Mantid | Keywords: | MPI |
Cc: | Blocked By: | ||
Blocking: | Tester: | Vickie Lynch |
Description
It makes sense for logging to file to be disabled by default as you also end up with a file containing the log that usually goes to stdout.
Other changes are to enable catalog searching by default and possibly to change the name of the user.properties file - the home directories on the fermi cluster are shared with those on the analysis machines, which could lead to surprises if someone's modified their settings when running MantidPlot.
Also, there are a number of properties that should have their values changed to suppress this kind of irrelevant output on startup:
ConfigService-[Warning] Required properties path "/home/tr9/Downloads/mantid-mpi-2.2.561-1.el6.x86_64/colormaps/" in the "colormaps.directory" variable does not exist. ConfigService-[Warning] Required properties path "/home/tr9/Downloads/mantid-mpi-2.2.561-1.el6.x86_64/plugins/qtplugins/mantid/" in the "mantidqt.plugins.directory" variable does not exist. ConfigService-[Warning] Required properties path "/home/tr9/Downloads/mantid-mpi-2.2.561-1.el6.x86_64/pvplugins/" in the "pvplugins.directory" variable does not exist. ConfigService-[Notice] ParaView is available FrameworkManager-[Notice] No PV plugin library directory
Change History
comment:2 Changed 8 years ago by Russell Taylor
The same /etc/mantid.local.properties file as is installed on the SNS analysis computers has been installed on fermi.
It's contents is:
datasearch.searcharchive = On default.facility=SNS
comment:4 Changed 8 years ago by Russell Taylor
Re #5883. Set several properties to empty in the MPI build.
This avoids a bunch of warnings in the log when starting mantid. The properties relate to gui stuff anyway so are irrelevant here.
Changeset: 68801484732e65db43d453668e40621ebd18b9f3
comment:5 Changed 8 years ago by Russell Taylor
Re #5883. Use a different user properties file for the MPI build.
The fermi cluster at ORNL uses the usual SNS home areas (so the same as the analysis workstations, for example). If the user properties file is the same, confusion could arise if things are set in it in and interactive MantidPlot session. The MPI build now uses Mantid-mpi.user.properties instead.
Changeset: 8a07fa61f8895b0c1ffc48c01679e9163c967e6f
comment:6 Changed 8 years ago by Russell Taylor
Re #5883. Logging changes for MPI build.
The MPI build no longer logs to file by default (as this duplicates the console channel which ends up in a log file for a job).
The format of log messages to the console has been changed to include hostname & process id so that messages can be separated according to which mpi rank they relate to. The rank is explicitly logged at startup.
Changeset: 64172a8f2c44a04a1e9462bba304b9ce6a238886
comment:7 Changed 8 years ago by Russell Taylor
Re #5883. Quiet irrelevant log message on startup of local mpi build.
Changeset: d3c78b0c7bbe783beced926bc8a194271923b93d
comment:8 Changed 8 years ago by Russell Taylor
- Status changed from accepted to verify
- Resolution set to fixed
comment:9 Changed 8 years ago by Vickie Lynch
- Status changed from verify to verifying
- Tester set to Vickie Lynch
comment:10 Changed 8 years ago by Vickie Lynch
- Status changed from verifying to closed
Can see host and process id in log
comment:11 Changed 8 years ago by Russell Taylor
Re #5883. Set several properties to empty in the MPI build.
This avoids a bunch of warnings in the log when starting mantid. The properties relate to gui stuff anyway so are irrelevant here.
Changeset: 68801484732e65db43d453668e40621ebd18b9f3
comment:12 Changed 8 years ago by Russell Taylor
Re #5883. Use a different user properties file for the MPI build.
The fermi cluster at ORNL uses the usual SNS home areas (so the same as the analysis workstations, for example). If the user properties file is the same, confusion could arise if things are set in it in and interactive MantidPlot session. The MPI build now uses Mantid-mpi.user.properties instead.
Changeset: 8a07fa61f8895b0c1ffc48c01679e9163c967e6f
comment:13 Changed 8 years ago by Russell Taylor
Re #5883. Logging changes for MPI build.
The MPI build no longer logs to file by default (as this duplicates the console channel which ends up in a log file for a job).
The format of log messages to the console has been changed to include hostname & process id so that messages can be separated according to which mpi rank they relate to. The rank is explicitly logged at startup.
Changeset: 64172a8f2c44a04a1e9462bba304b9ce6a238886
comment:14 Changed 8 years ago by Russell Taylor
Re #5883. Quiet irrelevant log message on startup of local mpi build.
Changeset: d3c78b0c7bbe783beced926bc8a194271923b93d
comment:15 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 6729
Actually, for the archive access we should probably just use the same /etc/mantid.local.properties mechanism as is used elsewhere. Best to keep things consistent.