26.5 Troubleshooting
This section covers frequent problems encountered with SCPM. Learn how they
can arise and how you can solve these issues.
26.5.1 SCPM and NetworkManager
NetworkManager and SCPM share functionality. Both integrate a machine
into an existing network, hiding this transaction from the user.
NetworkManager works dynamically and adapts to any new environment. SCPM is
used to restore defined system setups.
Using NetworkManager and SCPM in parallel does not work properly, because NetworkManager does
not provide configurations that can be restored by SCPM. SCPM works
exceedingly well for anyone who needs reproducible setups. Any private user
constantly switching networks should consider using NetworkManager if network setup
is the only component that needs to be adjusted. If you want to use SCPM to
manage your system configuration but NetworkManager to manage networking, remove the
network resource from SCPM.
If you want to use SCPM for network configuration management,
disable NetworkManager.
26.5.2 Termination During the Switch Process
Sometimes SCPM stops working during a switch procedure. This may be caused
by some outside effect, such as a user abort, a power failure, or even an
error in SCPM itself. If this happens, an error message stating SCPM is
locked appears the next time you start SCPM. This is for system safety,
because the data stored in its database may differ from the state of the
system. To resolve this issue, run scpm
recover. SCPM performs all missing
operations of the previous run. You can also run scpm
recover -b, which tries to undo all already
performed operations of the previous run. If you are using the YaST
profile manager, get a recover dialog on start-up that offers
to perform the commands described above.