Many places on the Web say that the content type of the manifest file is incorrect, or that the file format is incorrect, etc. After debugging, it turns out that this error can also occur if the file is not accessible (e.g., the server is down).

sudo apt install libcanberra-gtk-module libcanberra-gtk3-module
Sometimes just before installing a reference materials

https://askubuntu.com/questions/342202/failed-to-load-module-canberra-gtk-module-but-already-installed

Execute the following command in server A (Windows Server 2008 R2) to access the service health of remote server B (Windows Server 2003) :

sc \\servername query “servicename”

The results returned are as follows:

[SC] OpenSCManager FAILED 1722: The RPC server is unavailable.

Solution: Just restart server A. Because I really don’t know what causes it, it is OK to run the command in my native machine, but the operating system of my native machine is exactly the same as that of server A, so it should not be the setting problem of server B.

Reproduced in: https://www.cnblogs.com/yumianhu/p/3707538.html

capacity expansion method :
capacity expansion method point here

Gparted when deleting “Linux swap” reported an error:
swapoff failed: Cannot allocate memory

found a solution online:
error report solution point here

results at the end of the cat /proc/meminfo check found that their available memory is not enough… After adding memory to it, delete “Linux swap” without returning an error

the ubuntu 18.04 desktop will not boot, possibly because the configuration of the graphical desktop was damaged while installing the remote desktop.

because baidu is not specific error files and related configuration. You can only delete the desktop system.

then the problem came, sudo apt install ubuntu-desk reported dependency problems, not to install.

so baidu, can use tasksel, perform really pop up a graphic after installation tools:

this installation should be OK, but TAB to OK, press ENTER, error:

tasksel aptitude failed (100)

is just another round of rummaging, but the good news is that something is wrong with the source of LINUX.

to view their current source, is a new ali cloud, may be posted online at that time there is a leak. Hurry up and get a new Qing Hua.

command-line switch:

CD/etc/apt/

vi sources.list

delete all content

copy and paste:

# 默认注释了源码镜像以提高 apt update 速度，如有需要可自行取消注释
deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ bionic main restricted universe multiverse
# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ bionic main restricted universe multiverse
deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ bionic-updates main restricted universe multiverse
# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ bionic-updates main restricted universe multiverse
deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ bionic-backports main restricted universe multiverse
# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ bionic-backports main restricted universe multiverse
deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ bionic-security main restricted universe multiverse
# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ bionic-security main restricted universe multiverse

and tasksel will be running again. It’s like seeing the light of day again and tears running down my face.

http://hi.baidu.com/wwt06/item/29d5d5246f3a71d50f37f9f6

dlink set port map illustration (to solve the failure problem of electric TCP link test)

today to find a resource when you want to use the next donkey, so download the online reputation of emule a5.0a Xtreme8.0

test steps appear in the installation process, click test after. The problem arises:

Testing IP: 122.85.120.171 (122.85.120.171)

, Starting TCP connection test…
TCP test failed! UDP test will not be performed.
Connection test finished.

Results in detail:

• TCP connection test failed.
  It was not possible, to establish a TCP connection to your eMule.
  Other users will only be able to connect to you with the help of a server, resulting in a low ID for you. While eMule still works, this will give you several disadvantages. Therfore it is highly recommended to solve this problem.

How to resolve port problems… Something is interfering with your network communications. There are two main reasons for this:

• If you are using a firewall, ensure that your firwall don’t block the required ports! You might need to set a rule to allow the ports to be available.
• If you use a router, make sure that your router forwards the required ports to your local IP!
• You can find more details and guides here in the online help.

this problem indicates that the TCP connection test fails and the udp test cannot be completed, which will become the low ID group and affect the normal function. We specifically look at the how to resolve Port Problems section, which focuses on how to resolve port problems and gives two main reasons:

1. If you use a firewall. To ensure that the firewall is not blocking this required port, you may need to set a rule to allow port use.

2. If you are using a router, make sure your router port maps to your own local IP!

for these two problems, let’s look at them separately. Easy to view for firewalls. Turn off the firewall at most. After the test does not matter, no firewall can still test not pass. Therefore, it is likely to be the second reason. The second reason should be checked in the router Settings. The specific steps are as follows:

(note that I am using a dlink di-524m router, which may have different Settings depending on the router)

enter in the browser: “192.168.0.1” to open the router interface, log in with admin, and click “advanced Settings” — “port forwarding”

set specific rules as follows:

be careful here because we are dealing with TCP connections. So we chose the HTTP application, but otherwise we chose the computer name. Then click the arrow on the left to automatically add the IP address, and notice what port number you want to test, fill in the port box:

here is 15866, so we fill in 15866 in the port, the final effect is as follows:

