Tag Archives: operations

451 4.7.0 temporary server error. Please try again later. Prx5

4.7.0 Temporary Server Error. Please try again later. PRX5 solves the instance
It’s sunny and beautiful this morning! Suddenly, I received a call from a customer, saying that all outlook POP3 of their Company’s Exchange 2013 could not be used normally. The user and password verification box popped up, and it was of no use to enter the password repeatedly or confirm directly.
After communication, I was informed that there was a similar fault before, that was when the service of POP stopped and started, and no modification was made recently. After learning the situation, I logged in to the server remotely and checked that the Exchange service was started normally without any problems.
So I quickly configured a POP mode on my computer, and I got an error when Verifying the user name and password. It didn’t matter if I entered the password repeatedly or confirmed it directly, as described by the customer, as shown in the figure below

What do you do next?Restart the server?This is the next best thing. Maybe a restart can solve your problem temporarily, but the reason is not found, and the problem recurs later. How to deal with it?
451 4.7.0 Temporary Server Error. Please try again later. PRX5
The Telnet test format is as follows:
 
telnet mail.xxx.com 25
Ehlo XXX or HELo, [ESMTP ehlo XXX, SMTP HELo, I’ll fill ehlo XXX, XXX whatever]
Mail from:[email protected][administrator address]
RCPT to:[email protected][recipient address]
Data [Start writing email]
From :XXX[sender address]
To :XXX[Recipient address]
Subject: CEShi pop3 Send and Receive [subject]
Ceshi pop3 send and receive[Note: The body of the email should be blank, otherwise it will be automatically determined as the subject. If you want to send Chinese, you need to download Telnet client separately, see attachment]
.[End of message identifier]
Normally it will prompt you that the message has been queued for sending
Quit [After sending the email]
 

Step 1. Google the cause of the error and find the solution to the problem.
Reference 1.
https://social.technet.microsoft.com/Forums/exchange/en-US/fc26dac5-d4e2-49da-903d-361ea8b85388/451-470-temporary-server-error-please-try-again-later-prx5
I talked to a MS support rep today and they confirmed the same problem, except to resolve it we had to add the local server’s IP to our hosts file:
192.168.1.5 server
192.168.1.5 server. The domain. The local
Restart “Microsoft Frontend Transport” and “Microsoft Exchange Transport” services
The support agent stated that he’s seen this in a few cases now. All of which are when the Exchange server front and back-ends reside on the same box. Sounds like an Exchange bug to me.
Reference 2,
http://blog.5dmail.net/user1/1/2014414174021.html
 

Exchange Server 2013 cannot receive emails sent from outside. Remote Host said: 451 4.7.0 Temporary Server Error. Please try again later. PRX2
 
[Reason analysis]
The Exchange Server 2013 in question was installed with multiple roles. Including the mailbox and client access roles of DOMAIN control and Exchange 2013, and because the client server is hosted in the computer room, it is equipped with two network CARDS, which are configured with an Intranet IP and a public network IP respectively, the fault is mainly caused by the two network CARDS using different DNS.
 
Step 2: Modify the local C:\Windows\System32\drivers\etc\ hosts file, add and save the local records of Exchange 2013 server.

Step 3. Check the Exchange server and THE AD domain server, and check that the DNS is pointing to the inside and there is no record pointing to the outside.
Step 4. Restart the “Microsoft Frontend Transport” and the “Microsoft Exchange Transport” services


Step 5: If you restart the “Microsoft Frontend Transport”, the Transport service has stopped and cannot get up, restart the server?No, we open the task manager, find Msexchangetransport.exe finish the task and restart the Transport service.

Step 6. After the processing, we tested a Telnet test. The specific method referred to the description in the previous part of the article, and the email was successfully sent.

Step 7. When opening Outlook, the test has been successfully tested, the receiving and sending is normal, and there is no password box prompt, and the fault is solved. Thank you for your patience to watch, thank you!

 

Reproduced in: https://blog.51cto.com/yuntcloud/1584670

SFTP login error: fatal error: received unexpected end of file from SFTP server

