I'm having trouble installing gcc on a new SLES 12 box. The goal here is actually to get R Shiny running, but when I try to install any packages I get the below error: sudo su - -c "R -e \"install.packages('Rcpp',repos='https://cran.rstudio.com/ ')\"" make: g++: Command not found This leads me to believe I need to install gcc. which gcc: which: no gcc in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/games) gcc -version: `If 'gcc' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf gcc` This is where the trouble begins. When I zypper in gcc: `Problem: gcc-4.7-7.1.1.x86_64 requires gcc47, but this requirement cannot be provided uninstallable providers: gcc47-4.7.2_20130108-2.1.6.i586[oss] gcc47-4.7.2_20130108-2.1.6.x86_64[oss]` Ok.. zypper in gcc47-4.7.2_20130108-2.1.6.x86_64 Results: `Problem: gcc47-4.7.2_20130108-2.1.6.x86_64 requires glibc-devel, but this requirement cannot be provided uninstallable providers: glibc-devel-2.17-4.4.1.i586[oss] glibc-devel-2.17-4.4.1.x86_64[oss]` Right then... zypper in glibc-devel Results: `Problem: glibc-devel-2.17-4.4.1.x86_64 requires glibc = 2.17, but this requirement cannot be provided uninstallable providers: glibc-2.17-4.4.1.i586[oss] glibc-2.17-4.4.1.x86_64[oss]` zypper in glibc Results: `'glibc' is already installed. No update candidate for 'glibc-2.19-17.72.x86_64'. The highest available version is already installed. So somewhere in this chain of dependencies an RPM needs a lower version of something I already have. I don't want to downgrade the system. Is there some way to get the most up to date GCC that will work with glibc-2.19? Am I doing something wrong here? Am I missing a repo? SLSE12:~ # cat /etc/os-release NAME="SLES" VERSION="12" VERSION_ID="12" PRETTY_NAME="SUSE Linux Enterprise Server 12" ID="sles" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:12" # zypper lr -u # | Alias | Name | Enabled | Refresh | URI --+-----------+-----------+---------+---------+------------------------------------------------------------------------------- 1 | gcc | gcc | Yes | No | http://download.opensuse.org/repositories/devel:/gcc/SLE-12/ 2 | oss | oss | Yes | No | http://download.opensuse.org/distribution/12.3/repo/oss/ 3 | r-patched | r-patched | Yes | No | http://download.opensuse.org/repositories/devel:/languages:/R:/patched/SLE_12/

I am having trouble updating a SLES 12.5 server. Zypper is not working supposedly due to another zypper process already running:

# zypper lu
System management is locked by the application with pid 25074 (zypper).
Close this application before trying again.

If I try again, the PID changes:

# zypper lu
System management is locked by the application with pid 27117(zypper).
Close this application before trying again.

If I try to kill 27117, it doesn't work as it is not there anymore:

# kill 27117
bash: kill: (27117) - No such process

The PID is stored in

# cat /var/run/zypp.pid
31776

and here too, if I repeat the command, I get a different PID:

# cat /var/run/zypp.pid
525

This is what zypper.log looks like when I issue a zypper lu command:

