How to Solve Error: could not read ok from ADB Server.failed to start daemon error: cannot connect to daemon

Problem Description:
Execute the command adb connect 127.0.0.1:62001, the error is reported as follows:

* daemon not running; starting now at tcp:5037
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon

Reason analysis:
Use the command to check whether the port is occupied or not netstat -ano | findstr “5037”

Check that port 5037 is occupied

Solution:
Execute the command kill process to release port 5037:

taskkill -f -pid 15276

Re-execute the adb connect 127.0.0.1:62001 command, the connection is successful

Two solutions to Cannot load module file xxx.iml

I recently got the code of a Pycharm project from my classmate, and then opened it on my computer and reported an error: Cannot load module file xxx.iml: File xxx.iml doed not exist. Would you like to remove module’xxxx’ from the project? At this time, the directory structure of the entire project is incomplete, and some files cannot be displayed. The reason for the correction may be that the project name was changed by the classmate when he gave me the project, or the project he gave me was not at the same level as the project directory he used (for example, what he copied to me was under a large project code Subprojects), causing problems.

There are two final solutions:

One way is to click File in the upper left corner of the Pycharm software, then click Invalidate Caches / Restart…, and then click Invalidate and Restart after the pop-up dialog box to wait for the project to reload, the problem is solved.

Another method is to delete the .idea folder in the project directory when the project is closed, and then reopen the problem with Pycharm to solve the problem. In addition, some friends may use Pycharm under the Linux platform. The .idea folder is hidden and cannot be seen directly. Then you can use the la command to view the files under the project, and then execute the command rm -r .idea.

QT Creator Error while building deploying project

Error while building deploying project
is reported by QT creator

When QT creator compiles QT project, an error is reported: error while building deploying project.

The following tips may also appear

qt creator needs a tool chain set up to build. configure a tool chain in projects mode

 

This situation occurs when I open the past project, but the new project does not have this error.

The solution is as follows:

1. When the error reporting project is open, click the projects column on the left side of QT creator

Reload the XXX build desktop QT of the project in the build directory of the general column_ xxx_ Qt_ xxx_ Debug。 (by default, this part is gray and not enabled. Click Import exiting build below to enable it.)

 

After this operation, you can compile normally!

 

 

Ruby Install Error running ‘requirements_osx_brew_update_system ruby-2.3.1

Operating system: macOS 10.12.1

Install Ruby 2.3.1 error

The specific error message is as follows.

chaorenbuhuifeideMacBook-Air:~ chaorenbuhuifei$ rvm install 2.3.1

Searching for binary rubies, this might take some time.

Found remote file https://rubies.travis-ci.org/osx/10.12/x86_64/ruby-2.3.1.tar.bz2

Checking requirements for osx.

Installing requirements for osx.

Updating system…….

Error running ‘requirements_osx_brew_update_system ruby-2.3.1′,

showing last 15 lines of /Users/chaorenbuhuifei/.rvm/log/1481424365_ruby-2.3.1/update_system.log

https://github.com/Homebrew/homebrew/wiki/Common-Issues

and make sure `brew update` works before continuing.’

++ rvm_pretty_print stderr

++ case “${rvm_pretty_print_flag:=auto}” in

++ case “${TERM:-dumb}” in

++ case “$1” in

++ [[ -t 2 ]]

++ return 1

++ printf %b ‘Failed to update Homebrew, follow instructions here:

https://github.com/Homebrew/homebrew/wiki/Common-Issues

and make sure `brew update` works before continuing.\n’

Failed to update Homebrew, follow instructions here:

https://github.com/Homebrew/homebrew/wiki/Common-Issues

and make sure `brew update` works before continuing.

++ return 1

Requirements installation failed with status: 1.

Error running ‘requirements_osx_brew_update_system ruby-2.3.1’

 

How to Solve:

Step 1:

$ brew install autoconf automake libtool pkg-config apple-gcc42 libyaml readline libxml2 libxslt libksba openssl sqlite

This method will report error

Error: No available formula with the name “apple-gcc42”

==> Searching for similarly named formulae…

Error: No similarly named formulae found.

==> Searching taps…

This formula was found in a tap:

homebrew/dupes/apple-gcc42

To install it, run:

brew install homebrew/dupes/apple-gcc42

 

Step 2:

$brew install homebrew/dupes/apple-gcc42

 

then re-install

$rvm install 2.3.1

 

 

DVWA Uncaught Error: Call to undefined function mysql_connect() in /Applications/XAMPP/xampp

DVWA connection error after installation

Fatal error: Uncaught Error: Call to undefined function mysql_ connect() in /Applications/XAMPP/xamppfiles/htdocs/dvwa/dvwa/includes/ dvwaPage.inc.php:461 Stack trace: #0 /Applications/XAMPP/xamppfiles/htdocs/dvwa/ login.php (8): dvwaDatabaseConnect() #1 {main} thrown in /Applications/XAMPP/xamppfiles/htdocs/dvwa/dvwa/includes/ dvwaPage.inc.php on line 461

The reason is: Line 461 here is mysql_ Connect() is no longer used, but mysqli instead_ Just connect (), and add an I
to MySQL

After modification,
was successfully connected

If there is a similar error, open the corresponding file and change Mysql to mysqli

An error occurred: Sorry,Faithfully yours, nginx Error

Many reasons are analyzed as follows:
1. Before the system using the network cable internal test no problem, at this time the error reported using the cell phone hotspot, the network IP can not be obtained.
2. The request path of the page does not point to the specified background service address: http://localhost : port number

3. Due to the caching mechanism of nginx, restart nginx and clean the browser’s cache:
stop command: nginx.exe -s stop;
Start command: start nginx;
4. The most serious problem is (key):
the previous nginx was not closed, but it was restarted, or this is: at that time, the CMD window was directly closed, thinking that it had been completely closed. In fact, the process is not closed at all.
As shown in the following figure:

if there are multiple processes, the front-end will visit the back-end and there will be multiple turns. If an error is reported, the process must be killed and nginx will be OK.

Uncaught SyntaxError: Cannot use import statement outside a module

Uncaught syntax error: cannot use import statement outside a module & lt; analysis and solution

Error message:

Error analysis:

In HTML web page, browser loads JavaScript script through script tag. Since the default language of browser scripts is JavaScript, type = “application/JavaScript” can be omitted. We learned from the error report that the import statement cannot be used outside the module, because the loading of the module implements ES6 syntax. Therefore, when the browser loads the HTML file, it is necessary to add the attribute of type = “module” to the script tag.

terms of settlement:

How to Solve Error occurred during initialization of boot layer

problem

When using jdk9 or above, eclipse will report an error when running the program, indicating: error occurred during initialization of boot layer, that is, an error occurred during initialization of boot layer
this is because we cannot execute a single class

solve

Delete module directly- info.java This document

VUE Error: Cannot find module ‘webpack/bin/config-yargs’

For a Vue project downloaded from the Internet, when the terminal executes NPM run dev, an error is reported, as shown in the figure below:

As can be seen from the above error report, webpack cli needs to be installed

Terminal input: NPM install webpack cli

Then execute: NPM run dev OK! It’s ready to run!

Zeal Open html,css, javascript Error: Content rendering error

Problem
Recently, after updating html,css,javascript, the following Content rendering error occurs

Solution
Delete the corresponding files in the following resource folder
JavaScript.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.e49be9481ede.jsCSS.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.e49be9481ede.jsHTML.docset\Contents\Resources\Documents\developer.mozilla.org\static\build\js\react-main.e49be9481ede.js
js file named similarly to react-main.<hashcode>.js
Take the css docs fix as an example
Edit --> Preferences

Delete the files in the corresponding folder

ok