IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Non-root user configuration problems

The following content provides information about non-root user configuration problems.


Error messages are displayed on the console when installing or configuring ITCAM agent for WebSphere Applications or J2EE as a non-root user on the AIX system

The problem: Error messages are displayed on the console when you run ITCAM agent for WebSphere Applications or J2EE installation or configuration as a non-root user on the AIX system.

The reason: The problem was caused by lacking of the required access to create the System Preference control files.

The solution: You can use either of the following way to solve this problem:


Non-root data collector configuration cannot lock system preferences

The problem: When using a non-root user to install and configure the data collector, system preferences cannot be locked. The following error is displayed in the console:

java.lang.SecurityException: Could not lock System prefs. Lock file access denied.
at java.util.prefs.FileSystemPreferences.
  checkLockFile0ErrorCode(FileSystemPreferences.java:937)
at java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:926) 
at java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:732)
at java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:825) 
at java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:476)
at java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:51) 
at java.util.prefs.FileSystemPreferences$4.run(FileSystemPreferences.java:437)
at java.util.TimerThread.mainLoop(Timer.java:447)
at java.util.TimerThread.run(Timer.java:397)

The reason: This is a limitation of JRE, please reference http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4438983


What to do if you tried to install and configure the data collector using a non-root user that did not have permissions to write to the temporary directory

The problem: The configuration will fail if you used a non-root user that did not have permissions to write to the temporary directory. You must perform the following procedure to correct this issue and perform a subsequent successful configuration of the data collector.

The solution:

  1. Undo your initial (failed) configuration of the data collector by using the Configuration Tool (config_dc.sh script) to unconfigure it. See the installation and customization guide for details.

  2. Perform one of the following:

    • Give the non-root user ID read and write access to the /tmp and /var/tmp directories:

      1. Log on as root and give the non-root user ID read and write access to /tmp.

      2. If your operating system is HP or Solaris, give the non-root user ID read and write access to /var/tmp also.

      3. Remove all files and directories under /tmp and (HP or Solaris only) /var/tmp.

    • If you have concerns about removing all files under /tmp and (HP or Solaris only) /var/tmp, specify a different temporary directory:

      1. Modify the DC_home/config_dc/config_dc.sh file. Add the following parameters to the file:
        -Dtemp.dir=<tmp_dir>
        -Djava.io.tmpdir=<tmp_dir>

        ...where <tmp_dir> is the directory you want the Configuration Tool to write to. The user for the installation should have read, write, and execute privileges to this directory.

  3. Run the Configuration Tool (config_dc.sh script) to configure the data collector. See the installation and customization guide for details.


Parent topic:

data collector

+

Search Tips   |   Advanced Search