2023-10-10 22:10:52  myhostname(27119) [zypper] main.cc(main):97 ===== Hi, me zypper 1.13.64
2023-10-10 22:10:52  myhostname(27119) [zypper] main.cc(main):98 ===== 'zypper' 'lu' =====
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(_autodetectSystemArchitecture):73 Uname architecture is 'x86_64'
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(_autodetectTextLocale):209 Default text locale is 'en'
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(Impl):343 libzypp: 16.22.8
2023-10-10 22:10:52  myhostname(27119) [zypp] IniParser.cc(parse):84 Start parsing /etc/zypp/zypp.conf[g___]
2023-10-10 22:10:52  myhostname(27119) [zypp] IniParser.cc(parse):138 Done parsing /etc/zypp/zypp.conf[_eF_]
2023-10-10 22:10:52  myhostname(27119) [Progress++] ProgressData.cc(report):88 {#1|/etc/zypp/zypp.conf}END
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(Impl):621 ZConfig singleton created.
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 libzypp: 16.22.8
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 libsolv: 0.6.39
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 zypp.conf: '/etc/zypp/zypp.conf'
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 TextLocale: 'en' (en)
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 SystemArchitecture: 'x86_64' (x86_64)
2023-10-10 22:10:52  myhostname(27119) [zypp] PathInfo.cc(assert_dir):354 mkdir /var/tmp/zypp.hVcxMA/zypper 00755
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(Zypper):552 Zypper instance created.
2023-10-10 22:10:52  myhostname(27119) [zypper] media.h(MediaCallbacks):182 Set media callbacks..
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processGlobalOptions):891 START
2023-10-10 22:10:52  myhostname(27119) [Measure] Measure.cc(log):178 START MEASURE(ReadConfig)
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):21 Going to read zypper config using Augeas...
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):103 Done reading conf files:
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):108 user conf read: no
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):109 global conf read: yes
2023-10-10 22:10:52  myhostname(27119) [Measure] Measure.cc(log):178 ELAPSED(ReadConfig) 0 (u 0.01 s 0.00 c 0.00)
2023-10-10 22:10:52  myhostname(27119) [Measure] Measure.cc(log):178 MEASURE(ReadConfig) 0 (u 0.01 s 0.00 c 0.00) [0 (u 0.00 s 0.00 c 0.00)]
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1019 Verbosity 1
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1020 Output type 1
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1280 repos.d dir = /etc/zypp/repos.d
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1281 cache dir = /var/cache/zypp
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1282 raw cache dir = /var/cache/zypp/raw
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1283 solv cache dir = /var/cache/zypp/solv
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1284 package cache dir = /var/cache/zypp/packages
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processGlobalOptions):1296 Repositories enabled
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processGlobalOptions):1414 DONE
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processCommandOptions):1606 START
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processCommandOptions):3536 Done parsing options.
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processCommandOptions):3555 Done
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(_openLockFile):168 Open lockfile /var/run/zypp.pid
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(readLockFile):223 read: Lockfile /var/run/zypp.pid has pid 27117 (our pid: 27119)
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(isProcessRunning):195 Checking /proc/27117{d 0555 0/0}
2023-10-10 22:10:52  myhostname(27119) [zypp++] ZYppFactory.cc(isProcessRunning):209 Is running: zypper
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(zyppLocked):270 27117 is running and has a ZYpp lock. Sorry.
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(_closeLockFile):186 Close lockfile /var/run/zypp.pid
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 ZYppFactory.cc(getZYpp):404 THROW:    System management is locked by the application with pid 27117 (zypper).
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Close this application before trying again.
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Zypper.cc(assertZYppPtrGod):267 CAUGHT:   System management is locked by the application with pid 27117 (zypper).
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Close this application before trying again.
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(assertZYppPtrGod):303 A ZYpp transaction is already in progress.
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.h(setExitCode):250 setExitCode 7
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Zypper.cc(assertZYppPtrGod):307 THROW:    ZYpp locked
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Zypper.cc(safeDoCommand):1582 CAUGHT:   ZYpp locked
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(safeDoCommand):1583 Caught exit request: exitCode 7
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(cleanup):5575 START
2023-10-10 22:10:52  myhostname(27119) [zypper] main.cc(~Bye):82 ===== Exiting main() =====
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(~Zypper):559 Zypper instance destroyed. Bye!
2023-10-10 22:10:52  myhostname(27119) [zypp] PathInfo.cc(recursive_rmdir):435 recursive_rmdir /var/tmp/zypp.hVcxMA
2023-10-10 22:10:52  myhostname(27119) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/zypp.hVcxMA{d 0700 0/0}

Any idea of what could be going on here? I have solved this in the past by rebooting, but I want to find a better, not so drastic solution. **UPDATE**: I never found the solution, but I found a rude workaround. Since the PID keeps changing that means that after a process closes and before the new one is spawn, there is a time gap where I can run zypper lu. So I just try again and again until I hit that gap and it works just fine.

