CN114760314A

CN114760314A - Server management method, device, computer equipment and storage medium

Info

Publication number: CN114760314A
Application number: CN202210353897.0A
Authority: CN
Inventors: 张斗斗; 张楠; 李春霞; 郭佳迪
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2022-04-06
Filing date: 2022-04-06
Publication date: 2022-07-15

Abstract

The application relates to a server management method, a server management device, a computer device, a storage medium and a computer program product, which can be used in the technical field of big data, the technical field of financial science and technology or other related fields. The method comprises the following steps: displaying a server management interface comprising a server selection area and at least one management option, the server selection area comprising an identification of a plurality of servers; determining a plurality of target servers in response to a selection operation of the identifications of the plurality of servers; responding to the selection operation of the management options, executing the management operation corresponding to the management options on the target servers to obtain an execution result; and displaying the execution result on the server management interface. By adopting the method, the visual page is provided, a plurality of Nginx servers can be managed in batches, the workload is reduced, the management efficiency of the servers is improved, and production safety risk accidents caused by manual operation errors are avoided.

Description

Server management method, device, computer equipment and storage medium

Technical Field

The present application relates to the field of big data technologies, and in particular, to a server management method, an apparatus, a computer device, and a storage medium.

Background

With the continuous development of computer technology, the requirements of users for the server are higher and higher, and the Nginx server is in the midst of business. Nginx is a high-performance HTTP server and reverse proxy server, and can also be used as IMAP/POP3/SMTP proxy server. The Nginx server occupies less memory, has strong concurrency capability and has very wide application scenes.

In the related art, when an enterprise user or a personal user applies a Nginx server, generally, a plurality of Nginx servers are required to work cooperatively to issue an operation instruction to the plurality of Nginx servers for high concurrency and load balancing requirements. Therefore, the operation and maintenance personnel can only manually operate several or tens of servers, and operate the servers one by using the same command line, which results in low operation efficiency.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a server management method, apparatus, computer device, computer-readable storage medium, and computer program product capable of centrally managing a plurality of servers.

In a first aspect, the present application provides a server management method. The method comprises the following steps:

displaying a server management interface, wherein the server management interface comprises a server selection area and at least one management option, and the server selection area comprises identifiers of a plurality of servers;

Determining a plurality of target servers in response to a selection operation of the identities of the plurality of servers;

responding to the selection operation of the management options, executing the management operation corresponding to the management options on the target servers to obtain an execution result;

and displaying the execution result on the server management interface.

In one embodiment, the server management interface further includes a file uploading path selection area, and the management options include a file selection option and a synchronous uploading option;

before the step of executing the management operation corresponding to the management option on the target servers in response to the selection operation of the management option and obtaining an execution result, the method further includes:

responding to the trigger operation of the file uploading path selection area, and acquiring an uploading path of a target file;

responding to the triggering operation of the file selection option to acquire a target file;

the responding to the selection operation of the management option, executing the management operation corresponding to the management option on the target servers to obtain an execution result, and the executing step comprises the following steps:

and responding to the selection operation of the synchronous uploading option, uploading the target file to the target servers based on the uploading path of the target file, and obtaining an execution result, wherein the execution result comprises uploading success and uploading failure.

In one embodiment, the management options include a verification option;

and responding to the selection operation of the verification option, and performing verification operation on the configuration files corresponding to the target servers to obtain an execution result, wherein the execution result comprises correct verification and wrong verification.

In one embodiment, the verifying the configuration files corresponding to the target servers to obtain an execution result includes:

acquiring configuration files corresponding to the target servers;

if the format of the configuration file conforms to a preset grammar rule, determining that the execution result is correct in verification;

and if the format of the configuration file does not accord with the preset grammar rule, determining that the execution result is verification failure.

In one embodiment, the management options include a load option;

And responding to the selected operation of the loading option, and sending a loading instruction to the target servers, wherein the loading instruction is used for enabling the target servers to carry out loading operation on the configuration files corresponding to the target servers, so as to obtain an execution result, and the execution result comprises successful loading and failed loading.

In one embodiment, the method further comprises:

displaying a process management page, wherein the process management page comprises a plurality of process display areas corresponding to a plurality of servers respectively, the process display areas comprise a registration information display sub-area, an operation information display sub-area and at least one operation option, and the at least one operation option comprises a starting option;

responding to the selection operation of the starting option, determining a starting instruction corresponding to the starting option, and sending the starting instruction to the server to start the server, wherein the selection operation is determined according to the registration information displayed in the registration information display sub-area;

receiving a starting result of the server, wherein the starting result comprises first running state information and first port occupation information;

And displaying the first running state information and the occupation condition of the first port in the running information display sub-area.

In one embodiment, the operation options further include a stop option, and the method further comprises:

responding to the selected operation of the stop option, determining that the stop option corresponds to a stop operation instruction, and sending the stop operation instruction to the server to stop operation of the server, wherein the selected operation is determined according to the registration information displayed in the registration information display sub-area;

