Generally, the VNC configuration of the/etc/Nova/nova.conf configuration file is improper
Open, replace with
2. Modify novncproxy_base_URL, try to use IP address instead of domain name
For server_proxyclient_Address if you use a domain name, you need to modify the resolution in the local host file
Add a line: IP addresses Domain name
After modification Systemctl restart openstack-nova-compute.service restart the service
Problem solving
Conclusion: it is caused by setting agent
1. Check the global settings
Enter git config -- Global - e to check whether there are proxy settings for [HTTP] and [HTTPS] in the global configuration, such as proxy= socks://localhost:1080, if any, delete it.
2. Check the config in the current. Git file
In the current working directory, cat ./.Git/config
As shown in the figure above, delete the agent.
Note that this prompt is not the problem, that is, the error is not invoking “make – J2 – L2”, it just indicates that you use dual threaded computing, just like the dual core of a computer. Similarly, “- J4 – L4” and “- J8 – L8” will appear. As shown in the figure above, the problem is that I missed a semicolon when writing C + + code;
An error is reported in one of the published layers. There is an alarm next to this error. Layer’s data source is not register
so it’s OK to register the database, but it seems that there are other situations, which will be encountered in the record in the future
Packaging succeeded，but publishing failed
Failed to execute.Parameters are not valid
Please consult the GP Results Window for enhanced error
description or contact your administrator for the server logs.
Failed to load response data：no data found for resource with given identifier
Failed to load the response data. No data was found for the ID
request stateless code, indicating that no resources were requested to the background
Solution: set the timeout of the front-end request to be longer
NFS startup error restart failed
Restart failed
Search for solutions
The reason is/etc/exports. A folder was previously set as a shared directory, and then the folder was deleted. Therefore, an error will occur when the NFS service is started.
The nonexistent folder needs to be deleted
Find out how to solve it
Use the VI editor to enter/etc/exports
find out whether the corresponding file paths exist in/etc/exports one by one
check and find that there is no exports folder, only the exports file
so use vi to enter the/etc/exports file, delete all
save and exit, Restart NFS successfully
reason:
Because the back-end does not write cross-domain-related information to the header, the front-end cannot load data.
analysis:
1. First, check whether there are cross-domain-related configurations in the project, and then find out whether there are configurations.
2. This should be added only when the controller is executed.
3. Because our project has built an interceptor to intercept the token parsing into user-related information, because if there is no token expiration, the interceptor will throw an exception. When returning, cross-domain-related things will not be added. So the front end cannot be loaded.
Solution:
Add response and related cross domain information to the interceptor
In addition, you need to know the execution sequence of interceptors and filters
* ** -> Filter -> Interceptor -> ControllerAdvice -> Aspect -> Controller
[oracle@hellow ~]$ lsnrctl start
LSNRCTL for Linux: Version 12.1.0.2.0 – Production on 04-Nov-2021 15:30:14
Copyright © 1991, 2014, Oracle. All rights reserved.
TNS-01106: Listener using listener name LISTENER has already been started
– The ps command did not find the listening process
[root@sh ~]# ps -ef | grep -i tns
root 36 2 0 Jan26 ?00:00:00 [netns]
root 14995 14824 0 15:30 pts/1 00:00:00 grep -i tns
– Check the listening status, error reported; TNS-01189
[oracle@sh ~]$ lsnrctl status
LSNRCTL for Linux: Version 12.1.0.2.0 – Production on 4-NOV-2021 15:57:39
Copyright © 1991, 2014, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hello)(PORT=1521)))
TNS-01189: The listener could not authenticate the user
– There are basically 2 reasons for this problem,
1, the ip and hostname in /etc/hosts file are not the same
2, the listener.ora listener host is not the current host.
After checking, the listener.ora listener host is incorrectly filled in
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hellow)(PORT = 1521))
)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
)
)
After changing to the current host name, restart the listener to resume normal.
Solutioin:
Add android.injected.testOnly=false in gradle.properties files
Solution: it can be seen from the above that ROS is compiled through python2.7. Check your own Python version and modify it to the corresponding version to successfully run rqt and rqt_ graph.
(1) Problem Description
This week at work, the company’s project using mybatis and pagehelper for paging queries, start the project, query data actually reported an error, the error reported as follows.
Exception in thread “main” org.apache.ibatis.plugin.PluginException: Could not find method on interface org.apache.ibatis.executor.Executor named query. Cause: java.lang.NoSuchMethodException: org.apache.ibatis.executor.Executor.query(org.apache.ibatis.mapping.MappedStatement, java.lang.Object, org.apache.ibatis.session.RowBounds, org.apache.ibatis.session.ResultHandler, org.apache.ibatis.cache.CacheKey, org.apache.ibatis.mapping.BoundSql)
Exception in thread "main" org.apache.ibatis.plugin.PluginException: Could not find method on interface org.apache.ibatis.executor.Executor named query. Cause: java.lang.NoSuchMethodException: org.apache.ibatis.executor.Executor.query(org.apache.ibatis.mapping.MappedStatement, java.lang.Object, org.apache.ibatis.session.RowBounds, org.apache.ibatis.session.ResultHandler, org.apache.ibatis.cache.CacheKey, org.apache.ibatis.mapping.BoundSql)
at org.apache.ibatis.plugin.Plugin.getSignatureMap(Plugin.java:63)
at org.apache.ibatis.plugin.Plugin.wrap(Plugin.java:26)
at com.github.pagehelper.PageInterceptor.plugin(PageInterceptor.java:151)
at org.apache.ibatis.plugin.InterceptorChain.pluginAll(InterceptorChain.java:12)
at org.apache.ibatis.session.Configuration.newExecutor(Configuration.java:289)
at org.apache.ibatis.session.defaults.DefaultSqlSessionFactory.openSessionFromDataSource(DefaultSqlSessionFactory.java:78)
at org.apache.ibatis.session.defaults.DefaultSqlSessionFactory.openSession(DefaultSqlSessionFactory.java:32)
Caused by: java.lang.NoSuchMethodException: org.apache.ibatis.executor.Executor.query(org.apache.ibatis.mapping.MappedStatement, java.lang.Object, org.apache.ibatis.session.RowBounds, org.apache.ibatis.session.ResultHandler, org.apache.ibatis.cache.CacheKey, org.apache.ibatis.mapping.BoundSql)
at java.lang.Class.getMethod(Class.java:1786)
at org.apache.ibatis.plugin.Plugin.getSignatureMap(Plugin.java:60)After thinking for a long time, I didn’t understand what went wrong. Then I inadvertently checked the underlying source code of PageHelper and found that there were errors, as shown below:
Then enter the query () method and jump to the source code of the mybatis framework. It is found that the method in the mybatis framework has only four parameters, while the query () method with six parameters is used in the PageHelper, resulting in an error.
The reason for the problem is that there must be a mismatch between the versions of the mybatis framework and the page helper. I checked that the mybatis version used in the company’s project is 3.0.4 and the PageHelper version is 5.0.0. The solution is simple. Replace the corresponding framework version.
(2) Solution
There are two ways to solve this problem:
Change the version corresponding to mybatis and PageHelper (this is the simplest way). Instead of using the PageHelper plug-in, customize the mybatis paging plug-in
1. Method 1: replace mybatis version
I checked the page helper dependency repository and found that the page helper supports mybatis version 3.2.6 at least.
2. Custom mybatis paging plug-in
The version of mybatis 3.0.4 used by our company. At that time, the technical manager specially told me that if it is a problem with the dependent version, the dependency of PageHelper can be replaced at will, but the dependent version of mybatis cannot be replaced. Ah, I think it’s not just a custom mybatis paging plug-in… I can’t help it. I can only view some articles about custom paging plug-ins, and then write one myself. If necessary, you can check the article [mybatis implementation of custom paging plug-in].
JD-GUI
Check ide of jar
URL
http://java-decompiler.github.io/
Found JD-GUI error after upgrading Big Sur
ERROR launching ‘JD-GUI’
No suitable Java version found on your system!
This program requires Java 1.8+
Make sure you install the required Java version.
Need to replace files
[The source site may have anti-theft chain mechanism, we suggest to save the image and upload it directly (img-tyA4R80g-1635526847601)(evernotecid://4E256570-D902-4601-B913-1C7B0CBD5BA0/appyinxiangcom/ 23501392/ENResource/p275)]
Content
Replace the content