I am using NFS client to connect to NFS cluster. I have noticed that the default behaviour when server is unavailable is to retry the TCP connections from the same source TCP port, which I have confirmed by tcpdump (many SYN packets, different seq numbers, but same source port). By default NFS uses priviledged ports (1024 and and now on each reconnect attempt will be from different TCP port. NFS client is SLES12 SP4, the same behaviour is also on Oracle Linux 7.7. NFS server is HAE cluster based on SLES12 SP4. Is this behaviour documented somewhere? Why it does use the same port every time by default but not when using noresvport?

Where can I find the syslog config file under SLES 12? rsyslog and syslog-service are installed according to YaST2 and rcsyslog status outputs: ServerName:~ # rcsyslog status Usage: /sbin/rcsyslog {start|stop|status|try-restart|restart|force-reload|reload} rsyslog.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled) Active: active (running) since Wed 2015-03-04 16:05:46 CET; 1 day 17h ago Main PID: 787 (rsyslogd) CGroup: /system.slice/rsyslog.service ââ787 /usr/sbin/rsyslogd -n

Somehow I ended up in SLES 15 with error messages like this: > (systemd): PAM unable to dlopen(/lib64/security/pam_ldap.so): /lib64/security/pam_ldap.so: cannot open shared object file: No such file or directory However I'm not sure what lead to that situation, and also I'm unsure how to fix it, because there is no RPM with pam_ldap.so it seems. The system had been upgraded from SLES 12 SP5 via SLES 15 SP3 to SLES 15 SP4. Obviously LDAP client configuration was intended and once worked, but it does not at the moment.

I am in the middle of an activity and have never worked with SLES10 SP4 In SLES11 zypper update glibc* updates all glibc packages .. but this is not working in SLES10 SP4 .. can someone tell me how to update a single package in SLES10 SP4

After upgrading from SLES12 SP5 to SLES15 SP6 I noticed that the %clean phase of some RPM spec files fail for some strange reason when using rpmbuild -ba. The RPMs (SRPM, RPMs) are written correctly, but when cleaning up I see errors like this: ~~~lang-text Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.IXMkuS + umask 022 + cd /home/windl/rpmbuild/BUILD + cd iredir-0.5.1n + for d in "/home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64" + '[' -n /home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64 -a /home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64 '!=' / ']' + ls -l /home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64 total 12 drwxr-xr-x 6 windl dvmed 4096 Mar 10 10:40 etc drwxr-xr-x 6 windl dvmed 4096 Mar 10 10:40 usr drwxr-xr-x 5 windl dvmed 4096 Mar 10 10:40 var + rm -rf /home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64 rm: cannot remove '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64/usr/lib/ocf/resource.d/xola': Directory not empty rm: cannot remove '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64/usr/lib/iredir': Directory not empty rm: cannot remove '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64/etc/ocf/xola/isredir': Directory not empty rm: cannot remove '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64/etc/ocf/xola/idredir': Directory not empty rm: cannot remove '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.1n-0.0.x86_64/etc/init.d': Directory not empty error: Bad exit status from /var/tmp/rpm-tmp.IXMkuS (%clean) ~~~ This is very strange as rm -rf is supposed to remove non-empty directories. I added the ls command after having experienced the issue: ~~~lang-rpm %clean # called for %install for d in "%{buildroot}" do [ -n "$d" -a "$d" != / ] && ls -l "$d" && rm -rf "$d" done ~~~ What might cause this? It seems like some asynchronous effect tto me. ~ is on NFS (also hosted by SLES15 (but SP5) (nfs-kernel-server-2.1.1-150500.22.3.1.x86_64, kernel 5.14.21-150500.55.83-default)). /usr/bin/rm is from coreutils-8.32-150400.9.6.1.x86_64. More Details ------------ I changed the RPM spec file to recursively list the whole directory, also adding -v to the rm command. When I see is that a directory contains four (normal) files that are deleted just before rm complains the directory isn't empty. More tests ---------- The effect is strange: When I created a test script that creates a directory, adds four files, and then removed that directory, it always works, while the rpmbuild -ba always fails for the same directory. Well, the total length of the paths for the rpmbuild is somewhat longer, but still smaller than say 120 characters. So I ran the whole thing under strace -f -s64with these results: ~~~lang-strace 1079 newfstatat(7, "xola", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 1079 openat(7, "xola", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_NOFOLLOW|O_DIRECTORY) = 3 1079 fstat(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 1079 fcntl(3, F_GETFL) = 0x38800 (flags O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW|O_DIRECTORY) 1079 fcntl(3, F_SETFD, FD_CLOEXEC) = 0 1079 getdents64(3, 0x55d729e27910 /* 6 entries */, 1048576) = 176 1079 close(3) = 0 1079 openat(7, "xola", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_NOFOLLOW|O_CLOEXEC|O_DIRECTORY) = 3 1079 fstat(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 1079 fcntl(3, F_GETFL) = 0x38800 (flags O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW|O_DIRECTORY) 1079 fcntl(3, F_SETFD, FD_CLOEXEC) = 0 1079 fcntl(3, F_DUPFD_CLOEXEC, 3) = 8 1079 getdents64(3, 0x55d729e27910 /* 6 entries */, 1048576) = 176 1079 getdents64(3, 0x55d729e27910 /* 0 entries */, 1048576) = 0 1079 close(3) = 0 1079 unlinkat(8, "isredir", 0) = 0 1079 write(1, "removed '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.3n-0.0.x86_64"..., 102) = 102 1079 unlinkat(8, "idredir.xml", 0) = 0 1079 write(1, "removed '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.3n-0.0.x86_64"..., 106) = 106 1079 unlinkat(8, "isredir.xml", 0) = 0 1079 write(1, "removed '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.3n-0.0.x86_64"..., 106) = 106 1079 unlinkat(8, "idredir", 0) = 0 1079 write(1, "removed '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.3n-0.0.x86_64"..., 102) = 102 1079 close(8) = 0 1079 unlinkat(7, "xola", AT_REMOVEDIR) = -1 ENOTEMPTY (Directory not empty) 1079 write(2, "rm: ", 4) = 4 1079 write(2, "cannot remove '/home/windl/rpmbuild/BUILDROOT/iredir-0.5.3n-0.0."..., 99) = 99 1079 write(2, ": Directory not empty", 21) = 21 1079 write(2, "\n", 1) = 1 1079 close(7) = 0 1079 close(6) = 0 ~~~ So in my interpretation the xolasubdirectory has four files (with . and .. that are six directory entries). Before ls -lR showed ~~~lang-text /home/windl/rpmbuild/BUILDROOT/iredir-0.5.3n-0.0.x86_64/usr/lib/ocf/resource.d/xola: total 56 drwxr-xr-x 2 windl dvmed 4096 Mar 12 08:03 . drwxr-xr-x 3 windl dvmed 4096 Mar 12 08:03 .. -r-xr-xr-x 1 windl dvmed 13228 Oct 21 2019 idredir -r--r--r-- 1 windl dvmed 5543 Oct 10 2019 idredir.xml -r-xr-xr-x 1 windl dvmed 13507 Oct 21 2019 isredir -r--r--r-- 1 windl dvmed 5774 Oct 10 2019 isredir.xml ~~~ The four files were deleted successfully (rm -vrf being used), but then the directory could not be deleted. Somewhow I suspect the NFS attribute cache on either the client or on the server to cause this.

For some reason my server with SLES 15 SP4 is not keeping the log data in journalctl for more than 2 days. My journald.conf looks like this:

[Journal]
Storage=persistent
Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
SystemMaxUse=10G
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
MaxRetentionSec=2month
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
#ReadKMsg=yes
#Audit=yes

But no matter what I try, no log is older than 2 days. I also tried with the

--since

and

--until

flag but still no luck. What can I do to make journald logs persistent?

one of the SuSE 12 LinuxServers has reported disk failure. Fortunately the Database Server has Software Raid hence the system is still up and running. But as recommended, we would like to replace the failed disk with a new one and rebuild the software raid on it. System Information is : Total 4 Internal Disks. sda, sdb , sdc and sdd The fdisk partitions are : fdisk -l Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x0007d757 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 2105343 2103296 1G fd Linux raid autodetect /dev/sdb2 2105344 39858175 37752832 18G fd Linux raid autodetect /dev/sdb3 39858176 1953523711 1913665536 912.5G fd Linux raid autodetect Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x000a0e8a Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 1953523711 1953521664 931.5G fd Linux raid autodetect Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x000caaad Device Boot Start End Sectors Size Id Type /dev/sdd1 2048 1953523711 1953521664 931.5G fd Linux raid autodetect Software RAID --> sda + sdb (sda is failed disk) Software RAID --> sdb + sdc DBServer# cat /proc/mdstat Personalities : [raid1] md3 : active raid1 sdc1 sdd1 976760640 blocks super 1.0 [2/2] [UU] bitmap: 2/8 pages [8KB], 65536KB chunk md0 : active raid1 sdb1 sda10 1051584 blocks super 1.0 [2/1] [_U] bitmap: 1/1 pages [4KB], 65536KB chunk md2 : active raid1 sdb3 sda30 956832576 blocks super 1.0 [2/1] [_U] bitmap: 2/8 pages [8KB], 65536KB chunk md1 : active raid1 sdb2 sda20 18876288 blocks super 1.0 [2/1] [_U] bitmap: 0/1 pages [0KB], 65536KB chunk unused devices: So md0,md1 and md2 have failed devices namely sda1,sda2 and sda3 Please note that it also has 2 VGs defined as shown below, 1 VG - system (/dev/md2) 2 VG - ora_db (/dev/md3) pvdisplay --- Physical volume --- PV Name /dev/md3 VG Name ora_db PV Size 931.51 GiB / not usable 3.81 MiB Allocatable yes PE Size 4.00 MiB Total PE 238466 Free PE 84866 Allocated PE 153600 PV UUID vgPdWQ-x6CW-vvdF-moxh-FKyb-wpSU-NdJqSm --- Physical volume --- PV Name /dev/md2 VG Name system PV Size 912.51 GiB / not usable 2.81 MiB Allocatable yes PE Size 4.00 MiB Total PE 233601 Free PE 182401 Allocated PE 51200 PV UUID rdff2n-ztxd-lcBY-nAqk-8O9u-fnFG-BVI91v The grub.conf shows : (Relevant part) if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod part_msdos msdos insmod diskfilter mdraid1x lvm insmod ext2 set root='lvmid/m7AEp0-79EG-D2Vi-ELzE-BTzh-C8mN-CLxrpz/S0eZEl-PlBX-E1ZL-oCwL-SmUx-4Qe4-Mz9NHX' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='lvmid/m7AEp0-79EG-D2Vi-ELzE-BTzh-C8mN-CLxrpz/S0eZEl-PlBX-E1ZL-oCwL-SmUx-4Qe4-Mz9NHX' 7c2e3a9c-5f5b-47e3-8a0a-d1e66f12747c else search --no-floppy --fs-uuid --set=root 7c2e3a9c-5f5b-47e3-8a0a-d1e66f12747c fi font="/share/grub2/unicode.pf2" fi if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm set locale_dir=$prefix/locale set lang=POSIX insmod gettext fi terminal_output gfxterm insmod part_msdos msdos insmod diskfilter mdraid1x insmod ext2 set root='mduuid/531cd341e2c7d5a71c542ad04d9ea589' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/531cd341e2c7d5a71c542ad04d9ea589' 96c11697-c3b7-4f11-90fc-3aef207db526 else search --no-floppy --fs-uuid --set=root 96c11697-c3b7-4f11-90fc-3aef207db526 fi Quote: The procedure to follow should go like this, > First we mark /dev/sda1 as failed: mdadm --manage /dev/md0 --fail /dev/sda1 > Then we remove /dev/sda1 from /dev/md0: mdadm --manage /dev/md0 --remove /dev/sda1 > Now we do the same steps again for /dev/sda2 and sda3 (which is part > of /dev/md1 and /dev/md2) > > Then power down the system: shutdown -h now > and replace the old /dev/sdb hard drive with a new one > > After inserting new SATA disk /dev/sda, boot the system. > > Then we create the exact same partitioning as on /dev/sda. We can do > this with one simple command: > sfdisk -d /dev/sdb | sfdisk /dev/sda > Check if both the disks have same partitions (fdisk -l) > 8.Next we add /dev/sda1 to /dev/md0 and /dev/sda2 to /dev/md1 and /dev/sda3 to /dev/md3: mdadm --manage /dev/md0 --add /dev/sda1 mdadm --manage /dev/md1 --add /dev/sda2 mdadm --manage /dev/md2 --add /dev/sda3 > Confirm the synchronisation in progress cat /proc/mdstat Please let me know if I have missed something. 2 important points I guess would be, how should I take care of lvm and grub in this case. Do I have to do something extra to take care of it or the command sfdisk -d /dev/sdb | sfdisk /dev/sda , should take care of LVM as well. How should I take care of grub in this case? As grun.conf shows entries pertaining to LVM as well as MDADM. Do I have to change anything here before I shutdown the system? I understand the system has 2 pointers to take care of mdadm+lvm. Which have complicated things. Else would it be easier to setup completely new system? Not yet tried anything. Only collecting information. grub.cfg ### BEGIN /etc/grub.d/00_header ### if [ -f ${config_directory}/grubenv ]; then load_env -f ${config_directory}/grubenv elif [ -s $prefix/grubenv ]; then load_env fi if [ "${env_block}" ] ; then load_env -f "${env_block}" fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry if [ "${env_block}" ] ; then save_env -f "${env_block}" next_entry fi set boot_once=true else set default="${saved_entry}" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod part_msdos msdos insmod diskfilter mdraid1x lvm insmod ext2 set root='lvmid/m7AEp0-79EG-D2Vi-ELzE-BTzh-C8mN-CLxrpz/S0eZEl-PlBX-E1ZL-oCwL-SmUx-4Qe4-Mz9NHX' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='lvmid/m7AEp0-79EG-D2Vi-ELzE-BTzh-C8mN-CLxrpz/S0eZEl-PlBX-E1ZL-oCwL-SmUx-4Qe4-Mz9NHX' 7c2e3a9c-5f5b-47e3-8a0a-d1e66f12747c else search --no-floppy --fs-uuid --set=root 7c2e3a9c-5f5b-47e3-8a0a-d1e66f12747c fi font="/share/grub2/unicode.pf2" fi if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm set locale_dir=$prefix/locale set lang=POSIX insmod gettext fi terminal_output gfxterm insmod part_msdos msdos insmod diskfilter mdraid1x insmod ext2 set root='mduuid/531cd341e2c7d5a71c542ad04d9ea589' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/531cd341e2c7d5a71c542ad04d9ea589' 96c11697-c3b7-4f11-90fc-3aef207db526 else search --no-floppy --fs-uuid --set=root 96c11697-c3b7-4f11-90fc-3aef207db526 fi insmod gfxmenu loadfont ($root)/grub2/themes/SLE/DejaVuSans-Bold14.pf2 loadfont ($root)/grub2/themes/SLE/DejaVuSans10.pf2 loadfont ($root)/grub2/themes/SLE/DejaVuSans12.pf2 loadfont ($root)/grub2/themes/SLE/ascii.pf2 insmod png set theme=($root)/grub2/themes/SLE/theme.txt export theme if [ x${boot_once} = xtrue ]; then set timeout=0 elif [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=8 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=8 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'SLES12' --class sles12 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-690785da-f0f0-4250-b693-5a008acbba10' { load_video set gfxpayload=keep insmod gzio insmod part_msdos msdos insmod diskfilter mdraid1x insmod ext2 set root='mduuid/531cd341e2c7d5a71c542ad04d9ea589' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/531cd341e2c7d5a71c542ad04d9ea589' 96c11697-c3b7-4f11-90fc-3aef207db526 else search --no-floppy --fs-uuid --set=root 96c11697-c3b7-4f11-90fc-3aef207db526 fi echo 'Loading Linux 3.12.28-4-default ...' linux /vmlinuz-3.12.28-4-default root=UUID=690785da-f0f0-4250-b693-5a008acbba10 resume=/dev/md1 splash=silent quiet crashkernel=232M-:116M showopts echo 'Loading initial ramdisk ...' initrd /initrd-3.12.28-4-default } submenu 'Advanced options for SLES12' --hotkey=1 $menuentry_id_option 'gnulinux-advanced-690785da-f0f0-4250-b693-5a008acbba10' { menuentry 'SLES12, with Linux 3.12.28-4-default' --hotkey=2 --class sles12 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.12.28-4-default-advanced-690785da-f0f0-4250-b693- 5a008acbba10' { load_video set gfxpayload=keep insmod gzio insmod part_msdos msdos insmod diskfilter mdraid1x insmod ext2 set root='mduuid/531cd341e2c7d5a71c542ad04d9ea589' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/531cd341e2c7d5a71c542ad04d9ea589' 96c11697-c3b7-4f11-90fc-3aef207db526 else search --no-floppy --fs-uuid --set=root 96c11697-c3b7-4f11-90fc-3aef207db526 fi echo 'Loading Linux 3.12.28-4-default ...' linux /vmlinuz-3.12.28-4-default root=UUID=690785da-f0f0-4250-b693-5a008acbba10 resume=/dev/md1 splash=silent quiet crashkernel=232M-:116M showopts echo 'Loading initial ramdisk ...' initrd /initrd-3.12.28-4-default } menuentry 'SLES12, with Linux 3.12.28-4-default (recovery mode)' --hotkey=3 --class sles12 --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.12.28-4-default-recovery- 690785da-f0f0-4250-b693-5a008acbba10' { load_video set gfxpayload=keep insmod gzio insmod part_msdos msdos insmod diskfilter mdraid1x insmod ext2 set root='mduuid/531cd341e2c7d5a71c542ad04d9ea589' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/531cd341e2c7d5a71c542ad04d9ea589' 96c11697-c3b7-4f11-90fc-3aef207db526 else search --no-floppy --fs-uuid --set=root 96c11697-c3b7-4f11-90fc-3aef207db526 fi echo 'Loading Linux 3.12.28-4-default ...' linux /vmlinuz-3.12.28-4-default root=UUID=690785da-f0f0-4250-b693-5a008acbba10 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe crashkernel=232M-:116M echo 'Loading initial ramdisk ...' initrd /initrd-3.12.28-4-default } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_memtest86+ ### ### END /etc/grub.d/20_memtest86+ ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### ### BEGIN /etc/grub.d/80_suse_btrfs_snapshot ### ### END /etc/grub.d/80_suse_btrfs_snapshot ### ### BEGIN /etc/grub.d/90_persistent ### ### END /etc/grub.d/90_persistent ### I did install grub on /dev/sdb. Please find the output. # grub2-install /dev/sdb Installing for i386-pc platform. error: cannot read `/dev/sda': Input/output error. error: cannot read `/dev/sda': Input/output error. error: cannot read `/dev/sda': Input/output error. error: cannot read `/dev/sda': Input/output error. error: cannot read `/dev/sda': Input/output error. grub2-install: warning: Couldn't find physical volume `(null)'. Some modules may be missing from core image.. error: cannot read `/dev/sda': Input/output error. error: cannot read `/dev/sda': Input/output error. error: cannot read `/dev/sda': Input/output error. error: cannot read `/dev/sda': Input/output error. error: cannot read `/dev/sda': Input/output error. grub2-install: warning: Couldn't find physical volume `(null)'. Some modules may be missing from core image.. Installation finished. No error reported. Not sure why it gave sda errors though. And then cross checked with following command again. # dd bs=512 count=1 if=/dev/sdb 2>/dev/null| strings ZRr= `|f \|f1 GRUB Geom Hard Disk Read Error

Apologies if this is a stoopid question. With some effort I have managed to install openSUSE Leap 15.3 on my laptop. As you may know 15.3 is rather different to earlier releases in that it apparently "uses binaries from" SLE 15 SP3. Unfortunately, another difference appears to be that many packages which were there all the way up to 15.2 appear to be missing, I've seen the line [There is no official package available for openSUSE Leap 15.3](https://software.opensuse.org/package/llvm) (this example is llvm) way more often than I care. So my question: Is it generally possible / safe to use SLE 15 SP3 repositories instead? (I see that one of the automatic update repositories is indeed SLE.) I daren't simply try for fear of damaging my system.

I tried to resize partitions on a SLES 15 server by using gdisk. No matter what I try to do, I cant get it to work after rebooting the system. Initial situation: I have a boot partition (/dev/sda1), a / partition (/dev/sda2), a /home partition (/dev/sda3) and swap (/dev/sda4). I want to recreate the /home partition with less space and increase space on the / partition. These are the steps I did: 1.

/home

2. delete and recreate partitions:

SRV01:~ # gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.8

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/sda: 209715200 sectors, 100.0 GiB
Model: Virtual disk
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): E6F4D731-D49F-4BD7-8AF7-A0EDA544AE8C
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 209715166
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         1050623   512.0 MiB   EF00
   2         1050624        84936703   40.0 GiB    8300
   3        84936704       143968255   28.1 GiB    8300
   4       143968256       209715166   31.3 GiB    8200

