Recently I upgraded the Ubuntu to latest version here is the detail:
But after upgrading to this version, Chrome and some other apps are behaving strangely. for instance look at the various screenshots of chrome where CSS colours are "spilled":
here is another one
this is how github looks:
also Rider (C# IDE) and Intellij Idea Icons appear are white squares.
Anyone facing the same issues? what is the solution in this case or any workaround? Firefox is unaffected and so is VSCode.
Recently I encountered a problem on one of the nodes of kubernetes where system was running at a crawling speed. after investigating I found that several instances of systemd-udevd were running.
systemctl status systemd-udevd
● systemd-udevd.service - udev Kernel Device Manager
Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor preset: enabled)
Active: active (running) since Sun 2022-03-13 08:32:29 EET; 31s ago
TriggeredBy: ● systemd-udevd-control.socket
● systemd-udevd-kernel.socket
Docs: man:systemd-udevd.service(8)
man:udev(7)
Main PID: 541638 (systemd-udevd)
Status: "Processing with 18 children at max"
Tasks: 19
Memory: 18.0M
CGroup: /system.slice/systemd-udevd.service
├─541638 /lib/systemd/systemd-udevd
├─541857 /lib/systemd/systemd-udevd
├─541858 /lib/systemd/systemd-udevd
├─541859 /lib/systemd/systemd-udevd
├─541860 /lib/systemd/systemd-udevd
├─541862 /lib/systemd/systemd-udevd
├─541863 /lib/systemd/systemd-udevd
├─541864 /lib/systemd/systemd-udevd
├─541865 /lib/systemd/systemd-udevd
├─541866 /lib/systemd/systemd-udevd
├─541867 /lib/systemd/systemd-udevd
├─541868 /lib/systemd/systemd-udevd
├─541869 /lib/systemd/systemd-udevd
├─541870 /lib/systemd/systemd-udevd
├─541871 /lib/systemd/systemd-udevd
├─541872 /lib/systemd/systemd-udevd
├─541873 /lib/systemd/systemd-udevd
├─541874 /lib/systemd/systemd-udevd
└─541875 /lib/systemd/systemd-udevd
Mar 13 08:32:29 xxxx.cloud systemd[1]: Starting udev Kernel Device Manager...
Mar 13 08:32:29 xxxx.cloud systemd[1]: Started udev Kernel Device Manager.
I tried stopping the service, terminated processes and even disable it but to no avail. it keeps getting spawned and hogs the system completely. I also stopped docker and k3s-agent but the systemd-udevd service just keeps appearing. This is what the journal entries look like:
- Logs begin at Sun 2022-03-13 04:44:26 EET, end at Sun 2022-03-13 08:39:17 EET. --
Mar 13 07:56:39 xxxx.cloud systemd[1]: Stopping udev Kernel Device Manager...
Mar 13 07:56:40 xxxx.cloud systemd[1]: systemd-udevd.service: Succeeded.
Mar 13 07:56:40 xxxx.cloud systemd[1]: Stopped udev Kernel Device Manager.
Mar 13 07:56:40 xxxx.cloud systemd[1]: Starting udev Kernel Device Manager...
Mar 13 07:56:40 xxxx.cloud systemd[1]: Started udev Kernel Device Manager.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=9/KILL
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525892 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525893 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525894 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525896 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525897 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525898 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525899 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525900 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525901 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Killing process 525902 (systemd-udevd) with signal SIGKILL.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Failed with result 'signal'.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 1.
Mar 13 07:57:46 xxxx.cloud systemd[1]: Stopped udev Kernel Device Manager.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Found left-over process 525885 (systemd-udevd) in control group while starting unit. Ignoring.
Mar 13 07:57:46 xxxx.cloud systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Found left-over process 525886 (systemd-udevd) in control group while starting unit. Ignoring.
Mar 13 07:57:46 xxxx.cloud systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Found left-over process 525887 (systemd-udevd) in control group while starting unit. Ignoring.
Mar 13 07:57:46 xxxx.cloud systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Found left-over process 525889 (systemd-udevd) in control group while starting unit. Ignoring.
Mar 13 07:57:46 xxxx.cloud systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 13 07:57:46 xxxx.cloud systemd[1]: systemd-udevd.service: Found left-over process 525890 (systemd-udevd) in control group while starting unit. Ignoring.
Mar 13 07:57:46 xxxx.cloud systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
these are the latest entries from udevadm monitor
DEV [71139.321376] add /kernel/slab/:A-0000256/cgroup/filp(183862:containerd.service) (cgroup)
UDEV [71139.328358] add /kernel/slab/kmalloc-512/cgroup/kmalloc-512(183862:containerd.service) (cgroup)
UDEV [71139.335767] add /kernel/slab/sock_inode_cache/cgroup/sock_inode_cache(183862:containerd.service) (cgroup)
UDEV [71139.343031] add /kernel/slab/proc_inode_cache/cgroup/proc_inode_cache(183862:containerd.service) (cgroup)
UDEV [71139.344456] add /kernel/slab/:A-0000128/cgroup/pid(183862:containerd.service) (cgroup)
UDEV [71139.346948] add /kernel/slab/dentry/cgroup/dentry(183862:containerd.service) (cgroup)
UDEV [71139.350987] add /kernel/slab/kmalloc-64/cgroup/kmalloc-64(183862:containerd.service) (cgroup)
UDEV [71139.354438] add /kernel/slab/skbuff_head_cache/cgroup/skbuff_head_cache(183862:containerd.service) (cgroup)
UDEV [71139.355760] add /kernel/slab/kmalloc-32/cgroup/kmalloc-32(183862:containerd.service) (cgroup)
UDEV [71139.356428] add /kernel/slab/:A-0001024/cgroup/PING(183862:containerd.service) (cgroup)
UDEV [71139.358485] add /kernel/slab/:A-0000040/cgroup/pde_opener(183862:containerd.service) (cgroup)
UDEV [71139.362871] add /kernel/slab/kmalloc-4k/cgroup/kmalloc-4k(183862:containerd.service) (cgroup)
UDEV [71139.363302] add /kernel/slab/:A-0000192/cgroup/cred_jar(183862:containerd.service) (cgroup)
UDEV [71139.397978] add /kernel/slab/inode_cache/cgroup/inode_cache(183862:containerd.service) (cgroup)
UDEV [71139.427001] add /kernel/slab/:A-0000208/cgroup/vm_area_struct(183862:containerd.service) (cgroup)
UDEV [71139.454891] add /kernel/slab/:A-0000064/cgroup/anon_vma_chain(183862:containerd.service) (cgroup)
UDEV [71139.466958] add /kernel/slab/anon_vma/cgroup/anon_vma(183862:containerd.service) (cgroup)
UDEV [71139.474103] add /kernel/slab/mm_struct/cgroup/mm_struct(183862:containerd.service) (cgroup)
UDEV [71139.741501] remove /kernel/slab/sock_inode_cache/cgroup/sock_inode_cache(183862:containerd.service) (cgroup)
UDEV [71139.757452] remove /kernel/slab/:A-0000192/cgroup/cred_jar(183862:containerd.service) (cgroup)
UDEV [71139.796371] add /kernel/slab/kmalloc-rcl-64/cgroup/kmalloc-rcl-64(183862:containerd.service) (cgroup)
UDEV [71139.804806] remove /kernel/slab/anon_vma/cgroup/anon_vma(183862:containerd.service) (cgroup)
UDEV [71139.810391] remove /kernel/slab/proc_inode_cache/cgroup/proc_inode_cache(183862:containerd.service) (cgroup)
UDEV [71139.811768] remove /kernel/slab/kmalloc-64/cgroup/kmalloc-64(183862:containerd.service) (cgroup)
UDEV [71139.812294] remove /kernel/slab/:A-0000128/cgroup/pid(183862:containerd.service) (cgroup)
UDEV [71139.812943] remove /kernel/slab/inode_cache/cgroup/inode_cache(183862:containerd.service) (cgroup)
UDEV [71139.813327] remove /kernel/slab/skbuff_head_cache/cgroup/skbuff_head_cache(183862:containerd.service) (cgroup)
UDEV [71139.834801] remove /kernel/slab/kmalloc-4k/cgroup/kmalloc-4k(183862:containerd.service) (cgroup)
UDEV [71139.835222] add /kernel/slab/kmalloc-1k/cgroup/kmalloc-1k(183862:containerd.service) (cgroup)
UDEV [71139.835556] remove /kernel/slab/dentry/cgroup/dentry(183862:containerd.service) (cgroup)
UDEV [71139.836431] remove /kernel/slab/kmalloc-512/cgroup/kmalloc-512(183862:containerd.service) (cgroup)
UDEV [71139.836938] remove /kernel/slab/:A-0000256/cgroup/filp(183862:containerd.service) (cgroup)
UDEV [71139.845860] remove /kernel/slab/:A-0000040/cgroup/pde_opener(183862:containerd.service) (cgroup)
UDEV [71139.858633] remove /kernel/slab/mm_struct/cgroup/mm_struct(183862:containerd.service) (cgroup)
UDEV [71139.859594] remove /kernel/slab/:A-0000208/cgroup/vm_area_struct(183862:containerd.service) (cgroup)
UDEV [71139.860200] remove /kernel/slab/:A-0000064/cgroup/anon_vma_chain(183862:containerd.service) (cgroup)
UDEV [71139.921380] remove /kernel/slab/kmalloc-32/cgroup/kmalloc-32(183862:containerd.service) (cgroup)
UDEV [71139.925817] remove /PING(183862:containerd.service) (cgroup)
UDEV [71139.926651] remove /kernel/slab/kmalloc-1k/cgroup/kmalloc-1k(183862:containerd.service) (cgroup)
UDEV [71139.929972] remove /kernel/slab/kmalloc-rcl-64/cgroup/kmalloc-rcl-64(183862:containerd.service) (cgroup)
Can anyone help me understand whats going on and how can I fix this?
How do I allow all traffic that occurs on VLAN / internal ports without any blocking but on external IP I allow selected ports. so I want the machines on VLAN to communicate freely but I want restricted access from public IPs
assume for instance (fictional IPs)
Machine A
Machine B
Machine C
I do not want firewall for any traffic on 192.168.0.* but I want selected ports to be opened on each public IP depending on the machine
on a remote machine there are two network interfaces.
I want the VSFTPD to only receive and entertain requests from the public IP and localhost and not from the VLAN or any machines on VLAN. I added the following rules t the UFW:
ufw allow proto tcp from 33.33.22.22 to any port 20:21
this is for passive FTP
ufw allow proto tcp from 33.33.22.22 to any port 40000:40100
however with this setting the FileZilla is stuck
Connecting to 33.33.22.22
Connection established, waiting for welcomemessage...
Initializing TLS
verifying certificate
Logged in
Retrieving directory listing...
and then it is stuck for few seconds and then retries.
with this setting
ufw allow proto tcp from any to any port 40000:40100
it starts working but then connections from other machines on VLAN is also possible. how can I achieve the desired results or that's not possible?
I recently started practicing kubernetes on my local machine which is ubuntu 21.04L in a virtual machine (VMWare). Whenever I shutdown it is stuck for few minutes for containerd-shim with the following message.
How can I reduce the service time for graceful shutdown or is it some error?
I'm using Ubuntu 21.04. I had libreoffice removed as I use online service so desktop app are not needed. However, even after removing the software update keeps telling me to download and update libreoffice packages.
How do I remove them from the updates also and why it keeps tracking Libreoffice? Is it that some portion of libreoffice is still on my machine somewhere?
Update: I removed using the following command
sudo apt-get remove --purge libreoffice* && sudo apt-get clean && sudo apt-get autoremove
I recently started using a remote Ubuntu server for development and testing machine. However the hosting provider reported a crypto mining process was running and he had to shut down the server.
There were no logs or any data that could identify that process or anything that could help figure out what happened. Then it happened again, but this time they captured this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
246369 redis 20 0 13928 11444 908 S 746.7 0.2 62801:13 /tmp/kmv --pool pool.hashvault.pro:80 --username TRTLv2TW8sjC5LmSpiDdRZ2ndnEwPRpJ9Lgz3vgGY2CTSLkLeKAUFMefEeT6idQBxzSLsXfAvAqfhH5zkxMM3sHu2RL8xh1n5Pg --password x --algorithm chukwa_v2
The only ports that are open are Redis port, 6379.
admin@nicotine2:~$ sudo ufw status
Status: active
To Action From
-- ------ ----
22 ALLOW Anywhere
9200 DENY Anywhere
6379/tcp ALLOW Anywhere
22 (v6) ALLOW Anywhere (v6)
9200 (v6) DENY Anywhere (v6)
6379/tcp (v6) ALLOW Anywhere (v6)
When I checked, there was no /tmp/kmv folder anywhere to be found. This has happened for the 2nd time.
Any clues, recommendations or suggestions to avoid this?
I'm not an expert of Ubuntu but I'm learning it while using it for everyday tasks. my experience has been good so far. just that I face a few glitches sometimes.
I have this weird problem from the very beginning, usually I restart but that's not the solution because often the processes are running and I just simply can't kill them like that.
I use VMware to run Ubuntu 19.04. on Windows Ctrl+Alt+Del key combination is very common to Lock and Unlock the screen and system level options. Sometimes accidentally I press them and I get this
I don't know if that's VMWare or LINUX itself but then nothing works and I have to shutdown the guest and restart it.
My questions are:
What exactly is this blank screen with cursor blinking? Is it that OS has crashed or the GUI Wayland has shut down? Or is it some pause state?
What should I do in this case that I can preserve my work or better yet resume it?
P.S: Just found out that it's not Ctrl + Alt + Del. The way my laptop keyboard is, I confirmed I press Ctrl + Alt + F12. I found What does "Ctrl + Alt + F12" do? but nothing works, and after like few minutes (5+ or more) the virtual machine restarts.
I'm running Ubuntu as my guest OS from vmware and want to add a new HDD. so I added this
The 10 GB HDD added but I do not see it appearing in Ubuntu anywhere. I tried sudo ls /dev/sd* and all I got was sda0 and sda1.
I tried GParted but it won't run. I tried KDE Partition manager but it errors out saying you are not the root. I tried Ubuntu's built-in disk manager and this is what it shows:
and here is the output of lsblk:
So what should I do? How do I get the new HDD in linux?
I have recently started using linux - ubuntu 18.04 at work, so here is the list of apps I have installed that I need everyday:
Here is the VM configuration (my company uses VMWare)
now the problem is it keeps freezing for no obvious reason.
Sometime it takes 5-10 minutes to recover. sometimes I have to reset my machine (a virtual one off course). Surprisingly, a Windows 10 VM with identical hardware/software configuration runs smooth with no such problems.
so I'm pretty confused. All that is on internet that Hardware community is not so nice etc with LINUX hence it suffers native drivers. but to me it should not have any problem on a virtual machine.
so is this a common problem with LINUX that I'm facing everyday or is this me doing something wrong? and How do I fix it?