Suse working with SMT server

From Notes_Wiki

Home > Suse > Suse working with SMT server

About SMT

To help with product updates and registrations centrally via a local server without requiring each server to have outgoing connectivity directly to Suse Customer Center (SCC) or Internet. This also helps in avoiding repeat download of OS update packages for each server over WAN link.


Error while registering an internal machine with local SMT

We might see error such as below while using local SMT server: 

Activating SLES_SAP 15.1 x86_64 ...
Error: Registration server returned 'Product not (fully) mirrored on this server.
Mirroring of the following repos has to be enabled on the SMT server:
  * SLE-Product-SLES_SAP15-SP1-Pool (SLES_SAP,15.1,x86_64)
  * SLE-Product-SLES_SAP15-SP1-Updates (SLES_SAP,15.1,x86_64)

For these refer:


Basics of SMT

We can use

To list all repos
smt-repos
List only repos that are mirrored
smt-repos -m
See whether specific repository is mirrored
smt-repos | grep SLE-Product-SLES_SAP15-SP1-Pool
Enable mirroring for a repository
  • smt-repos -m -e SLE-Product-SLES_SAP15-SP1-Pool
  • smt-repos -m -e SLE-Product-SLES_SAP15-SP1-Updates
Then sync via
smt-sync; smt-mirror


Troubleshooting SMT issues

Unfortunately when we enable verbose and logging for smt-sync it is clear that sites are not reachable 

 smt-sync -v 5 --logfile /tmp/smt.log

followed by 'tail -f /tmp/smt.log' we can see: 

2023-06-22 11:40:54 main - [info]  Downloading Product and Repository information
2023-06-22 11:40:54 SMT::SCCAPI - [info]  list products
2023-06-22 11:40:59 SMT::SCCAPI - [error]  Connection to registration server failed with: 500 CURL ERROR(28) Timeout was reached
2023-06-22 11:40:59 main - [error]  Error while fetching Product and Repository data.
2023-06-22 11:40:59 main - [info]  Downloading Subscription information
2023-06-22 11:40:59 SMT::SCCAPI - [info]  list organization subscriptions
2023-06-22 11:41:04 SMT::SCCAPI - [error]  Connection to registration server failed with: 500 CURL ERROR(28) Timeout was reached
2023-06-22 11:41:04 main - [error]  Error while fetching Subscriptions data.
2023-06-22 11:41:04 main - [info]  Downloading Order information
2023-06-22 11:41:04 SMT::SCCSync - [info]  Downloading Orders skipped
2023-06-22 11:41:04 main - [info]  Flagging repositories which can be mirrored
2023-06-22 11:41:04 SMT::SCCAPI - [info]  list organization repositories
2023-06-22 11:41:09 SMT::SCCAPI - [error]  Connection to registration server failed with: 500 CURL ERROR(28) Timeout was reached


Enabling repositories at SMT server for sync / mirror

We can see which repositories are enabled via: 

# smt-repos | grep SLE-Product-SLES_SAP15-SP1-Pool
| No      | 2910 | nu   | SLE-Product-SLES_SAP15-SP1-Pool                                     | sle-15-ppc64le | SLE-Product-SLES_SAP15-SP1le                                    | No              | No      |
| No      | 2911 | nu   | SLE-Product-SLES_SAP15-SP1-Pool                                     | sle-15-x86_64  | SLE-Product-SLES_SAP15-SP14                                     | Yes             | No      |

We can optionally enable a repo using: 

# smt-repos -m -e SLE-Product-SLES_SAP15-SP1-Pool
1 repository enabled.

Then validate whether repository is enabled properly or not via: 

# smt-repos | grep SLE-Product-SLES_SAP15-SP1-Pool
| No      | 2910 | nu   | SLE-Product-SLES_SAP15-SP1-Pool                                     | sle-15-ppc64le | SLE-Product-SLES_SAP15-SP1le                                    | No              | No      |
| Yes     | 2911 | nu   | SLE-Product-SLES_SAP15-SP1-Pool                                     | sle-15-x86_64  | SLE-Product-SLES_SAP15-SP14                                     | Yes             | No      |


Refer:


Home > Suse > Suse working with SMT server

Retrieved from "http://www.sbarjatiya.com/notes_wiki/index.php?title=Suse_working_with_SMT_server&oldid=8117"