Command (? for help): d
Partition number (1-4): 4

Command (? for help): d
Partition number (1-3): 3

Command (? for help): d
Partition number (1-2): 2

Command (? for help): n
Partition number (2-128, default 2): 2
First sector (34-209715166, default = 1050624) or {+-}size{KMGTP}:
Last sector (1050624-209715166, default = 209715166) or {+-}size{KMGTP}: +60G
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300):
Changed type of partition to 'Linux filesystem'

Command (? for help): n
Partition number (3-128, default 3): 3
First sector (34-209715166, default = 126879744) or {+-}size{KMGTP}:
Last sector (126879744-209715166, default = 209715166) or {+-}size{KMGTP}: +8G
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300):
Changed type of partition to 'Linux filesystem'

Command (? for help): n
Partition number (4-128, default 4): 4
First sector (34-209715166, default = 143656960) or {+-}size{KMGTP}:
Last sector (143656960-209715166, default = 209715166) or {+-}size{KMGTP}:
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300): L
Type search string, or  to show all codes: swap
8200 Linux swap                          a502 FreeBSD swap
a582 Midnight BSD swap                   a901 NetBSD swap
bf02 Solaris swap
Hex code or GUID (L to show codes, Enter = 8300): 8200
Changed type of partition to 'Linux swap'

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y

