Unix Package Server Troubleshooting Tips

Article:HOWTO5056  |  Created: 2005-09-29  |  Updated: 2005-09-29  |  Article URL http://www.symantec.com/docs/HOWTO5056
Article Type
How To



Question
How do I troubleshoot the connection between a Unix client and a package server?

Answer

Unix Package Server Troubleshooting Tips

 

 

1.      What steps do I follow to troubleshoot the connection from the Unix client to the package servers?

 

·         The client must be able to resolve the hostname of the package server (PS). This can be done with DNS or by updating the client’s /etc/hosts file. The former method is officially supported. There is no guarantee that the client and PS will communicate without hostname resolution.

 

·         Try pinging the PS from the client.  If ICMP protocol is not enabled, you will not be able to ping even if the PS can be accessed via HTTP.

 

·         Use utilities such as wget, curl or telnet to try to reach the PS via HTTP/HTTPS. Use the package url taken from the “codebases” file (see below for details on the location of the codebases file.)

 

·         If the above work, the NS Agent for Unix process on the client should be connecting and downloading packages from the PS.

 

2.      From which package server(s) will a Unix client get packages? Where on the client is this information stored, even if only temporarily?

 

  • The NS agent on the client will query the Notification Server (NS) for possible download locations. The response from the NS is stored in a temporary “codebase” file, located in the following directory: 

 

.../nsagent/var/packages/<GUID>/.aex-pkg-codebases-<GUID>  

 

(where <GUID> is a package GUID from the client policies.)

 

This file looks something like this:

 

<response type="codebases">
  <packages>
    <package guid="{afafafaf-039b-4418-9a0a-70a9c7445f9c}">
      <codebases speedTest="1">
        <codebase url="
http://grisha-ns/Altiris/NS/NSCap/Bin/Unix/6.0/SWD/SamplePackage" snapshot="http://grisha-ns/Altiris/NS/Agent/GetPackageSnapshot.asp" />
        <codebase url="
file://grisha-ns/NSCap/Bin/Unix/6.0/SWD/SamplePackage" snapshot="http://grisha-ns/Altiris/NS/Agent/GetPackageSnapshot.asp" />
      </codebases>
    </package>
  </packages>
</response>

 

The NS Agent for Unix/Linux will ignore all codebases except for HTTP/HTTPS.

 

  • The list of files to be downloaded is stored in a “snapshot” file, located in the following directory:  

 

.../nsagent/var/packages/<GUID>/.aex-pkg-snapshot-<GUID>

 

(where <GUID> is a package GUID from the client policies.)

 

Please note that both the "codebase" and the "snapshot" files are created only after the NS Agent for Unix attempts to download a package and only if the NS is accessible.

 

3.      If the information for the location of the package server is not being keep on the client and a user/administrator does not have access to the NS server, how can you trouble shoot the connection to the package server?

 

  • If you do not have access to the NS, you will not be able to get available "codebases" for a package download. However, once these codebases are obtained, they will be used even if NS is not accessible.

 

4.      What type of account or services is used to connect to the package server? Is there a security challenge of some type when the client contacts the package server?

 

·         All communication between the NS and PS Agent for UNIX use the cURL library included with the agent. (See http://curl.haxx.se)

 

5.      What configuration file holds information on update schedules and such for the client and where is it located.

 

  • The policy update schedules are kept in the client policies file. The NS Agent for Unix reads this information and stores it in a local configuration file, located in the following directory:

 

            .../nsagent/etc/client.conf.

 

This is the only configuration file used by the NS Agent for Unix.

 

Please read the user guide for further details, as well as the comments inside the client.conf file for specific descriptions of each option.

 


Legacy ID



2741


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


Terms of use for this information are found in Legal Notices