Use the disk2vhd tool to report an error. Cancel use Volume Shadow Copy because the Windows Volume Shadow service cannot be turned on. The resulting VHD should be mounted on the IDE’s virtual hard disk in VMware, otherwise the blue screen 0x0000007B.
Tag Archives: ProgrammerAH
Ask for help
# for help! (R language novice)
to carry out summary(lm(change~AQI,data=dat)) operation, the system will report an error, the content is as follows:
Error in quantile.default(resid) : factors are not allowed
Warning messages:
1:
using type = “numeric” with a factor response will be ignored
2: In Ops. Factor (y, z$residuals) : ‘-‘ not meaningful for factors
3: In Ops. Factor (r, 2) : ‘^ not meaningful for factors
, I hope you can help me!!
error: command ‘arm-linux-gnueabihf-gcc’ failed with exit status 1, Raspberry Pi installation paramiko
sudo apt-get install gcc
sudo apt-get install gcc libffi-dev libssl-dev python3-dev
pip3 install paramiko
div>
remote: error: GH007: Your push would publish a private email address.
Cannot run program “git.exe”: CreateProcess error=2 the correct solution
The operation steps are as follows:
Download Github For Windows client and install it.
after successful installation, connect to your account.
first check for error reporting

Setting–> VersionControl—> Git

Find the GitHub installation directory (mine is the default)

Point Gt.exe to the Android Studio reference

test

Next, test the project


Like this article friends, welcome to follow WeChat public “Java interview talent”, watch more exciting content