3. read partition table with

4. create filesystem for /home partition:

SRV01:~ # mkfs.xfs /dev/sda3
meta-data=/dev/sda3              isize=512    agcount=4, agsize=524288 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=0    bigtime=0 inobtcount=0
data     =                       bsize=4096   blocks=2097152, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
Discarding blocks...Done.

5. resize the / filesystem

SRV01:~ # btrfs filesystem resize max /
Resize device id 1 (/dev/sda2) from 40.00GiB to max

6. add new device UUIDs into fstab (device UUID for / partition stays the same, otherwise it would be needed to update it in /boot partition in the grub config as well) 7. mount filesystems with

-a

At this point everything works without any issue. But if I reboot the system the Bootloader opens up and then I get the message

: Problem with revocation key (-74)

How can this be resolved?

**the Question: where is this officially documented?** cannot find it in eg.: https://linux.die.net/man/1/df i have a suspicion that it is related to that the user doesn’t have UNIX level permission for those shares. user@sles:~> df -h|grep -i foobar user@sles:~> sudo df -h|grep -i foobar 1.2.3.4:/foobar 110G 40M 110G 1% /root/foobar 1.2.3.4:/foobar2 180G 106G 75G 59% /root/foobar2 user@sles:~> but this can confuse people that just want to list ALL the mounted shares without root permission.

