| how can I generate and change random large files to test snapshot performance? Posted: 24 Apr 2022 07:27 AM PDT I have an attach volume that gets a snapshot every hour. In order to test the snapshot performance, I need to run a process that will, between snapshot backups, generate a large amount of "churn" or file change. There are two questions related to this: - simply and obviously, how to generate large blocks of text EFFICIENTLY and write them to disc. With my limited knowledge about the only thing I can think of is a
for loop generating random characters, but that's probably extremely slow. Also, the new randomness if replacing a file has to be such that the snapshot essentially has no patterns to match. - what is the most effective way to store this? e.g. 1 Gigabyte in 1000 files, or 100 GB in 10 files
Since a picture is worth 1K words, I drew up this conceptually: 
Thanks in advance for insight on coupling tools-to-use with insight on the file system. |
| zypper hung while installing custom package Posted: 24 Apr 2022 06:34 AM PDT I need some help in debugging a package installation failure. Initially I thought it's scriptlet failure but the "rpm" child process of zypper seems to be exiting with 0 and staying as Not sure what's the culprit here. process list: root 3856 2618 0 10:06 ? 00:00:00 \_ sshd: cloud-user [priv] cloud-u+ 3878 3856 0 10:06 ? 00:00:00 | \_ sshd: cloud-user@pts/0 cloud-u+ 3879 3878 0 10:06 pts/0 00:00:00 | \_ -bash root 3921 3879 0 10:07 pts/0 00:00:00 | \_ sudo su root 3922 3921 0 10:07 pts/0 00:00:00 | \_ su root 3923 3922 0 10:07 pts/0 00:00:00 | \_ bash root 4484 3923 25 10:11 pts/0 00:02:49 | \_ strace -o zyppertrace -f -ff zypper --non-interactive --no-gpg-checks install ../mypackage root 4486 4484 3 10:11 pts/0 00:00:21 | \_ zypper --non-interactive --no-gpg-checks install ../mypackage.noarch root 4511 4486 0 10:11 pts/0 00:00:00 | \_ /usr/bin/systemd-inhibit --what=sleep:shutdown:idle --who=zypp --mode=block --why=Zypp commit running. /u root 4513 4511 0 10:11 pts/0 00:00:00 | | \_ /usr/bin/cat root 4512 4486 0 10:11 pts/0 00:00:00 | \_ /usr/bin/python3 /usr/lib/zypp/plugins/commit/snapper.py root 4516 4486 0 10:11 pts/0 00:00:00 | \_ /bin/bash /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.sh root 4639 4486 3 10:12 pts/0 00:00:18 | \_ [rpm] <defunct>
Could you please help me in debugging the failure. I have strace output of all the child processes. Below is the strace of zypper process (pid 4486) after the exit of rpm process: poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 1 ([{fd=22, revents=POLLIN}]) read(22, "+ exit 0\n", 4096) = 9 fcntl(22, F_GETFL) = 0x800 (flags O_RDONLY|O_NONBLOCK) fcntl(22, F_SETFL, O_RDONLY|O_NONBLOCK) = 0 fcntl(22, F_GETFL) = 0x800 (flags O_RDONLY|O_NONBLOCK) fcntl(22, F_SETFL, O_RDONLY|O_NONBLOCK) = 0 poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = ? ERESTART_RESTARTBLOCK (Interrupted by signal) --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=4639, si_uid=0, si_status=0, si_utime=1095, si_stime=723} --- restart_syscall(<... resuming interrupted poll ...>) = 0 poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 1 ([{fd=22, revents=POLLIN}]) read(22, "+ exit 0\n", 4096) = 9 fcntl(22, F_GETFL) = 0x800 (flags O_RDONLY|O_NONBLOCK) fcntl(22, F_SETFL, O_RDONLY|O_NONBLOCK) = 0 fcntl(22, F_GETFL) = 0x800 (flags O_RDONLY|O_NONBLOCK) fcntl(22, F_SETFL, O_RDONLY|O_NONBLOCK) = 0 poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = ? ERESTART_RESTARTBLOCK (Interrupted by signal) --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=4639, si_uid=0, si_status=0, si_utime=1095, si_stime=723} --- restart_syscall(<... resuming interrupted poll ...>) = 0 poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) poll([{fd=22, events=POLLIN|POLLERR|POLLHUP}], 1, 5000) = 0 (Timeout) 0 (Timeout)
Installation with rpm package manager is getting completed without any issues. When I left it without killing any processes, it took 1 hour to get cleared. As this is getting installed as part of cloud-init scripts, the image setup is getting stalled. OS: SUSE Linux Enterprise Server 15 SP1 |
| Hibernate on udev event while suspended/ACPI low battery wakeup Posted: 24 Apr 2022 07:36 AM PDT I want to hibernate on low battery: SUBSYSTEM=="power_supply", \ ATTR{status}=="Discharging", \ ATTR{capacity}=="[0-5]", \ RUN+="/usr/bin/systemctl hibernate", \
This works well if the system is awake. If suspended however, it doesn't hibernate until I wake it, then instead of allowing me to unlock it immediately hibernates. I have tried adding: ATTR{power/wakeup}="enabled"
without success. Indeed there is no wakeup currently in /sys/class/power_supply/*/power/. How can I make this event either work while suspended, or trigger a wakeup (and then hibernate) itself, without me opening the lid? NB: I am aware of hybrid-sleep, but that is not what I want, firstly since I would like to conserve some battery; but also so that I can use suspend-then-hibernate such that it hibernates on either low battery or time delay. |
| SCP not working with crontab Posted: 24 Apr 2022 05:55 AM PDT I tried SCP to copy files to another server. It's working for me when login in the server with ec2-user and sudo command. scp -i /usr/local/apache/htdocs/v9/id_rsa -P 20202 /usr/local/apache/htdocs/v9/test.csv sFTPUSER@sftp.domain.com:/inbound
Issue with crontab, I setup cron once in a day using custom file copyfile.sh and write below code in the file /usr/bin/scp -i /usr/local/apache/htdocs/v9/id_rsa -P 20202 /usr/local/apache/htdocs/v9/test.csv sFTPUSER@sftp.domain.com:/inbound rm /usr/local/apache/htdocs/v9/test.csv
from the above script only rm script working fine but scp not working... Is there anything I am missing here? |
| How to set an uninstalled package as installed in pacman? Posted: 24 Apr 2022 05:35 AM PDT I want to set two packages that I (stupidly) installed without using pacman as installed, so I don't have to bother uninstalling them and reinstalling through pacman. |
| apt-get error with fish shell: gpgv not installed Posted: 24 Apr 2022 05:22 AM PDT I've recently been trying out fish shell and tried to run sudo apt-get update and received the following error: Err:1 http://us.archive.ubuntu.com/ubuntu impish InRelease gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
gpgv is definitely installed and when I run the update in bash (and zsh) it works fine. I can't find anything in the fish docs or elsewhere about this. Any help much appreciated. |
| Fixed filesystem error Posted: 24 Apr 2022 07:49 AM PDT I was working on my VM when suddenly I realised all my files have been marked as read-only. I found it strange, so I rebooted, and then I was prompted into "BusyBox". For some unknown reason, an error has happened in the file system. I ran fcsk as shown in the picture below. Im theory, it fixed different errors. As I am not fully aware of what fcsk has done, and from my previous experience on Windows fixing its file system, I am now a bit sceptical on whether the file system is really "fixed" or there are corrupted files. - Can I trust the fixing process?
- Is there a way I can check that all the data is OK without having to open files one by one?
- When an error like the one shown in the picture below happens, what can it be the consequences for the actual data in the drive? Could I expect partial file corruption? full file corruption?
|
| How to replace, in an XML file, specific strings of characters in some specified tags with other strings of characters embedded in tags Posted: 24 Apr 2022 07:38 AM PDT I need to replace, in an XML file, specific strings of characters in some specified tags with other strings of characters embedded in tags. I saw this question: Find xml tag and replace the text inside the tag to a parameter value multiple occurrences So I will use it as a starting point, although my real example is about XML files containing an Asian language. What would be the match statement if one only needs to replace part of the text embedded in the tags, knowing that any group of characters could be used? <?xml version="1.0"?> <xml> <c><a>This is *an example*</a></c> <b> <a>I wish to replace *an example*</a> <a>*an example* should be replaced by some other text embedded in tags.</a> </b> </xml>
The resulting code should look like this: <?xml version="1.0"?> <xml> <c><a>This is <d>a test</d></a></c> <b> <a>I wish to replace <d>a test</d></a> <a><d>a test</d> should be replaced by some other text embedded in tags.</a> </b> </xml>
One of the solution proposed in the above mentioned question was to use an XSL file, and in that case I would need to modify the line match="a/text()[.='an example']" But maybe there are simpler ways to do that (xmlstarlet or other tools...) Thanks for your help |
| How to find the required dependency software on CentOS? Posted: 24 Apr 2022 04:50 AM PDT I am trying to install scientific computation software on CentOS. According to the manual, I need to install amdfftw-3.1 but when I try to search amdfftw with yum, it returns nothing: [beta@login03 0]$ yum search amdfftw Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * epel: mirror.lzu.edu.cn Warning: No matches found for: amdfftw No matches found
My question is:
On CentOS or Linux systems, how should I find the right software which I'm required to install? And I often see that when I'm required to install a package, for example, BLAS, it turns out I need to install a library, sudo yum install libblas-dev, how should I know whether I should install the software or the library? |
| Is this a issue? How do I resolve it? Posted: 24 Apr 2022 04:43 AM PDT This shows every time I run sudo apt update. Is it a issue? 
|
| Is it possible to have .iso with live distribution of linux but without an installer? Posted: 24 Apr 2022 04:19 AM PDT I thought iso file is a file that allows us to install some distribution and some part of it (not sure what is it) gives us possibility to run live version (without installing the OS). However our professor claimed there can be only live version on iso, without possibility of installing it. My questions are: - Is professor right?
- What allows us to run live version? Is it property of OS? Property of way iso file is created? Something else?
|
| Mounting NFSv4 NAS folders hangs Posted: 24 Apr 2022 06:07 AM PDT I have a QNAP NAS sharing folders using NFSv4. Until now I used to mount my folders as follows: $sudo mount -t nfs -o nfsvers=4 192.168.1.50:/Music ~/Music/
192.168.1.50 is the IP of my NAS and 192.168.1.2 is the IP for my PC.
Everything was working perfectly until I upgraded to Ubuntu 22.04 LTS and it stopped working (I have touched absolutely nothing on the NAS server!). If I run it with the -v parameter, the output is as follows: $sudo mount -t nfs -o nfsvers=4 192.168.1.50:/Music ~/Music/ mount.nfs: timeout set for Sun Apr 24 12:34:04 2022 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.50,clientaddr=192.168.1.2'.
And it hangs like this, even if I leave it waiting for 1 hour. Finally I have to cancel by pressing Control+C. I have tried disabling NFSv4 and using version 3, and in that case it does work (but I need to use version 4). Any idea? Thanks!
Here are attached some outputs of different commands, in case it is helpful: $sudo rpcinfo -p 192.168.1.50 program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100011 1 udp 30002 rquotad 100011 2 udp 30002 rquotad 100011 1 tcp 30002 rquotad 100011 2 tcp 30002 rquotad 100005 1 udp 30000 mountd 100005 1 tcp 30000 mountd 100005 2 udp 30000 mountd 100005 2 tcp 30000 mountd 100005 3 udp 30000 mountd 100005 3 tcp 30000 mountd 100003 4 tcp 2049 nfs 100024 1 udp 30001 status 100024 1 tcp 30001 status $sudo showmount --exports 192.168.1.50 Export list for 192.168.1.50: /Music 192.168.1.2
|
| Unable to shut down Posted: 24 Apr 2022 05:31 AM PDT My computer was stuck at some point when I shut it down. Ubuntu 20.04 LTS. It didn't move after I had waited for an hour. Then I pushed the power button to shut it down. Log: Apr 24 15:46:38 B365-M-AORUS-ELITE systemd[1]: Starting Message of the Day... Apr 24 15:46:38 B365-M-AORUS-ELITE systemd[1]: motd-news.service: Succeeded. Apr 24 15:46:38 B365-M-AORUS-ELITE systemd[1]: Finished Message of the Day. Apr 24 15:47:41 B365-M-AORUS-ELITE rtkit-daemon[831]: Supervising 3 threads of 2 processes of 1 users. Apr 24 15:47:41 B365-M-AORUS-ELITE rtkit-daemon[831]: Supervising 3 threads of 2 processes of 1 users. Apr 24 15:48:41 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating service name='org.gnome.Nautilus' requested by ':1.42' (uid=1000 pid=1497 comm="/usr/bin/gnome-shell " label="unconfined") Apr 24 15:48:41 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.gnome.Nautilus' Apr 24 15:48:41 B365-M-AORUS-ELITE dbus-daemon[595]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.254' (uid=1000 pid=9571 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 24 15:48:41 B365-M-AORUS-ELITE systemd[1]: Starting Hostname Service... Apr 24 15:48:41 B365-M-AORUS-ELITE dbus-daemon[595]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 24 15:48:41 B365-M-AORUS-ELITE systemd[1]: Started Hostname Service. Apr 24 15:48:41 B365-M-AORUS-ELITE nautilus[9571]: Called "net usershare info" but it failed: Failed to execute child process "net" (No such file or directory) Apr 24 15:49:11 B365-M-AORUS-ELITE systemd[1]: systemd-hostnamed.service: Succeeded. Apr 24 15:52:18 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating service name='org.gnome.gedit' requested by ':1.231' (uid=1000 pid=9571 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 24 15:52:18 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.gnome.gedit' Apr 24 15:53:13 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:53:13 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata database store and lookup manager... Apr 24 15:53:13 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata database store and lookup manager... Apr 24 15:53:13 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1' Apr 24 15:53:13 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata database store and lookup manager. Apr 24 15:53:13 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:53:13 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata extractor... Apr 24 15:53:13 B365-M-AORUS-ELITE tracker-extract[9647]: Set scheduler policy to SCHED_IDLE Apr 24 15:53:13 B365-M-AORUS-ELITE tracker-extract[9647]: Setting priority nice level to 19 Apr 24 15:53:13 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Apr 24 15:53:13 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata extractor. Apr 24 15:53:33 B365-M-AORUS-ELITE systemd[1284]: tracker-extract.service: Succeeded. Apr 24 15:53:51 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:53:51 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata extractor... Apr 24 15:53:51 B365-M-AORUS-ELITE tracker-extract[9680]: Set scheduler policy to SCHED_IDLE Apr 24 15:53:51 B365-M-AORUS-ELITE tracker-extract[9680]: Setting priority nice level to 19 Apr 24 15:53:51 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Apr 24 15:53:51 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata extractor. Apr 24 15:54:01 B365-M-AORUS-ELITE systemd[1284]: tracker-extract.service: Succeeded. Apr 24 15:54:02 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:54:02 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata extractor... Apr 24 15:54:02 B365-M-AORUS-ELITE tracker-extract[9705]: Set scheduler policy to SCHED_IDLE Apr 24 15:54:02 B365-M-AORUS-ELITE tracker-extract[9705]: Setting priority nice level to 19 Apr 24 15:54:02 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Apr 24 15:54:02 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata extractor. Apr 24 15:54:12 B365-M-AORUS-ELITE systemd[1284]: tracker-extract.service: Succeeded. Apr 24 15:54:32 B365-M-AORUS-ELITE tracker-store[9636]: OK Apr 24 15:54:32 B365-M-AORUS-ELITE systemd[1284]: tracker-store.service: Succeeded. Apr 24 15:54:33 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:54:33 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata database store and lookup manager... Apr 24 15:54:33 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1' Apr 24 15:54:33 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata database store and lookup manager. Apr 24 15:54:33 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:54:33 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata extractor... Apr 24 15:54:33 B365-M-AORUS-ELITE tracker-extract[9743]: Set scheduler policy to SCHED_IDLE Apr 24 15:54:33 B365-M-AORUS-ELITE tracker-extract[9743]: Setting priority nice level to 19 Apr 24 15:54:33 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Apr 24 15:54:33 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata extractor. Apr 24 15:54:43 B365-M-AORUS-ELITE systemd[1284]: tracker-extract.service: Succeeded. Apr 24 15:55:03 B365-M-AORUS-ELITE tracker-store[9734]: OK Apr 24 15:55:03 B365-M-AORUS-ELITE systemd[1284]: tracker-store.service: Succeeded. Apr 24 15:55:29 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:55:29 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata database store and lookup manager... Apr 24 15:55:29 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1' Apr 24 15:55:29 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata database store and lookup manager. Apr 24 15:55:30 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:55:30 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata extractor... Apr 24 15:55:30 B365-M-AORUS-ELITE tracker-extract[9781]: Set scheduler policy to SCHED_IDLE Apr 24 15:55:30 B365-M-AORUS-ELITE tracker-extract[9781]: Setting priority nice level to 19 Apr 24 15:55:30 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Apr 24 15:55:30 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata extractor. Apr 24 15:55:40 B365-M-AORUS-ELITE systemd[1284]: tracker-extract.service: Succeeded. Apr 24 15:56:00 B365-M-AORUS-ELITE tracker-store[9770]: OK Apr 24 15:56:00 B365-M-AORUS-ELITE systemd[1284]: tracker-store.service: Succeeded. Apr 24 15:58:03 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:58:03 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata database store and lookup manager... Apr 24 15:58:03 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1' Apr 24 15:58:03 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata database store and lookup manager. Apr 24 15:58:03 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=1294 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Apr 24 15:58:03 B365-M-AORUS-ELITE systemd[1284]: Starting Tracker metadata extractor... Apr 24 15:58:03 B365-M-AORUS-ELITE tracker-extract[9821]: Set scheduler policy to SCHED_IDLE Apr 24 15:58:03 B365-M-AORUS-ELITE tracker-extract[9821]: Setting priority nice level to 19 Apr 24 15:58:03 B365-M-AORUS-ELITE dbus-daemon[1295]: [session uid=1000 pid=1295] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Apr 24 15:58:03 B365-M-AORUS-ELITE systemd[1284]: Started Tracker metadata extractor. Apr 24 15:58:13 B365-M-AORUS-ELITE systemd[1284]: tracker-extract.service: Succeeded. Apr 24 15:58:33 B365-M-AORUS-ELITE tracker-store[9810]: OK Apr 24 15:58:33 B365-M-AORUS-ELITE systemd[1284]: tracker-store.service: Succeeded. Apr 24 16:00:12 B365-M-AORUS-ELITE gnome-shell[8724]: ###!!! [Parent][PImageBridgeParent] Error: RunMessage(msgname=PImageBridge::Msg_WillClose) Channel closing: too late to send/recv, messages will be lost Apr 24 16:00:12 B365-M-AORUS-ELITE systemd[1284]: gnome-launched-firefox.desktop-8724.scope: Succeeded. pr 24 16:00:18 B365-M-AORUS-ELITE dbus-daemon[595]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.78' (uid=1000 pid=1497 comm="/usr/bin/gnome-shell " label="unconfined") Apr 24 16:00:18 B365-M-AORUS-ELITE systemd[1]: Starting PackageKit Daemon... Apr 24 16:00:18 B365-M-AORUS-ELITE PackageKit: daemon start Apr 24 16:00:18 B365-M-AORUS-ELITE dbus-daemon[595]: [system] Successfully activated service 'org.freedesktop.PackageKit' Apr 24 16:00:18 B365-M-AORUS-ELITE systemd[1]: Started PackageKit Daemon. Apr 24 16:00:18 B365-M-AORUS-ELITE gnome-shell[1497]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2 Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Color management. Apr 24 16:00:20 B365-M-AORUS-ELITE pulseaudio[1290]: ICE default IO error handler doing an exit(), pid = 1290, errno = 32 Apr 24 16:00:20 B365-M-AORUS-ELITE kernel: [21079.436251] rfkill: input handler enabled Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-rfkill.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Date & Time handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Maintenance of expirable data. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME RFKill handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-datetime.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped GNOME Date & Time handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-a11y-settings.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped GNOME Accessibility settings. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-screensaver-proxy.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-sharing.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-smartcard.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped GNOME Smartcard handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-usb-protection.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped GNOME USB protection handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-wwan.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped GNOME WWan management. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: unattended-upgrades.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-housekeeping.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped GNOME Maintenance of expirable data. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-wacom.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: at-spi-dbus-bus.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-keyboard.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-media-keys.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-power.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-print-notifications.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Accessibility settings. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Keyboard handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Media keys handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Power management handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Printer notifications. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Freedesktop screensaver handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Sharing handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Smartcard handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Sound sample caching handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME USB protection handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Wacom handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME WWan management. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME XSettings. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: pulseaudio.service: Failed with result 'exit-code'. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-color.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped GNOME Color management. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-sound.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped GNOME Sound sample caching handling. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gsd-xsettings.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped GNOME XSettings. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping Session 2 of user ideal. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME X11 Session (session: ubuntu). Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Session. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME session X11 services. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME X11 Session. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Session (session: ubuntu). Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Session is initialized. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target GNOME Shell on X11. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopping GNOME Shell on X11... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped target Current graphical user session. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: unicast-local-avahi.path: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped Path trigger for Avahi .local domain notifications. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: update-notifier-crash.path: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped Path trigger for Apport crash notifications. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: update-notifier-release.path: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Removed slice system-getty.slice. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Removed slice system-modprobe.slice. Apr 24 16:00:20 B365-M-AORUS-ELITE gnome-shell[1497]: gnome-shell: Fatal IO error 0 (Success) on X server :0. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped target Graphical Interface. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped target Multi-User System. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped target Login Prompts. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped target Sound Card. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped target Timers. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: anacron.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Trigger anacron every hour. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: apt-daily-upgrade.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Daily apt upgrade and clean activities. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: apt-daily.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Daily apt download activities. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: e2scrub_all.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: fstrim.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Discard unused blocks once a week. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: fwupd-refresh.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Refresh fwupd metadata regularly. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: logrotate.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Daily rotation of log files. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: man-db.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Daily man-db regeneration. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: motd-news.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Message of the Day. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: systemd-tmpfiles-clean.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Daily Cleanup of Temporary Directories. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: ua-messaging.timer: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopped Ubuntu Advantage update messaging. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: systemd-rfkill.socket: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. Apr 24 16:00:20 B365-M-AORUS-ELITE ModemManager[738]: <info> Caught signal, shutting down... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping Modem Manager... Apr 24 16:00:20 B365-M-AORUS-ELITE NetworkManager[598]: <info> [1650787220.0884] modem-manager: ModemManager no longer available Apr 24 16:00:20 B365-M-AORUS-ELITE ModemManager[738]: <info> ModemManager is shut down Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping Accounts Service... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping ACPI event daemon... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped Path trigger for new release of Ubuntu notifications. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: gnome-session-monitor.service: Succeeded. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1284]: Stopped Monitor Session leader for GNOME Session. Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping Save/Restore Sound Card State... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping LSB: automatic crash report generation... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping Manage, Install and Generate Color Profiles... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping Regular background program processing daemon... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping Make remote CUPS printers available locally... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping GNOME Display Manager... Apr 24 16:00:20 B365-M-AORUS-ELITE systemd[1]: Stopping irqbalance daemon... Apr 24 16:00:20 B365-M-AORUS-ELITE evolution-alarm[1696]: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Apr 24 16:00:20 B365-M-AORUS-ELITE update-notifier[2779]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Apr 24 16:00:20 B365-M-AORUS-ELITE xdg-desktop-por[1893]: xdg-desktop-portal-gtk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Apr 24 16:00:20 B365-M-AORUS-ELITE seahorse[2270]: seahorse: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Apr 24 16:00:20 B365-M-AORUS-ELITE gnome-calendar[2269]: gnome-calendar: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Apr 24 16:00:20 B365-M-AORUS-ELITE nautilus[9571]: org.gnome.Nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (**) Option "fd" "26" Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (II) event2 - Power Button: device removed Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (**) Option "fd" "29" Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (II) event9 - Video Bus: device removed Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (**) Option "fd" "30" Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (II) event1 - Power Button: device removed Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (**) Option "fd" "31" Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (II) event0 - Sleep Button: device removed Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (**) Option "fd" "32" Apr 24 16:00:20 B365-M-AORUS-ELITE /usr/lib/gdm3/gdm-x-session[1380]: (II) event3 - USB Keyboard USB Keyboard: device removed
|
| Who loads bridge.ko modules when Linux system starts? Posted: 24 Apr 2022 03:47 AM PDT When my CentOS Linux system starts, bridge.ko and ebtable_broute are loaded, I'd like to know which module is loading these modules. [root]# lsmod | grep bridge bridge 266240 0 stp 16384 1 bridge llc 16384 2 bridge,stp [root]# lsmod | grep ebtable_brout ebtable_broute 16384 1 bridge 200704 1 ebtable_broute ebtables 36864 3 ebtable_nat,ebtable_filter,ebtable_broute
|
| Duplicity: Exclude files from verification Posted: 24 Apr 2022 03:52 AM PDT I use duplicity to backup a set of directories, using a daily cron job. I have another daily cron job to duplicity verify --compare-data the backup, as a sanity check, which runs shortly after the backup. I'd like to exclude some frequently changing files from the verification, so that I don't always get false positives in the resulting cron email. That is, I don't want to have those files reported in the number of differences found. I still want to backup those files (otherwise I'd simply exclude them from the backup in the first place). Unfortunately, when verifying, duplicity applies the --exclude/--include options only to the file system side, not to the backup side. That is, when I exclude more files in the verification than were excluded in the backup, duplicity reports those files as missing (present in the backup but missing in the file system). Hence the --exclude option can't be used to exclude files from being verified altogether. There's the --file-to-restore option, which also applies to verification (allows to verify a specific path), but it only accepts a single path, not a set of patterns and no exclusions like with --include/--exclude. Is there some other way to achieve what I want, that is, verify an existing backup against the file system, excluding certain files (preferably file patterns) from both sides of the verification? |
| Why oom_reaper when having vm.panic_on_oom = 1 Posted: 24 Apr 2022 05:22 AM PDT From what I understand from its author : The OOM killer currently allows to kill only a single task in a good hope that the task will terminate in a reasonable time and frees up its memory. (…) It has been shown (e.g. by Tetsuo Handa) that it is not that hard to construct workloads which break the core assumption mentioned above and the OOM victim might take unbounded amount of time to exit because it might be blocked in the uninterruptible state waiting for on an event (e.g. lock) which is blocked by another task looping in the page allocator. This patch reduces the probability of such a lockup by introducing a specialized kernel thread (oom_reaper) which tries to reclaim additional memory by preemptively reaping the anonymous or swapped out memory owned by the oom victim under an assumption that such a memory won't be needed when its owner is killed and kicked from the userspace anyway. In short, the oom_reaper kernel thread aims at lowering the probability of inappropriate decisions from the oom_killer. From what I understand from RHEL 8 documentation : The /proc/sys/vm/panic_on_oom file contains a value which is the switch that controls Out of Memory (OOM) behavior. When the file contains 1, the kernel panics on OOM and stops functioning as expected. The default value is 0, which instructs the kernel to call the oom_killer function when the system is in an OOM state. In short : having vm.panic_on_oom = 1 an OOM state won't trigger oom_killer launch. And therefore, logically, no need for its oom_reaper crutch. However, oom_reaper appears launched (under linux-5.4) at system init irrespective of vm.panic_on_oom value. Why ? Is there something I missed ? Something that makes the oom_reaper necessary even in case the killer won't ever be launched ? If not, how is it possible to prevent oom_reaper to be launched when vm.panic_on_oom = 1 ?
Note 1 : Of course I understand from the reading of the code that it won't be built if CONFIG_MMU is not set but this is obviously not an option on my system. |
| Fedora transaction test error on dnf update: file "conflicts" Posted: 24 Apr 2022 04:46 AM PDT I am trying to update Fedora using sudo dnf update. It lists the packages to be updated, downloads them, but then fails with this message: Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction test error: file /usr/bin/coredumpctl from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/system-generators/systemd-veritysetup-generator from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/system/systemd-binfmt.service from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/system/systemd-homed.service from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-binfmt from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-coredump from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-homed from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-portabled from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-sysctl from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-veritysetup from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/share/man/man5/org.freedesktop.portable1.5.gz from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/share/man/man8/systemd-coredump.8.gz from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/share/polkit-1/actions/org.freedesktop.home1.policy from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/share/polkit-1/actions/org.freedesktop.portable1.policy from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64
I tried googling but I am at a loss here (I am not an expert). I noticed no other issue or problem with the system so I don't know where this new problem comes from. Thanks a lot! EDIT: I tried to do sudo dnf clean all and then sudo dnf update, but this didn't help. I post the full output below. Then as suggested I tried sudo dnf upgrade --advisory=FEDORA-2022-1bf06aa328 and the output of that is: Last metadata expiration check: 0:10:03 ago on Sat 23 Apr 2022 03:59:43 PM CEST. No security updates needed, but 97 updates available Dependencies resolved. Nothing to do. Complete!
The output from sudo dnf update is below: Fedora 35 - x86_64 6.4 MB/s | 79 MB 00:12 Fedora 35 openh264 (From Cisco) - x86_64 4.1 kB/s | 2.5 kB 00:00 Fedora Modular 35 - x86_64 2.0 MB/s | 3.3 MB 00:01 Fedora 35 - x86_64 - Updates 3.3 MB/s | 29 MB 00:08 Fedora Modular 35 - x86_64 - Updates 1.7 MB/s | 2.9 MB 00:01 RPM Fusion for Fedora 35 - Free 2.0 MB/s | 934 kB 00:00 RPM Fusion for Fedora 35 - Free - Updates 1.2 MB/s | 401 kB 00:00 RPM Fusion for Fedora 35 - Nonfree 353 kB/s | 239 kB 00:00 RPM Fusion for Fedora 35 - Nonfree - Updates 345 kB/s | 100 kB 00:00 skype (stable) 26 kB/s | 5.2 kB 00:00 Last metadata expiration check: 0:00:01 ago on Sat 23 Apr 2022 03:59:43 PM CEST. Dependencies resolved. ================================================================================ Package Arch Version Repo Size ================================================================================ Installing: kernel x86_64 5.16.20-200.fc35 updates 86 k kernel-core x86_64 5.16.20-200.fc35 updates 46 M kernel-modules x86_64 5.16.20-200.fc35 updates 51 M kernel-modules-extra x86_64 5.16.20-200.fc35 updates 3.3 M Upgrading: at x86_64 3.2.5-3.fc35 updates 61 k cups x86_64 1:2.3.3op2-17.fc35 updates 1.3 M cups-client x86_64 1:2.3.3op2-17.fc35 updates 71 k cups-filesystem noarch 1:2.3.3op2-17.fc35 updates 14 k cups-filters x86_64 1.28.14-1.fc35 updates 770 k cups-filters-braille x86_64 1.28.14-1.fc35 updates 38 k cups-filters-libs x86_64 1.28.14-1.fc35 updates 136 k cups-ipptool x86_64 1:2.3.3op2-17.fc35 updates 3.9 M cups-libs x86_64 1:2.3.3op2-17.fc35 updates 265 k dhcp-client x86_64 12:4.4.3-2.fc35 updates 799 k dhcp-common noarch 12:4.4.3-2.fc35 updates 126 k distribution-gpg-keys noarch 1.68-1.fc35 updates 356 k ffmpeg-libs x86_64 4.4.2-1.fc35 rpmfusion-free-updates 8.4 M firefox x86_64 99.0.1-1.fc35 updates 104 M fwupd x86_64 1.7.7-1.fc35 updates 1.9 M fwupd-plugin-flashrom x86_64 1.7.7-1.fc35 updates 42 k fwupd-plugin-modem-manager x86_64 1.7.7-1.fc35 updates 71 k fwupd-plugin-uefi-capsule-data x86_64 1.7.7-1.fc35 updates 2.1 M gdisk x86_64 1.0.9-1.fc35 updates 244 k gegl04 x86_64 0.4.36-1.fc35 updates 3.0 M gzip x86_64 1.10-6.fc35 updates 149 k imath x86_64 3.1.5-1.fc35 updates 94 k iwl100-firmware noarch 39.31.5.1-131.fc35 updates 137 k iwl1000-firmware noarch 1:39.31.5.1-131.fc35 updates 247 k iwl105-firmware noarch 18.168.6.1-131.fc35 updates 216 k iwl135-firmware noarch 18.168.6.1-131.fc35 updates 224 k iwl2000-firmware noarch 18.168.6.1-131.fc35 updates 218 k iwl2030-firmware noarch 18.168.6.1-131.fc35 updates 226 k iwl3160-firmware noarch 1:25.30.13.0-131.fc35 updates 2.5 M iwl3945-firmware noarch 15.32.2.9-131.fc35 updates 77 k iwl4965-firmware noarch 228.61.2.24-131.fc35 updates 90 k iwl5000-firmware noarch 8.83.5.1_1-131.fc35 updates 361 k iwl5150-firmware noarch 8.24.2.2-131.fc35 updates 133 k iwl6000-firmware noarch 9.221.4.1-131.fc35 updates 152 k iwl6000g2a-firmware noarch 18.168.6.1-131.fc35 updates 333 k iwl6000g2b-firmware noarch 18.168.6.1-131.fc35 updates 339 k iwl6050-firmware noarch 41.28.5.1-131.fc35 updates 291 k iwl7260-firmware noarch 1:25.30.13.0-131.fc35 updates 15 M iwlax2xx-firmware noarch 20220411-131.fc35 updates 39 M libertas-usb8388-firmware noarch 2:20220411-131.fc35 updates 101 k libipa_hbac x86_64 2.7.0-1.fc35 updates 31 k libsolv x86_64 0.7.22-1.fc35 updates 403 k libsss_autofs x86_64 2.7.0-1.fc35 updates 32 k libsss_certmap x86_64 2.7.0-1.fc35 updates 74 k libsss_idmap x86_64 2.7.0-1.fc35 updates 36 k libsss_nss_idmap x86_64 2.7.0-1.fc35 updates 39 k libsss_sudo x86_64 2.7.0-1.fc35 updates 29 k linux-firmware noarch 20220411-131.fc35 updates 187 M linux-firmware-whence noarch 20220411-131.fc35 updates 48 k nspr x86_64 4.32.0-6.fc35 updates 137 k openexr-libs x86_64 3.1.5-1.fc35 updates 1.1 M ostree x86_64 2022.2-1.fc35 updates 229 k ostree-libs x86_64 2022.2-1.fc35 updates 424 k perl-HTML-Parser x86_64 3.78-1.fc35 updates 119 k perl-libwww-perl noarch 6.62-1.fc35 updates 202 k pipewire x86_64 0.3.50-1.fc35 updates 39 k pipewire-alsa x86_64 0.3.50-1.fc35 updates 62 k pipewire-gstreamer x86_64 0.3.50-1.fc35 updates 59 k pipewire-jack-audio-connection-kit x86_64 0.3.50-1.fc35 updates 135 k pipewire-libs x86_64 0.3.50-1.fc35 updates 1.5 M pipewire-pulseaudio x86_64 0.3.50-1.fc35 updates 27 k pipewire-utils x86_64 0.3.50-1.fc35 updates 325 k python3-beautifulsoup4 noarch 4.11.0-1.fc35 updates 134 k python3-regex x86_64 2022.3.15-1.fc35 updates 347 k rsync x86_64 3.2.3-9.fc35 updates 388 k smartmontools x86_64 1:7.3-2.fc35 updates 586 k squashfs-tools x86_64 4.5.1-1.fc35 updates 226 k sssd x86_64 2.7.0-1.fc35 updates 23 k sssd-ad x86_64 2.7.0-1.fc35 updates 205 k sssd-client x86_64 2.7.0-1.fc35 updates 143 k sssd-common x86_64 2.7.0-1.fc35 updates 1.5 M sssd-common-pac x86_64 2.7.0-1.fc35 updates 88 k sssd-ipa x86_64 2.7.0-1.fc35 updates 268 k sssd-kcm x86_64 2.7.0-1.fc35 updates 103 k sssd-krb5 x86_64 2.7.0-1.fc35 updates 68 k sssd-krb5-common x86_64 2.7.0-1.fc35 updates 83 k sssd-ldap x86_64 2.7.0-1.fc35 updates 152 k sssd-nfs-idmap x86_64 2.7.0-1.fc35 updates 34 k sssd-proxy x86_64 2.7.0-1.fc35 updates 65 k sstp-client x86_64 1.0.17-1.fc35 updates 67 k systemd-container x86_64 249.11-1.fc35 updates 523 k systemd-oomd-defaults noarch 249.11-1.fc35 updates 24 k systemd-rpm-macros noarch 249.11-1.fc35 updates 26 k replacing systemd-rpm-macros.noarch 249.9-1.fc35 systemd-udev x86_64 249.11-1.fc35 updates 1.8 M replacing systemd-udev.x86_64 249.9-1.fc35 tzdata noarch 2022a-2.fc35 updates 432 k tzdata-java noarch 2022a-2.fc35 updates 156 k wavpack x86_64 5.4.0-5.fc35 updates 212 k xen-libs x86_64 4.15.2-3.fc35 updates 637 k xen-licenses x86_64 4.15.2-3.fc35 updates 49 k xfce4-terminal x86_64 1.0.0-1.fc35 updates 692 k xorg-x11-xinit x86_64 1.4.0-14.fc35 updates 55 k xz x86_64 5.2.5-9.fc35 updates 214 k xz-libs x86_64 5.2.5-9.fc35 updates 92 k Installing dependencies: libjose x86_64 11-3.fc35 fedora 64 k sssd-idp x86_64 2.7.0-1.fc35 updates 34 k Removing: kernel x86_64 5.16.16-200.fc35 @updates 0 kernel-core x86_64 5.16.16-200.fc35 @updates 87 M kernel-modules x86_64 5.16.16-200.fc35 @updates 51 M kernel-modules-extra x86_64 5.16.16-200.fc35 @updates 3.1 M Transaction Summary ================================================================================ Install 6 Packages Upgrade 93 Packages Remove 4 Packages Total download size: 489 M Is this ok [y/N]: y Downloading Packages: Fedora 35 - x86_64 -209% [=========================================-] 49 kB/s |(1/99): libjose-11-3.fc35.x86_64.rpm 572 kB/s | 64 kB 00:00 (2/99): kernel-5.16.20-200.fc35.x86_64.rpm 396 kB/s | 86 kB 00:00 (3/99): openexr-libs-3.1.4-1.fc35_3.1.5-1.fc35. 508 kB/s | 118 kB 00:00 (4/99): kernel-modules-extra-5.16.20-200.fc35.x 177 kB/s | 3.3 MB 00:18 (5/99): sssd-idp-2.7.0-1.fc35.x86_64.rpm 36 kB/s | 34 kB 00:00 (6/99): at-3.2.5-3.fc35.x86_64.rpm 56 kB/s | 61 kB 00:01 (7/99): kernel-core-5.16.20-200.fc35.x86_64.rpm 1.9 MB/s | 46 MB 00:24 (8/99): cups-2.3.3op2-17.fc35.x86_64.rpm 391 kB/s | 1.3 MB 00:03 (9/99): cups-filesystem-2.3.3op2-17.fc35.noarch 16 kB/s | 14 kB 00:00 (10/99): cups-client-2.3.3op2-17.fc35.x86_64.rp 53 kB/s | 71 kB 00:01 (11/99): cups-filters-braille-1.28.14-1.fc35.x8 46 kB/s | 38 kB 00:00 (12/99): cups-filters-libs-1.28.14-1.fc35.x86_6 77 kB/s | 136 kB 00:01 (13/99): cups-filters-1.28.14-1.fc35.x86_64.rpm 139 kB/s | 770 kB 00:05 (14/99): cups-libs-2.3.3op2-17.fc35.x86_64.rpm 108 kB/s | 265 kB 00:02 (15/99): dhcp-client-4.4.3-2.fc35.x86_64.rpm 142 kB/s | 799 kB 00:05 (16/99): dhcp-common-4.4.3-2.fc35.noarch.rpm 85 kB/s | 126 kB 00:01 (17/99): distribution-gpg-keys-1.68-1.fc35.noar 121 kB/s | 356 kB 00:02 (18/99): kernel-modules-5.16.20-200.fc35.x86_64 1.0 MB/s | 51 MB 00:49 (19/99): cups-ipptool-2.3.3op2-17.fc35.x86_64.r 166 kB/s | 3.9 MB 00:23 (20/99): fwupd-plugin-flashrom-1.7.7-1.fc35.x86 44 kB/s | 42 kB 00:00 (21/99): fwupd-plugin-modem-manager-1.7.7-1.fc3 45 kB/s | 71 kB 00:01 (22/99): fwupd-1.7.7-1.fc35.x86_64.rpm 156 kB/s | 1.9 MB 00:12 (23/99): gdisk-1.0.9-1.fc35.x86_64.rpm 102 kB/s | 244 kB 00:02 (24/99): fwupd-plugin-uefi-capsule-data-1.7.7-1 151 kB/s | 2.1 MB 00:14 (25/99): gzip-1.10-6.fc35.x86_64.rpm 84 kB/s | 149 kB 00:01 (26/99): imath-3.1.5-1.fc35.x86_64.rpm 62 kB/s | 94 kB 00:01 (27/99): iwl100-firmware-39.31.5.1-131.fc35.noa 68 kB/s | 137 kB 00:02 (28/99): iwl1000-firmware-39.31.5.1-131.fc35.no 108 kB/s | 247 kB 00:02 (29/99): iwl105-firmware-18.168.6.1-131.fc35.no 99 kB/s | 216 kB 00:02 (30/99): iwl135-firmware-18.168.6.1-131.fc35.no 98 kB/s | 224 kB 00:02 (31/99): gegl04-0.4.36-1.fc35.x86_64.rpm 161 kB/s | 3.0 MB 00:18 (32/99): iwl2000-firmware-18.168.6.1-131.fc35.n 100 kB/s | 218 kB 00:02 (33/99): iwl2030-firmware-18.168.6.1-131.fc35.n 105 kB/s | 226 kB 00:02 (34/99): iwl3945-firmware-15.32.2.9-131.fc35.no 51 kB/s | 77 kB 00:01 (35/99): iwl4965-firmware-228.61.2.24-131.fc35. 56 kB/s | 90 kB 00:01 (36/99): iwl5000-firmware-8.83.5.1_1-131.fc35.n 115 kB/s | 361 kB 00:03 (37/99): iwl5150-firmware-8.24.2.2-131.fc35.noa 65 kB/s | 133 kB 00:02 ...OMISSIS... (99/99): ffmpeg-libs-4.4.2-1.fc35.x86_64.rpm 1.3 MB/s | 8.4 MB 00:06 [DRPM] openexr-libs-3.1.4-1.fc35_3.1.5-1.fc35.x86_64.drpm: done -------------------------------------------------------------------------------- Total 2.1 MB/s | 488 MB 03:56 Delta RPMs reduced 489.0 MB of updates to 488.1 MB (0.2% saved) Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction test error: file /usr/bin/coredumpctl from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/system-generators/systemd-veritysetup-generator from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/system/systemd-binfmt.service from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/system/systemd-homed.service from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-binfmt from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-coredump from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-homed from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-portabled from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-sysctl from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/lib/systemd/systemd-veritysetup from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/share/man/man5/org.freedesktop.portable1.5.gz from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/share/man/man8/systemd-coredump.8.gz from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/share/polkit-1/actions/org.freedesktop.home1.policy from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64 file /usr/share/polkit-1/actions/org.freedesktop.portable1.policy from install of systemd-udev-249.11-1.fc35.x86_64 conflicts with file from package systemd-249.7-2.fc35.x86_64
EDIT: The output of sudo dnf check is: cryptsetup-libs-2.4.2-1.fc35.x86_64 is a duplicate with cryptsetup-libs-2.4.3-1.fc35.x86_64 evolution-data-server-3.42.4-1.fc35.x86_64 is a duplicate with evolution-data-server-3.42.4-2.fc35.x86_64 evolution-data-server-langpacks-3.42.4-1.fc35.noarch is a duplicate with evolution-data-server-langpacks-3.42.4-2.fc35.noarch libreoffice-data-1:7.2.5.2-6.fc35.noarch is a duplicate with libreoffice-data-1:7.2.6.2-1.fc35.noarch pam-1.5.2-5.fc35.x86_64 is a duplicate with pam-1.5.2-7.fc35.x86_64 pcre2-10.37-4.fc35.x86_64 is a duplicate with pcre2-10.39-1.fc35.x86_64 pcre2-syntax-10.37-4.fc35.noarch is a duplicate with pcre2-syntax-10.39-1.fc35.noarch selinux-policy-35.15-1.fc35.noarch is a duplicate with selinux-policy-35.16-1.fc35.noarch selinux-policy-targeted-35.15-1.fc35.noarch is a duplicate with selinux-policy-targeted-35.16-1.fc35.noarch smartmontools-selinux-1:7.2-11.fc35.noarch is a duplicate with smartmontools-selinux-1:7.3-2.fc35.noarch systemd-249.7-2.fc35.x86_64 is a duplicate with systemd-249.11-1.fc35.x86_64 systemd-249.7-2.fc35.x86_64 is a duplicate with systemd-249.9-1.fc35.x86_64 systemd-libs-249.7-2.fc35.x86_64 is a duplicate with systemd-libs-249.11-1.fc35.x86_64 systemd-libs-249.7-2.fc35.x86_64 is a duplicate with systemd-libs-249.9-1.fc35.x86_64 systemd-networkd-249.7-2.fc35.x86_64 is a duplicate with systemd-networkd-249.11-1.fc35.x86_64 systemd-networkd-249.7-2.fc35.x86_64 is a duplicate with systemd-networkd-249.9-1.fc35.x86_64 systemd-pam-249.7-2.fc35.x86_64 is a duplicate with systemd-pam-249.11-1.fc35.x86_64 systemd-pam-249.7-2.fc35.x86_64 is a duplicate with systemd-pam-249.9-1.fc35.x86_64 systemd-resolved-249.7-2.fc35.x86_64 is a duplicate with systemd-resolved-249.11-1.fc35.x86_64 systemd-resolved-249.7-2.fc35.x86_64 is a duplicate with systemd-resolved-249.9-1.fc35.x86_64 systemd-rpm-macros-249.7-2.fc35.noarch is a duplicate with systemd-rpm-macros-249.9-1.fc35.noarch systemd-udev-249.7-2.fc35.x86_64 is a duplicate with systemd-udev-249.9-1.fc35.x86_64 vim-data-2:8.2.4621-1.fc35.noarch is a duplicate with vim-data-2:8.2.4701-1.fc35.noarch vim-filesystem-2:8.2.4621-1.fc35.noarch is a duplicate with vim-filesystem-2:8.2.4701-1.fc35.noarch Error: Check discovered 24 problem(s)
Running sudo dnf upgrade --allowerasing --best did not help (same error as with sudo dnf update). EDIT: output of dnf repoquery --duplicates Fedora 35 - x86_64 4.5 MB/s | 79 MB 00:17 Fedora 35 openh264 (From Cisco) - x86_64 2.2 kB/s | 2.5 kB 00:01 Fedora Modular 35 - x86_64 1.9 MB/s | 3.3 MB 00:01 Fedora 35 - x86_64 - Updates 4.5 MB/s | 29 MB 00:06 Fedora Modular 35 - x86_64 - Updates 1.7 MB/s | 2.9 MB 00:01 RPM Fusion for Fedora 35 - Free 1.2 MB/s | 934 kB 00:00 RPM Fusion for Fedora 35 - Free - Updates 1.1 MB/s | 401 kB 00:00 RPM Fusion for Fedora 35 - Nonfree 722 kB/s | 239 kB 00:00 RPM Fusion for Fedora 35 - Nonfree - Updates 322 kB/s | 100 kB 00:00 skype (stable) 20 kB/s | 5.2 kB 00:00 Last metadata expiration check: 0:00:01 ago on Sat 23 Apr 2022 06:18:21 PM CEST. cryptsetup-libs-0:2.4.2-1.fc35.x86_64 cryptsetup-libs-0:2.4.3-1.fc35.x86_64 evolution-data-server-0:3.42.4-1.fc35.x86_64 evolution-data-server-0:3.42.4-2.fc35.x86_64 evolution-data-server-langpacks-0:3.42.4-1.fc35.noarch evolution-data-server-langpacks-0:3.42.4-2.fc35.noarch libreoffice-data-1:7.2.5.2-6.fc35.noarch libreoffice-data-1:7.2.6.2-1.fc35.noarch pam-0:1.5.2-5.fc35.x86_64 pam-0:1.5.2-7.fc35.x86_64 pcre2-0:10.37-4.fc35.x86_64 pcre2-0:10.39-1.fc35.x86_64 pcre2-syntax-0:10.37-4.fc35.noarch pcre2-syntax-0:10.39-1.fc35.noarch selinux-policy-0:35.15-1.fc35.noarch selinux-policy-0:35.16-1.fc35.noarch selinux-policy-targeted-0:35.15-1.fc35.noarch selinux-policy-targeted-0:35.16-1.fc35.noarch smartmontools-selinux-1:7.2-11.fc35.noarch smartmontools-selinux-1:7.3-2.fc35.noarch systemd-0:249.11-1.fc35.x86_64 systemd-0:249.7-2.fc35.x86_64 systemd-0:249.9-1.fc35.x86_64 systemd-libs-0:249.11-1.fc35.x86_64 systemd-libs-0:249.7-2.fc35.x86_64 systemd-libs-0:249.9-1.fc35.x86_64 systemd-networkd-0:249.11-1.fc35.x86_64 systemd-networkd-0:249.7-2.fc35.x86_64 systemd-networkd-0:249.9-1.fc35.x86_64 systemd-pam-0:249.11-1.fc35.x86_64 systemd-pam-0:249.7-2.fc35.x86_64 systemd-pam-0:249.9-1.fc35.x86_64 systemd-resolved-0:249.11-1.fc35.x86_64 systemd-resolved-0:249.7-2.fc35.x86_64 systemd-resolved-0:249.9-1.fc35.x86_64 systemd-rpm-macros-0:249.7-2.fc35.noarch systemd-rpm-macros-0:249.9-1.fc35.noarch systemd-udev-0:249.7-2.fc35.x86_64 systemd-udev-0:249.9-1.fc35.x86_64 vim-data-2:8.2.4621-1.fc35.noarch vim-data-2:8.2.4701-1.fc35.noarch vim-filesystem-2:8.2.4621-1.fc35.noarch vim-filesystem-2:8.2.4701-1.fc35.noarch
EDIT: I did sudo package-cleanup --cleandupes but I am unsure how to deal with this: Last metadata expiration check: 0:03:48 ago on Sun 24 Apr 2022 01:39:51 PM CEST. Installed package systemd-249.11-1.fc35.x86_64 not available. Installed package systemd-udev-249.9-1.fc35.x86_64 not available. Installed package systemd-libs-249.11-1.fc35.x86_64 not available. Installed package systemd-rpm-macros-249.9-1.fc35.noarch not available. Installed package systemd-networkd-249.11-1.fc35.x86_64 not available. Installed package systemd-pam-249.11-1.fc35.x86_64 not available. Installed package systemd-resolved-249.11-1.fc35.x86_64 not available. Installed package vim-data-2:8.2.4701-1.fc35.noarch not available. Installed package vim-filesystem-2:8.2.4701-1.fc35.noarch not available. Error: Problem: The operation would result in removing the following protected packages: systemd, systemd-udev (try to add '--skip-broken' to skip uninstallable packages)
|
| zdump and date do not show the same daylight saving information Posted: 24 Apr 2022 07:26 AM PDT I am using my localtime set to be Israel. I updated the system clock and hardware clock, and using zdump I get: ~# zdump /usr/share/zoneinfo/Israel /usr/share/zoneinfo/Israel Wed Apr 20 16:11:36 2022 IDT
But, using date I get: ~ # date Wed Apr 20 15:11:41 IST 2022
The correct form is of zdump, so date doesn't comply, and I want to know why. I will also share /etc and /tmp content: ~ # ls -l /etc /tmp /etc: total 20631 -rw-r--r-- 1 1000 1000 30 Aug 11 2006 fs-version -rw-r--r-- 1 1000 1000 128 Dec 18 2018 fstab -rw-r--r-- 1 1000 1000 9 Apr 19 2006 group -rw-r--r-- 1 1000 1000 204 Dec 18 2018 hosts drwxr-xr-x 1 1000 1000 2048 Jan 10 2019 init.d -rwxr--r-- 1 1000 1000 3482 Sep 12 2019 inittab drwxr-xr-x 1 1000 1000 2048 Dec 18 2018 iproute2 drwxr-xr-x 1 1000 1000 2048 Feb 21 2019 libnl lrwxrwxrwx 1 1000 1000 14 Dec 18 2018 localtime -> /tmp/localtime -rw-r--r-- 1 1000 1000 101 Apr 19 2006 mtab -rw-r--r-- 1 1000 1000 2780 Dec 18 2018 ntp.conf -rw-r--r-- 1 1000 1000 25 Dec 18 2018 passwd -rw------- 1 1000 1000 25 Dec 18 2018 passwd- -rw-r--r-- 1 1000 1000 1882 Jan 1 1970 profile -rw-r--r-- 1 1000 1000 2478 Feb 20 2006 protocols lrwxrwxrwx 1 1000 1000 16 Dec 18 2018 resolv.conf -> /tmp/resolv.conf -rw-r--r-- 1 1000 1000 20 Sep 12 2019 rootfs.version -rw-r--r-- 1 1000 1000 15958 Feb 20 2006 services drwxr-xr-x 1 1000 1000 2048 Dec 18 2018 ssl -rw-r--r-- 1 root root 1736 Jan 13 1970 syslog.conf lrwxrwxrwx 1 1000 1000 13 Dec 18 2018 timezone -> /tmp/timezone drwxr-xr-x 1 1000 1000 2048 Dec 20 2018 udev /tmp: total 8 lrwxrwxrwx 1 root root 26 Apr 20 15:10 localtime -> /usr/share/zoneinfo/Israel -rw-r--r-- 1 root root 46 Apr 20 15:10 resolv.conf drwxr-xr-x 2 root root 80 Apr 20 15:10 run drwxr-x--- 6 root root 160 Apr 20 15:10 sx-web -rw-r--r-- 1 root root 7 Apr 20 15:10 timezone
Why is the difference in Daylight Saving and how can I correct it? |
| Diagnosing absurdly long boot time on Pop!_OS 21.10 Posted: 24 Apr 2022 05:30 AM PDT Recently switched my computer from Win10 to Pop OS. Noticed that it takes significantly longer to reach the login screen: before it felt pretty much instant and now it takes >1 minute. It's booting off a fast NVME M.2 and with a Ryzen 7-5800h, so I know it's not hardware limited. Did some digging in the terminal and this is what I found: jianzen@dragon-7:~$ systemd-analyze Startup finished in 5.520s (firmware) + 388ms (loader) + 4.798s (kernel) + 1min 37.591s (userspace) = 1min 48.299s graphical.target reached after 1min 37.544s in userspace jianzen@dragon-7:~$ systemd-analyze blame 6.388s NetworkManager-wait-online.service 5.102s plymouth-quit-wait.service 562ms docker.service 305ms accounts-daemon.service 274ms man-db.service ... jianzen@dragon-7:~$ systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 37.544s └─multi-user.target @1min 37.544s └─docker.service @1min 36.981s +562ms └─network-online.target @1min 36.950s └─NetworkManager-wait-online.service @1min 30.560s +6.388s └─NetworkManager.service @1min 30.483s +64ms └─dbus.service @1min 30.481s └─basic.target @1min 30.477s └─sockets.target @1min 30.477s └─cups.socket @1min 30.589s └─sysinit.target @1min 30.443s └─systemd-backlight@backlight:acpi_video0.service @1.820s +3ms └─system-systemd\x2dbacklight.slice @1.819s └─system.slice @130ms └─-.slice @130ms
Nothing in blame points towards a culprint, and in critical-chain it bottlenecks at sysinit.target, so I really don't know where to go next in working out what's causing such a slow boot. EDIT: Additional information to clarify filesystem. jianzen@dragon-7:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme1n1 259:0 0 931.5G 0 disk ├─nvme1n1p1 259:1 0 431.5G 0 part /mnt/SLibrary └─nvme1n1p2 259:2 0 500G 0 part /mnt/Drive 2 nvme0n1 259:3 0 476.9G 0 disk ├─nvme0n1p1 259:4 0 3G 0 part /boot/efi ├─nvme0n1p2 259:5 0 30G 0 part /home ├─nvme0n1p3 259:6 0 30G 0 part [SWAP] └─nvme0n1p4 259:7 0 413.9G 0 part / jianzen@dragon-7:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> PARTUUID=1e9f9308-e092-4249-b178-4c1e61d9bd37 /boot/efi vfat umask=0077 0 0 UUID=375f4eac-da6d-4d87-a17a-aed548fe7961 /home ext4 noatime,errors=remount-ro 0 0 /dev/mapper/cryptswap none swap defaults 0 0 UUID=7f37168f-738f-475e-b593-237ccf58d0a5 / ext4 noatime,errors=remount-ro 0 0 /dev/disk/by-uuid/FCC2A5FFC2A5BE70 /mnt/Drive\0402 auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=Drive%202 0 0 /dev/disk/by-uuid/6bee998f-b10b-4d1e-951a-a86b6d1b8b59 /mnt/SLibrary auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=SLibrary 0 0
EDIT Pt. 2 Running dmesg puts out the following errors (along with everything else): [ 0.240256] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210930/dswload2-162) [ 0.240269] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210930/psobject-220) [ 0.839449] integrity: Problem loading X.509 certificate -65 [ 4.826083] ================================================================================ [ 4.826138] UBSAN: invalid-load in /build/linux-RFp8Q8/linux-5.16.19/drivers/net/wireless/mediatek/mt76/dma.c:162:13 [ 4.826199] load of value 103 is not a valid value for type '_Bool' [ 98.377451] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership [ 114.634906] ================================================================================ [ 114.634914] UBSAN: invalid-load in /build/linux-RFp8Q8/linux-5.16.19/net/mac80211/status.c:1164:21 [ 114.634921] load of value 255 is not a valid value for type '_Bool' [ 120.040061] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership [ 355.714107] TCP: wlp4s0: Driver has suspect GRO implementation, TCP performance may be compromised.
|
| Install mailx on CentOS 9 Posted: 24 Apr 2022 07:03 AM PDT I can't install mailx on CentOS 9. yum install mailx -y Last metadata expiration check: 0:04:13 ago on Sat 09 Apr 2022 07:55:59 PM UTC. No match for argument: mailx Error: Unable to find a match: mailx
|
| Source a script in Linux for all users logging in that echo some things Posted: 24 Apr 2022 06:51 AM PDT We have CENTOS 7.x Linux with bash shell. I need a some environment variables to be set and some messages involving these env vars to be echoed (a banner kind of thing, but dynamic because it's got these env vars) for all users when they login or open an xterm/konsole. I've set this up in /etc/profile.d/somescript.sh I see that when I log in, the env vars are indeed set, but the echoing doesn't happen. Why is that? I see code in /etc/profile that reads like: for i in /etc/profile.d/*.sh /etc/profile.d/sh.local ; do if [ -r "$i" ]; then if [ "${-#*i}" != "$-" ]; then . "$i" else . "$i" >/dev/null fi fi done
Is it because of the output redirection above in the else branch? Or possibly some other script in the hierarchy of startup scripts that clear the screen? Or something else? How do I resolve this? |
| Shell script: Call variable with parameters/arg Posted: 24 Apr 2022 06:11 AM PDT I have the following function in a bash script: testcur.sh : #!/bin/bash function valcurl { if [[ $1 != "" ]] then tbl=$2 # can be multiple values data=/home/data btic=$data/$tbl"_btic" kline=$data/$tbl"_kline" if [[ "$1" == "btic" ]] then errbtic=$data/$tbl"_btic_err" elif [[ "$1" == "kline" ]] then errkline=$data/$tbl"_kline_err" fi # how do I replace the parameter $1 to call the variable? cat $1 | jq . 2> $"err"$1 if [[ -z $"err"$1 ]] then echo "correct" else echo "contain error" fi else echo "Not var found, only btic or kline" fi } valcurl $1 $2
Is this possible or is there another way? |
| Failing to change my keymap for X11 on void linux Posted: 24 Apr 2022 06:04 AM PDT I have installed a recent version of void linux on a Fujitsu Lifebook E751. - uname -a results in 4.12.11_1 #1 SMP PREEMPT Fri Sep 8 20:17:18 UTC 2017 x86_64 GNU/Linux.
- Xorg version is 1.19.3, Protocol Ver. 11
After installations I had a us keyboard mapping. This is driving me nuts, hence I tried to change it by writing several variants of a /etc/X11/xorg.conf. None worked. After consulting google several times I followed the official Xorg guide. I concocted this configuration: Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "neo" Option "XkbModel" "pc105" EndSection
But despite all efforts, the problem stays the same. I get (EE) Error loading keymap /var/lib/xkb/server-0.xkm (EE) XKB: Failed to load keymap. Loading default keymap instead.
In the end the US-keyboard is loaded. This is driving me totally nuts! |
| shell: keep trailing newlines ('\n') in command substitution Posted: 24 Apr 2022 07:18 AM PDT I want to be able to capture the exact output of a command substitution, including the trailing new line characters. I realise that they are stripped by default, so some manipulation may be required to keep them, and I want to keep the original exit code. For example, given a command with a variable number of trailing newlines and exit code: f(){ for i in $(seq "$((RANDOM % 3))"); do echo; done; return $((RANDOM % 256));} export -f f
I want to run something like: exact_output f
And have the output be: Output: $'\n\n' Exit: 5
I'm interested in both bash and POSIX sh. |
| Rsyslog regular expression Posted: 24 Apr 2022 04:06 AM PDT I have a lot of incoming syslog messages on my rsyslog server. It's a stormshield that sends different categories of messages (connection, web, alarm, ...) I can't configure a different facility for each category so I need to use regular expression to split incoming messages in differents files. All messages are different and have more or less fields in the message, but there is one field logtype to identify the category : Syslog message Msg = bullshitcontentbullshitcontent logtype:"connection" bullshitcontentbullshitcontent
So the question is : How can I collect the string of the logtype field with a POSIX regular expression that is understandable by rsyslog and - if you know how - split in different files depending of the value of the logtype? |
| Execute script in new gnome-terminal loading bashrc Posted: 24 Apr 2022 05:04 AM PDT I have a script in a gnome-terminal shell and I would like to open a new terminal, load the bashrc configuration, execute a new script and avoid the closure of the new terminal window. I have tried to execute this commands: gnome-terminal -x bash
the script above open a new shell and loads bashrc, but I don't know how to execute a script automatically. gnome-terminal -x ./new_script.sh
the script above open a new shell and execute the script but doesn't load bashrc and close the window.
The result that I would like to obtain is to feel like opening a new terminal as clicking the term icon but execute a script after the bashrc setup. |
| Bash: Assign output of pipe to a variable Posted: 24 Apr 2022 07:06 AM PDT I am trying to get the output of a pipe into a variable. I tried the following things: echo foo | myvar=$(</dev/stdin) echo foo | myvar=$(cat) echo foo | myvar=$(tee)
But $myvar is empty. I don't want to do: myvar=$(echo foo)
Because I don't want to spawn a subshell. Any ideas? Edit: I don't want to spawn a subshell because the command before the pipe needs to edit global variables, which it can't do in a subshell. Can it? The echo thing is just for simplification. It's more like: complex_function | myvar=$(</dev/stdin)
And I don't get, why that doesn't work. This works for example: complex_function | echo $(</dev/stdin)
|
| Installing Qubes OS and handling the Installation Destination Page Posted: 24 Apr 2022 03:24 AM PDT I'm trying to install Qubes OS on my computer. I have just deleted the Ubuntu Partition in order to install it, but there's a problem with the storage configuration, and I need to find a suitable stage1 device. There's nothing I can do... What should I be doing in such a case? |
| Determine which graphics driver Xorg uses Posted: 24 Apr 2022 07:35 AM PDT On a fresh Arch Linux installation, I had difficulties with the graphics drivers. In the process, I have installed a lot of different drivers to somehow get the display working. Now I need to determine which driver X is using. How to do that? The installed packages include xf86-video-intel, xf86-video-nouveau, nvidia, xorg-drivers. To solve a strange issue to launch any graphical desktop manager i had to replace nividia-libgl with mesa-libgl. Graphics: Intel HD Graphics 4000 / Nvidia GT 750M The content of Xorg.0.log is: http://pastebin.com/YwiMZmG6 |
| Networking and Samba from a quest OS running on qemu Posted: 24 Apr 2022 07:07 AM PDT I'm trying to test some software on a big endian system to ensure compatibility. My plan is to use qemu on Ubuntu 12.04 to emulate a MIPS system. So far I've been able to create the quest system successfully, but I haven't been able to network it with the host system. I can access the outside world from the guest system (e.g. wget or apt-get), but my attempts at setting up samba have failed. According to this, in QEmu 1.1 and newer the network bridge helper can set tun/tap up for you without the need for additional scripting. I'm trying to use that since I've seen different versions of the scripts. Right now qemu-system-mips -version reports the following: QEMU emulator version 1.0.50 (Debian 1.0.50-2012.03-0ubuntu2.1), Copyright (c) 2003-2008 Fabrice Bellard
I've compiled from the 1.4.1 source and used the version from apt-get. Both report the same thing. I'm working under the assumption that I have version 1.1 or later despite what -version is telling me. Anyway, the next instruction was to turn on the setuid attribute for the default network helper: sudo chmod u+s /usr/local/libexec/qemu-bridge-helper
Next I created a bridge.conf file in /etc/qemu/ and /usr/local/etc/qemu with -rw-r--r-- for permissions. The contents of the file are: allow br0
If I start QEmu with the following command: qemu-system-mips -M malta -kernel vmlinux-2.6.32-5-4kc-malta -hda disk.img -append "root=/dev/sda1 console=ttyS0" -nographic -net nic -net bridge,br=br0 -smb /home/uli/samba
or with qemu-system-mips -M malta -kernel vmlinux-2.6.32-5-4kc-malta -hda disk.img -append "root=/dev/sda1 console=ttyS0" -nographic -netdev bridge,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1
or with qemu-system-mips -M malta -kernel vmlinux-2.6.32-5-4kc-malta -hda disk.img -append "root=/dev/sda1 console=ttyS0" -nographic -netdev tap,helper=/usr/local/libexec/qemu-bridge-helper,id=hn0 -device virtio-net-pci,netdev=hn0,id=nic1
I get the following error: failed to get mtu of bridge `br0': No such device failed to launch bridge helper qemu-system-mips: -net bridge,br=br0: Device 'bridge' could not be initialized
Fair enough, I didn't create the br0 bridge. I've tried creating one with a script I don't understand, but then my quest MIPS QEmu system no longer connects to anything. It sees br0, but it doesn't get an IP address. Clearly I'm doing something wrong here: ifconfig br0 down brctl delbr br0 ifconfig eth2 0.0.0.0 promisc up brctl addbr br0 brctl setfd br0 0 brctl addif br0 eth2 echo 1 > /proc/sys/net/ipv4/conf/br0/proxy_arp echo 1 > /proc/sys/net/ipv4/conf/eth2/proxy_arp echo 1 > /proc/sys/net/ipv4/ip_forward dhclient br0 ifconfig br0 up
Is there an easier way to do this? Personally, I would be fine just using the SMB server on \10.0.2.4\qemu that's described here, but that hasn't worked for me either (115 errors when I try to mount the share, presumably because of networking trouble). Update Once I create the bridge, I see the following output from ifconfig on the host machine: br0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:10.2.32.101 Bcast:10.2.32.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:85 errors:0 dropped:0 overruns:0 frame:0 TX packets:51 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8235 (8.2 KB) TX bytes:9227 (9.2 KB) eth2 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:196581 errors:0 dropped:0 overruns:0 frame:0 TX packets:44205 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:139517339 (139.5 MB) TX bytes:3365206 (3.3 MB)
Checking the brctl show output, I see the following: bridge name bridge id STP enabled interfaces br0 8000.XXXXXXXXXXXX no eth2
Now I start the quest system in QEmu. If I run ifconfig, I see the following: eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:536 errors:1 dropped:51 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:55083 (53.7 KiB) TX bytes:2862 (2.7 KiB) Interrupt:10 Base address:0x1020
And the bridge looks like this: bridge name bridge id STP enabled interfaces br0 8000.XXXXXXXXXXXX no eth2 tap0
Unfortunately with this setup, the quest system has lost the limited "user mode" networking it once had (i.e. wget and apt-get no longer work). The only IP address I see is for the bridge, so I'm not sure how the quest will appear on the network. The host still appears, at the same IP address as br0. Update Here is the output from iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination
|
No comments:
Post a Comment