Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE Linux Enterprise Point of Service 11 SP3 and SUSE Linux Enterprise Point of Service 12 Image Server

13 Troubleshooting

This section describes the analysis and correction of some specific error situations in a SUSE® Linux Enterprise Point of Service system.

13.1 Debugging SUSE Linux Enterprise Point of Service Commands

You can set the verbosity level for console output and log files of all SUSE Linux Enterprise Point of Service commands and tools in the same way, with the POS_FORCE_VERBOSITY environment variable.

The verbosity level for the console output can be specified with --verbose=level or -v level. The verbosity level for the log files can be specified with --syslog=level. The level can have the following values: emerg (panic conditions), alert (conditions needing immediate correction), crit (critical conditions), err (errors), warn (warnings), notice (conditions requiring special handling), info (informational messages), or debug (debugging messages).

13.2 Collecting SUSE Linux Enterprise Point of Service Data for Bug Reporting

For easy collection of SUSE Linux Enterprise Point of Service log files, configuration files and LDAP directory content for bug reporting, the save_poslogs tool is provided. For more information, see Section B.3.13, “save_poslogs”.

13.3 Server Infrastructure

The setup and operating procedures for SUSE Linux Enterprise Point of Service servers in most of the cases are easy. However, the distributed nature of the system might provide some challenges. The following section describes frequently encountered difficulties with name resolution.

13.3.1 Name Resolution

Care must be taken to ensure that the system can resolve its own name to its IP address on the branch network, especially when configuring the Branch Servers with posInitBranchserver.

If the system has only one network interface or if the eth0 interface is the branch network interface, the correct resolution is done through the /etc/hosts file, where YaST adds the correct entries. Otherwise, add the corresponding line to /etc/hosts manually or make sure that DNS can resolve the host name.

13.3.1.1 Symptoms

If the DHCP server configuration file /etc/dhcpd.conf is not created properly, poscheckip returns the following error code:

# poscheckip
# echo $?
1

If the dhcpd.conf file is created properly, poscheckip returns the correct host name, address, netmask and domain as follows:

# poscheckip
bs      192.168.150.1   255.255.255.0   Lab.HQ.myorg.us
# echo $?
0

13.3.1.2 Tips

  • Make sure that /etc/named.conf lists the right parent. Configure the DNS server as forwarder.

  • Add the host name to /etc/hosts.

  • When using DHCP to configure the external (WAN) network interface of the Branch Server, set the DHCP client on the Branch Server to modify named.conf instead of resolv.conf in /etc/sysconfig/network/config. The variables are MODIFY_RESOLV_CONF_DYNAMICALLY and MODIFY_NAMED_CONF_DYNAMICALLY. The template file is prepared for this.

13.3.2 Problems with Terminals after Branch Server Change

When a Branch Server is changed or reinstalled, but some terminals are still registered in the LDAP (for example, there are some scWorkstation objects under a respective scLocation), these terminals will not boot correctly. You need to re-create their config.<MAC> files manually.

To do this, run pos dump-all on the Branch Server. The command will create the needed files for all the affected terminals.

13.3.3 Problems with Changing the Branch Server Password

If it is not possible to change the Branch Server password using the posInitBranchServer -p command, you can change it manually:

On the Admin server, change the password in the LDAP database. Enter the following command in the command line (replace the mybranch, myorgunit, myorg and us variables with your configured values):

ldappasswd -x -d localhost -D "cn=admin,o=myorg,c=us" -w "admin_password" "cn=mybranch,ou=myorg,o=myorg,c=us" -s "new_branch_password"

On a Branch Server, follow the same procedures as in Section 4.1.1, “Changing the Administration Server Password”, but with a new Branch Server password and configuration file /etc/SLEPOS/branchserver.conf.

13.4 Operation

The following sections describe frequently encountered difficulties with system operation.

13.4.1 Image Building

Image Creator or KIWI cannot determine which user groups (GIDs) are to be created in post-installation scripts by the selected packages. If there is a conflict between GIDs added in the user configuration and GIDs added by post-installation scripts, image building will fail.

13.4.1.1 Symptoms

Image building fails with a message like groupadd: GID 100 is not unique or similar.

13.4.1.2 Tip

When configuring users to be created on the target system, avoid conflicting GIDs.

