Extension loader not responding
The extension loader might not successfully copy data to your data model due to issues with the BMC Remedy AR System server. Use the following procedure if the extension loader stops responding or fails to run.
To troubleshoot extension loader process issues
- In the AR System Administration Console, log on to the BMC Atrium CMDB server to verify that you can connect to the AR System server.
- To verify that you can access the BMC Atrium CMDB server, log on to the
cmdbdriverprogram and issue the
For more information about using
cmdbdriver, see cmdbdriver program.
- Make sure that the database server has at least 15 percent of space available and can grow the transaction log as needed during the installation.
auto-extendoption in the database to make sure that the space on the database server automatically extends.
- If the extension loader stops responding, check the arerror.log or armonitor.log files to make sure that the
arserver.exe(Microsoft Windows) or
arserverd(UNIX) server process did not restart or stop responding.
During the installation, the Admin thread 390600 is busy, Therefore, you might receive timeout messages when you try to access the AR System Administration Console.
- If the AR System server stops responding during the extensions installation, abort the installation and troubleshoot the AR System issue.
- If you are installing the extensions as a non-root user, make sure that you use the same user ID that you used to install the AR System server and BMC Atrium CMDB.
- To verify that your system has sufficient space (at least 600 MB of free space and 1 GB of temp space), perform the following steps:
- Check the %TEMP% directory (Windows) or /tmp (UNIX) for space.
- On Windows, check hard disk space using Explorer. On UNIX, use the
df- kcommand to verify that you have a reasonable amount of swap space on the system.
- On UNIX, type
ulimit -afrom the console to verify that the
ulimitsettings are set high.
The following output is from a system that is functional. A default system has a process size limit of 64 KB, which is not large enough for the BMC Remedy installer.
- time (seconds) unlimited
- file (blocks) unlimited
- data (kbytes) unlimited
- stack (kbytes) 8192
- coredump (blocks) unlimited
- nofiles (descriptors) 64
- vmemory (kbytes) unlimited
- On IBM AIX, perform the following steps:
lsattr -E -l sys0 -a ncargsto make a note of the value from
chdev -l sys0 -a ncargs=128to temporarily change
ncargsto its maximum for the system.
- If any processes on AIX stopped responding, use the
AIXcommand to troubleshoot the issue.
- On Windows, set the
VMparameter in the boot.ini file to allow 32-bit programs to use 3 GB of random access memory (RAM).