I need to find out what repo 'git-core' comes from. $ zypper search git-core Refreshing service 'nu_novell_com'. Removing repository 'SLE11-WebYaST-SP1-Pool' [done] Removing repository 'SLE11-WebYaST-SP1-Updates' [done] Adding repository 'SLES11-SP2-Updates' [done] Adding repository 'SLE11-WebYaST-SP2-Pool' [done] Adding repository 'SLES11-SP2-Extension-Store' [done] Adding repository 'SLES11-SP2-Core' [done] Adding repository 'SLE11-WebYaST-SP2-Updates' [done] Adding repository 'SLE11-SP2-Debuginfo-Core' [done] Adding repository 'SLE11-SP2-Debuginfo-Updates' [done] Retrieving repository 'SLES11-SP2-Core' metadata [done] Building repository 'SLES11-SP2-Core' cache [done] Retrieving repository 'SLES11-SP2-Extension-Store' metadata [done] Building repository 'SLES11-SP2-Extension-Store' cache [done] Retrieving repository 'SLES11-SP2-Updates' metadata [done] Building repository 'SLES11-SP2-Updates' cache [done] Loading repository data... Reading installed packages... S | Name | Summary | Type --+----------+----------------+-------- i | git-core | Core git tools | package Searching the man pages for zypper, it seems like 'what-provides' would provide this information. It just says "System Packages". $zypper what-provides git-core Refreshing service 'nu_novell_com'. Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+----------+---------+----------------+--------+------------------------------------------------------------------ v | git-core | package | 2.0.0-201.1 | x86_64 | Software configuration management (SLE_11_SP2) v | git-core | package | 1.6.0.2-7.31.2 | x86_64 | SUSE-Linux-Enterprise-Software-Development-Kit-11-SP2 11.2.2-1.66 v | git-core | package | 2.0.0-201.1 | i586 | Software configuration management (SLE_11_SP2) i | git-core | package | 1.8.4-165.1 | x86_64 | (System Packages) These are the repos that exist. ls /etc/zypp/repos.d/ nu_novell_com:SLE11-SP2-Debuginfo-Core.repo nu_novell_com:SLES11-SP1-Pool.repo nu_novell_com:SLE11-SP2-Debuginfo-Updates.repo nu_novell_com:SLES11-SP1-Updates.repo nu_novell_com:SLE11-WebYaST-SP2-Pool.repo nu_novell_com:SLES11-SP2-Core.repo nu_novell_com:SLE11-SP1-Debuginfo-Pool.repo nu_novell_com:SLE11-WebYaST-SP2-Updates.repo nu_novell_com:SLES11-SP2-Extension-Store.repo nu_novell_com:SLE11-SP1-Debuginfo-Updates.repo nu_novell_com:SLES11-Extras.repo nu_novell_com:SLES11-SP2-Updates.repo On CentOS I would run a repoquery or yum info. How can I tell which repo git 1.8.4 comes from on sles? **Update** I fixed this by using a SLES 11 SP2 image instead of SLES 11 SP1. Leaving question open if someone can still answer the question.