receiving a stopping result of the server, wherein the stopping result comprises second running state information and second port occupation information;

and displaying the second running state information and the occupation condition of a second port in the running information display sub-area.

In a second aspect, the application further provides a server management device. The device comprises:

the server management system comprises a first display module, a second display module and a display module, wherein the first display module is used for displaying a server management interface, the server management interface comprises a server selection area and at least one management option, and the server selection area comprises identifiers of a plurality of servers;

a selection module for determining a plurality of target servers in response to a selection operation of the identities of the plurality of servers;

The selection module is used for responding to the selection operation of the management options and executing the management operation corresponding to the management options on the target servers to obtain an execution result;

and the second display module is used for displaying the execution result on the server management interface.

In one embodiment, the server management interface further includes a file upload path selection area, and the management options include a file selection option and a synchronous upload option;

the device further comprises:

the first response module is used for responding to the triggering operation of the file uploading path selection area and acquiring the uploading path of the target file;

the second response module is used for responding to the triggering operation of the file selection option and acquiring a target file;

the selection module is specifically used for:

and responding to the selected operation of the synchronous uploading option, uploading the target file to the target servers based on the uploading path of the target file, and obtaining an execution result, wherein the execution result comprises uploading success and uploading failure.

In one embodiment, the management options include a verification option;

the selection module is specifically used for:

In one embodiment, the selecting module is specifically configured to:

acquiring configuration files corresponding to the target servers;

In one embodiment, the management options include a load option;

a selection module specifically configured to:

and responding to the selected operation of the loading option, sending a loading instruction to the target servers, wherein the loading instruction is used for enabling the target servers to carry out loading operation on the configuration files corresponding to the target servers, and obtaining an execution result, and the execution result comprises loading success and loading failure.

In one embodiment, the apparatus further comprises:

the third display module is used for displaying a process management page, the process management page comprises a plurality of process display areas corresponding to a plurality of servers respectively, each process display area comprises a registration information display sub-area, an operation information display sub-area and at least one operation option, and each operation option comprises a starting option;

A third response module, configured to determine, in response to a selection operation on the start option, a start instruction corresponding to the start option, and send the start instruction to the server, so as to start the server, where the selection operation is determined according to the registration information displayed in the registration information display sub-region;

the receiving module is used for receiving a starting result of the server, wherein the starting result comprises first running state information and first port occupation information;

and the fourth display module is used for displaying the first running state information and the occupation condition of the first port in the running information display sub-area.

In one embodiment, the operation options further include a stop option, and the apparatus further comprises:

a fourth response module, configured to determine, in response to an operation of selecting the stop option, that the stop option corresponds to a stop instruction, and send the stop instruction to the server, so as to stop operating the server, where the operation of selecting is determined according to the registration information displayed in the registration information display sub-region; receiving a stopping result of the server, wherein the stopping result comprises second running state information and second port occupation information; and displaying the second running state information and the occupation condition of a second port in the running information display sub-area.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:

responding to the selected operation of the management options, executing the management operation corresponding to the management options on the target servers to obtain an execution result;

and displaying the execution result on the server management interface.

In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:

and displaying the execution result on the server management interface.

In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:

and displaying the execution result on the server management interface.

The server management method, the server management device, the computer equipment, the storage medium and the computer program product comprise the following steps: displaying a server management interface comprising a server selection area and at least one management option, the server selection area comprising an identification of a plurality of servers; determining a plurality of target servers in response to a selection operation of the identities of the plurality of servers; responding to the selected operation of the management options, executing the management operation corresponding to the management options on the target servers to obtain an execution result; and displaying the execution result on the server management interface. By adopting the method, a visual page is provided, a plurality of Nginx servers can be managed in batch, the workload is reduced, the management efficiency of the servers is improved, and production safety risk accidents caused by manual operation errors are avoided.

Drawings

FIG. 1 is a flow diagram illustrating a method for server management in one embodiment;

FIG. 2 is a schematic diagram of a login interface in one embodiment;

FIG. 3 is a schematic diagram of a server selection area in one embodiment;

FIG. 4 is a flowchart illustrating steps of obtaining a target file and an upload path of the target file according to an embodiment;

FIG. 5 is a diagram illustrating results of uploading in one embodiment;

FIG. 6 is a diagram illustrating a verification result in one embodiment;

FIG. 7 is a schematic flow chart of the verification step in one embodiment;

FIG. 8 is a schematic diagram of a server management interface in one embodiment;

FIG. 9 is a flowchart illustrating steps performed by a user in selecting a server in a server selection area in one embodiment;

FIG. 10 is a flowchart illustrating a file upload step in one embodiment;

FIG. 11 is a diagram of an edit interface for a master configuration file, in one embodiment;

FIG. 12 is a flowchart illustrating the editing step of the master configuration file in one embodiment;

FIG. 13 is a flowchart illustrating the steps of starting a server in one embodiment;