check the small box on the left and click save Settings at the top. With respect to ok. (This function opens only one port when the same port number is entered at the beginning and the end.)

retested the connection and found that the TCP test passed but the udp port test failed:

has a detail:

UDP connection test failed.

A sent UDP packet could not be received by your eMule. UDP communication is used for Kad and to reduce bandwidth usage (Overhead) – which will not work for you. Although the main operativeness of eMule is still available to you by TCP communication.

mean: udp test fails, a packet has not been sent out your emule software receives, udp communication is used by the kad network (no server network) and use less bandwidth overhead (network) – now it will not work for you, even if via TCP communications has made, the main operation effect.

should also be the problem that the port cannot be opened. Before, our port ends and starts with the same number 15866, so only this port is opened. Of course, whether to enable udp port is an optional item. It’s a must. See if you want to use it. Here we simply repeat the previous setup, except that the port is changed to UDP. Here Is 52027. After selecting udp (not TCP), please pay attention to select UDP in the protocol. Retest after saving:

and it’s perfect! Perfect! Now that you know how to set up port mappings, you can solve some of the software problems you encounter.

reprint please indicate from: oh! Ding dong http://wodingdong.com/

docker port mapping or starting container Error Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen

phenomenon:

[root@localhost ~]# docker run -d -p 9000:80 centos:httpd /bin/sh -c /usr/local/bin/start.sh
d5b2bd5a7bc4895a973fe61efd051847047d26385f65c278aaa09e4fa31c4d76
docker: Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen (6bda693d1143657e46bee0300276aa05820da2b21a3d89441e820d1a274c48b6): (iptables failed: Iptables — wait-T nat-a Docker-P TCP-D 0/0 — Dport 9000-j DNAT — to-Destination 172.17.0.2:80! -i docker0: iptables: No chain/target/match by that name.
(exit status 1)).

[root@localhost ~]# docker start d5b2bd5a7bc4
Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen (4127da7466709fd45695a1fbe98e13c2ac30c2a554e18fb902ef5a03ba308438): (iptables failed: Iptables — wait-T nat-a Docker-P TCP-D 0/0 — Dport 9000-j DNAT — to-Destination 172.17.0.2:80! -i docker0: iptables: No chain/target/match by that name.
(exit status 1))
Error: failed to start containers: d5b2bd5a7bc4

reason :
docker service startup custom chain docker due to centos7 firewall has been removed

The

firewall is based on iptables for data filtering, which may cause conflicts with Docker.

when firewalld is started or restarted, the rules of DOCKER will be removed from the iptables, thus affecting the normal work of DOCKER.

when you are using Systemd, firewalld will start before Docker, but if you start after Docker or restart firewalld, you will need to restart the Docker process.

restart docker service and regenerate the custom docker

chain

Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination        
DOCKER     all  --  0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT)
target     prot opt source               destination        

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination        
DOCKER     all  --  0.0.0.0/0           !127.0.0.0/8          ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination        
MASQUERADE  all  --  172.17.0.0/16        0.0.0.0/0          
MASQUERADE  tcp  --  172.17.0.2           172.17.0.2           tcp dpt:8080

Chain DOCKER (2 references)
target     prot opt source               destination        
RETURN     all  --  0.0.0.0/0            0.0.0.0/0          
DNAT       tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:8888 to:172.17.0.2:8080
root@router:playbook#iptables -t nat -nL
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination        
DOCKER     all  --  0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT)
target     prot opt source               destination        

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination        
DOCKER     all  --  0.0.0.0/0           !127.0.0.0/8          ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination        
MASQUERADE  all  --  172.17.0.0/16        0.0.0.0/0          
MASQUERADE  tcp  --  172.17.0.2           172.17.0.2           tcp dpt:8080

Chain DOCKER (2 references)
target     prot opt source               destination        
RETURN     all  --  0.0.0.0/0            0.0.0.0/0          
DNAT       tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:8888 to:172.17.0.2:8080

restart docker service then start the container
systemctl restart docker
docker start foo

solution

problem may be that there is an updated version of Visual C ++ Redistributable that SQL Server is trying to install, for example, from Visual Studio 2017. If you don’t need the latest C ++ Redistributable component, one way to resolve this problem is to add or remove programs and undistribute all references to Visual C ++ 2017 Redistributable. After this, the SQL Server installation should continue without error.

The problem is likely that there’s a newer version of the Visual C++ Redistributable than SQL Server is trying to install, e.g., from Visual Studio 2017. So another way to address this, if you don’t need the latest C++ redistributable, is to go to Add or Remove Programs and uninstall all references to Visual C++ 2017 Redistributable. After this, the SQL Server installation should proceed without errors.