> https://blog.koehntopp.info/2024/07/22/crowdstroke.html > > -> > > So, if you ask me what my takeaway from the Crowdstrike issue is, I’d > say: boot counting/boot assessment/automatic fallback should really be > a MUST for today’s systems. Before* you invoke your first kernel you > need have tracking of boot attempts and a logic for falling back to > older versions automatically. It’s a major shortcoming that this is > not default behaviour of today’s distros, in particular commercial > ones. > > Of course systemd has supported this for a long time: Automatic Boot > Assessment > > Windows does not do that, but Linux could. If commercial Linux distros > were to use this feature. > > -> > > https://systemd.io/AUTOMATIC_BOOT_ASSESSMENT/ -> **Question**: can anybody write a very short step-by-step howto, how to enable the feature on SLES and RHEL that if boot fails, it would automatically boot with an older kernel? This looks like a so rarely used feature of systemd that there aren't any good howtos in the internet for it to be more widespread.

After adding a new "interface" to the /etc/sysconfig/ifcfg-foobar: BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='1.2.3.4/24' MTU='9000' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' VLAN_ID='50' ETHERDEVICE='bond0' What is the proper method to bring this new interface up? /etc/init.d/networking restart just killed my SSH session and I had to reboot the server. Came in via another interface that was using bond0. Or was the problem that I wasn't running the /etc/init.d/networking restart command in a screen/tmux session on the server? Using SLES 11.4

Well, I thought it's just logical that the kernel changes /proc/sys/kernel/random/boot_id during boot, and then keeps that value while running. At least that would make sense to me if the intended use of boot_id is to find out *when* the machine rebooted. When monitoring the file using monit, I noticed that the file seems to change even if the machine did not reboot; that means the timestamp of the file changes, not the contents. So I wonder who changes the file's timestamps. For reference, here's my monit configuration being used: ~~~lang-monitrc check file bootid with path /proc/sys/kernel/random/boot_id #if changed timestamp then alert if content != "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}" then alert if changed checksum then alert group local ~~~ When checking the monitoring results I got: ~~~lang-text File 'bootid' status OK monitoring status Monitored monitoring mode active on reboot start permission 444 uid 0 gid 0 size 0 B access timestamp Tue, 07 May 2024 11:01:31 change timestamp Tue, 07 May 2024 11:01:31 modify timestamp Tue, 07 May 2024 11:01:31 content match no checksum d174a6b860689b62417af5eccd2b17ee (MD5) data collected Tue, 07 May 2024 11:46:11 ~~~ Cross-checking I got: ~~~lang-text # stat /proc/sys/kernel/random/boot_id File: '/proc/sys/kernel/random/boot_id' Size: 0 Blocks: 0 IO Block: 1024 regular empty file Device: 4h/4d Inode: 9770501 Links: 1 Access: (0444/-r--r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2024-05-07 11:01:31.721335498 +0200 Modify: 2024-05-07 11:01:31.721335498 +0200 Change: 2024-05-07 11:01:31.721335498 +0200 Birth: - # uptime 11:49am up 14 days 0:49, 4 users, load average: 0.00, 0.00, 0.00 ~~~ The system is running SLES12 SP5 on x86_64, and the only "suspects" are cron-jobs and "snapper": ~~~lang-journal May 07 11:00:01 v04 systemd: Started Session 7426 of user root. May 07 11:00:01 v04 systemd: Started Session 7428 of user root. May 07 11:00:01 v04 systemd: Started Session 7427 of user root. May 07 11:00:01 v04 CRON: (root) CMD ([ -x /usr/lib64/sa/sa1 ] && exe May 07 11:00:01 v04 run-crons: suse.de-snapper: OK ~~~

