An error is reported as shown in the figure
First error
At this point we type: cd /etc/apt
Then we type: sudo gedit sources.list
At this point we comment out the beginning of
deb cdrom.......
At this point we then do:sudo apt-get update
Second error
Open “software and update”, find the error source in other software and delete it. Finally, in sudo apt get update
This error comes from sass loader. Semver does not match because node sass @latest is v5.0.0 and sass loader expects ^ 4.0.0
there is an unresolved issue in their repository that needs to be fixed
Solution:
uninstall node sass
npm uninstall node-sass // If an error is reported during unloading, it is recommended to directly change node sass to 4.14.1 in package.json and delete node from the folder_ Delete the module folder and NPM install
CentOS uses Yum install to install the software. An error is reported
failure: repodata/repomd.xml from google-chrome: [Errno 256] No more mirrors to try.
https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate has expired."
Baidu later found that the system time was wrong. Just modify the operating system time
date #Check the time, here to check the system time of the operating system
date -s "2021-11-29 11:05:00" #Set the time, set it to the correct time here
Then you can install the yum software
org.springframework.context.ApplicationContextException: Failed to start bean 'webServerStartStop'; nested exception is org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat server at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:181) ~[spring-context-5.3.13.jar!/:5.3.13] at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:54) ~[spring-context-5.3.13.jar!/:5.3.13] at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:356) ~[spring-context-5.3.13.jar!/:5.3.13] at java.lang.Iterable.forEach(Iterable.java:75) ~[na:1.8.0_171] at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:155) ~[spring-context-5.3.13.jar!/:5.3.13] at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:123) ~[spring-context-5.3.13.jar!/:5.3.13] at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:935) ~[spring-context-5.3.13.jar!/:5.3.13] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586) ~[spring-context-5.3.13.jar!/:5.3.13] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145) ~[spring-boot-2.5.7.jar!/:2.5.7] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:765) [spring-boot-2.5.7.jar!/:2.5.7] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:445) [spring-boot-2.5.7.jar!/:2.5.7] at org.springframework.boot.SpringApplication.run(SpringApplication.java:338) [spring-boot-2.5.7.jar!/:2.5.7] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1354) [spring-boot-2.5.7.jar!/:2.5.7] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1343) [spring-boot-2.5.7.jar!/:2.5.7] at com.pn.boot.MybatisLogApplication.main(MybatisLogApplication.java:12) [classes!/:0.0.1-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_171] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_171] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_171] at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_171] at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49) [3-boot-mybatis-log-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT] at org.springframework.boot.loader.Launcher.launch(Launcher.java:108) [3-boot-mybatis-log-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT] at org.springframework.boot.loader.Launcher.launch(Launcher.java:58) [3-boot-mybatis-log-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT] at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88) [3-boot-mybatis-log-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT] Caused by: org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat server at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.start(TomcatWebServer.java:229) ~[spring-boot-2.5.7.jar!/:2.5.7] at org.springframework.boot.web.servlet.context.WebServerStartStopLifecycle.start(WebServerStartStopLifecycle.java:43) ~[spring-boot-2.5.7.jar!/:2.5.7] at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:178) ~[spring-context-5.3.13.jar!/:5.3.13] ... 22 common frames omitted Caused by: java.lang.IllegalArgumentException: standardService.connector.startFailed at org.apache.catalina.core.StandardService.addConnector(StandardService.java:238) ~[tomcat-embed-core-9.0.55.jar!/:na] at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.addPreviouslyRemovedConnectors(TomcatWebServer.java:282) ~[spring-boot-2.5.7.jar!/:2.5.7] at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.start(TomcatWebServer.java:213) ~[spring-boot-2.5.7.jar!/:2.5.7] ... 24 common frames omitted Caused by: org.apache.catalina.LifecycleException: Protocol handler start failed at org.apache.catalina.connector.Connector.startInternal(Connector.java:1075) ~[tomcat-embed-core-9.0.55.jar!/:na] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ~[tomcat-embed-core-9.0.55.jar!/:na] at org.apache.catalina.core.StandardService.addConnector(StandardService.java:234) ~[tomcat-embed-core-9.0.55.jar!/:na] ... 26 common frames omitted Caused by: java.net.BindException: 地址已在使用 at sun.nio.ch.Net.bind0(Native Method) ~[na:1.8.0_171] at sun.nio.ch.Net.bind(Net.java:433) ~[na:1.8.0_171] at sun.nio.ch.Net.bind(Net.java:425) ~[na:1.8.0_171] at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[na:1.8.0_171] at org.apache.tomcat.util.net.NioEndpoint.initServerSocket(NioEndpoint.java:271) ~[tomcat-embed-core-9.0.55.jar!/:na] at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:226) ~[tomcat-embed-core-9.0.55.jar!/:na] at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1213) ~[tomcat-embed-core-9.0.55.jar!/:na] at org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:1299) ~[tomcat-embed-core-9.0.55.jar!/:na] at org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:614) ~[tomcat-embed-core-9.0.55.jar!/:na] at org.apache.catalina.connector.Connector.startInternal(Connector.java:1072) ~[tomcat-embed-core-9.0.55.jar!/:na] ... 28 common frames omitted
The reason for Linux tomcat port occupancy is to close all the tomcats that are enabled in Linux.
Troubleshooting other directory phenomena
phenomenon
[root@Zeratul:~]# mkdir /mnt/sd0
[root@Zeratul:~]# mount 192.168.28.195:/nfsroot /mnt/sd0 -t nfs -o nolock;cd /mnt/sd0
[root@Zeratul:sd0]# ls
[root@Zeratul:sd0]#
After mounting NFS, there is nothing.
Or removing -t NFS will directly report an error.
[root@Zeratul:sd0]#
[root@Zeratul:sd0]# mount 192.168.28.195:/nfsroot /mnt/sd0 -o nolock;cd /mnt/sd0
mount: mounting 192.168.28.195:/nfsroot on /mnt/sd0 failed: No such device
[root@Zeratul:sd0]#
Check
1. Ping target machine –> OK
2. View the NFS module of the board end system
[root@Zeratul:sd0]# modprobe nfs
modprobe: applet not found
[root@Zeratul:sd0]#
You can see that the NFS module is not loaded in the kernel.
Solution:
In the Linux source code directory, make menuconfig make the following settings
File systems --->
[*] Network File Systems --->
<*> NFS client support
[*] NFS client support for NFS version 3
[*] NFS client support for the NFSv3 ACL protocol extension
[*] NFS client support for NFS version 4 (EXPERIMENTAL)
[*] NFS client support for NFSv4.1 (DEVELOPER ONLY)
[*] Root file system on NFS
[*] Networking support --->
Networking options --->
[*] IP: kernel level autoconfiguration
After configuration, make uimage compile uimage
Re burn kernel
other
Sometimes when you enter make menuconfig in the terminal, you will be prompted
$ make menuconfig
HOSTCC scripts/kconfig/mconf.o
<command-line>:0:12: fatal error: curses.h: No such file or directory
compilation terminated.
scripts/Makefile.host:108: recipe for target 'scripts/kconfig/mconf.o' failed
make[1]: *** [scripts/kconfig/mconf.o] Error 1
Makefile:542: recipe for target 'menuconfig' failed
make: *** [menuconfig] Error 2
Solution:
sudo apt-get install libncurses5-dev
Failed to Set Network:
2021-11-29 11:37:47.767 30318 ERROR nova.compute.manager [instance: a9cf9419-c14d-4de0-8a66-1ed30431db3b] ConnectFailure: Unable to establish connection to http://127.0.0.1:9696/v2.0/ports/f7eaf0bb-fb46-4a18-ab13-5dca89e7ec51.json: HTTPConnectionPool(host='127.0.0.1', port=9696): Max retries exceeded with url: /v2.0/ports/f7eaf0bb-fb46-4a18-ab13-5dca89e7ec51.json (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f22087db1d0>: Failed to establish a new connection: [Errno 111] ECONNREFUSED',))
Manually curl can be found should be looking for the network node when looking for the wrong node
Check the configuration file, find the place where the IP is configured, change the IP and restart the nova-compute service
Restart the virtual machine again and you can see that it is already reporting a different error
Solution
sudo cp /usr/lib/x86_64-linux-gnu/sssd/conf/sssd.conf /etc/sssd/.
sudo chmod 600 /etc/sssd/sssd.conf
1. The following error occurred in Git packaging:
[ERROR] Failed to perform fetch
Failed to perform fetch
org.eclipse.jgit.api.errors.TransportException: http://gitlab.cmvideo.cn/sales_ability/sales-center/agency.git: Authentication is required but no CredentialsProvider has been registered
at org.eclipse.jgit.api.FetchCommand.call (FetchCommand.java:254)
at pl.project13.maven.git.JGitProvider.fetch (JGitProvider.java:350)
at pl.project13.maven.git.JGitProvider.getAheadBehind (JGitProvider.java:338)
at pl.project13.maven.git.GitDataProvider.lambda$loadGitData$17 (GitDataProvider.java:168)
at pl.project13.maven.git.GitDataProvider.lambda$memoize$23 (GitDataProvider.java:266)
at pl.project13.maven.git.GitDataProvider.lambda$loadGitData$18 (GitDataProvider.java:169)
at pl.project13.maven.git.GitDataProvider.maybePut (GitDataProvider.java:249)
at pl.project13.maven.git.GitDataProvider.loadGitData (GitDataProvider.java:169)
at pl.project13.maven.git.GitCommitIdMojo.loadGitDataWithJGit (GitCommitIdMojo.java:587)
at pl.project13.maven.git.GitCommitIdMojo.loadGitData (GitCommitIdMojo.java:548)
at pl.project13.maven.git.GitCommitIdMojo.execute (GitCommitIdMojo.java:443)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
at org.codehaus.classworlds.Launcher.main (Launcher.java:47)
2. Solution:
Perhaps you can find a solution by: https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/421
In 3.0.0, we got two new attributes (GIT. Local. Branch. Ahead/GIT. Local. Branch. Behind), which are almost correct only when git pull before is used. This git pull may cause such transmission exceptions (and require the Internet).
Using 3.0.1 will have clearer offline options. The real solution is to let the plug-in work in offline mode unless specified. This plug-in generates a warning when the user operates in offline mode and uses the above options.
<build>
<plugins>
<plugin>
<groupId>pl.project13.maven</groupId>
<artifactId>git-commit-id-plugin</artifactId>
<configuration>
<offline>true</offline>
</configuration>
</plugin>
</plugins>
</build>
or
<configuration>
<excludeProperties>
<excludeProperty>^git.local.branch.*$</excludeProperty>
</excludeProperties>
</configuration>
error: Your local changes to the following files would be overwritten by checkout:
view/index/article/show.tpl
Please commit your changes or stash them before you switch branches.
Aborting
Cause of occurrence
You have modified the branch content, and the other branch has the same file
Solution:
Git checkout – f plus an F to force switching
Note: this method will result in the loss of your current modified branch content. If you switch back again, you will find that your changes have disappeared
1.Problem: When executing the command: yum makecache fast, an error is reported: yum makecache: error: argument timer: invalid choice: ‘fast’ (choose from ‘timer’) as follows
2. the cause and solution: CentOS 8 does not have fast this command, remove it!