FIG. 14 is a flowchart illustrating the step of shutting down the server in one embodiment;

FIG. 15 is a diagram of a process management interface in one embodiment;

FIG. 16 is a block diagram showing the construction of a server management apparatus according to an embodiment;

FIG. 17 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

In an embodiment, a server management method is provided, and this embodiment is exemplified by applying the method to a terminal, it is to be understood that the method may also be applied to a server, and may also be applied to a system including a terminal and a server, and is implemented by interaction between the terminal and the server, where the terminal may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart car-mounted devices, and the like. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device and the like, and the server can be realized by an independent server or a server cluster formed by a plurality of servers. In this embodiment, as shown in fig. 1, the server management method includes the following steps:

And 102, displaying a server management interface.

The server management interface comprises a server selection area and at least one management option, wherein the server selection area comprises the identifications of a plurality of servers.

Specifically, the terminal may display a server management interface corresponding to the server management system in response to a trigger operation of the user. The trigger operation may be a login operation of the user to the server management system, or the like. The server management interface can comprise a server selection area and at least one management option, wherein the server selection area displays the identification of a plurality of servers, and the plurality of servers are servers which are registered in the server management system in advance. The management options are a variety of management operations that may be performed on the server, which may be in the form of virtual buttons.

Alternatively, as shown in fig. 2, it may be a login page of the server management system. The login page may include a prompt information display area, a login information input box, a login option, and a reset option. And the terminal responds to the triggering operation of the user on the identifier of the server management system and displays the login page of the server management system. Specifically, the server management system may be a management system of a Nginx server (a Nginx server management platform), and thus the guidance information displayed in the guidance information display area may be "welcome login to the Nginx server management platform". The user can input login information in a login information input box, and prompt information can be displayed in the login information input box, wherein the prompt information can be 'please input a user name' and 'please input a password'; correspondingly, the login information comprises login account information and login password information, the terminal responds to the input operation of a user in a login information input box, the login account information and the login password information corresponding to the input operation are obtained, the terminal responds to the triggering operation of a user login option, the obtained login account information and the obtained login password information are verified, and if the verification is passed, the terminal can display a server management interface.

Alternatively, the terminal may also display a login page of the server management system and a server management interface without a trigger operation by the user.

Alternatively, the server may be a Nginx server; the process of registering the server in the server management system may be: the server sends registration information to a database corresponding to the server management system, wherein the registration information may include IP address information, authentication name information, password information, SSH and FTP port numbers of the server, directory information where the master configuration file is located, information of department affiliated to the server, information of usage (usage category) of the server, and the like. Based on the registration information of the server, the server management system can be connected with the Nginx server to form a management process, and interactive information can be loaded to the front end of the system to be displayed, so that a user can clearly and clearly view conditions such as a Nginx server list, an operating state and port occupation.

In response to a selection operation of the identities of the plurality of servers, a plurality of target servers are determined, step 104.

Specifically, the user may determine that a plurality of servers need to be managed based on the actual application scenario, and thus, the terminal may determine a plurality of servers selected by the user, that is, a plurality of target servers, in response to a selection operation of the user for the identities of the plurality of servers.

In one example, a server selection area in a server management interface may directly display the identification of multiple rows of servers.

In another example, as shown in fig. 3, the server selection area in the server management interface may be a virtual button, and the terminal may display a pull-down menu interface on the server management interface in response to a triggering operation of the virtual button by the terminal, where the pull-down menu interface displays a plurality of hierarchical levels, and a first hierarchical level may be a plurality of department options distinguished according to affiliation department information of a plurality of servers, and may include a first department option, a second department option, a third department option, and so on. The plurality of options corresponding to the second hierarchy may be a plurality of usage options determined according to usage information of each server, and may include, for example, "develop" usage options, "test" usage options, …, until the last hierarchy, where identifiers of a plurality of servers are displayed.

One possible case may be, for example, that the terminal, in response to a user's trigger operation for any one of the first department option, the second department option, and the third department option, may display an identification of a server for which the subordinate department information coincides with the department option.

Another possible case may be that, in response to a trigger operation of the user on the first department option, the terminal may display a plurality of usage options corresponding to the second hierarchy, which may include a "development" usage option and a "test" usage option, and in response to a trigger operation of the user on the "development" usage option, the terminal may display identifications of a plurality of servers indicating that the affiliation department information coincides with the first department option and that the usage information coincides with the "development" usage option, and the terminal may use the plurality of servers in the first department and used for development usage as target servers.

And 106, responding to the selection operation of the management options, executing the management operation corresponding to the management options on the target servers, and obtaining an execution result.

Specifically, based on a plurality of management options displayed on the server management interface, a user can trigger any one of the management options according to an actual application scene, and the terminal responds to the selection operation of the user on the management options, executes the management operation corresponding to the management option on the plurality of target servers, and obtains an execution result corresponding to the management operation.