Install koa error Cannot find module’internal/fs’
Scenario: Node and NPM are installed locally, but the node version is lower than 8.0.0, so the node version management tool N is used to upgrade the version. After the upgrade, koA is installed and an error is reported
Cause: Changes to the node version on which NPM depends
Solution: 1. Remove NPM NPM Uninstall NPM-g 2. Reinstall Node, because NPM will be installed at the same time that Node is installed
Reproduced in: https://juejin.im/post/5c9c915a6fb9a070d90f753e
Method to solve the error during initialization when DST Dont Starve Together starts
I first saw this article and its derivative articles at https://zhidao.baidu.com/question/588974190311347845.html
I tried several ways mentioned in the article, but I couldn’t solve the problem.
Then it occurred to me that I had disabled 3D acceleration for Red Alert 2 since the last time it was running properly.
Why don’t you just turn on 3d acceleration?
You could really…
So continue to play, happy.
Raspberry Pi 3 installation and software configuration issues collection
After hosting ali, toutiao, and Meituan interviews this year, I’ve made an important discovery… > > >
Permanent update address:
https://my.oschina.net/bysu/blog/1583968
System related information
bysu@bysu:~ $ inxi
CPU~Quad core ARMv7 rev 4 (v7l) (-MCP-) speed~1200 MHz Kernel~4.9.41-v7+ armv7l Up~14:21 Mem~102.5/927.3MB HDD~NA(-) Procs~291 Client~Shell inxi~2.3.5
bysu@bysu:~ $ uname -a
Linux bysu 4.9.41-v7+ #1023 SMP Tue Aug 8 16:00:15 BST 2017 armv7l GNU/Linux
System article
Software installation configuration section
Samba related
Error executing restart service command.
bysu@bysu:~ $ sudo systemctl start samba
Failed to restart samba.service: Unit samba.service is masked.
For the solution, see here
bysu@bysu:~ $ sudo rm /lib/systemd/system/samba.service
bysu@bysu:~ $ sudo systemctl enable samba
samba.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable samba
update-rc.d: error: samba Default-Start contains no runlevels, aborting.
bysu@bysu:~ $ sudo systemctl start samba
bysu@bysu:~ $ sudo systemctl status samba
● samba.service - LSB: ensure Samba daemons are started (nmbd, smbd and samba)
Loaded: loaded (/etc/init.d/samba; generated; vendor preset: enabled)
Active: active (exited) since Sat 2017-12-02 15:28:45 UTC; 9s ago
Docs: man:systemd-sysv-generator(8)
Process: 2525 ExecStart=/etc/init.d/samba start (code=exited, status=0/SUCCESS)
Dec 02 15:28:45 bysu systemd[1]: Starting LSB: ensure Samba daemons are started (nmbd, smbd and samba)...
Dec 02 15:28:45 bysu samba[2525]: Starting nmbd (via systemctl): nmbd.service.
Dec 02 15:28:45 bysu samba[2525]: Starting smbd (via systemctl): smbd.service.
Dec 02 15:28:45 bysu systemd[1]: Started LSB: ensure Samba daemons are started (nmbd, smbd and samba).
SSH write failed broken pipe
Write failed: Broken pipe
It’s usually because the SSHD on the server sees that a connection has been closed at some point without a message, and then the client side breaks.
There are three solutions:
Add the following configuration in /etc/ssh/sshd_config of the server: ClientAliveInterval 60
2 if it is difficult to change the server, you can change the client setting: add config file in ~/.ssh/ folder, and add the following configuration: ServerAliveInterval 10, tell the SSH client to send a “keep-alive” packet to the other side every 10 seconds.
3 If you only want to use it temporarily for one operation, you can add an argument to the login command: sSH-O ServerAliveInterval=10 [email protected].
Original: http://blog.csdn.net/hongchangfirst/article/details/51308366
Author: hongchangfirst
Hongchangfirst homepage: http://blog.csdn.net/hongchangfirst
WebHost failed to process a request.Memory gates checking failed because the free memory (140656640 …
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/49648990
Exception: System.ServiceModel.ServiceActivationException: The service '/WCF/SynCacheService.svc' cannot be activated due to an exception during compilation. The exception message is: Memory gates checking failed because the free memory (140656640 bytes) is less than 5% of total memory. As a result, the service will not be available for incoming requests. To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.. ---> System.InsufficientMemoryException: Memory gates checking failed because the free memory (140656640 bytes) is less than 5% of total memory. As a result, the service will not be available for incoming requests. To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.
at System.ServiceModel.Activation.ServiceMemoryGates.Check(Int32 minFreeMemoryPercentage, Boolean throwOnLowMemory, UInt64& availableMemoryBytes)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CheckMemoryCloseIdleServices(EventTraceActivity eventTraceActivity)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
--- End of inner exception stack trace ---
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
Process Name: w3wp
Process ID: 7636
Today, an error occurred in the project, and the above information is prompted. This is a mistake made when using WCF. If you have the same error, please check the sign and take your seat. Memory entry check failed because free memory is less than 5%.
To solve this problem, add a node on the corresponding Web.config of WCF. The node structure is as follows:
<configuration>
<system.serviceModel>
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" minFreeMemoryPercentageToActivateService="0"/>
......
</system.serviceModel>
</configuration>
Under the system.Servicemodel node
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" minFreeMemoryPercentageToActivateService="0"/>
The route addition failed: Either the interface index is wrong or the gateway do es not lie on the s
VPN server network segment :192.168.1.0/24
Client internal network segment :192.168.2.0/24
VPN server IP 10.0.10.0
VPN client IP 10.0.10.1
Xp system connection VPN add route times error
The route addition failed: Either the interface index is wrong or the gateway do es not lie on the same network as the interface. Check the IP Address Table for the machine.
Add the command: Route Add 192.168.1.0 Mask 255.255.255.0 10.0.10.0
The client does not have this problem with Windows 7
Search the Internet for a long time to get the most meaningful words are :XP system is not supported and so on
Think xp is really out of date
Accidentally checking the routing table of the client system found that XP is different from Win7 (VPN link)
Xp: 192.168.1.0 255.255.255.0 10.0.1.1 10.0.1.1 1
Windows 7 is: 192.168.1.0 255.255.255.0 10.0.1.0 10.0.1.1 11
I don’t know why, but it will solve my temporary problem
Change the command to Route Add 192.168.1.1 Mask 255.255.255.0 10.0.10.0
Windows 7 was ok in my test though not perfect
Of course, a more rigorous word is to judge the system before choosing different commands
I hope I can help those in need
An I/O operation initiated by the Registry failed unrecoverably
The WIN2003 server reported an error with the following error message: An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system’s image of the Registry. Registry failure caused by an I/O operation. The registry, which contains the system image of the registry, will not be able to read, write, or refresh. In cases like this, it is generally necessary to restart the system with and restore the system configuration information with an emergency repair disk. However, there is no remote desktop to connect and restart (plus the console parameter is also not available). There is also no restart with serverView hardware monitoring software, so you can’t go to the IDC room of century Internet. The shutdown – I command suddenly occurred to me. Ping first, it looks normal, then add the REMOTE host’S IP using shutdown – I, and reboot successfully.