STFP suddenly failed to log in, no restart, no configuration change, and suddenly an error was reported
ERROR: Received unexpected end-of-file from SFTP server
ERROR: unable to connect to server
status: waiting for retry…

The first possibility:
Password expired, change password, verify this problem, just su (SFTP username) on the server, for example: su Test

If the password prompt has expired, directly change the password, you can log in
Change password command
1. Switch to SFTP user: Su Test
2. Enter the old password for Test
3. Press the prompt to enter a new password. Don’t repeat the old password
Suggestion: The password expiration time can be changed, the default is 90 days, we can change a little longer
 
The second possibility:
Modify the configuration file and remember to back up the file
1. The vi/etc/SSH/sshd_config
Delete the Subsystem SFTP/usr/libexec/openssh/SFTP – “#” in front of the server,
Save the exit and restart SSH
# service SSHD restart
Then reconnect to the FTP test.
 

Disk BLK_ update_ request: I/O error

1. Try 1:
Blk_update_request: I/O error, dev fd0, Sector 0 error resolved

Reference document:

https://bbs.archlinux.org/viewtopic.php?pid=1166918#p1166918
http://www.cyberciti.biz/faq/linux-end_request-ioerror-dev-fd0-sector0/

blk_update_request: I/O error, dev fd0, sector 0 when booting Linux on hardware with floppy drive controller on
Resolve the error message by closing the floppy drive module:
#
# /etc/modprobe.d/modprobe.conf
#
blacklist floppy
Try 2:

< strong> When dMESg occurs, the following message indicates a problem with the disk. /strong> < br> < br> Info fld=0x139066d0

end_request: I/O error, dev sda, sector 328230608

The I/O error Buffer
The on
device sda, logical block 41028826

sd 0:0:0:0: SCSI error:
The return
code = 0x08000002

sda: Current: sense key: Medium Error


Add. Sense: Unrecovered read error

 

Info fld=0x139066d0

end_request: I/O error, dev sda, sector 328230608

The I/O error Buffer
The on
device sda, logical block 41028826

sd 0:0:0:0: SCSI error:
The return
code = 0x08000002

sda: Current: sense key: Medium Error


Add. Sense: Unrecovered read error

 

Info fld=0x139066d0

end_request: I/O error, dev sda, sector 328230608

The I/O error Buffer
The on
device sda, logical block 41028826

sd 0:0:0:0: SCSI error:
The return
code = 0x08000002

sda: Current: sense key: Medium Error


Add. Sense: Unrecovered read error

 

Info fld=0x139066d0

end_request: I/O error, dev sda, sector 328230608

The I/O error Buffer
The on
device sda, logical block 41028826

sd 0:0:0:0: SCSI error:
The return
code = 0x08000002

sda: Current: sense key: Medium Error


Add. Sense: Unrecovered read error

1. First detect the failure
Badblock-s-v-o /root/bb.log /dev/sda save the results to bb.log

[root@logging ~]# badblocks -s -v -o /root/badblocks.log /dev/sda
Checking blocks 0 to 586061784
Checking for bad blocks (read-only test): done                                
Pass completed, 173 bad blocks found.

 
Smartctl-a /dev/sda3 (Quickly detect errors after read and write)
2. Repair method of logical bad path

, badblock-s-w /dev/sda END START (END stands for the END of the sector to be repaired, START stands for the beginning of the sector to be repaired)
, fsck-a /dev/sda
After the repair, badblock-s-v-o /root/bb.log /dev/sda will be used to monitor for bad tracks. If there are bad tracks, it is a bad hard drive. Hard disk bad way to use the isolation method, first of all, the monitoring of the hard disk bad way and then partition when the hard disk bad way in the sector is divided in a partition (size is generally greater than the size of the bad sector), the partition of the bad way partition can achieve the purpose of isolation
3. 0 Bad track and hard drive (ready to replace hard drive)
The repair method of bad track of 0 track is to isolate track of 0 track. When using FDSK to divide the area, divide the area from track of 1.
If it's a bad drive, it can only be quarantined and not repaired
 

Reproduced in: https://www.cnblogs.com/wangjq19920210/p/9238910.html

error while loading shared libraries: requires glibc 2.5 or later dynamic linker

C development environment under Linux setup process
– install glibc
 
Some software may require that your system’s Glibc be higher than a certain version to work, and if your Glibc is lower than the required version, you will have to upgrade your Glibc in order to run the software. Such as:
Error while loading Shared Libraries: Requires glibc 2.5 or later Dynamic Linker
 
You can look for compiled RPM packages or use source code to upgrade Glibc.
 
RPM package glibc
RPM is relatively easy to install, but the dependency problem is difficult to solve. Give a download address:
http://mirrors.jtlnet.com/centos/5.5/os/i386/CentOS/
$ RPM – the ivh glibc 2.5-49.. I386 RPM
 
But I’m using CentOS 4.8 and it doesn’t seem to be compatible…
error: Failed dependencies:
Glibc-common = 2.5-49 is needed by glibC-2.5-49. I386
glibc > 2.3.4 conflicts with glibc – common – 2.3.4-2.43 el4_8. 3. The i386
 
After the installation is complete, you can check whether you have upgraded:
$ ls -l /lib/libc.so.6
lrwxrwxrwx 1 root root 11 10-08 22:08 /lib/libc.so.6 -> Libc – 2.5. So
 
compile and install glibc
Download the glibc
[root@localhost test]# pwd
/test
[root @ localhost test] # wget http://ftp.gnu.org/gnu/glibc/glibc-2.9.tar.bz2
 
Download the glibc – linuxthreads
[root @ localhost test] # wget http://ftp.gnu.org/gnu/glibc/glibc-linuxthreads-2.5.tar.bz2
 
Unpack the
[root-@localhost test]# tar-jvxf glibc-2.9.tar.bz2
[root @ localhost test] # CD glibc 2.9
[root-@localhost glibc-2.9]# tar-jvxf../glibc – linuxthreads – 2.5. Tar..bz2
 
configuration
[root @ localhost glibc 2.9] # CD..
[root@localhost test]# exportCFLAGS=”-g -O2 -march=i486″
[root@localhost test]# mkdir glibc-build
[root@localhost test]# cd glibc-build
[root@localhost glibc-build]# .. /glibc-2.9/configure –prefix=/usr –disable-profile — enabling -add-ons –with-headers=/usr/include –with-binutils=/usr/bin
 
The installation
[root@localhost glibc-build]# make
[root@localhost glibc-build]# make install
 
Three points should be paid attention to during installation and compilation:
1. To unzip glibC-LinuxThreads into glibc directory.
2. Cannot run configure in glibc’s current directory.
Otherwise, if there is an error: error “Glibc cannot be Compiled without optimization”, please add the optimization switch: [root-@localhost test]# export CFLAGS=” -g-O2-March =i486″

Reproduced in: https://blog.51cto.com/rockhooray/787500

Solution: error in the RPC receive loop

Abstract: Cloud computing and virtualization are popular concepts in the field of informatization in recent years. With the deepening of these concepts in China, the new generation of virtual machine, virtualization environment has been more and more in our daily environment. The flexible and fast deployment management mode of virtual machine is gradually accepted by the field of operation and maintenance. In the field of practice, we are also facing new problems and failures when using virtualized environments that require us to…
Cloud computing and virtualization are popular concepts in the field of informatization in recent years. With the deepening of these concepts in China, the new generation of virtual machine, virtualization environment has been more and more in our daily environment. The flexible and fast deployment management mode of virtual machine is gradually accepted by the field of operation and maintenance.
In the field of practice, we also face some new problems and failures when using virtualized environment, which require us to re-study and explore, so as to keep up with the development process and solve the practical problems in the enterprise.
This article records the minor problems I encountered while managing and maintaining a Windows virtual machine (built on VM Ware), and keeps a record of them for those who need them to check.
1. Problem description
The author is installing and maintaining a Windows server running version 2008 R2. The server is based on VM Ware virtual machine environment, and resource allocation and management are carried out through VM Ware console. Due to the server’s purpose, the author conducted additional security hardening operations and log checking operations, and found that the logs contained the following Warning information.
Unlike Linux/AIX text logs, Windows logs are stored and presented in binary mode and organized into different types. As you can see from the screenshot above, in the Application type, the system generates warlike log information at a very high frequency (two per second). Application-type logs are generally the log contents written to the operating system level by Application output.
The Source column prompts to indicate which application wrote the log content. This column we confirm is from VMWare Tools.
2. Problem analysis
VMWare Tools is an optional part of a VMWare virtual machine. In newer versions, VMWare Tools is a mandatory version of the virtual machine. Simply put, VMWare Tools is a plug-in tool that is embedded at the operating system level of a virtual machine. My main responsibility is to improve hardware compatibility and interaction experience. If we compare a virtual machine to a unit running in a container, VMWare Tools is an important component in the communication between the two.
Based on the error case this time, we can find the main contents of the fault log are as follows:
[ warning] [vmusr:vmusr] Error in the RPC receive loop: RpcIn: Unable to send.
The author has no experience with this error, and judging from the prompts and the frequency of failures, it looks like VMware Tools is sending RPC messages over a continuous connection. But the call did not complete successfully. At one point, the author wondered if RPC ports were closed during the strengthening of the operating system, but later confirmed that this was not the case.
3. Problem analysis and solution
By inquiring the data, I found the fault analysis and reason from the VMWare official. This logging phenomenon is possible in both Windows and Linux environments. The official explanation for the problem is as follows:
Cause
This issue occurs when the VMware Tools daemon (vmtoolsd) handles more than two Terminal Sessions. When a user connects to a Windows virtual machine, each terminal session should have one vmtoolsd running; however, vmtoolsd is limited to only two sessions running simultaneously.
Thus the Windows Application Event log fills up with warning messages similar to this until the total connection count is > 2?per session:
Simply put, the problem occurs when multiple users are connected to the virtual machine at the same time. Every time a user connects to a virtual machine using VMTool, the background virtual machine allocates a background daemon that matches vmToolSD. This can occur if multiple users are connected to the system at the same time, or if the remote Desktop interface is simply closed without a formal launch. The vmToolsd process is limited to two sessions at a time.
When this happens, VMTools writes a warning level message to the operating system.
Then, you need to determine the current number of connected users and whether there are more than one VMToolSD working at the same time. An accidental scene, the author looked at the task manager, found clues.
In the task manager, there is indeed more than one VMToolsd.exe connection, which corresponds to the multiple system users I created. This is due to the fact that when I created the user, I used the remote desktop for testing separately and did not quit.
Once you find the cause of the problem, you can start to fix it. The idea of VMWare’s official solution is that if too many logs occur too often, the warn-level log switch can be turned off and not written to the operating system.
Closing the log is done primarily through configuration files. On Windows 7, 2008, the log configuration directory is: C:\ProgramData\VMware\VMware Tools\. In earlier Versions of Windows, the directory path was C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\.
In Linux, the configuration directory is: /etc/vmware-tools/tools.conf.
On the corresponding directory, the configuration file name is called tools.conf. If the file does not exist, you can create your own directory to configure. The author does not have this file in the corresponding directory of the server, it is created first.
Write the following in the file:
[logging]
vmusr.level = error
vmsvc.level = error
Then restart VMTools Services and ensure that the multi-user connection is disconnected and the configuration takes effect. I chose to restart the server. Then the problem is solved.
4, the conclusion
As virtualization is widely used in operations and maintenance environments, it is believed that more and more virtualization-related failures will appear and be resolved.
The original address: http://blog.itpub.net/17203031/viewspace-1260657
In addition, the ranger safety net webmaster also found this result:
Reason: Due to vmTools limitations, an alert will appear when VMTools processes more than 2 terminal connections
Solution: Disable the alarm generation log as follows
Into the C: \ ProgramData \ VMware \ VMware Tools \
Find the tools. Conf
Notepad editor
Add the following fields
[logging]
vmusr.level = error
Restart the VMware Tools service

Reproduced in: https://blog.51cto.com/prince0330/1713958

Solution of 500 internal server error reported by [SVN] TortoiseSVN

Background: For some reason, I restarted the physical machine of SVN service. After restarting, I found that everyone accessing SVN reported the following error.

Since no changes have been made before the restart, I am a little confused about this error. I have tried firewall, network management, cache cleaning and other methods, but still haven’t solved the problem. There is no problem between the network, can ping and Telnet each other, but the access report 500 errors.
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — omitted here for a long time of research time…
Solutions:
1. Log in to SVN Server and open VisualSVN Server management tool.
2. Right-click to open the property “Properties”, as shown in the figure below:

3. See the “Automatically adjust Permissions “option on the General screen. If the value has been checked, undo the check and apply it. During the process, it will re-serve.

 
After the above steps, I visited SVN again and found that the problem was solved. After such a long study, the rain finally cleared up. This should be a SVN permission failure, I hope this method can help you open the article.

Reproduced in: https://www.cnblogs.com/whylaughing/p/7646419.html

Windows encountered 1152 when installing software: error extracting files to the temporary location

Today met 1152: when installing the software Error extracting files to the temporary location Error. There are not too many relevant methods on Baidu. After solving the problem, I will sort out the methods to solve the problem. Hope to be of help to a friend who has the same problem.

if some “bad” temporary files are extracted from previous failed installations, the error of extracting the files to a temporary location usually occurs. Clean that folder and try again is the right way. This means that if you unzip a file into the same folder over and over again, it could cause problems, or corrupted files in the Windows temporary folder could be the problem. What you can do is :
1. Clear Windows temporary folder
2. Clear extract folder or use other location
3. Check folder permissions
4. Clear failed boot of program installation.
First, clear the Windows temporary folder

Windows provides a built-in tool to clean up temporary storage. You can use it to remove all bad or corrupted files that could have prevented the extraction of these files. Any installer can use the Windows temporary folder, so you’ll find lots of files in that location. Storage sense will clear other folders along with a temporary folder, but you can choose which one to clear last.
enter setting > System & gt; Storage & gt; Configure storage awareness or run immediately. If your storage space is low, this tool will also fix the problem.
can delete everything in the Windows temporary folder directly, but if any files are locked, they will not be deleted. Storage sense or disk cleanup tool or any other garbage file cleanup application will ensure that the problem is overridden.
Clear the extract folder or use another location
If you are unzipping the ZIP file into another folder and are receiving the same error, it is best to delete everything in it. Sometimes damage can result if the previous installation is not completed. You can also use different locations to extract the file and see if it works.
if it is possible that the temporary file location already has a bad copy from a previous installation, it is a good idea to redownload the program and try it.
Three, check the folder permissions

you will not be able to extract files into this folder when you temporarily lose access to it. If for some reason you lose access to the folder you are unzipping, it will fail. So here’s what you should do :
• right-click folder > Property
• switch to the Security TAB and check if you are listed under the user group. Select your username and check to see if you have read, write, and execute permissions.
• click the edit button, suggest removing all permissions, and then add again. It will make sure you get the right permissions in the end.
once completed, manually copy the file to the folder and delete the file to check if it is working.
Four, clear the program installation failed boot
If all else fails, the last resort is to use a clean boat. If the problem is caused by something other than storage space or a corrupted temporary file, it will be fixed here.

Vsftpd: 500 oops: vsftpd: refusing to run with writable root inside chroot() error

This error is often encountered when using the user to log in to FTP after we have restricted the user from jumping out of his/her home directory:
 

500 OOPS: vsftpd: refusing to run with writable root inside chroot ()

 
This problem occurs in the latest update due to the following update:
 

- Add stronger checks for the configuration error of running with a writeable root directory inside a chroot(). This may bite people who carelessly turned on chroot_local_user but such is life.

 
Since 2.3.5, VSFTPD has enhanced security checks so that if a user is restricted to his or her home directory, the user’s home directory can no longer have write permissions! If the check finds that write permissions are still available, the error is reported.
To fix this error, remove write permissions from the user’s home directory with the command chmod A-w /home/user, and replace the directory with your own. Or you can add one of the following two items to the VSFTPD profile:
allow_writeable_chroot=YES

