I started a zypper dup process to upgrade from leap 15.5 to 15.6. I broke the process down into steps with logs at each step. The preparation and setup steps worked fine as far as I can see.
Text of the process steps
https://susepaste.org/5fcc9614fa48
My hardware configuration
https://susepaste.org/346fd55b1a56
Repos Before
https://susepaste.org/ce74eac69cb3
Repos Cleaned
https://susepaste.org/37784cf99231
Packman disabled via yast
Zypper DUP Dry-run Download-only was run but produced no listing to my log
https://susepaste.org/4e5ec8a5d876
Actual Zypper DUP was run but hung almost at the end
https://susepaste.org/d50f44903151
Please use paste.opensuse.org:
Click on one of your links and read:
This service is now obsolete. New service has been setup and is available at https://paste.opensuse.org.
Paste fixes in order (susepaste needs to be fixed)
openSUSE Paste Text Steps
openSUSE Paste Hardware
openSUSE Paste Repos Before
openSUSE Paste Clean
openSUSE Paste DUP Setup
openSUSE Paste DUP Run
For years now…
I made a Request.
Sorry. Found out after I posted. Fixed links in Post 3
Hardware lists are short enough to copy and paste here directly.
Please describe here what you last saw before the “hang”. What to you does “hang” mean, and its consequences for purposes of this thread?
The DUP was running in a ROOT terminal (ctrl+alt+F1) as displayed in the log 04-zypper-dup-run.txt. It had nearly reached the end of the process -
(2250/2273) Removing: python3-qt3d-qt5-devel-5.15.6-bp155.1.8.x86_64 […done]
(2251/2273) Installing: yast2-samba-client-4.6.1-150600.1.2.noarch […done]
(2252/2273) Installing: yast2-ntp-client-4.6.0-150600.1.3.noarch […
The hangup was during line 2252 trying to install yast2-ntp-client. Processing just stopped. I waited for quite some time and pressed ctrl+C to cancel the process. This resulted in zypper saying it was trying to gracefully terminate and another long wait. I pressed ctrl+C again which resulted in another “cleaning up” message. There was some sort of processing going on as the disk activity light would occasionally flash so I left running it overnight.
This morning I tried ctrl+alt+F7 and the system returned to KDE where I found thing pretty much accessible except for no access to the internet. I have not attempted a reboot.
What error(s) result when you attempt internet access, such as zypper ref or pinging your ISP? Does /etc/resolv.conf exist and point to a sensible location? What does ip a report?
Results for queries -`
freda@localhost.heavy1] ~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 44:8a:5b:5a:e2:2e brd ff:ff:ff:ff:ff:ff
altname enp1s0
inet 192.168.0.2/24 brd 192.168.0.255 scope global dynamic noprefixroute eth0
valid_lft 76952sec preferred_lft 76952sec
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ pingtest www.aspect1.net
pingtest: Begins at Tue 14 Jan 12:25:19 MST 2025
pingtest: An address was specified - www.aspect1.net
pingtest: Pinging www.aspect1.net
ping: www.aspect1.net: Name or service not known
pingtest: Ends at Tue 14 Jan 12:25:19 MST 2025
pingtest: Elapsed Time 0 Days, 0 Hours, 0 Mins, 0 Secs
freda@localhost.heavy1] ~ $ pingtest 8.8.8.8
pingtest: Begins at Tue 14 Jan 12:27:35 MST 2025
pingtest: An address was specified - 8.8.8.8
pingtest: Pinging 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
— 8.8.8.8 ping statistics —
5 packets transmitted, 0 received, 100% packet loss, time 4082ms
pingtest: Ends at Tue 14 Jan 12:27:49 MST 2025
pingtest: Elapsed Time 0 Days, 0 Hours, 0 Mins, 14 Secs
freda@localhost.heavy1] ~ $
`
Zypper fails due to no net access.
Please always provide error messages, along with whatever command created them, not summaries of what you saw.
You apparently have an IP assigned, but didn’t report on /etc/resolv.conf. If it’s OK, it may be a that your firewall is running but not configured to allow anything through it. Try turning it off until you know zypper has finished its job.
The firewall was apparently the issue. I am now able to access the internet, ping various sites, run zypper refresh and run my browser (firefox).
Should I attempt a restart of the DUP process using the same command line?
echo 'zypper -v --releasever 15.6 dist-upgrade --allow-vendor-change --allow-downgrade' >04-zypper-dup-run.txt
date | tee --append 04-zypper-dup-run.txt
echo "==============================================================" | tee --append 04-zypper-dup-run.txt
zypper -v --releasever 15.6 dist-upgrade --allow-vendor-change --allow-downgrade | tee --append 04-zypper-dup-run.txt
The firewall commands I issued -
freda@localhost.heavy1] ~ $ sudo firewall-cmd --state
not running
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ sudo firewall-cmd --list-all
public (default, active)
target: default
ingress-priority: 0
egress-priority: 0
icmp-block-inversion: no
interfaces: eth0
sources:
services: dhcpv6-client kdeconnect kdeconnect-kde
ports: 1714-1764/tcp 1714-1764/udp
protocols:
forward: no
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ sudo systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; preset: disabled)
Active: active (running) since Sun 2025-01-05 15:27:13 MST; 1 week 2 days ago
Docs: man:firewalld(1)
Main PID: 1351 (firewalld)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/firewalld.service
└─1351 /usr/bin/python3 /usr/sbin/firewalld --nofork --nopid
Jan 05 15:27:13 localhost systemd[1]: Started firewalld - dynamic firewall daemon.
Jan 12 15:52:23 localhost.heavy1 firewalld[1351]: Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/firew>
return func(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/firew>
self.fw.reload()
File "/usr/lib/python3.6/site-packages/firew>
for interface in nm_get_interfaces_in_zone>
File "/usr/lib/python3.6/site-packages/firew>
for interface in nm_get_interfaces():
File "/usr/lib/python3.6/site-packages/firew>
for active_con in nm_get_client().get_acti>
File "/usr/lib/python3.6/site-packages/firew>
_nm_client = NM.Client.new(None)
gi.repository.GLib.GError: g-invoke-error-quar>
Jan 12 15:59:52 localhost.heavy1 firewalld[1351]: WARNING: Service 'kdeconnect' already set, ign>
Jan 12 15:59:52 localhost.heavy1 firewalld[1351]: WARNING: Service 'kdeconnect' already set, ign>
Jan 12 15:59:52 localhost.heavy1 firewalld[1351]: WARNING: Service 'kdeconnect' already set, ign>
Jan 12 15:59:52 localhost.heavy1 firewalld[1351]: WARNING: Service 'kdeconnect' already set, ign>
Jan 12 15:59:52 localhost.heavy1 firewalld[1351]: WARNING: Service 'kdeconnect' already set, ign>
Jan 12 16:03:23 localhost.heavy1 firewalld[1351]: ERROR: Invalid option: 'CleanupModulesOnExit=n>
Jan 12 16:03:23 localhost.heavy1 firewalld[1351]: ERROR: Invalid option: 'NftablesFlowtable=off'
Jan 12 16:03:23 localhost.heavy1 firewalld[1351]: ERROR: Invalid option: 'NftablesCounters=no'
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ sudo systemctl stop firewalld
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ sudo systemctl status firewalld
○ firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; preset: disabled)
Active: inactive (dead) since Tue 2025-01-14 20:28:47 MST; 1min 2s ago
Duration: 1w 2d 5h 1min 31.112s
Docs: man:firewalld(1)
Process: 1351 ExecStart=/usr/sbin/firewalld --nofork --nopid $FIREWALLD_ARGS (code=exited, s>
Main PID: 1351 (code=exited, status=0/SUCCESS)
Jan 12 15:59:52 localhost.heavy1 firewalld[1351]: WARNING: Service 'kdeconnect' already set, ign>
Jan 12 15:59:52 localhost.heavy1 firewalld[1351]: WARNING: Service 'kdeconnect' already set, ign>
Jan 12 15:59:52 localhost.heavy1 firewalld[1351]: WARNING: Service 'kdeconnect' already set, ign>
Jan 12 15:59:52 localhost.heavy1 firewalld[1351]: WARNING: Service 'kdeconnect' already set, ign>
Jan 12 16:03:23 localhost.heavy1 firewalld[1351]: ERROR: Invalid option: 'CleanupModulesOnExit=n>
Jan 12 16:03:23 localhost.heavy1 firewalld[1351]: ERROR: Invalid option: 'NftablesFlowtable=off'
Jan 12 16:03:23 localhost.heavy1 firewalld[1351]: ERROR: Invalid option: 'NftablesCounters=no'
Jan 14 20:28:44 localhost.heavy1 systemd[1]: Stopping firewalld - dynamic firewall daemon...
Jan 14 20:28:47 localhost.heavy1 systemd[1]: firewalld.service: Deactivated successfully.
Jan 14 20:28:47 localhost.heavy1 systemd[1]: Stopped firewalld - dynamic firewall daemon.
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ ping -c1 google.com
PING google.com (192.178.49.174) 56(84) bytes of data.
64 bytes from phx19s05-in-f14.1e100.net (192.178.49.174): icmp_seq=1 ttl=117 time=10.3 ms
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 10.342/10.342/10.342/0.000 ms
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ ping -c1 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=9.25 ms
--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 9.252/9.252/9.252/0.000 ms
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ ping -c1 www.aspect1.net
PING www.aspect1.net (172.67.130.48) 56(84) bytes of data.
64 bytes from 172.67.130.48 (172.67.130.48): icmp_seq=1 ttl=55 time=17.5 ms
--- www.aspect1.net ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 17.470/17.470/17.470/0.000 ms
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ ping -c1 paste.opensuse.org
PING proxy-prg2.opensuse.org (195.135.223.50) 56(84) bytes of data.
64 bytes from legacy-ip.atlas.opensuse.org (195.135.223.50): icmp_seq=1 ttl=49 time=169 ms
--- proxy-prg2.opensuse.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 169.399/169.399/169.399/0.000 ms
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ sudo ufw status
sudo: ufw: command not found
freda@localhost.heavy1] ~ $
freda@localhost.heavy1] ~ $ sudo iptables -L -v
Chain INPUT (policy ACCEPT 68 packets, 9033 bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 168 packets, 13356 bytes)
pkts bytes target prot opt in out source destination
freda@localhost.heavy1] ~ $
After restarting the zypper DUP process I am now on 15.6.
This problem is now solved.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.