I have a server which OS is Ubuntu 18.04.03 configured four IP addresses on four different interfaces. Now there is a interface I need to restart, and I can not interfere with other three interfaces. So I think I can't using sudo netplan apply. Is there any way to restart specificed interface?
Thankyou in advance!
My environment:
I have three servers in my studio. Server A is an NFS server, server B and C are NFS clients.
Server B and C mount A:/raid/data on local /data. SELinux is disabled, ufw is not installed, iptables is default. And there is a layer-2 switch without any connection limit to the three servers.
What I found:
This morning I tried to execute ls /data on server B, and after about 5 mins, there was not any output.
When I connected to server C, and tried to execute ls /data, it worked normally.
What I tried:
I executed the commands listed above, and all of them were stuck without any output.
df -Th
df
ls /
fuser -m -v /data
I tried to execute umount -f /data, it said device is busy.
I tried ping server A on server B, it responded with low latency.
What I need:
Is there any solution which doesn't involve rebooting the server? And what causes this problem? How can I avoid it?
NFS server IP is 192.168.0.70, and NFS client IP is 192.168.0.84.
My /etc/exports file just like this:
/my/share/dir 192.168.0.84(ro,sync,no_subtree_check)
And I use below commend to mounting:
sudo mount -t nfs 192.168.0.70:/my/share/dir /mnt/my_mount
The error message is:
username@client84:~$ sudo mount -t nfs 192.168.0.70:/src_dir/ /home/username/mount_point/
mount.nfs: Connection timed out
And the status of NFS serverm is:
username@server70:~$ systemctl status nfs-kernel-server.service
● nfs-kernel-server.service - LSB: Kernel NFS server support
Loaded: loaded (/etc/init.d/nfs-kernel-server)
Active: active (exited) since Wed 2020-01-08 15:04:49 CST; 19h ago
Process: 7199 ExecStop=/etc/init.d/nfs-kernel-server stop (code=exited, status=0/SUCCESS)
Process: 7209 ExecStart=/etc/init.d/nfs-kernel-server start (code=exited, status=0/SUCCESS)
I tried capture package on NFS server, and this is what I got:
15:09:43.563798 IP (tos 0x0, ttl 64, id 54562, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.760 > 192.168.0.70.2049: Flags [S], cksum 0x794a (correct), seq 1313175943, win 29200, options [mss 1460,sackOK,TS val 3280514213 ecr 0,nop,wscale 7], length 0
15:09:43.563826 IP (tos 0x0, ttl 64, id 24797, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.760: Flags [R.], cksum 0xc358 (correct), seq 0, ack 1313175944, win 0, length 0
15:09:44.564453 IP (tos 0x0, ttl 64, id 3109, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.926 > 192.168.0.70.2049: Flags [S], cksum 0xdeea (correct), seq 3201409466, win 29200, options [mss 1460,sackOK,TS val 3280514463 ecr 0,nop,wscale 7], length 0
15:09:44.564485 IP (tos 0x0, ttl 64, id 24971, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.926: Flags [R.], cksum 0x29f3 (correct), seq 0, ack 3201409467, win 0, length 0
15:09:46.565080 IP (tos 0x0, ttl 64, id 20545, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.979 > 192.168.0.70.2049: Flags [S], cksum 0xef6c (correct), seq 1309605842, win 29200, options [mss 1460,sackOK,TS val 3280514963 ecr 0,nop,wscale 7], length 0
15:09:46.565101 IP (tos 0x0, ttl 64, id 25141, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.979: Flags [R.], cksum 0x3c69 (correct), seq 0, ack 1309605843, win 0, length 0
15:09:48.565600 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.70 tell 192.168.0.84, length 46
15:09:48.565630 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.0.70 is-at aa:bb:cc:dd:ee:ff, length 28
15:09:50.565751 IP (tos 0x0, ttl 64, id 27321, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.861 > 192.168.0.70.2049: Flags [S], cksum 0x3093 (correct), seq 797104581, win 29200, options [mss 1460,sackOK,TS val 3280515964 ecr 0,nop,wscale 7], length 0
15:09:50.565779 IP (tos 0x0, ttl 64, id 25423, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.861: Flags [R.], cksumARP 0x8178 (correct), seq 0, ack 797104582, win 0, length 0
15:09:55.579799 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.84 tell 192.168.0.70, length 28
15:09:55.580001 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.0.84 is-at aa:bb:cc:dd:ee:ff, length 46
15:09:58.566416 IP (tos 0x0, ttl 64, id 36260, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.959 > 192.168.0.70.2049: Flags [S], cksum 0x15eb (correct), seq 3839178472, win 29200, options [mss 1460,sackOK,TS val 3280517964 ecr 0,nop,wscale 7], length 0
15:09:58.566449 IP (tos 0x0, ttl 64, id 26424, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.959: Flags [R.], cksum 0x6ea0 (correct), seq 0, ack 3839178473, win 0, length 0
15:10:08.567151 IP (tos 0x0, ttl 64, id 40969, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.889 > 192.168.0.70.2049: Flags [S], cksum 0x067e (correct), seq 3163776281, win 29200, options [mss 1460,sackOK,TS val 3280520464 ecr 0,nop,wscale 7], length 0
15:10:08.567203 IP (tos 0x0, ttl 64, id 26636, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.889: Flags [R.], cksum 0x68f7 (correct), seq 0, ack 3163776282, win 0, length 0
15:10:18.567873 IP (tos 0x0, ttl 64, id 4325, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.671 > 192.168.0.70.2049: Flags [S], cksum 0xf5c0 (correct), seq 1263459889, win 29200, options [mss 1460,sackOK,TS val 3280522964 ecr 0,nop,wscale 7], length 0
15:10:18.567897 IP (tos 0x0, ttl 64, id 27229, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.671: Flags [R.], cksum 0x61fe (correct), seq 0, ack 1263459890, win 0, length 0
15:10:28.568630 IP (tos 0x0, ttl 64, id 38694, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.853 > 192.168.0.70.2049: Flags [S], cksum 0x9aff (correct), seq 705253310, win 29200, options [mss 1460,sackOK,TS val 3280525464 ecr 0,nop,wscale 7], length 0
15:10:28.568665 IP (tos 0x0, ttl 64, id 29520, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.853: Flags [R.], cksum 0x1101 (correct), seq 0, ack 705253311, win 0, length 0
15:10:38.569313 IP (tos 0x0, ttl 64, id 40959, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.929 > 192.168.0.70.2049: Flags [S], cksum 0x8924 (correct), seq 66026915, win 29200, options [mss 1460,sackOK,TS val 3280527964 ecr 0,nop,wscale 7], length 0
15:10:38.569343 IP (tos 0x0, ttl 64, id 31363, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.929: Flags [R.], cksum 0x08ea (correct), seq 0, ack 66026916, win 0, length 0
15:10:43.573606 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.70 tell 192.168.0.84, length 46
15:10:43.573620 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.0.70 is-at aa:bb:cc:dd:ee:ff, length 28
15:10:48.570034 IP (tos 0x0, ttl 64, id 25891, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.722 > 192.168.0.70.2049: Flags [S], cksum 0x687f (correct), seq 272599298, win 29200, options [mss 1460,sackOK,TS val 3280530465 ecr 0,nop,wscale 7], length 0
15:10:48.570077 IP (tos 0x0, ttl 64, id 32321, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.722: Flags [R.], cksum 0xf209 (correct), seq 0, ack 272599299, win 0, length 0
15:10:53.579804 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.84 tell 192.168.0.70, length 28
15:10:53.580011 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.0.84 is-at aa:bb:cc:dd:ee:ff, length 46
15:10:58.570709 IP (tos 0x0, ttl 64, id 41869, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.749 > 192.168.0.70.2049: Flags [S], cksum 0x7edd (correct), seq 580671080, win 29200, options [mss 1460,sackOK,TS val 3280532965 ecr 0,nop,wscale 7], length 0
15:10:58.570731 IP (tos 0x0, ttl 64, id 32668, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.749: Flags [R.], cksum 0x122c (correct), seq 0, ack 580671081, win 0, length 0
15:11:08.571380 IP (tos 0x0, ttl 64, id 3221, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.817 > 192.168.0.70.2049: Flags [S], cksum 0xf10d (correct), seq 160428860, win 29200, options [mss 1460,sackOK,TS val 3280535465 ecr 0,nop,wscale 7], length 0
15:11:08.571416 IP (tos 0x0, ttl 64, id 33817, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.817: Flags [R.], cksum 0x8e20 (correct), seq 0, ack 160428861, win 0, length 0
15:11:18.572069 IP (tos 0x0, ttl 64, id 47816, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.753 > 192.168.0.70.2049: Flags [S], cksum 0xb122 (correct), seq 2139992997, win 29200, options [mss 1460,sackOK,TS val 3280537965 ecr 0,nop,wscale 7], length 0
15:11:18.572107 IP (tos 0x0, ttl 64, id 34217, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.753: Flags [R.], cksum 0x57f9 (correct), seq 0, ack 2139992998, win 0, length 0
15:11:28.572748 IP (tos 0x0, ttl 64, id 64308, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.867 > 192.168.0.70.2049: Flags [S], cksum 0x9ade (correct), seq 1463543813, win 29200, options [mss 1460,sackOK,TS val 3280540465 ecr 0,nop,wscale 7], length 0
15:11:28.572775 IP (tos 0x0, ttl 64, id 36325, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.867: Flags [R.], cksum 0x4b79 (correct), seq 0, ack 1463543814, win 0, length 0
15:11:33.579799 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.84 tell 192.168.0.70, length 28
15:11:33.580030 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.0.84 is-at aa:bb:cc:dd:ee:ff, length 46
15:11:38.573414 IP (tos 0x0, ttl 64, id 63669, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.920 > 192.168.0.70.2049: Flags [S], cksum 0xf76b (correct), seq 4101628992, win 29200, options [mss 1460,sackOK,TS val 3280542965 ecr 0,nop,wscale 7], length 0
15:11:38.573440 IP (tos 0x0, ttl 64, id 38585, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.920: Flags [R.], cksum 0xb1ca (correct), seq 0, ack 4101628993, win 0, length 0
15:11:48.574103 IP (tos 0x0, ttl 64, id 28920, offset 0, flags [DF], proto TCP (6), length 60)
192.168.0.84.769 > 192.168.0.70.2049: Flags [S], cksum 0xb826 (correct), seq 3096401474, win 29200, options [mss 1460,sackOK,TS val 3280545466 ecr 0,nop,wscale 7], length 0
15:11:48.574137 IP (tos 0x0, ttl 64, id 38789, offset 0, flags [DF], proto TCP (6), length 40)
192.168.0.70.2049 > 192.168.0.84.769: Flags [R.], cksum 0x7c4a (correct), seq 0, ack 3096401475, win 0, length 0
Please give me some advice, thank you in advance.
I'm managing lots of servers which runs Ubuntu 18.04 server. And it has at lest 4 NIC for each server. My server will reboot every weekend, and I always found the NIC name changed after reboot. Sometimes is onboad NIC, sometimes is PCI-e NIC, some times is all of NIC, sometimes none of theme.
I know I can fix it by config /etc/udev/rules.d/70-persistent-net.rules file, specific which MAC address corresponding which name. But I still want know why the NIC name always and how can I fix it in a easier way (edit rules file could cost me whole day or worse).
Thanks in advance.
ssh -x as usual. But this time I logon, it note xhost: unable to open display "". And when I execute virt-manager, it shows like this:Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
(virt-manager:16045): Gtk-WARNING **: cannot open display:
/etc/ssh/ssh_config and make sure it have configured like below:ForwardAgent yes
ForwardX11 yes
ForwardX11Trusted yes
And then check the remote host's /etc/ssh/ssh_config and make sure it have configured like below:
X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
And then I execute virt-manager, it still shows like below:
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
(virt-manager:16045): Gtk-WARNING **: cannot open display:
Then I tried few commands like below, it seemes useless.
$ sudo vncserver
New 'My_Local_Host:15 (root)' desktop at :15 on machine My_Local_Host
Starting applications specified in /etc/X11/Xvnc-session
Log file is /root/.vnc/My_Local_Host:15.log
Use xtigervncviewer -SecurityTypes VncAuth -passwd /root/.vnc/passwd :15 to connect to the VNC server.
$ export DISPLAY=localhost:15
$ xhost +
xhost: unable to open display "localhost:15"
Finally I installed gksu and tried to open virt-manager by it, but it still useless:
gksu virt-manager
(gksu:17242): Gtk-WARNING **: cannot open display: localhost:15
Can you give me some advice? Thank you!
I bought some memory stick which is ovcerclockable. The default frequency is 2.4GHz, the frequency can be configured up to 3.6GHz. And I confiured frequency and the voltage in BIOS, set the frequency to 3.6GHz. Then I ran the memtester86 8.1, to test if overclocking is stable, and it passed all test with no error on 3.6 GHz. Finally, I entery the OS(my OS version is 18.04),and execue sudo dmidecode --type 17 | grep -i speed, it shows like below:
Speed: 2400 MT/s
Configured Clock Speed: 3600 MT/s
Speed: 2400 MT/s
Configured Clock Speed: 3600 MT/s
Speed: 2400 MT/s
Configured Clock Speed: 3600 MT/s
Speed: 2400 MT/s
Configured Clock Speed: 3600 MT/s
Speed: 2400 MT/s
Configured Clock Speed: 3600 MT/s
Speed: 2400 MT/s
Configured Clock Speed: 3600 MT/s
Speed: 2400 MT/s
Configured Clock Speed: 3600 MT/s
Speed: 2400 MT/s
Configured Clock Speed: 3600 MT/s
I wonder which is the "actual" frequency of my memory? Did I overclocking success?
And I tried another command, sudo lshw -short -C memory, and it shows this:
H/W path Device Class Description
=========================================================
/0/0 memory 64KiB BIOS
/0/1b memory System Memory
/0/1b/0 memory 8GiB DIMM DDR4 Synchronous 2400 MHz (0.4 ns)
/0/1b/1 memory 8GiB DIMM DDR4 Synchronous 2400 MHz (0.4 ns)
/0/1b/2 memory 8GiB DIMM DDR4 Synchronous 2400 MHz (0.4 ns)
/0/1b/3 memory 8GiB DIMM DDR4 Synchronous 2400 MHz (0.4 ns)
/0/20 memory System Memory
/0/20/0 memory 8GiB DIMM DDR4 Synchronous 2400 MHz (0.4 ns)
/0/20/1 memory 8GiB DIMM DDR4 Synchronous 2400 MHz (0.4 ns)
/0/20/2 memory 8GiB DIMM DDR4 Synchronous 2400 MHz (0.4 ns)
/0/20/3 memory 8GiB DIMM DDR4 Synchronous 2400 MHz (0.4 ns)
/0/33 memory 768KiB L1 cache
/0/34 memory 12MiB L2 cache
/0/35 memory 19MiB L3 cache
/0/1 memory
/0/3 memory
/0/100/1f.2 memory Memory controller
It just let me more confusing. Dose overclocking independent with OS? Or I should add some payload to let memory speed up? Can you give me some advice? Thank you!
Today I execute sudo apt update and sudo apt upgrade to upgrade my OS.It downloaded about 300MB file. After upgrade it shows these:
Errors were encountered while processing:
nfs-common
samba-common
cups-daemon
postgresql-10
cups-core-drivers
winbind
libpam-winbind:amd64
samba
samba-common-bin
linux-firmware
libnss-winbind:amd64
cups
linux-image-generic
linux-generic
I think maybe it is the problem of dependency so I execute comman sudo apt install -f. And it gave more error:
eading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-image-4.4.0-146-generic linux-modules-4.4.0-146-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
16 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up samba-common (2:4.7.6+dfsg~ubuntu-0ubuntu2.10) ...
dpkg: error processing package samba-common (--configure):
installed samba-common package post-installation script subprocess returned error exit status 10
Setting up cups-daemon (2.2.7-1ubuntu2.5) ...
/var/lib/dpkg/info/cups-daemon.postinst: 150: /var/lib/dpkg/info/cups-daemon.postinst: update-rc.d: not found
dpkg: error processing package cups-daemon (--configure):
installed cups-daemon package post-installation script subprocess returned error exit status 127
Setting up postgresql-10 (10.8-0ubuntu0.18.04.1) ...
/var/lib/dpkg/info/postgresql-10.postinst: 110: /var/lib/dpkg/info/postgresql-10.postinst: invoke-rc.d: not found
dpkg: error processing package postgresql-10 (--configure):
installed postgresql-10 package post-installation script subprocess returned error exit status 127
dpkg: dependency problems prevent configuration of cups-core-drivers:
cups-core-drivers depends on cups-daemon (>= 2.2.7-1ubuntu2.5); however:
Package cups-daemon is not configured yet.
dpkg: error processing package cups-core-drivers (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of winbind:
winbind depends on samba-common (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.10); however:
Package samba-common is not configured yet.
dpkg: error processing package winbind (--configure):
dependency problems - leaving unconfigured
Setting up auditd (1:2.8.2-1ubuntu1) ...
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
/var/lib/dpkg/info/auditd.postinst: 62: /var/lib/dpkg/info/auditd.postinst: update-rc.d: not found
dpkg: error processing package auditd (--configure):
installed auditd package post-installation script subprocess returned error exit status 127
dpkg: dependency problems prevent configuration of libpam-winbind:amd64:
libpam-winbind:amd64 depends on samba-common (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.10); however:
Package samba-common is not configured yet.
libpam-winbind:amd64 depends on winbind (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.10); however:
Package winbind is not configured yet.
dpkg: error processing package libpam-winbind:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of samba:
samba depends on samba-common (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.10); however:
Package samba-common is not configured yet.
dpkg: error processing package samba (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of samba-common-bin:
samba-common-bNo apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
No apport report written because MaxReports is reached already
in depends on samba-common (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.10); however:
Package samba-common is not configured yet.
dpkg: error processing package samba-common-bin (--configure):
dependency problems - leaving unconfigured
Setting up linux-firmware (1.173.6) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-48-generic
/usr/sbin/update-initramfs: 157: /usr/sbin/update-initramfs: mkinitramfs: not found
update-initramfs: failed for /boot/initrd.img-4.15.0-48-generic with 127.
dpkg: error processing package linux-firmware (--configure):
installed linux-firmware package post-installation script subprocess returned error exit status 127
No apport report written because MaxReports is reached already
Setting up rpcbind (0.2.3-0.6) ...
/var/lib/dpkg/info/rpcbind.postinst: 92: /var/lib/dpkg/info/rpcbind.postinst: update-rc.d: not found
dpkg: error processing package rpcbind (--configure):
installed rpcbind package post-installation script subprocess returned error exit status 127
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of libnss-winbind:amd64:
libnss-winbind:amd64 depends on samba-common (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.10); however:
Package samba-common is not configured yet.
libnss-winbind:amd64 depends on winbind (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.10); however:
Package winbind is not configured yet.
dpkg: error processing package libnss-winbind:amd64 (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of nfs-common:
nfs-common depends on rpcbind; however:
Package rpcbind is not configured yet.
dpkg: error processing package nfs-common (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of cups:
cups depends on cups-core-drivers (>= 2.2.7-1ubuntu2.5); however:
Package cups-core-drivers is not configured yet.
cups depends on cups-daemon (>= 2.2.7-1ubuntu2.5); however:
Package cups-daemon is not configured yet.
dpkg: error processing package cups (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of linux-image-generic:
linux-image-generic depends on linux-firmware; however:
Package linux-firmware is not configured yet.
dpkg: error processing package linux-image-generic (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
dpkg: dependency problems prevent configuration of linux-generic:
linux-generic depends on linux-image-generic (= 4.15.0.50.52); however:
Package linux-image-generic is not configured yet.
dpkg: error processing package linux-generic (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
Errors were encountered while processing:
samba-common
cups-daemon
postgresql-10
cups-core-drivers
winbind
auditd
libpam-winbind:amd64
samba
samba-common-bin
linux-firmware
rpcbind
libnss-winbind:amd64
nfs-common
cups
linux-image-generic
linux-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
My OS version is:
Linux MyUbuntu105 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
And I just upgrade OS from 16.04 to 18.04, dose it could cause this issue? How can I fix it? Thank you!