https://blog.csdn.net/Mr_791063894/article/details/83753607
div>
Severe: error filterStart error resolution
The following error occurs:
SEVERE: Error filterStart
Aug 27, 2013 9:37:44 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [/test] startup failed due to previous errors
Based on my own experience and solutions, here is my approach:
First remove < from web.xml; filter> Tag, and then restart Tomcat. The error will be reported in the background of Tomcat to see what is the cause of the error.
If a package is missing, the necessary package is imported, and any other errors resolve themselves. Mine is not short of bags
SEVERE: End event threw exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.tomcat.util.IntrospectionUtils.callMethod1(IntrospectionUtils.java:928)
at org.apache.tomcat.util.digester.SetNextRule.end(SetNextRule.java:193)
at org.apache.tomcat.util.digester.Rule.end(Rule.java:229)
at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1138)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParse
r.java:604)
According to the information I collected on the Internet, it is probably due to the inconsistency or lower version of the JDK version; Select a unified version of the development and running environments
If the version is not unified, the unified version, if the version is low, then change to a high version.
(However, I also have a problem here, if the server can not connect to the external network, then the program started under Tomcat is still an error)
Here is the download link for the JDK:
http://www.oracle.com/technetwork/java/javase/archive-139210.html
Illegal escape character in string literal
HTTP error code compact version
IIS status code editing under HTTP
1XX – Information prompt
These status codes represent temporary responses. The client should be prepared to receive one or more 1XX responses before receiving the general response.
100 – Go ahead.
101 – Switch protocol.
2 xx – success
This type of status code indicates that the server has successfully accepted the client request.
200 – Ok. The client request has been successful.
201 – Created.
202 – Accepted.
203 – Non-authoritative information.
204 – No content.
205 – Reset content.
206 – Part content.
3XX – Redirection
The client browser must do more to implement the request. For example, a browser might have to request a different page on the server or repeat the request through a proxy server.
301 – The object has been permanently removed, that is, permanently redirected.
302 – The object has been temporarily moved.
304 – Not modified.
307 – Temporary redirection.
4XX – Client error
An error has occurred and there seems to be a problem with the client. For example, if the client requests a page that does not exist, the client does not provide valid authentication information. 400 – Wrong request.
401 – Access denied. IIS defines a number of different 401 errors that point to a more specific reason for the error. These specific error codes are displayed in the browser but not in the IIS log:
401.1 – Login failed.
401.2 – Server configuration causes logon failure.
401.3 – not authorized due to ACL restrictions on resources.
401.4 – Filter authorization failed.
401.5 – ISAPICGI application authorization failed.
401.7 – Access is denied by the URL authorization policy on the Web server. This error code is dedicated to IIS 6.0.
403 – Access disabled: IIS defines a number of different 403 errors that point to a more specific reason for the error:
403.1 – Execute access is prohibited.
403.2 – Read access is prohibited.
403.3 – Write access is prohibited.
403.4 – SSL is required.
403.5 – SSL 128 is required.
403.6 – IP address rejected.
403.7 – Client certificates are required.
403.8 – Site access denied.
403.9 – Too many users.
403.10 – Invalid configuration.
403.11 – Password change.
403.12 – Denied access to the mapping table.
403.13 – Client certificate revoked.
403.14 – Reject directory listing.
403.15 – Client access permission is exceeded.
403.16 – The client certificate is untrusted or invalid.
403.17 – Client certificate has expired or is not in effect.
403.18 – The requested URL cannot be executed in the current application pool. This error code is dedicated to IIS 6.0.
403.19 – CANNOT perform CGI for clients in this application pool. This error code is dedicated to IIS 6.0.
403.20 – Passport login failed. This error code is dedicated to IIS 6.0.
404 – Not found.
404.0 – (none) – No files or directories were found.
404.1 – The Web site cannot be accessed on the requested port.
404.2 – The Web services Extension locking policy blocks this request.
404.3-MIME mapping policy blocks this request.
405 – HTTP predicates used to access this page are not allowed (methods are not allowed)
406 – The client browser does not accept the MIME type of the requested page.
407 – Proxy authentication is required.
412 – Prerequisites failed.
413 – The requesting entity is too large.
414 – Request URI is too long.
415 – Unsupported media type.
416 – The requested scope cannot be satisfied.
417 – Execution failed.
423 – Locking error.
5XX – Server error
The server was unable to complete the request due to an error.
500 – Internal server error.
500.12 – The application is busy restarting on the Web server.
500.13 – The Web server is too busy.
500.15 – Direct requests to Global.asa are not allowed.
500.16 — The UNC authorization credentials are incorrect. This error code is dedicated to IIS 6.0.
500.18 – THE URL authorization store cannot be opened. This error code is dedicated to IIS 6.0.
500.100 – Internal ASP error.
501 – The header value specifies an unimplemented configuration.
502 – The Web server received an invalid response while using it as a gateway or proxy server.
502.1 – CGI application timeout.
502.2 – CGI application error. application.
503 – Service unavailable. This error code is dedicated to IIS 6.0.
504 – Gateway timeout.
The 505-HTTP version is not supported.
Reproduced in: https://blog.51cto.com/cold2076goddess/1432464
When ifconfig configures the network, “siocsifaddr: no such device” and “eth0: error while getting interface” appear flags:No such dev”
Eth0 :ERROR while getting interface flags:No such device. Screenshot below.

After a lot of searching on the Internet, someone suggested that maybe your network card name is not “eth0” but something else. So I entered a single line of code “ifconfig-a” to check all the network card parameters, only to find that my network card name is not “eth0”, but “eno16777736”. So the real statement to modify the nic parameters should be “ifconfig eno16777736 192.168.11.2”.

After that, I used the secureCRT remote login management tool and used “192.168.11.2” to login the virtual machine remotely!
You must be logged in to the server (unauthorized)
Problem description
K8S cluster has 3 masters with the same certificate file, one master is normal, and the other two masters have questions: enter kubectl get nodes kubectl get Po – all-minus namespaces is logged with an error You must be logged in to the server(unauthorized)
The solution
Cluster if installed using administrator:
export KUBECONFIG=/etc/kubernetes/admin.conf
If the cluster is installed with a regular user:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
div>
Error: could not find or load main class
The Internet said a lot of methods, only said I used
CMD runs Java Chinese garbled code
Set environment variable — system environment variable
Add entry: JAVA_TOOL_OPTIONS
value: -dfile.encoding = utf-8-duser. language=en
The main class could not be loaded
Method 1. Remove the package *
method 2. Suppose the class test is in the SRC directory. Once compiled, run in the SRC sibling directory
java src.test
Reproduced in: https://www.cnblogs.com/so-easy/p/11369745.html
error C2679: binary ‘<<' : no operator found which takes a right-hand operand of type 'std::string'
No header file added & LT; string> ,cout cannot directly output variables of the String class.
Docker run failed with the following error in logs, standard_ init_ linux.go:211 : exec user process caused “exec format error“
Standard_init_linux. go:211: exec User Process caused “exEC Format Error”
The paper
This problem is encountered in the secondary DockerUI project on the board, which adopts arm7L architecture. The image is based on the Centos Docker build of X86_64, and then the image is packaged into a tar file by Docker Save, and then the image is extracted from the tar file compressed by Docker Load. The image transfer itself is not a problem, and multiple operations have been performed prior to this.
displays the container exit status when docker runs, and docker logs, the container, will report the above error. The reason is that the arch architecture is different, which will affect the docker build image.
1. Pull the official mirror, still report the same error.
2 search this image in dockerhub, sure enough, found a clue, as shown in the red box in the figure below:

Problem location
1. Problems on baidu generally point to entrypoint in dockerfile. I did not encounter various shell
2 and coding problems, because my project is pure CSS +js+ HTML. Finding the root of the problem on Google is that ARCH is different.
Solution
now that the root cause of the problem has been found, it is easy to handle, just need to rebuild docker build on the current arch Linux.
While e sometimes it feels like solving a case, follow the clues to find the root of the problem and solve it. The process was painful, but the results were pretty good.
Error msb8036: Windows SDK version not found···
The article directories
Solution: Reset the target solution

when running a program, an error occurs:
Error MSB8036: Windows SDK version 8.1 could not be found. Install the required version of the Windows SDK, or change the SDK version in the project property page or by right-clicking on the solution and selecting “Reset the Solution target.”

Solution: Reset the target solution
<
- project/KBD> – & gt; reset target solution KBD>
select the appropriate SDK version and platform toolset (general default)
rebuild solution 
C ා connect mysql: fatal error encountered during command execution solution
Fatal error encountered during command execution
Make along while, discovery code is no problem, finally Baidu broad net friend
Solution:
Allow User Variables=True in the connection string
server=; port=3306; user=root; password=1111; database=shujukuming; CharSet=gb2312; Allow User Variables=True;”
As appears Error:Cause : peer not authenticated
Sometimes when importing projects, this error occurs! Causes the project to fail to build.
The solution is simple: change gradle’s version number! The diagram below:


Change gradle version 2.1.2 to 2.3.2 and just refactor