Troubleshooting the Remote Agent for Linux or UNIX Servers

Article:HOWTO51794  |  Created: 2011-05-04  |  Updated: 2011-06-15  |  Article URL http://www.symantec.com/docs/HOWTO51794
Article Type
How To


Subject


Troubleshooting the Remote Agent for Linux or UNIX Servers

If you experience problems with the Remote Agent for Linux or UNIX Servers (Remote Agent) review the following questions and answers.

Table: Troubleshooting the Remote Agent

Question

Answer

Some characters do not appear correctly in the terminal session during the installation. What should I do?

This error occurs when the system location uses a non-English language character-set on the computer on which you install the Remote Agent. You can switch to another location setting of the same language to try to resolve this issue.

The Remote Agent installer is unable to install the Remote Agent. The following error is reported in the installralus log file:

VxIF::Error:: Unable to compress files. Hash(0x8711e8)->({GUNZIP.EN_US} not found on <hostname>

To support the uncompressing of the Remote Agent platform-specific packages, you can install the GNU data compression utility. Install this utility on the computer on which you want to install the Remote Agent.

The utility is available at the following URL:

http://www.gzip.org

The Remote Agent for Linux or UNIX Servers is installed on a UNIX or Linux server in an NIS domain. Backup Exec is unable to browse resources on the server. What should I do?

Verify if the group line and the password line in the nsswitch.conf file are set to compatibility mode. If they are, then you must configure the /etc/passwd and /etc/group files. Refer to the nsswitch.conf man pages for additional information on how to configure the nsswitch.conf to use compatibility mode.

Alternatively, change the password line and the group line to NIS files so that the UNIX or Linux server validates the user through NIS. If the NIS server is unavailable or if the user is not found, the local files are used for validation.

I cannot load the Remote Agent. When I attempt to load the Remote Agent in console mode, /beremote --log-console shows the following message:

ACE_SV_Semaphore_Complex: no space left on device.

What should I do?

This issue occurs when the computer reaches its maximum limit on allowable semaphores. It can occur after an unexpected termination of the Remote Agent. When the Remote Agent unexpectedly terminates, it is unable to clean up some of the semaphore resources that it used. Other processes may have caused the use of semaphores to reach the limit. You must restart the computer to safely recover it from this condition.

If other processes are running, it may not be feasible to restart the computer. Instead, you can use the commands that let you list and then remove all semaphores in use by the operating system. Be careful when you select semaphores to remove. Semaphores that are in use by the Remote Agent cannot be identified. If you remove semaphores of other programs that are in use, those programs can become unstable.

To list semaphores, you can type the following command:

ipcs -a

To remove semaphores for each identifier that is listed, you can type the following command:

ipcrm -s <id>

I cannot load the Remote Agent. When I attempt to load the Remote Agent in console mode, /beremote --log-console shows the following message:

Error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory.

What should I do?

This error indicates that the libstdc++.so.5 library is not in the /usr/lib directory. This library is necessary to let the Remote Agent start and function. To resolve this issue, install the libstdc++5 package.

You can install this package from the media on which your copy of Linux was provided. Or, you can run the following command from a computer that has Internet access:

apt-get install libstdc++5

For SUSE Linux Enterprise Server 11, run the following command:

zypper install libstdc++5


Legacy ID



id-SF700161544_be2010_adm


Article URL http://www.symantec.com/docs/HOWTO51794


Terms of use for this information are found in Legal Notices