Optionally, the terminal may determine a management instruction corresponding to the management option based on an operation of the user for selecting the management option, and send the management instruction to the multiple target servers, so that the multiple target servers may execute the management operation corresponding to the management option, and the multiple target servers obtain an execution result of the management operation and return the execution result to the terminal. The terminal may display the execution result on the server management interface.

Optionally, the terminal may determine a management operation corresponding to the management option based on a selection operation of the user on the management option, and the terminal executes the management operation on the plurality of target servers to obtain an execution result. The terminal may display the execution result on the server management interface.

And step 108, displaying the execution result on the server management interface.

In the server management method, a server management interface including a server selection area and at least one management option is displayed, wherein the server selection area includes identifiers of a plurality of servers. In response to a selection operation of the identities of the plurality of servers, a plurality of target servers is determined. And responding to the selected operation of the management options, executing the management operation corresponding to the management options on the target servers, and obtaining an execution result. And displaying the execution result on the server management interface. By adopting the method, a visual page is provided, a plurality of Nginx servers can be managed in batch, the workload is reduced, the management efficiency of the servers is improved, and production safety risk accidents caused by manual operation errors are avoided.

In one embodiment, the server management interface further comprises a file uploading path selection area, and the management options comprise a file selection option and a synchronous uploading option.

Correspondingly, as shown in fig. 4, before the step of executing the management operation corresponding to the management option on the multiple target servers in response to the operation of selecting the management option, and obtaining an execution result, the server management method further includes:

step 202, responding to the trigger operation of the file uploading path selection area, and acquiring the uploading path of the target file.

Specifically, the server management interface displayed by the terminal further includes a file upload path selection area, where the file upload path selection area may be an input box, and the trigger operation on the file upload path selection area may be an input operation of a user. And the terminal responds to the input operation of the user and acquires the uploading path of the target file corresponding to the input operation. The upload path of the target file may be default "/data/nginx/app _ conf/".

And step 204, responding to the triggering operation of the file selection option, and acquiring the target file.

Specifically, a server management interface displayed by the terminal includes a plurality of management options, where the management options may be a file selection option and a synchronous upload option. And the terminal responds to the input operation of the user and acquires the uploading path of the target file corresponding to the input operation. The terminal responds to the triggering operation (selecting operation) of the user on the file selecting option, and the terminal can acquire the target file in the preset file directory.

Correspondingly, the specific execution process of step 106 "responding to the operation selected for the management option, executing the management operation corresponding to the management option on the multiple target servers, and obtaining the execution result" includes:

and responding to the selection operation of the synchronous uploading option, uploading the target file to a plurality of target servers based on the uploading path of the target file, and obtaining an execution result.

The execution result comprises uploading success and uploading failure.

In particular, the management option may be a synchronized upload option. And the terminal responds to the input operation of the user and acquires the uploading path of the target file corresponding to the input operation. And the terminal responds to the triggering operation (selecting operation) of the user on the file selecting option and acquires the target file in the preset file directory. And the terminal responds to the selection operation of the user on the synchronous uploading option, and synchronously uploads the target file to a plurality of target servers selected by the user through the uploading path of the target file based on the obtained uploading path of the target file. The management operation is a file synchronization upload operation.

In this way, as shown in fig. 5, the execution result is displayed on the server management interface displayed on the terminal.

In this embodiment, the repeated operation of uploading the application configuration file by the Nginx server cluster can be completed by one-key operation of the visual Web page, so that the workload is greatly reduced.

In one embodiment, the management options include a verification option.

Specifically, the terminal may generate the verification instruction in response to a user selecting the verification option. The terminal respectively sends the verification instructions to a plurality of target servers, so that the target servers can verify the configuration files of the target servers, wherein the configuration files can comprise a main configuration file or an application configuration file. And the target server checks each configuration file based on the checking instruction to obtain a checking result, and returns the checking result to the terminal respectively.

In one possible implementation manner, the terminal may generate the verification instruction in response to the user selecting the verification option. The terminal can acquire the configuration files corresponding to the target servers based on the verification instruction, and verify each configuration file.

In this way, as shown in fig. 6, the execution result (verification result) may be displayed on the server management interface displayed on the terminal, and for example, the identification information of the target server and the execution result of the target server may be displayed separately. The identification information of the target server may be: "Server 85.18.125.192," the execution result may be "check correct".

In an embodiment, as shown in fig. 7, a specific execution process of "performing a verification operation on configuration files corresponding to a plurality of target servers to obtain an execution result" in step 106 includes:

step 302, obtaining configuration files corresponding to a plurality of target servers.

Specifically, the configuration file corresponding to the target server may be a master configuration file or an application configuration file. The terminal can obtain the configuration files corresponding to the target servers based on the verification flexibility; the terminal can also send the check instruction to the target server so that the target server can obtain the corresponding configuration file.

And step 304, if the format of the configuration file conforms to the preset grammar rule, determining that the execution result is correct.

Specifically, the terminal checks the grammar format of the configuration file according to the preset grammar rule, and if the grammar format of the configuration file conforms to the preset grammar rule, the configuration file can be determined to be normal, and the check result can be correct.

And step 306, if the format of the configuration file does not accord with the preset grammar rule, determining that the execution result is verification failure.

Specifically, the terminal checks the syntax format of the configuration file according to a preset syntax rule, and if the syntax format of the configuration file does not conform to the preset syntax rule, it can be determined that the configuration file is abnormal, and the check result may be a check error.

In one embodiment, the management options include a load option.

in response to the selection operation of the loading option, the terminal may send a loading instruction to the multiple target servers based on an SSH (secure shell protocol) technology, where the loading instruction is used to enable the multiple target servers to perform a loading operation on the configuration files corresponding to the multiple target servers, so as to obtain an execution result, where the execution result includes a successful loading and a failed loading. The function of different operations completed by the terminal according to different selections of the user on the loading option and the verification option is as shown in the following table 1:

TABLE 1

In one example, the user may perform a trigger operation on the configuration deployment option, and the terminal displays the server management interface in response to the user's trigger operation on the configuration deployment option, which may be displayed on the navigation page. The server management interface may be as shown in fig. 8, and includes a server selection area, a file upload path selection area, and a plurality of management options including a file selection option, a synchronous upload option, a verification option, a load option, an edit application configuration file option, and a submit change option. The server management interface further comprises a prompt message display area, and the prompt message displayed in the prompt message display area may be: "application profiles can only be uploaded (. conf), one at a time. If the server has the file with the same name, the file can be automatically backed up in the current directory ". The prompt message displayed in the prompt message display area may further include: "select file then choose right encoding (default UTF-8), click on file name to preview content. And each time the application configuration file is uploaded or submitted, clicking ' checking configuration ' and ' loading configuration ' to finish checking and deploying '.

Alternatively, as shown in fig. 9, the user may select a server in the server selection area, for example, a pull-down menu interface may be displayed on the server management interface, the pull-down menu interface displaying a plurality of hierarchical levels, the first hierarchical level may be a plurality of department options distinguished according to affiliate department information of a plurality of servers, and may include a department option of developing one part, a department option of developing two parts, and so on. The plurality of options corresponding to the second level may include a "develop" use option, a "test" use option, and so on. The user can select a department option for developing a part and a use option for "development", and the terminal can determine whether the servers corresponding to the selection operation are "85.18.125.192" and "85.18.125.193" in response to the selection operation by the user. The server management interface further comprises a server display area, and the terminal can display the identification information of the server in the server display area.

In this way, the user may input an upload path of the target file in the file upload path selection area, for example, "/data/nginx/app _ conf/" default by the system may be, and the upload path input by the user according to the actual application scenario may be. The terminal responds to the triggering operation (selecting operation) of the user on the file selecting option, and obtains the target file in the preset file directory. The terminal responds to the selection operation of the user on the synchronous uploading option and the uploading path of the target file input by the user, and can synchronously upload the target file to a plurality of target Nginx servers selected by the user to complete the synchronous uploading operation of the target file.

Specifically, the terminal may perform an authentication connection with each Nginx server in the Nginx server cluster and establish a file transfer communication based on the FTP file transfer technology, and each remote Nginx server opens an instruction monitoring interface (21 port) to start monitoring and waits for a connection with the terminal. The terminal (for example, the spring boot background) may serve as a client to initiate a connection request, and the connection request is sent to each target server, so that a control connection is established. Each of the Nginx servers controls connection establishment in response to the connection request. In this way, the terminal can upload the target file (local file) to each target server included in the list of the Nginx server by one key.

Specifically, the terminal needs to traverse a server list composed of a plurality of target servers, and sequentially upload a target file selected by the user to a specified file storage directory of each target server. And the terminal responds to the input operation of the user on the file uploading path selection area and acquires the uploading path of the target file.

Optionally, the terminal may include a front-end page and a back-end server, and the back-end server may be a spring boot back-end. In this way, the front-end page may send a file upload request to the background server, where the file upload request includes a server list composed of multiple target servers and an upload path of a target file. The background server will traverse the server list and connect with each target server remote server to establish communication, and the specific uploading process may be to query whether an uploading path (user-defined uploading path) of the target file exists as shown in fig. 10. If the path uploaded by the user through the user definition does not exist in the target server, the background server can display prompt information on a front-end page, and the prompt information can be 'whether to create the path' and can ensure humanized setting. The front end page may save the personalized upload path in response to a user triggering the create option. In this way, the background server can synchronously upload the target file to the directory corresponding to the personalized upload path newly created by the user in the server based on the upload path of the target file.

According to the method and the device, repeated operation of uploading the application configuration file in the Nginx server cluster by a user can be completed through one-key operation of the Web interface, and the workload is greatly reduced.

In one example, the server management method further comprises: and displaying an editing interface.

Specifically, the user selects a target server from the server drop-down box, that is, the user needs to edit a configuration file of the target server. The configuration file of the target server includes an application configuration file and a master configuration file. An application profile editing option and a main profile editing option may be displayed on the editing interface.

Alternatively, in response to the user triggering an operation with respect to the main profile editing option, as shown in fig. 11, the terminal may be an editing interface of the main profile. The editing interface of the main configuration file comprises a server selection area, an nginx.conf editing option, a change submitting option, an encoding format selection area, a configuration checking option and a configuration loading option, and further comprises a prompt area, wherein prompt information displayed in the prompt area can be' prompt: please select the server and the encoding format (default UTF-8) to edit the master configuration file and submit, if the server has the file with the same name, the backup will be automatically performed in the current directory, and each time the master configuration file is submitted, the 'check configuration' button and the 'load configuration' button are clicked to complete the check and deployment ". The editing process of the main configuration file may be that, as shown in fig. 12, the terminal determines the target server in response to a triggering operation of the user on the server selection area. The terminal can respond to the triggering operation of the user for editing the nginx.conf option, and the main configuration file is displayed on the front-end interface. The user can browse, check and edit the content of the file, finally click to submit the change, the terminal responds to the triggering operation of the user on the option of submitting the change, obtains the latest file after the user changes, and submits the latest file to the target server.

Under the condition that the name of the file changed by the user has the same name, the terminal can acquire real-time date information and update the name information of the file according to the real-time date information. The file with the same name is used as a new file name for backup according to a date format, and online editing and submission of the configuration file are completed.

Specifically, the back-end logic of the module is that the system designates a remote Nginx server through the SSH service connection mentioned above, sends an instruction for viewing text content, the server executes the instruction, for example, the instruction for viewing the main configuration file content is "cat/usr/local/open/Nginx/nginx.conf", obtains the file text content, and finally the SpringBoot background sends the file content to Vue front-end to be displayed to the user. As shown in fig. 12, for the main configuration file, the user directly edits the contents of the modified file, and for the application configuration file, the user needs to fill in the directory and the file name of the file to be edited, and then edit the directory and the file name. The terminal obtains the application configuration file based on the directory information of the location of the application configuration file, displays the application configuration file at the front end, after the user finishes editing and modifying, clicks a 'submit modify' button, the system submits the content of the file modified by the user to the appointed directory of the server, the front end Vue sends a request to the spring boot, the content of the file modified by the user, the file name and the file directory are sent to the background, the content of the file is written into a temporary file by the background, then the spring boot background is connected with the server through the FTP technology mentioned above and prepares the temporary file to upload, before uploading, the server is connected and accessed through the SSH technology to check whether the directory sent by the user has the file with the same name or not, if so, a timestamp in the format of 'yyyyyyMMyHHmmss' is added to the file on the server as a new file name, the file is backed up, then the temporary file is uploaded to a file directory uploaded by a user, if the server does not have the file with the same name in the directory, the file is directly uploaded, and the file modified by the user is used as the latest file.

According to the server management method provided by the embodiment of the invention, the online editing and submitting of the configuration file replace the traditional command line operation of a user, so that the error rate is reduced, and the file is backed up according to the change date and is convenient to restore later.

And the server group partitioning module is used for classifying the Nginx servers recorded in the database according to department categories and use purposes, wherein the research and development are divided into a first research and development part, a second research and development part, a third research and development part and the like according to the department categories, and the use purposes are divided into development and testing. The front end is based on a CascaderPro custom cascade selector component to bind departments and purposes to which the Nginx server belongs. When a user accesses the page, the Spring Boot background sends department numbers of all servers stored in the database to a first-level menu of a drop-down box of a front-end cascade selector Vue, when the user clicks the first-level menu of the cascade selector to select a certain department server, the Vue front end sends a request for loading the use of the server according to the department selected by the user to the Spring Boot background, after the Spring Boot background receives the request, the Spring Boot background inquires the database according to the sent department numbers to obtain use information and returns the use information to the Vue front end, the user selects the use of the server of the second-level menu, the Vue front end sends the request to the background again, the background accurately inquires IP information according to the department and the use and sends the IP information to the front end for display, and the flow chart is as shown in FIG. 11. The technology realizes the dynamic loading drop-down frame display of the server information. The user can select a single server to operate or select a server group to operate. The Nginx servers are integrated and classified through the design of a cascade selector assembly, so that a user can view and use the Nginx servers more intuitively and clearly, and the working efficiency is improved.

In one embodiment, as shown in fig. 13, the server management method further includes:

step 402, displaying a process management page.

The process management page comprises a plurality of process display areas corresponding to the servers respectively, wherein the process display areas comprise a registration information display sub-area, an operation information display sub-area and at least one operation option, and the at least one operation option comprises a starting option.

Specifically, the terminal may display the process management interface in response to a user's trigger operation for the page switching option. The terminal can also respond to the triggering operation of the user on the process management option and display the process management interface.

And step 404, in response to the selection operation of the starting option, determining a starting instruction corresponding to the starting option, and sending the starting instruction to the server so as to start the server.

And the selection operation is determined according to the registration information displayed in the registration information display sub-area.

Specifically, the user determines the target server according to the actual application scene and the registration information displayed in the registration information display sub-region. In a process display area corresponding to the target server, the terminal responds to the trigger operation of the user on the starting option, determines a starting instruction corresponding to the starting option, and sends the starting instruction to the target server so as to start the target server.

Step 406, receiving the starting result of the server.

The starting result comprises first running state information and first port occupation information.

And step 408, displaying the first running state information and the occupation condition of the first port in the running information display sub-area.

Specifically, the first operating state information includes various operating states such as normal, abnormal, and off.

In one embodiment, the operation options further include a stop option.

Accordingly, as shown in fig. 14, the server management method further includes:

step 502, in response to the operation of selecting the stop option, determining that the stop option corresponds to a stop instruction, and sending the stop instruction to the server so as to stop running to the server.

Wherein the selection operation is determined according to the registration information displayed in the registration information display sub-area.

Step 504, receiving the stopping result of the server.

And the stopping result comprises second running state information and second port occupation information.

And step 506, displaying the second operation state information and the occupation condition of the second port in the operation information display sub-area.

The process management page comprises a plurality of process display areas corresponding to the servers respectively, wherein each process display area comprises a registration information display sub-area, an operation information display sub-area and at least one operation option, and the at least one operation option comprises a starting option.

In one example, as shown in fig. 15, the terminal may display a process management interface in response to a user's login operation to the server management system. The process management interface comprises a plurality of process display areas corresponding to a plurality of servers respectively, wherein each process display area comprises a registration information display sub-area, an operation information display sub-area and at least one operation option, and the at least one operation option comprises a starting option, a stopping option, a hot loading option and the like.

That is, the terminal displays a list of the Nginx server information, the running status of each Nginx server, the situation of occupied ports, and buttons for operating the Nginx process, including start, quick stop, ordered stop, and hot load. The instructions corresponding to the respective buttons are shown in table 2 below. When a certain Nginx server is in a running state and is in a non-starting state, a user clicks a starting button, the Nginx server is started completely, the running state is displayed normally, the port occupation condition is displayed, and the starting button is in a non-clickable state, so that the Nginx server is started. When a user wants to stop a certain running Nginx server, the user only needs to click a stop button as required to stop the Nginx service, at this time, the running state is changed into stop, the port occupation display is not started, the start button display is clickable, other buttons are changed into non-clickable states, and the stop operation of the Nginx service is completed. Similarly, clicking the hot load button designates a server to perform hot load process operation.

TABLE 2

Process and system for managing a process	Description of the preferred embodiment	Operation/presentation
			Starting up	Starting a current server	./nginx
Quick stop	Quickly stopping a current server	./nginx-s stop
			Ordered stopping	Orderly stopping current server	./nginx-s quit
Thermal loading	Current server hot load	./nginx-s reload
			Operating state	Viewing current server operating state	Normal, abnormal, shut down
Port occupation	Checking current server port occupation	ss-anp\|grep`nginxPID`

Specifically, the terminal may include a front-end interface and a back-end server, where the back-end server (a SpringBoot backend) may perform authentication connection with each of the Nginx servers and establish communication based on an SSH technique, and a specific scheme is that each of the Nginx servers serves as a server, the SpringBoot backend serves as a client that carries an IP and a port number of each of the Nginx servers stored in the query database and sends an SSH connection request to the server, and the server performs encryption authentication to check a login name and a password, and if the authentication passes, the connection establishment is successful. And the front-end user clicks a certain process button for process management, and the SpringBoot background sends an operation instruction corresponding to the process button to each Nginx server. And each Nginx server receives and executes the instruction, returns an execution result to the SpringBoot background, and then sends the execution result to the front-end page for displaying.

The method provided by the application can realize the functions of starting, quick stopping, ordered stopping, hot loading, the current running state of the server, the current port occupation condition of the server and the like of the Nginx server. After the Nginx servers are successfully started, the backend server may add the real-time running state information and the port occupation information of the servers to a preset static list, as shown in table 3 below, where the preset static list includes the process numbers and the port numbers of the servers.

The front end directly reads the static list data to display the static list data to the user, so that the data response time is greatly shortened, and the user experience is improved. When a user modifies server information or changes a server process, the system correspondingly updates the static list to achieve a data synchronization effect, for example, the user clicks a button for stopping the Nginx server at the front end, the Nginx service is terminated, the user clicks a start button again, the Nginx service is started, at this time, the process number of the Nginx server changes, the corresponding port number occupied by the Nginx server also numbers, the logic for updating the process number and the port number is that the current end requests to send to the background, the background is connected with a remote server, the process number and the port occupation of the latest Nginx server are obtained, the static list established in the front is updated by using the latest information, then the front end reads the list, each time of change is guaranteed, and the front end can read the latest server state and display the latest server state to the user. The user logs in the system for operation, checks list information of all servers, can also inquire a concerned server in a paging mode, checks the current running state and port occupation condition of all servers, clicks a process operation button to control the operation of the Nginx server in a one-key mode, the Nginx server cluster process operated by the user is abstracted to an interface for management through the function of a process management module, and the Nginx server cluster can be managed more intuitively and efficiently.