Giterror: error cloning remote repo ‘origin’ hudson.plugins.git .GitException

Last night the west wind withered green trees, alone on the tall buildings, look to the horizon road
Jenkins + GitLab continuous integration encountered the following error:

ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not init /root/.jenkins/workspace/eureka-service
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:787)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:579)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)
	at hudson.security.ACL.impersonate(ACL.java:290)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	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: hudson.plugins.git.GitException: Error performing command: git init /root/.jenkins/workspace/eureka-service
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2023)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1984)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1980)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1612)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:785)
	... 14 more
Caused by: java.io.IOException: Cannot run program "git" (in directory "/root/.jenkins/workspace/eureka-service"): error=2, 没有那个文件或目录
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
	at hudson.Proc$LocalProc.<init>(Proc.java:249)
	at hudson.Proc$LocalProc.<init>(Proc.java:218)
	at hudson.Launcher$LocalLauncher.launch(Launcher.java:935)
	at hudson.Launcher$ProcStarter.start(Launcher.java:454)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2012)
	... 18 more
Caused by: java.io.IOException: error=2, no such file
	at java.lang.UNIXProcess.forkAndExec(Native Method)
	at java.lang.UNIXProcess.<init>(UNIXProcess.java:247)
	at java.lang.ProcessImpl.start(ProcessImpl.java:134)
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
	... 23 more

Solutions:
To install Git on Jenkins’ host, execute the following command:
yum install git
Testing:

Solution to ebios read error: error 0x31 when installing snow leopard on virtual machine

2019 Unicorn enterprise heavily recruited Python engineer standard & GT; > >

EBIOS read error :error 0x31 error solution

EBIOS read error :error 0x31

Open the virtual machine’s Settings-> For Hardware, go to the CD/DVD(IDE) device, or go to the CD icon in the VM window status bar, click Settings, and replace the Dardarwin. Iso with the DMG image of the MAC system. Tick the boxes “Connected” or “Connect”. After completion, press the letter C to boot the installation DISC and enter the system installation interface after completion. Done!

Reproduced in: https://my.oschina.net/caiyuan/blog/165623

docker apache php-fpm AH01071: Got error ‘Primary script unknown\n’

Here’s the background:
In Docker, a container Alpine runs Apache (2.4.33, MPm_Event),
The other container runs PHP-FPM (7.2.8), so Apache and PHP-FPM are in remote linkage mode.

Many Settings refer to a large number of night data debugging, and all errors are reported:
AH01071: Got error ‘Primary script unknown\n’

After verification of configuration one by one, it is inconceivable that the problem is found. Let’s first give the correct configuration:
1. HTTPD. Conf
* Clear out lines like AddType Application/x-httpd-PHP PHP php7, which are not used by PHP-FPM.
* Similar paragraphs like the following are not required in httpd.conf:
< FilesMatch \.php$> SetHandler “proxy:fcgi://php-fpm:9000” < /FilesMatch>

2. The correct configuration requires only one line:
ProxyPassMatch ^/(.*\.php(/.*)?) $ fcgi://php-fpm:9000/v/php-fpm/www/$1
Put this line in your vhost.conf < VirtualHost> In the water.

Pay special attention!
1. My DocumentRoot path and the last path of ProxyPassMatch do not match!
(DocumentRoot/V/Apache/WWW) Apache startup needs to actually detect the existence of DocumentRoot path memory. That is, my data is in the Apache container, and after fCGI :// pushes the data to the PHP-FPM container, the PHP-FPM container needs to read this/V/Apache/WWW path, if it does not read, it will report an error AH01071. The foreground page says “File Not Find!”

Therefore, the core idea of the solution is to make the two containers have a common accessible file address. This is not redundant, with mount and other ways to solve.

2. Note the phP-FPM listen Settings
\php-fpm.d\www.conf
My listen = 172.0.0.3:9000
Here you cannot write 127.0.0.1, two containers in a virtual Intranet segment, and you can also write the Intranet address of the segment.