13.4.2 Image Distribution

The possyncimages tool distributes the boot and client images from the Administration Server to the Branch Server. It uses the rsync service to let the Branch Servers only download the files that need to be updated.

Enough space should be configured to keep at least two generations of image files. This redundancy ensures that there is a valid image available at all times.

rsync updates existing files, creates new files, and even deletes files that do not exist in the original download directory on the Administration Server.

13.4.2.1 Symptoms

The error message rsync: error writing 4 unbuffered bytes -exiting: Broken Pipe indicates that the Branch Server does not have enough disk space left to download all the images. Adequate space is required for both the staging area in /srv/SLEPOS/ and the service area in /srv/tftpboot.

13.4.2.2 Tips

  • Make sure that config.MAC files are regenerated (via the pos dump-all command on the Branch Server or via the scConfigUpdate attribute under the relevant scWorkstation set to TRUE) after new images have been distributed and especially after old images have been deleted.

  • Make sure that there is enough space for new images even before old images have been deleted or delete old images before uploading new ones.

13.4.3 Point of Service Terminal Configuration

The process of registering new Point of Service terminals and updating the configuration information usually works without administrator intervention; however, it is a complex process. To simplify this process, you must ensure the Administration Server always has a valid image configuration. In LDAP, the image versions must be entered and made active (see Section 4.6.2.6, “Adding an scPosImage Object” for details), and the image files must be made available with the right file name (image_name-version) and with the right permissions (world-readable).

13.4.3.1 Symptoms

The error message No Imageversion is available from posleases2ldap or pos dump-all means that no valid image file for the active version exists. Make sure that the image has been transferred to the Branch Server and that the version in LDAP has an active flag attached.

13.4.3.2 Tip

Keep at least two generations of image files available and active in LDAP at all times. The Point of Service downloads the latest client image version available on the Branch Server.

13.4.3.3 Troubleshooting Terminal Bootup Problems

If the Point of Service terminal does not successfully boot, check the following:

  • Verify that an scCashRegister object exists for the Point of Service terminal. For more information, see Section 4.6.2.1, “Adding an scCashRegister Object”.

  • Verify the configuration of the scCashRegister object for the Point of Service terminal. There must either be an scCashRegister object that corresponds to the HWTYPE attribute in the Point of Service terminal's hwtype.MAC.HASH file in the /srv/tftpboot/upload/hwtype directory or a default scCashRegister object that will work for the Point of Service terminal.

  • Verify that the Point of Service image configured in the scPosImageDn attribute of the scCashRegister object is available in the /srv/tftpboot/image/ directory on the Branch Server.

  • Do not delete any of the default LDAP objects that are created when you install SUSE Linux Enterprise Point of Service. In particular, do not delete the global default minimal scPosImage object that is created in the default Distribution Container, even if you do not plan to use the minimal image.

  • Each type of Point of Service terminal hardware must have a unique model name defined in the scCashRegisterName attribute of the scCashRegister object in LDAP.

    If two terminals have the same hardware name defined in their scPosImage objects, neither of them boots successfully, but an HWtype error is displayed on the Branch Server. To resolve the problem, change the scCashRegisterName value for one of the Point of Service terminals.

  • Check the boot.kiwi log file of the terminal which failed to boot. This log file is uploaded to the Branch Server when the terminal fails to boot. The file is located in upload/boot.kiwi.MAC. If kiwidebug is enabled, the log file is always uploaded before starting the system image.

13.4.4 Loading CDBoot Images

If there are multiple CD drives in the Point of Service terminal, there is no way to designate a CD drive to use; the system chooses the first one it finds.

13.4.4.1 Symptoms

If the Point of Service terminal does not find the drive with the boot CD, it returns BIOS errors.

13.4.4.2 Solution

To solve the problem, insert the CD in the bootable CD drive.

13.5 Known Issues

This section describes known issues of the SUSE® Linux Enterprise Point of Service 11 system.

13.5.1 Image Creator Does Not Verify Group Name Validity

Image creator does not verify group name validity, therefore the administrator must make sure to only use group names beginning with a letter.

13.5.2 Roles Are Not Safely Escaped

The role name and description must not contain | and \n characters. Safe characters for cn in LDAP are [-_a-zA-Z0-9].

Print this page