TABLE 3

Aiming at the problems occurring in the user operation server cluster, the invention designs and realizes a Nginx server cluster visual management method and system. The system is based on a front-end and back-end separation framework of the B/S, wherein the front end is realized by using Vue technology, and the back end is realized by using SpringBoot technology. The Web interface platform capable of enabling a user to visually operate the Nginx server cluster is provided, and mainly comprises a plurality of functional modules of process management, synchronous uploading, server group partition management, online editing and submitting of configuration files, verification and loading of the configuration files and the like, so that the problem of repeated operation of the current Nginx server cluster is solved, the workload and the misoperation rate are greatly reduced, and the working efficiency is improved.

It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not limited to being performed in the exact order illustrated and, unless explicitly stated herein, may be performed in other orders. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be rotated or alternated with other steps or at least a part of the steps or stages in other steps.

Based on the same inventive concept, the embodiment of the application also provides a server management device for implementing the server management method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the method, so specific limitations in one or more server management device embodiments provided below may refer to the limitations on the server management method in the foregoing, and details are not described here.

In one embodiment, as shown in fig. 16, there is provided a server management apparatus 600 including:

the first display module 601 is configured to display a server management interface, where the server management interface includes a server selection area and at least one management option, and the server selection area includes identifiers of multiple servers.

A selection module 602 for determining a plurality of target servers in response to a selection operation of the identities of the plurality of servers.

The selecting module 603 is configured to, in response to the operation of selecting the management option, execute the management operation corresponding to the management option on the multiple target servers to obtain an execution result.

And a second display module 604, configured to display the execution result on the server management interface.

the device further comprises:

the first response module is used for responding to the trigger operation of the file uploading path selection area and acquiring the uploading path of the target file;

a selection module specifically configured to:

In one embodiment, the management options include a verification option;

a selection module specifically configured to:

and responding to the selected operation of the verification option, performing verification operation on the configuration files corresponding to the target servers to obtain an execution result, wherein the execution result comprises correct verification and wrong verification.

In one embodiment, the selecting module is specifically configured to:

Acquiring configuration files corresponding to the target servers;

In one embodiment, the management options include a load option;

the selection module is specifically used for:

In one embodiment, the apparatus further comprises:

A third response module, configured to determine, in response to an operation of selecting the start option, a start instruction corresponding to the start option, and send the start instruction to the server, so as to start the server, where the operation of selecting is determined according to the registration information displayed in the registration information display sub-area;

The respective modules in the server management apparatus 600 described above may be wholly or partially implemented by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure thereof may be as shown in fig. 17. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used to store the XX data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a server management method.

It will be appreciated by those skilled in the art that the configuration shown in fig. 17 is a block diagram of only a portion of the configuration associated with the present application, and is not intended to limit the computing device to which the present application may be applied, and that a particular computing device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

In an embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.

In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, carries out the steps in the method embodiments described above.

It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.

It should be noted that the method and apparatus in the embodiments of the present disclosure may be used in the field of big data technology, and may be used in the field of financial technology or other related fields.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the various embodiments provided herein may be, without limitation, general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, or the like.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A server management method, the method comprising:

and displaying the execution result on the server management interface.

2. The method of claim 1, wherein the server management interface further comprises a file upload path selection area, and the management options comprise a file selection option and a synchronous upload option;

before the step of executing the management operation corresponding to the management option on the target servers in response to the selected operation on the management option to obtain an execution result, the method further includes:

responding to the triggering operation of the file uploading path selection area, and acquiring an uploading path of a target file;

the executing, in response to the operation of selecting the management option, the management operation corresponding to the management option on the target servers to obtain an execution result includes:

3. The method of claim 1, wherein the management options include a verification option;

4. The method according to claim 3, wherein the performing the verification operation on the configuration files corresponding to the target servers to obtain the execution result includes:

acquiring configuration files corresponding to the target servers;

5. The method of claim 1, wherein the management options include a load option;

6. The method of any one of claims 1 to 5, further comprising:

responding to the selected operation of the starting option, determining a starting instruction corresponding to the starting option, and sending the starting instruction to the server to start the server, wherein the selected operation is determined according to the registration information displayed in the registration information display sub-area;

7. The method of claim 6, wherein the operational options further include a stop option, the method further comprising:

8. A server management apparatus, characterized in that the apparatus comprises:

The selection module is used for responding to the selection operation of the management options, executing the management operation corresponding to the management options on the target servers and obtaining an execution result;

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.

10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.

11. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 7 when executed by a processor.