SUSE Support

Here When You Need Us

clientSetup4SMT.sh exists with "There are no enabled services defined."

This document (7010802) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 2
SUSE Linux Enterprise Server 11 Service Pack 1

Situation

clientSetup4SMT.sh shows the following output when trying to register a client:

clientSetup4SMT.sh --host smt.domain.tld
...
Do you accept this certificate? [y/n] y
Client setup finished.
Start the registration now? [y/n] y
/usr/bin/suse_register -i -L /root/.suse_register.log
There are no enabled services defined.
Use 'zypper addservice' or 'zypper modifyservice' commands to add or enable services.
There are no enabled repositories defined.
Use 'zypper addrepo' or 'zypper modifyrepo' commands to add or enable repositories.
Refreshing service 'SMT-http_smt_domain_tld'.
Permission to access 'http://smt.domain.tld//repo/repoindex.xml?credentials=NCCcredentials' denied.

Resolution

Preferred solution:

Instead of moving the data to a different location in the filesystem, mount the block device holding the SMT data directly at /srv/www/htdocs/repo and set the appropriate access permissions. The directory and its subfolders need to be owned by user 'smt' and group 'www' with permissions 755 for directories and 644 for files. An entry for /etc/fstab using a logical volume would look like:
/dev/vgname/lvname    /srv/www/htdocs/repo xfs     defaults 1 2
Possibility B)

/etc/smt.d/nu_server.conf
defines the http settings for /srv/www/htdocs/repo and already allows following symlinks in this directory. To make use of this, create symbolic links from inside the /srv/www/htdocs/repo directory and point to the subdirectories in the data folder, e.g.:

smt:~/data/repo # l
total 0
drwxr-xr-x 2 root root  77 Sep 20 16:56 ./
drwxr-xr-x 7 root root 151 Sep 20 16:56 ../
lrwxrwxrwx 1 root root  12 Sep 20 16:56 full -> /srv/www/htdocs/repo/full/
lrwxrwxrwx 1 root root  12 Sep 20 16:56 keys -> /srv/www/htdocs/repo/keys/
lrwxrwxrwx 1 root root  12 Sep 20 16:56 $RCE -> /srv/www/htdocs/repo/$RCE/
lrwxrwxrwx 1 root root  13 Sep 20 16:56 RPMMD -> /srv/www/htdocs/repo/RPMMD/
lrwxrwxrwx 1 root root  15 Sep 20 16:56 testing -> /srv/www/htdocs/repo/testing/
lrwxrwxrwx 1 root root  13 Sep 20 16:56 tools -> /srv/www/htdocs/repo/tools/
smt:~/data/repo #
Possibility C)

Edit /etc/apache2/default-server.conf and search for the line "Options None" (around line 22) and change this to "Options Indexes FollowSymLinks", then restart the apache2 service. This enables Index view and following symbolic links on the whole webserver. This is only recommended if the webserver is used to act as update server only and located on a protected, internal network.

Cause

The SMT directory /srv/www/htdocs/repo was moved to a different location in the file system and a symbolic link points to the new location. The Apache webserver does not follow symbolic links by default and thus access to the linked directory is denied.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7010802
  • Creation Date: 20-Sep-2012
  • Modified Date:03-Mar-2020
    • Subscription Management Tool
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

tick icon

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

tick icon

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

tick icon

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.