Known Issues

This document lists know issues about the latest stable version of Iometer and provides you with suggestions to bypass them.

2004.07.30
OS / platform issue / workaround scope
Linux / IA32 Segmentation fault with Red Hat 9
 
Issue: Running Dynamo on a Linux machine with a glibc (GNU libc) version 2.3 or higher (having NPTL support) - Red Hat 9 for instance - it comes to a segmentation fault after ending a test. This hapens due to the shift from LinuxThreads to NPTL (Native POSIX Thread Library) and the incompatibilities coming with that.
 
Workaround:
a.) Update the glibc with the version and proceedings described by Red Hat in https://rhn.redhat.com/errata/RHSA-2003-325.html.
b.) Before starting the Dynamo you have to run the following command:
export LD_ASSUME_KERNEL=2.4.1
2004.07.30 and older

List of known issues for version 2004.07.30.

2003.12.16
OS / platform issue / workaround scope
all Iometer crashes in batch mode when waiting for a dynamo
 
Issue: When running Iometer in batch mode, one gives a number of seconds to wait for the Dynamo instances defined in the configuration file (ICF). Due to a change since 2003.05.10, the Iometer is crashing when a Dynamo instance is not jumping in fast enough.
 
Workaround:
a.) Ensure that the Dynamo instances are attaching fast enough.
b.) Apply the needed change on source code level (file WaitingForManagers.cpp line 297 - 299):
 
correction: Remove if(theApp.IsBatchMode()) { exit(1); }
 
c.) Download the latest code from the CVS tree and go with that one.
d.) Use version 2003.05.10.
2003.12.16 only
Windows / IA32 wizard.mdb can not be opened
 
Issue: Trying to open wizard.mdb, MS Access is complaining and not able to repair the file. This is due to an corrupt image of this file in the iometer-2003.12.16.win32-setup.exe package.
 
Workaround: Download the wizard.mdb directly from the CVS server that can be accessed via the sourceforge.net page - the correct md5sum (for the 1.1 revision of the file) is 99faa1d0a50c6c6268d62505f917bae4.
2003.12.16 only
Windows / IA32 wizard.mdb complains about Excel version
 
Issue: The wizard.mdb is checking for a minimum version of Excel when creating the graphs. The original code didn't had a two digit version number (coming with MS Access 2000) in mind.
 
Workaround: Download the latest wizard.mdb (revision 1.3 or higher) directly from the CVS server that can be accessed via the sourceforge.net page.
2003.12.16 only
Linux / IA32 Segmentation fault with Red Hat 9
 
Issue: Running Dynamo on a Linux machine with a glibc (GNU libc) version 2.3 or higher (having NPTL support) - Red Hat 9 for instance - it comes to a segmentation fault after ending a test. This hapens due to the shift from LinuxThreads to NPTL (Native POSIX Thread Library) and the incompatibilities coming with that.
 
Workaround:
a.) Update the glibc with the version and proceedings described by Red Hat in https://rhn.redhat.com/errata/RHSA-2003-325.html.
b.) Before starting the Dynamo you have to run the following command:
export LD_ASSUME_KERNEL=2.4.1
2003.12.16 and older

List of known issues for version 2003.12.16.

2003.05.10
OS / platform issue / workaround scope
all iobw.tst doesn't match the given "Maximum Disk Size" value
 
Issue: When preparing a new filesystem with an value for "Maximum Disk Size" (field in the Target tab of the Iometer GUI) other then zero and bigger then 2 GB, then there is an variable overflow. This overflow results in another size of the iobw.tst file which then might be much smaller.
 
Workaround:
a.) Before starting your test, create the iobw.tst file (with the wished size) yourself using a tool (e.g. the dd tool under Unix). Then use zero as "Maximum Disk Size" - that way the worker uses the existing iobw.tst file and adapt to its size.
b.) Download the Iometer sources and apply the iometer_large_work_file patch (#821482) which was provided by Russell Reed.
2003.05.10 and older
Linux / IA32 Segmentation fault with Red Hat 9
 
Issue: Running Dynamo on a Linux machine with a glibc (GNU libc) version 2.3 or higher (having NPTL support) - Red Hat 9 for instance - it comes to a segmentation fault after ending a test. This hapens due to the shift from LinuxThreads to NPTL (Native POSIX Thread Library) and the incompatibilities coming with that.
 
Workaround:
a.) Update the glibc with the version and proceedings described by Red Hat in https://rhn.redhat.com/errata/RHSA-2003-325.html.
b.) Before starting the Dynamo you have to run the following command:
export LD_ASSUME_KERNEL=2.4.1
2003.05.10 and older
Solaris / SPARC Segmentation fault when having multiple swap devices
 
Issue: Running Dynamo on a Solaris machine, a detection of the swap devices is done. If you have multiple swap devices configured, the Dynamo crashes with a segmentation fault.
 
Workaround:
a.) Configure only one swap device
b.) Apply the needed changes (provided by Robert H. Creecy) on source code level (file IOManagerSolaris.cpp line 1198):
 
wrong: strs = (char *)malloc(num+1 * MAX_NAME);
correct: strs = (char *)malloc((num+1) * MAX_NAME);
2003.05.10 and older

List of known issues for version 2003.05.10.