CN112235138A - Server access monitoring method and device, proxy server and storage medium - Google Patents
Server access monitoring method and device, proxy server and storage medium Download PDFInfo
- Publication number
- CN112235138A CN112235138A CN202011085039.XA CN202011085039A CN112235138A CN 112235138 A CN112235138 A CN 112235138A CN 202011085039 A CN202011085039 A CN 202011085039A CN 112235138 A CN112235138 A CN 112235138A
- Authority
- CN
- China
- Prior art keywords
- access
- internet protocol
- protocol address
- access result
- slave
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides a server access monitoring method and device, a proxy server and a storage medium, and relates to the technical field of Internet. In the present application, first, a first access result for accessing a target server based on a primary internet protocol address is obtained. And secondly, if the first access result is access failure, accessing the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result. Then, a failure type of the first access result is determined based on the at least one second access result, wherein the failure type comprises a primary internet protocol address error. Based on the method, the problem that the failure type is difficult to effectively determine when the access to the server fails in the prior art can be solved.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a server access monitoring method and apparatus, a proxy server, and a storage medium.
Background
In the field of internet technology, in order to improve the response speed of a user to access a website (background server), a Content Delivery Network (CDN) may be used for proxy. In the prior art, generally, a cause of an access failure may be directly attributed to an Internet Protocol (IP) address error when a proxy node on a content distribution network accesses a background server to obtain data. The inventor researches and discovers that other reasons or types cause the access failure of the background server, so that the problem that the failure type of the access failure of the server is difficult to effectively determine exists.
Disclosure of Invention
In view of the above, an object of the present application is to provide a server access monitoring method and apparatus, a proxy server, and a storage medium, so as to solve the problem in the prior art that it is difficult to efficiently determine a failure type when an access to a server fails.
In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:
a server access monitoring method is applied to a proxy server, the proxy server is configured with a master internet protocol address and a slave internet protocol address, and the method comprises the following steps:
obtaining a first access result for accessing a target server based on the primary internet protocol address;
if the first access result is access failure, accessing the target server at least based on one slave internet protocol address to obtain at least one corresponding second access result;
determining a failure type of the first access result based on the at least one second access result, wherein the failure type includes a primary internet protocol address error.
In a preferred option of the embodiment of the present application, in the server access monitoring method, the step of obtaining at least one second access result corresponding to the target server based on at least one of the access from the internet protocol address includes:
aiming at each slave internet protocol address in at least one preset slave internet protocol address, at least one access is carried out on the target server based on the slave internet protocol address, and at least one initial access result corresponding to the slave internet protocol address is obtained;
for each slave internet protocol address, determining a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address;
and respectively taking the target access result of each slave internet protocol address as a second access result of the slave internet protocol address to obtain at least one second access result.
In a preferred option of this embodiment of the application, in the server access monitoring method, the step of determining, for each slave internet protocol address, a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address includes:
for each slave internet protocol address, if at least one initial access result corresponding to the slave internet protocol address is access failure, determining that a target access result of the slave internet protocol address is access failure;
and for each slave internet protocol address, if one initial access result exists in at least one initial access result corresponding to the slave internet protocol address and is successful in access, determining that the target access result of the slave internet protocol address is successful in access.
In a preferred option of the embodiment of the present application, in the server access monitoring method, the step of accessing the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result further includes:
performing at least one access to the target server based on the primary internet protocol address to obtain at least one initial access result corresponding to the primary internet protocol address;
determining a target access result of the primary internet protocol address based on at least one initial access result corresponding to the primary internet protocol address;
and taking the target access result of the primary Internet protocol address as a second access result of the primary Internet protocol address to obtain at least one second access result.
In a preferred option of an embodiment of the present application, in the server access monitoring method, the at least one second access result includes a second access result of re-accessing the target server based on the primary internet protocol address, and the step of determining a failure type of the first access result based on the at least one second access result includes:
if a second access result of re-accessing the target server based on the master internet protocol address is access failure and a second access result of accessing the target server based on each slave internet protocol address is access success, determining that the master internet protocol address is wrong;
and if the second access result of accessing the target server again based on the master internet protocol address is access failure and the second access result of accessing the target server based on each slave internet protocol address is access failure, determining that the machine room where the proxy server is located has a fault or the target server has a fault.
In a preferred option of the embodiment of the present application, in the server access monitoring method, the step of determining a failure type of the first access result based on the at least one second access result further includes:
and if the access result of re-accessing the target server based on the master internet protocol address is successful, and the access result of accessing the target server based on each slave internet protocol address is successful, determining that the master internet protocol address is error-free, the machine room where the proxy server is located is failure-free, and the target server is overload-free and failure-free.
In a preferred option of the embodiment of the present application, in the server access monitoring method, the step of determining a failure type of the first access result based on the at least one second access result further includes:
determining that the target server is overloaded if a second access result of re-accessing the target server based on the master internet protocol address is an access failure and a second access result of accessing the target server based on the plurality of slave internet protocol addresses is a partial access failure;
and if the second access result of accessing the target server again based on the master internet protocol address is successful, and the second access result of accessing the target server based on the plurality of slave internet protocol addresses is at least partial access failure, determining that the target server is overloaded.
An embodiment of the present application further provides a server access monitoring apparatus, which is applied to a proxy server, where the proxy server is configured with a master internet protocol address and a slave internet protocol address, and the apparatus includes:
a first access result obtaining module, configured to obtain a first access result for accessing a target server based on the primary internet protocol address;
a second access result obtaining module, configured to, when the first access result is an access failure, access the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result;
an access failure type determination module to determine a failure type of the first access result based on the at least one second access result, the failure type including a primary internet protocol address error.
On the basis, an embodiment of the present application further provides a proxy server, including:
a memory for storing a computer program;
and the processor is connected with the memory and is used for executing the computer program stored in the memory so as to realize the server access monitoring method.
On the basis, the embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed, the server access monitoring method is implemented.
According to the server access monitoring method and device, the proxy server and the storage medium, the master internet protocol address and the slave internet protocol address are configured on the proxy server, so that when the target server is accessed based on the master internet protocol address, the target server can be accessed based on the slave internet protocol address, and the type (reason) of the access failure is determined based on the access result. Therefore, compared with the technical scheme that the reason is directly attributed to the internet protocol address error when the access fails, the reason of the access failure can be determined more effectively, so that the problem that the failure type is difficult to be determined effectively when the access of the server fails in the prior art is solved, the targeted maintenance can be performed based on the determined failure reason, and the like, and the method has higher practical value.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
Fig. 1 is a block diagram of a proxy server according to an embodiment of the present disclosure.
Fig. 2 is a schematic flowchart of a server access monitoring method according to an embodiment of the present application.
Fig. 3 is a flowchart illustrating sub-steps included in step S120 in fig. 2.
Fig. 4 is a flowchart illustrating the sub-steps included in step S122 in fig. 3.
Fig. 5 is a flowchart illustrating other sub-steps included in step S120 in fig. 2.
Fig. 6 is a schematic block diagram of a server access monitoring apparatus according to an embodiment of the present application.
Icon: 10-a proxy server; 12-a memory; 14-a processor; 100-a server access monitoring device; 110-a first access result obtaining module; 120-a second access result obtaining module; 130-access failure type determination module.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
As shown in fig. 1, the present embodiment provides a proxy server 10, which may include a memory 12, a processor 14, and a server access monitoring apparatus 100.
Wherein the memory 12 and the processor 14 are electrically connected directly or indirectly to realize data transmission or interaction. For example, they may be electrically connected to each other via one or more communication buses or signal lines. The server access monitoring apparatus 100 includes at least one software function module that can be stored in the memory 12 in the form of software or firmware (firmware). The processor 14 is configured to execute an executable computer program stored in the memory 12, for example, a software functional module and a computer program included in the server access monitoring apparatus 100, so as to implement the server access monitoring method provided in the embodiment of the present application.
Alternatively, the Memory 12 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like.
The processor 14 may be a general-purpose processor including a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and the like.
It will be appreciated that the architecture shown in fig. 1 is merely illustrative and that the proxy server 10 may also include more or fewer components than shown in fig. 1, or have a different configuration than that shown in fig. 1, for example, and may also include a communication unit for interacting with other devices, such as a target server.
With reference to fig. 2, an embodiment of the present application further provides a server access monitoring method, which can be applied to the proxy server 10. Wherein. The method steps defined by the flow relating to the server access monitoring method may be implemented by the proxy server 10.
The specific process shown in FIG. 2 will be described in detail below.
Step S110, obtaining a first access result for accessing the target server based on the primary internet protocol address.
In this embodiment, the proxy server 10 is configured with a primary internet protocol address in advance, and can access a target server based on the primary internet protocol address (for example, based on a request of a terminal device for communication connection), so that a first access result of the access can be obtained.
And, when the first access result is an access failure, step S120 may be performed.
Step S120, accessing the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result.
In this embodiment, the proxy server 10 is further configured with a slave internet protocol address in advance, so that when the first access result is obtained based on step S110 and the first access result is an access failure, the proxy server 10 may access the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result.
Step S130, determining a failure type of the first access result based on the at least one second access result.
In this embodiment, after obtaining the at least one second access result based on step S120, the proxy server 10 may determine, based on the at least one second access result, the type of failure of the access failure when the target server is accessed based on the primary internet protocol address (i.e., the type of failure of the first access result).
Wherein the failure type (failure cause) may comprise a primary internet protocol address error.
Based on the above method, by configuring the master internet protocol address and the slave internet protocol address on the proxy server 10, it is made possible to access the target server based on the slave internet protocol address when access to the target server based on the master internet protocol address fails, thereby determining the type (cause) of the access failure based on the result of the access. Therefore, compared with the technical scheme that the reason is directly attributed to the internet protocol address error when the access fails, the reason of the access failure can be determined more effectively, so that the problem that the failure type is difficult to be determined effectively when the access of the server fails in the prior art is solved, and the targeted maintenance can be performed based on the determined failure reason.
In the first aspect, it should be noted that, in step S110, a specific manner of obtaining the access result is not limited, and may be selected according to actual application requirements.
For example, in an alternative example, after the proxy server 10 accesses the target server based on the primary internet protocol address each time, the obtained first access result may be stored in a target database (such as a local database), so that the first access result may be obtained by performing a data reading operation on the target database.
It is understood that, considering that there may be a duplicate result in the first access result obtained by performing the access, in some examples, the obtained first access result may also be subjected to a filtering process to filter the duplicate first access result, so as to avoid the problem of overloading the target database.
In the second aspect, it should be noted that, in step S120, a specific manner of obtaining the at least one second access result is not limited, and may be selected according to an actual application requirement.
For example, in an alternative example, in conjunction with fig. 3, step S120 may include step S121, step S122, and step S123, which are described in detail below.
Step S121, for each slave internet protocol address in the at least one preconfigured slave internet protocol address, performing at least one access to the target server based on the slave internet protocol address, and obtaining at least one initial access result corresponding to the slave internet protocol address.
In this embodiment, when the first access result is obtained based on step S110 and the first access result is an access failure, for each of the at least one slave internet protocol address configured in advance, at least one access may be performed on the target server based on the slave internet protocol address to obtain at least one corresponding initial access result. In this way, at least one initial access result corresponding to each of the slave internet protocol addresses can be obtained.
Step S122, for each slave internet protocol address, determining a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address.
In this embodiment, after obtaining the initial access result based on step S122, for each slave internet protocol address, the target access result of the slave internet protocol address may be determined based on at least one initial access result corresponding to the slave internet protocol address. In this way, the target access result corresponding to each slave internet protocol address can be obtained.
Step S123, using the target access result of each slave internet protocol address as the second access result of the slave internet protocol address, respectively, to obtain at least one second access result.
In this embodiment, after obtaining the target access result based on step S122, the target access result corresponding to each slave internet protocol address may be respectively used as the second access result of the slave internet protocol address. In this way, at least one second access result may be obtained for at least one of said slave internet protocol addresses.
Optionally, in the above example, a specific manner of obtaining the at least one initial access result based on step S121 is not limited, and may be selected according to an actual application requirement.
For example, in an alternative example, for each slave internet protocol address, an initial access result corresponding to the slave internet protocol address may be obtained based on one access to the target server by the slave internet protocol address.
For another example, in another alternative example, for each slave internet protocol address, multiple (e.g., 3, etc.) accesses to the target server based on the slave internet protocol address may be performed, and multiple initial access results corresponding to the slave internet protocol address may be obtained.
Optionally, in the above example, the specific manner of determining the target access result based on step S122 is not limited, and may be selected according to the actual application requirement.
For example, in an alternative example, if there is one initial access result corresponding to each slave internet protocol address, the initial access result may be used as the target access result.
For another example, in another alternative example, in conjunction with fig. 4, step S122 may include step S122a and step S122b, which are described in detail below.
Step S122a, for each slave internet protocol address, if at least one initial access result corresponding to the slave internet protocol address is an access failure, determining that the target access result of the slave internet protocol address is an access failure.
In this embodiment, after obtaining at least one initial access result corresponding to each slave ip address based on step S121, it may be determined whether each initial access result is an access failure, and thus, if each initial access result corresponding to one slave ip address is an access failure, it may be determined that the target access result of the slave ip address is an access failure.
Step S122b, for each slave internet protocol address, if one of the at least one initial access result corresponding to the slave internet protocol address is successful, determining that the target access result of the slave internet protocol address is successful.
In this embodiment, after obtaining the at least one initial access result corresponding to each slave internet protocol address based on step S121, it may be determined whether there is an initial access result as successful access in the at least one initial access result corresponding to each slave internet protocol address, and thus, if there is an initial access result as successful access in the at least one initial access result corresponding to a slave internet protocol address, it may be determined that the target access result of the slave internet protocol address is successful access.
On the basis of the above example, it should be further explained for step S120 that step S120 may further include other steps. For example, in an alternative example, the target server may be accessed again based on the primary internet protocol address, and based on this, in conjunction with fig. 5, step S120 may further include step S124, step S125 and step S126, which are described in detail below.
Step S124, performing at least one access to the target server based on the primary internet protocol address, and obtaining at least one initial access result corresponding to the primary internet protocol address.
In this embodiment, when the first access result is obtained based on step S110 and the first access result is an access failure, the target server may be accessed at least once again based on the primary internet protocol address to obtain at least one initial access result corresponding to the primary internet protocol address, that is, each access may obtain one initial access result.
Step S125, determining a target access result of the primary internet protocol address based on at least one initial access result corresponding to the primary internet protocol address.
In this embodiment, after obtaining at least one initial access result corresponding to the primary internet protocol address based on step S124, a target access result of the primary internet protocol address may be determined based on the at least one initial access result. For example, in one alternative example:
if at least one initial access result corresponding to the primary Internet protocol address is access failure, determining that a target access result of the primary Internet protocol address is access failure; and if one initial access result exists in at least one initial access result corresponding to the primary Internet protocol address, determining that the target access result of the primary Internet protocol address is successful in access.
Step S126, using the target access result of the primary internet protocol address as a second access result of the primary internet protocol address, and obtaining at least one second access result.
In this embodiment, after determining the target access result of the primary internet protocol address based on step S125, the target access result may be used as the second access result of the primary internet protocol address, thereby obtaining a second access result.
In the third aspect, it should be noted that, for step S130, a specific manner of determining the type of failure of the first access result is not limited, for example, different options may be available based on whether the obtained at least one second access result includes a second access result for accessing the target server again based on the primary internet protocol address.
Based on this, in an alternative example, the at least one second access result comprises a second access result of accessing the target server again based on the primary internet protocol address, and therefore, step S130 may comprise the sub-steps of:
if the second access result of re-accessing the target server based on the master internet protocol address is access failure and the second access result of accessing the target server based on each slave internet protocol address is access success, determining that the master internet protocol address is wrong (since only the second access result of the master internet protocol address is access failure, it is indicated that the master internet protocol address has problems, such as being blocked, and the like, the master internet protocol address is determined to be wrong);
if the second access result of re-accessing the target server based on the master internet protocol address is an access failure, and the second access result of accessing the target server based on each slave internet protocol address is an access failure, it is determined that the room where the proxy server 10 is located is a failure or the target server is a failure (the second access results of the master internet protocol address and the slave internet protocol addresses are both access failures, and since all the internet protocol address errors are less likely, it may be determined that the failure type is a room failure or a target server failure where the proxy server 10 is located, and a specific type may send notification information to a management server of a content distribution network where the proxy server 10 is located through the proxy server 10, so that the management server accesses the target server through the proxy servers 10 of different rooms, thereby determining whether the machine room in which the proxy server 10 is located is faulty or the target server is faulty).
In the above example, the second access result of re-accessing the target server based on the primary internet protocol address is an access failure, and therefore, when the second access result is an access success, the specific failure type determination rule is not limited, and may be selected according to the actual application requirement.
For example, in an alternative example, step S130 may include the following sub-steps:
if the access result of re-accessing the target server based on the master internet protocol address is successful, and the access result of accessing the target server based on each slave internet protocol address is successful, it is determined that there is no error in the master internet protocol address, no fault in the machine room where the proxy server 10 is located, and no overload and fault in the target server (i.e., the first access result may have miscalculations, or the fault error that has occurred has been recovered).
Also, in some examples, in order to obtain a more accurate result, the second access result obtained by accessing the target server based on the internet protocol address may be multiple, and thus, the step S130 may include the following sub-steps:
if a second access result of re-accessing the target server based on the master internet protocol address is an access failure and a second access result of accessing the target server based on a plurality of slave internet protocol addresses is a partial access failure, determining that the target server is overloaded (since all the second access results are not access failures, which indicates that there is a low possibility of errors in the internet protocol addresses, it may be determined that the failure type is target server overload);
if the second access result of re-accessing the target server based on the master internet protocol address is successful, and the second access result of accessing the target server based on the plurality of slave internet protocol addresses is at least partially failed, determining that the target server is overloaded (since not all the second access results are failed accesses, which indicates that there is a low possibility of errors in the internet protocol addresses, it may be determined that the type of failure is overloaded target server).
It is to be understood that, in the above example, the specific relationship between the master internet protocol address and the slave internet protocol address is not limited, and for example, the master internet protocol address and the slave internet protocol address may be different internet protocol addresses, or the master internet protocol address and the slave internet protocol address may be different internet protocol addresses belonging to the same network segment (for example, in one network segment, the first internet protocol address may be the master internet protocol address, and the other internet protocol addresses may be the slave internet protocol addresses).
With reference to fig. 6, the embodiment of the present application further provides a server access monitoring apparatus 100, which can be applied to the proxy server 10. The server access monitoring apparatus 100 includes a first access result obtaining module 110, a second access result obtaining module 120, and an access failure type determining module 130.
The first access result obtaining module 110 may be configured to obtain a first access result for accessing a target server based on the primary internet protocol address. In this embodiment, the first access result obtaining module 110 may be configured to execute step S110 shown in fig. 2, and reference may be made to the foregoing description of step S110 regarding relevant contents of the first access result obtaining module 110.
The second access result obtaining module 120 may be configured to, when the first access result is an access failure, access the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result. In this embodiment, the second access result obtaining module 120 may be configured to perform step S120 shown in fig. 2, and reference may be made to the foregoing description of step S120 for relevant contents of the second access result obtaining module 120.
The access failure type determining module 130 may be configured to determine a failure type of the first access result based on the at least one second access result, where the failure type includes a primary internet protocol address error. In this embodiment, the access failure type determining module 130 may be configured to execute step S130 shown in fig. 2, and reference may be made to the foregoing description of step S130 for relevant contents of the access failure type determining module 130.
In an embodiment of the present application, corresponding to the server access monitoring method, a computer-readable storage medium is further provided, in which a computer program is stored, and the computer program executes the steps of the server access monitoring method when running.
The steps executed when the computer program runs are not described in detail herein, and reference may be made to the foregoing explanation of the server access monitoring method.
In summary, according to the server access monitoring method and apparatus, the proxy server, and the storage medium provided by the present application, the master internet protocol address and the slave internet protocol address are configured on the proxy server, so that when the target server is failed to be accessed based on the master internet protocol address, the target server can be accessed based on the slave internet protocol address, and the type (cause) of the access failure is determined based on the result of the access. Therefore, compared with the technical scheme that the reason is directly attributed to the internet protocol address error when the access fails, the reason of the access failure can be determined more effectively, so that the problem that the failure type is difficult to be determined effectively when the access of the server fails in the prior art is solved, the targeted maintenance can be performed based on the determined failure reason, and the practical value is higher.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus and method embodiments described above are illustrative only, as the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, an electronic device, or a network device) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (10)
1. A server access monitoring method applied to a proxy server configured with a master internet protocol address and a slave internet protocol address, the method comprising:
obtaining a first access result for accessing a target server based on the primary internet protocol address;
if the first access result is access failure, accessing the target server at least based on one slave internet protocol address to obtain at least one corresponding second access result;
determining a failure type of the first access result based on the at least one second access result, wherein the failure type includes a primary internet protocol address error.
2. The server access monitoring method according to claim 1, wherein the step of obtaining at least one second access result corresponding to the at least one target server based on the at least one access from the internet protocol address comprises:
aiming at each slave internet protocol address in at least one preset slave internet protocol address, at least one access is carried out on the target server based on the slave internet protocol address, and at least one initial access result corresponding to the slave internet protocol address is obtained;
for each slave internet protocol address, determining a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address;
and respectively taking the target access result of each slave internet protocol address as a second access result of the slave internet protocol address to obtain at least one second access result.
3. The server access monitoring method according to claim 2, wherein the step of determining, for each slave internet protocol address, a target access result of the slave internet protocol address based on at least one initial access result corresponding to the slave internet protocol address comprises:
for each slave internet protocol address, if at least one initial access result corresponding to the slave internet protocol address is access failure, determining that a target access result of the slave internet protocol address is access failure;
and for each slave internet protocol address, if one initial access result exists in at least one initial access result corresponding to the slave internet protocol address and is successful in access, determining that the target access result of the slave internet protocol address is successful in access.
4. The server access monitoring method according to claim 2, wherein the step of obtaining at least one second access result corresponding to the at least one slave internet protocol address based on the at least one access to the target server further comprises:
performing at least one access to the target server based on the primary internet protocol address to obtain at least one initial access result corresponding to the primary internet protocol address;
determining a target access result of the primary internet protocol address based on at least one initial access result corresponding to the primary internet protocol address;
and taking the target access result of the primary Internet protocol address as a second access result of the primary Internet protocol address to obtain at least one second access result.
5. The server access monitoring method according to any one of claims 1 to 4, wherein the at least one second access result includes a second access result of re-accessing the target server based on the primary Internet protocol address, and the step of determining the type of failure of the first access result based on the at least one second access result includes:
if a second access result of re-accessing the target server based on the master internet protocol address is access failure and a second access result of accessing the target server based on each slave internet protocol address is access success, determining that the master internet protocol address is wrong;
and if the second access result of accessing the target server again based on the master internet protocol address is access failure and the second access result of accessing the target server based on each slave internet protocol address is access failure, determining that the machine room where the proxy server is located has a fault or the target server has a fault.
6. The server access monitoring method of claim 5, wherein the step of determining the type of failure of the first access result based on the at least one second access result further comprises:
and if the access result of re-accessing the target server based on the master internet protocol address is successful, and the access result of accessing the target server based on each slave internet protocol address is successful, determining that the master internet protocol address is error-free, the machine room where the proxy server is located is failure-free, and the target server is overload-free and failure-free.
7. The server access monitoring method of claim 5, wherein the step of determining the type of failure of the first access result based on the at least one second access result further comprises:
determining that the target server is overloaded if a second access result of re-accessing the target server based on the master internet protocol address is an access failure and a second access result of accessing the target server based on the plurality of slave internet protocol addresses is a partial access failure;
and if the second access result of accessing the target server again based on the master internet protocol address is successful, and the second access result of accessing the target server based on the plurality of slave internet protocol addresses is at least partial access failure, determining that the target server is overloaded.
8. A server access monitoring device for use with a proxy server configured with a master internet protocol address and a slave internet protocol address, the device comprising:
a first access result obtaining module, configured to obtain a first access result for accessing a target server based on the primary internet protocol address;
a second access result obtaining module, configured to, when the first access result is an access failure, access the target server based on at least one slave internet protocol address to obtain at least one corresponding second access result;
an access failure type determination module to determine a failure type of the first access result based on the at least one second access result, the failure type including a primary internet protocol address error.
9. A proxy server, comprising:
a memory for storing a computer program;
a processor coupled to the memory for executing the computer program stored by the memory to implement the server access monitoring method of any of claims 1-7.
10. A computer-readable storage medium storing a computer program, characterized in that the computer program, when executed, implements the server access monitoring method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011085039.XA CN112235138B (en) | 2020-10-12 | 2020-10-12 | Server access monitoring method and device, proxy server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011085039.XA CN112235138B (en) | 2020-10-12 | 2020-10-12 | Server access monitoring method and device, proxy server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112235138A true CN112235138A (en) | 2021-01-15 |
| CN112235138B CN112235138B (en) | 2023-06-02 |
Family
ID=74112063
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011085039.XA Active CN112235138B (en) | 2020-10-12 | 2020-10-12 | Server access monitoring method and device, proxy server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112235138B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102214223A (en) * | 2011-06-15 | 2011-10-12 | 奇智软件（北京）有限公司 | Method and system for browser access control |
| CN109347766A (en) * | 2018-12-07 | 2019-02-15 | 网宿科技股份有限公司 | A kind of method and device of scheduling of resource |
| CN110224996A (en) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Network Access Method, device, computer equipment and the storage medium of application program |
| CN110995542A (en) * | 2019-12-16 | 2020-04-10 | 金蝶智慧科技(深圳)有限公司 | Network state detection method, system and related equipment |
| CN111343630A (en) * | 2020-03-07 | 2020-06-26 | 山东浪潮通软信息科技有限公司 | Network connection state detection method, computer device, and storage medium |
-
2020
- 2020-10-12 CN CN202011085039.XA patent/CN112235138B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102214223A (en) * | 2011-06-15 | 2011-10-12 | 奇智软件（北京）有限公司 | Method and system for browser access control |
| CN109347766A (en) * | 2018-12-07 | 2019-02-15 | 网宿科技股份有限公司 | A kind of method and device of scheduling of resource |
| CN110224996A (en) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Network Access Method, device, computer equipment and the storage medium of application program |
| CN110995542A (en) * | 2019-12-16 | 2020-04-10 | 金蝶智慧科技(深圳)有限公司 | Network state detection method, system and related equipment |
| CN111343630A (en) * | 2020-03-07 | 2020-06-26 | 山东浪潮通软信息科技有限公司 | Network connection state detection method, computer device, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112235138B (en) | 2023-06-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110036599B (en) | Programming interface for network health information | |
| US6718376B1 (en) | Managing recovery of service components and notification of service errors and failures | |
| CN110572275B (en) | Network card switching method and device, server and computer readable storage medium | |
| US7356531B1 (en) | Network file system record lock recovery in a highly available environment | |
| EP3352433A1 (en) | Node connection method and distributed computing system | |
| US7370102B1 (en) | Managing recovery of service components and notification of service errors and failures | |
| CN110932933B (en) | Network condition monitoring method, computing device and computer storage medium | |
| CN107682172B (en) | Control center device, service system processing method and medium | |
| US20110264757A1 (en) | Notice of restored malfunctioning links | |
| CN111259072A (en) | Data synchronization method and device, electronic equipment and computer readable storage medium | |
| CN113141412B (en) | Domain name switching method, system, device, equipment and storage medium | |
| CN110968356A (en) | Method and device for acquiring configuration information | |
| US8977595B1 (en) | Message-recovery file log locating and monitoring | |
| CN111010342B (en) | Distributed load balancing implementation method and device | |
| CN112818307A (en) | User operation processing method, system, device and computer readable storage medium | |
| CN112565327B (en) | Access flow forwarding method, cluster management method and related device | |
| CN114296881A (en) | Container protection connection method, device, equipment and medium based on middleware deployment | |
| CN109324914B (en) | Service calling method, service calling device and central server | |
| CN112235138B (en) | Server access monitoring method and device, proxy server and storage medium | |
| CN111414247A (en) | Server switching method, device, management node and storage medium | |
| CN110752972A (en) | Network card state monitoring method, device, equipment and medium | |
| CN113596195B (en) | Public IP address management method, device, main node and storage medium | |
| US11693837B2 (en) | Model ML registry and model serving | |
| CN111130941B (en) | Network error detection method and device and computer readable storage medium | |
| WO2017049959A1 (en) | Service processing method and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |