systemctl enable lvm2-lvmetad.service
systemctl enable lvm2-lvmetad.socket
systemctl start lvm2-lvmetad.service
systemctl start lvm2-lvmetad.socket

installation requirements:

> # yum install curl-devel expat-devel gettext-devel openssl-devel zlib-devel asciidoc

> # yum Install GCC Perl-extutils-Makemaker

uninstall Centos built-in git1.7.1:

check the version with git – version, Cento6.5 should come with git version 1.7.1

> # yum remove git

download git2.2.1 and add git to your environment variable

> Wget # https://github.com/git/git/archive/v2.2.1.tar.gz

> # tar ZXVF v2.2.1. Tar. Gz

> # CD git – 2.2.1

> # make configure

> # ./configure –prefix=/usr/local/git –with-iconv=/usr/local/libiconv

> # make all doc

> # make install install-doc install-html

> # echo “export PATH=$PATH:/usr/local/git/bin” > > /etc/bashrc

> # source /etc/bashrc

installation problem:

/bin/sh: line 1: xmlto: command not found

make[1]: *** [git-add.1] Error 127

make[1]: Leaving directory `/root/src/git/Documentation’

make: *** [doc] Error 2

xmlto 4.2 installation

yum install xmlto

view version no

> # git –version

> The git version 2.2.1

may be a version mismatch, the solution is simple, with parameter vers=3

mount -t nfs -o vers=3,nolock,rw remote_ip:remote_dir local_dir

welcome to follow the official account

1. Install kernel-devel, and update the kernel and kernel-devel to the same version

# yum install -y kernel-devel gcc //安装kernel-devel和gcc编译工具链
# yum -y upgrade kernel kernel-devel //更新kernel和kernel-devel到最新版本
# reboot //重启，重启时，选择最新版本的内核启动

2. Start with the new version of the kernel and delete the old version

//启动之后
# uname -r //查看当前启动的内核版本

# rpm -qa | grep kernel-[0-9] //查看全部的内核

# yum remove 旧版本内核 //删除旧版本内核

after using MAC brew to install PHP mongodb extension, initialize new mongodb \Driver\Manager() to directly report an error:

dyld: lazy symbol binding failed: Symbol not found: _clock_gettime

solution: force brew to install PHP mongodb

from source code

brew install –build-from-source php71-mongodb

1. Download aptana studio 3.6.1 installation package

2. Installation Failed to correctly acquire intaller_nodejs_windows.msi file: CRC error?The main thing is that the current version of Aptana requires a Node version between 0.8.X and 0.11.x. I recommend a 0.10.x version of Node. https://nodejs.org/download/release/v0.10.13/

install this.

3. After successful installation, what is the reason if Failed to load the JNI Shared library?Mainly on your computer to install the JDK 64 – bit, aptana need is 32-bit JDK, to replace the JDK to reconfigure the path, too much trouble, so, we can install a 32-bit JDK, http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

install this.

4. Find the aptanastudio3.ini configuration file under the installation path of aptana, and add -vm C:/Program Files (x86)/Java/jre1.8.0_171/bin/javaw.exe in front of -vmargs. This path is javaw

in the bin under the installation path of the 32-bit JDK

aptanastudio3.ini configuration file contents are as follows:

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20140116-2212
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-name
Aptana Studio 3
-vm
C:/Program Files (x86)/Java/jre1.8.0_171/bin/javaw.exe
-vmargs
-Xms128m
-Xmx512m
-Xverify:none
-Declipse.p2.unsignedPolicy=allow
-Declipse.log.size.max=10000
-Declipse.log.backup.max=5
-Djava.awt.headless=true

5. And then how do aptana studio3 sinize it?

(1). Enter aptana studio3, click install new software option

in help

(2). Open http://www.eclipse.org/babel/downloads.php, found that two parameter

(3). Fill the two parameters into the box that pops up by clicking the add button, as shown in figure

(4). Then wait a moment and select Chinese(Simplified)

(5). Then all the way to next, restart the software to see the Chinese version of Aptana.

Connected to server
[2019-06-26 12:03:46,709] Artifact core:war exploded: Artifact is being deployed, please wait...
26-Jun-2019 12:03:46.837 严重 [RMI TCP Connection(3)-127.0.0.1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start: 
 org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:162)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:755)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:731)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
	at org.apache.catalina.startup.HostConfig.manageApp(HostConfig.java:1730)
	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.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:485)
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:434)
	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.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
	at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
	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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
	at sun.rmi.transport.Transport$1.run(Transport.java:200)
	at sun.rmi.transport.Transport$1.run(Transport.java:197)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@1efa7e50]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:162)
	at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:5016)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5149)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
	... 42 more
Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@79af5cc7]
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
	at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:722)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
	... 45 more
Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: error in opening zip file
	at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:142)
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
	... 48 more
Caused by: java.util.zip.ZipException: error in opening zip file
	at java.util.zip.ZipFile.open(Native Method)
	at java.util.zip.ZipFile.<init>(ZipFile.java:225)
	at java.util.zip.ZipFile.<init>(ZipFile.java:155)
	at java.util.jar.JarFile.<init>(JarFile.java:166)
	at java.util.jar.JarFile.<init>(JarFile.java:130)
	at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:170)
	at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:155)
	at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:139)
	... 49 more

26-Jun-2019 12:03:46.842 严重 [RMI TCP Connection(3)-127.0.0.1] org.apache.tomcat.util.modeler.BaseModelMBean.invoke Exception invoking method manageApp
 java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:731)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
	at org.apache.catalina.startup.HostConfig.manageApp(HostConfig.java:1730)
	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.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:485)
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:434)
	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.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
	at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
	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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
	at sun.rmi.transport.Transport$1.run(Transport.java:200)
	at sun.rmi.transport.Transport$1.run(Transport.java:197)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
[2019-06-26 12:03:46,850] Artifact core:war exploded: Error during artifact deployment. See server log for details.
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

26-Jun-2019 12:03:46.843 严重 [RMI TCP Connection(3)-127.0.0.1] org.apache.tomcat.util.modeler.BaseModelMBean.invoke Exception invoking method createStandardContext
 javax.management.RuntimeOperationsException: Exception invoking method manageApp
	at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:308)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:485)
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:434)
	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.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
	at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
	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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
	at sun.rmi.transport.Transport$1.run(Transport.java:200)
	at sun.rmi.transport.Transport$1.run(Transport.java:197)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:731)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
	at org.apache.catalina.startup.HostConfig.manageApp(HostConfig.java:1730)
	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.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
	... 33 more

26-Jun-2019 12:03:56.567 信息 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory D:\work\apache-tomcat-8.0.53（小蓝）\webapps\manager
26-Jun-2019 12:03:56.713 警告 [localhost-startStop-1] org.apache.tomcat.dbcp.dbcp2.BasicDataSourceFactory.getObjectInstance Name = hap_dev Property maxActive is not used in DBCP2, use maxTotal instead. maxTotal default value is 8. You have set value of "100" for "maxActive" property, which is being ignored.
26-Jun-2019 12:03:56.713 警告 [localhost-startStop-1] org.apache.tomcat.dbcp.dbcp2.BasicDataSourceFactory.getObjectInstance Name = hap_dev Property removeAbandoned is not used in DBCP2, use one or both of removeAbandonedOnBorrow or removeAbandonedOnMaintenance instead. Both have default value set to false. You have set value of "true" for "removeAbandoned" property, which is being ignored.
26-Jun-2019 12:03:56.713 警告 [localhost-startStop-1] org.apache.tomcat.dbcp.dbcp2.BasicDataSourceFactory.getObjectInstance Name = hap_dev Property maxWait is not used in DBCP2 , use maxWaitMillis instead. maxWaitMillis default value is -1. You have set value of "10000" for "maxWait" property, which is being ignored.
26-Jun-2019 12:03:56.738 信息 [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
26-Jun-2019 12:03:56.782 信息 [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory D:\work\apache-tomcat-8.0.53（小蓝）\webapps\manager has finished in 214 ms

jar package conflict, directly remove the local maven repository, re-download it, violence to resolve

VM9328 hbox.js:52 Uncaught TypeError: Failed to execute ‘removeChild’ on ‘Node’: Parameter 1 is not of type ‘Node’.
at object.remove (VM9328 hbox-js :52)
at hbox.fn. init._executive (VM9328 hbox.js:529)
at hbox.fn. init._closebox (VM9328 hbox.js:545)
At object.close (VM9328 hbox.js:570)
at VM9347 undefined:45

The

pop-up failed to close properly, because the external js is referenced once more, and the parent and child nodes are referenced once. Removing the external reference to the child node solves the problem.

nodejs I will not introduce, IT is very hot technology recently, the function is very powerful. I also did some research. Error when installing a nodejs software project:

npm ERR! Error: CERT_UNTRUSTED

after careful screening and Google, turns out to be the SSL problem:

solution:

npm config set strict-ssl false

or

npm config set registry=”http://registry.npmjs.org/”

to continue error error-code-elifecycle, execute the following command:
NPM cache clear –force
NPM install -g NPM (upgrade)

solution: command prompt (run as an administrator) [run as a super administrator for Windows, Linux requires sudo]

note: please try to run this command again as root/Administrator.

sudo
sudo NPM install –save-dev grunt
but this may not work, you need to do this:

sudo NPM install –unsafe-perm=true –save-dev grunt
perhaps you will still encounter an error, try

sudo npm install –unsafe-perm=true –allow-root –save-dev grunt

background: after installing nodejs on Linux, I have been using the NPM install command to install project dependencies that have been denied permission undefined. I am root.

solution, need this command.

npm install –unsafe-perm=true –allow-root

Replace an NPM installation source as follows:

1, through the config command NPM config set registry https://registry.npm.taobao.org NPM info the underscore (if there could be strings configured properly this command response)

2, command line specifies the NPM – registry https://registry.npm.taobao.org info the underscore and then install it

and then rerun NPM install -g **** OK ~~~

a good habit in the project life cycle when installing a new dependent module NPM install XXX – save
NPM added – save dependent module version information will be written to the package.
in the json every time such in server deployment directly cp package files NPM install can be in accordance with the package. The information in the json (reduction) deployment as dependent on good operation environment

of course, the most important thing is that node version compatibility is the first

according to my understanding, this kind of node, is not only to indicate the dependent package version, but also indicate the other version dependencies, such as running environment version number and build tools version, operating system, database version, because the node changing fast (also different update quickly, ECS grammar)

node version is too low?

install n module: sudo NPM install -g n (node has a module called n, which is used to manage versions of node.js)

upgrade node.js to the latest stable version in the terminal input: n stable

you can check the node version installed successfully: node-v

shares several common NPM commands

npm-v # displays the version and checks to see if NPM is installed correctly.

NPM install express # express module

NPM install -g express # global install express module

NPM list # lists installed modules

NPM show express # display module details

NPM update # updates all modules of the project in the current directory

NPM update express # updates the specified module of the project in the current directory

NPM update-g express # upgrade globally installed express module

NPM uninstall express # remove the specified module