I'm trying to run an app which apparently uses some Qt6 capabilities on my SLES 15 SP5. When I do that, I get the following error message:

qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: wayland, offscreen, xcb, wayland-egl.

Application could not be initialized!
    This is likely due to missing Qt platform dependencies.
    For a list of dependencies, please refer to https://doc.qt.io/qt-6/linux-requirements.html 
    To view missing libraries, set QT_DEBUG_PLUGINS=1 and re-run the application.

Warning: OpenGL Version check failed. Falling back to Mesa software rendering.
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: wayland, offscreen, xcb, wayland-egl.

Earlier versions of this app used to work. Also, I don't see a distribution package mentioning something like "libxcb-cursor". I tried choosing other platform plugin settings; wayland and wayland-egl just failed, and offscreen succeeded, but showed nothing. What can I do to get this application to run: Notes: * The app is NVIDIA NSight Compute 2024.1, in case that matters. * Assume I can get root access (but let's not get too crazy)

I am asking to install a package B that is replacing (**and** conflicting with) another package A. In order to do it without user input, in yum I use --allowerasing. Is there an option like that for zypper? The user is getting this message from zypper:

Resolving package dependencies...

Problem: the to be installed B-some-version.x86_64 conflicts with 'A' provided by the installed A-some-other-version.x86_64
 Solution 1: deinstallation of A-some-other-version.x86_64
 Solution 2: do not install B-some-version.x86_64

Choose from above solutions by number or cancel [1/2/c/d/?] (c):

I tried with --force which made no difference and I want it to go with option 1.

Created thin provisioning VM (Suse Linux) with 100 GB hard disk. Now due to space requirements, I need to increase the size to 200GB. Can someone please tell me how to increase the space of the "/" directory?

Below is the output of the df -h command.

Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        4.0M     0  4.0M   0% /dev
tmpfs            12G  8.0K   12G   1% /dev/shm
tmpfs           4.7G   18M  4.7G   1% /run
tmpfs           4.0M     0  4.0M   0% /sys/fs/cgroup
/dev/sda3        92G   53G   40G  57% /
/dev/sda1       511M  4.9M  507M   1% /boot/efi
tmpfs           2.4G   56K  2.4G   1% /run/user/467
tmpfs           2.4G   40K  2.4G   1% /run/user/465
tmpfs           2.4G   44K  2.4G   1% /run/user/1000
tmpfs           2.4G   40K  2.4G   1% /run/user/0

Below is the output of the fdisk -l command.

GPT PMBR size mismatch (209715199 != 419430399) will be corrected by write.
Disk /dev/sda: 200 GiB, 214748364800 bytes, 419430400 sectors
Disk model: Virtual disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 055ED88C-4E22-4F03-9C7F-4E4CCADBF54C

Device         Start       End   Sectors  Size Type
/dev/sda1       2048   1050623   1048576  512M EFI System
/dev/sda2  193429504 209715166  16285663  7.8G Linux swap
/dev/sda3    1050624 193429503 192378880 91.7G Linux filesystem

Partition table entries are not in disk order.

I tried Fixing the partition and Correcting the GPT PMBR size mismatch using the below commands and rebooted. The system reboots fine.

Enter into the disk partition place: 
fdisk /dev/sda

Command (m for help):   m  
Command action
  ...
   l   list known partition types
   m   print this menu
   p   print the partition table
   q   quit without saving changes
   w   write table to disk and exit
   x   extra functionality (experts only)

Command (m for help):   x

Expert command (m for help):   m
Command action
...
   f   fix partition order
   m   print this menu
   p   print the partition table
   q   quit without saving changes
   r   return to main menu
   v   verify the partition table
   w   write table to disk and exit

Expert command (m for help):   f
Done.

Expert command (m for help):   w

The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.

I turn off SWAP and delete the SWAP partition. I then deleted the "/" partition and created it again with the intended size of 190G.

Commands used:

swapoff -a

fdisk  /dev/sda

As "/" is still showing the older size I run the command xfs_growfs -d /. The size of the partition increases as intended. Now the issue is my system does not boot in normal mode(Just stays on 4 dots and lizard sign) whereas I can boot into recovery mode. Am I missing something?

We have multiple RMT Servers for patching SLES servers in our environment, how can we check which rmt server is the client currently registered to. Currently we check the baseurl of repo file. Is there any command or alternative?