CN104598158A - System and method for processing system event - Google Patents
System and method for processing system event Download PDFInfo
- Publication number
- CN104598158A CN104598158A CN201310526819.7A CN201310526819A CN104598158A CN 104598158 A CN104598158 A CN 104598158A CN 201310526819 A CN201310526819 A CN 201310526819A CN 104598158 A CN104598158 A CN 104598158A
- Authority
- CN
- China
- Prior art keywords
- system event
- memory storage
- event
- storage
- memory
- 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
- 238000000034 method Methods 0.000 title claims abstract description 28
- 230000005055 memory storage Effects 0.000 claims description 53
- 230000001360 synchronised effect Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 6
- 230000008520 organization Effects 0.000 description 2
- 108010028984 3-isopropylmalate dehydratase Proteins 0.000 description 1
- 230000006870 function Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0608—Saving storage space on storage systems
Abstract
The invention provides a system and a method for processing a system event. The method comprises the following steps: sending a request that one section of storage space on a storage device of a server is configured for storing the system event to a server; when the system even which needs to be recorded by BMC (Baseboard management Controller) exists on the server, judging whether the storage space of a memory arranged on the BMC is insufficient or not; when the storage space of the memory arranged on the BMC is sufficient, simultaneously storing the system event to memory and the storage space required on the storage device; and when the storage space of the memory arranged on the BMC is insufficient, storing the system event to the storage space required on the storage device, and notifying a system administrator to update the system event stored in the storage device. The system and the method can be used for conveniently and integrally recording the system event.
Description
Technical field
The present invention relates to a kind of event handling system and method, particularly relate to a kind of system event disposal system and method.
Background technology
Server is owing to needing the stability of height, so all can by the BMC(Baseboard Management Controller of server, baseboard management controller) system event (System event) that server occurs is stored in the storage area that BMC carries, but the built-in storage area of BMC very limited, to such an extent as to after space has been expired, new system event cannot be stored, cause usually having failed to record important system event.Thus.The system operator of server cannot be understood server and there occurs which kind of phenomenon on earth, also has no way of carrying out fault handling.In addition, method due to current storage system event is all that the storage area utilizing BMC to carry stores, therefore system operator also cannot carry out index and the Local Edit of system event, when the storage space that BMC carries is filled with time, whole system events also can only empty by system operator, no matter so important system event or unessential system event all will once be cleared, lose the importance of register system event.
Summary of the invention
In view of above content, be necessary to provide a kind of system event disposal system and method, by simultaneously storage system event on server and baseboard management controller, and when the memory space inadequate of baseboard management controller, the system event that update server stores and be synchronized with on baseboard management controller, ensures accuracy and the importance of system event record.
A kind of system event disposal system, run on the baseboard management controller BMC on server, this system comprises: request module, for send a configuration server memory storage the preceding paragraph storage space with the request of storage system event to server; Judge module, for when server there being system event need BMC to record, judges that whether the storage space of the storer that BMC carries is not enough; Memory module, for when the memory storage space judging that BMC carries is enough, this system event is stored in simultaneously in the storage space that storer and memory storage are asked, and when the memory storage space judging that BMC carries is not enough, this system event is stored to the storage space that memory storage is asked; Notification module, for when the memory storage space judging that BMC carries is not enough, notifies that system manager upgrades the system event stored in memory storage.
A kind of system event disposal route, be applied on the baseboard management controller BMC on server, the method comprises: request step: the memory storage the preceding paragraph storage space sending a configuration server with the request of storage system event to server; Determining step: when server there being system event need BMC to record, judges that whether the storage space of the storer that BMC carries is not enough; Storing step: when the memory storage space judging that BMC carries is enough, this system event is stored in simultaneously in the storage space that storer and memory storage are asked; Notifying process: when the memory storage space judging that BMC carries is not enough, this system event is stored to the storage space that memory storage is asked and notifies that system manager upgrades the system event stored in memory storage.
Compared to prior art, system event disposal system provided by the invention and method, by simultaneously storage system event on server and baseboard management controller, and when the memory space inadequate of baseboard management controller, the system event that update server stores and be synchronized with on baseboard management controller, make system manager can continue suitably delete and upgrade according to the importance of system event, also ensure that simultaneously and can not to be failed to record when there being new system event generation.Ensure accuracy and the importance of system event record.
Accompanying drawing explanation
Fig. 1 is the Organization Chart of present system event handling system preferred embodiment.
Fig. 2 is the functional block diagram of present system event handling system preferred embodiment.
Fig. 3 is the process flow diagram of present system event-handling method preferred embodiment.
Main element symbol description
| Server | 1 |
| Processor | 10 |
| BMC | 11 |
| Disposal system | 12 |
| Storer | 13 |
| Memory storage | 14 |
| Request module | 120 |
| Judge module | 121 |
| Memory module | 122 |
| Notification module | 123 |
| Synchronization module | 124 |
Following embodiment will further illustrate the present invention in conjunction with above-mentioned accompanying drawing.
Embodiment
As shown in Figure 1, be the Organization Chart of present system event handling system preferred embodiment.Described system event disposal system 12(is hereinafter referred to as " disposal system 12 ") run on the BMC11(Baseboard Management Controller of server 1, baseboard management controller) on.Described server 1 also comprises processor 10 and memory storage 14.
Described processor 10 for performing the program code of each program segment in described disposal system 12, to realize the function (referring to the description of Fig. 2) of each functional module in disposal system 12.Described memory storage 14 is for the related data of storage server 1.
Communicated by IPMI order (Intelligent Platform Management Interface, intelligent platform supervision interface) between described BMC11 and server 1.Described BMC11 self, with a storer 13, during for there being system event (System event) when server 1, stores this system event.The storage space of this storer 13 has certain size restriction.
As shown in Figure 2, be the functional block diagram of preferred embodiment of disposal system 12 of the present invention.Described disposal system 12 comprises request module 120, judge module 121, memory module 122, notification module 123 and synchronization module 124.
Described request module 120 is for sending one section of storage space on a configuration store device 14 with the request of storage system event to server 1.
Described judge module 121, for when server 1 there being system event need BMC to record, judges that whether the storage space of the storer 13 on BMC11 is not enough.Described judge module 121 can by judging that the size of the system event whether size of the residual memory space in current storage 13 is less than current needs record judges that whether the storage space of storer 13 is not enough.If current residual memory space size is less than the size of the system event of current needs record, represent the memory space inadequate of storer 13.If current residual memory space size is more than or equal to the size of the system event of current needs record, represent that the storage space of storer 13 is enough.In other preferred embodiments, if the size of the system event recorded is more fixing, whether whether described judge module 121 also can be less than a default threshold values by the remaining space judging in current storage 13, not enough to judge the storage space of storer 13.
This system event, for when judging that the storage space of the storer 13 on BMC11 is enough, is stored in the storage space that storer 13 and memory storage 14 are asked by described memory module 122 simultaneously.This system event also for when the memory space inadequate of determining storage device 13, is stored to the storage space that memory storage 14 is asked by described memory module 122.
Described notification module 123, for when the memory space inadequate of determining storage device 13, notifies the system event that system manager's update server 1 stores in memory storage 14.Described notification module 123 by mail or can transmit the prompting modes such as SNMP trap(Simple Network Management Protocol is self-trapping, notifies that system manager processes.System manager can delete system event inessential or processed in memory storage 14, to upgrade the system event in memory storage 14.
Described synchronization module 124 for after having upgraded when the system event that memory storage 14 stores, by the system event stores synchronized after renewal in storage space that memory storage 14 is asked in the storer 13 of BMC11.
As shown in Figure 3, be the process flow diagram of preferred embodiment of present system event-handling method.Should understand, system event disposal route of the present invention is not limited to step in process flow diagram shown in Fig. 3 and order.According to different embodiments, the step in process flow diagram shown in Fig. 3 can increase, remove or change order.
Step S111, request module 120 sends one section of storage space on a configuration store device 14 with the request of storage system event to server 1.
Step S112, when server 1 there being system event need BMC11 to record, judge module 121 judges that whether the storage space of the storer 13 on BMC11 is not enough.Described judge module 121 can by judging that the size of the system event whether size of the residual memory space in current storage 13 is less than current needs record judges that whether the storage space of storer 13 is not enough.If current residual memory space size is less than the size of the system event of current needs record, represent the memory space inadequate of storer 13, flow process enters step S113.If current residual memory space size is more than or equal to the size of the system event of current needs record, represent that the storage space of storer 13 is enough, flow process enters step S114.In other preferred embodiments, if the size of the system event recorded is more fixing, whether whether described judge module 121 also can be less than a default threshold values by the remaining space judging in current storage 13, not enough to judge the storage space of storer 13.
Step S113, this system event is stored in the storage space that storer 13 and memory storage 14 are asked by memory module 122 simultaneously, and flow process terminates.
Step S114, this system event is stored to the storage space that memory storage 14 is asked by memory module 122, and notification module 123 notifies the system event of storage in memory storage 14 in system manager's update server 1.System manager can delete system event inessential or processed in memory storage 14, to upgrade the system event in memory storage 14.
Step S115, after the system event that memory storage 14 stores has upgraded, synchronization module 124 by the system event stores synchronized after renewal in storage space that memory storage 14 is asked in the storer 13 of BMC11.
Above embodiment is only in order to illustrate technical scheme of the present invention and unrestricted, although with reference to above better embodiment to invention has been detailed description, those of ordinary skill in the art should be appreciated that and can modify to technical scheme of the present invention or be equal to the spirit and scope of replacing and should not depart from technical solution of the present invention.
Claims (8)
1. a system event disposal route, be applied on the baseboard management controller BMC on server, it is characterized in that, the method comprises:
Request step: send memory storage the preceding paragraph storage space of a configuration server with the request of storage system event to server;
Determining step: when server there being system event need BMC to record, judges that whether the storage space of the storer that BMC carries is not enough;
Storing step: when the memory storage space judging that BMC carries is enough, this system event is stored in simultaneously in the storage space that storer and memory storage are asked;
Notifying process: when the memory storage space judging that BMC carries is not enough, this system event is stored to the storage space that memory storage is asked and notifies that system manager upgrades the system event stored in memory storage.
2. the system as claimed in claim 1 event-handling method, is characterized in that, the method also comprises:
Synchronizing step: after the system event that memory storage stores has upgraded, by the system event stores synchronized after upgrading in storage space that memory storage is asked in the storer of BMC.
3. the system as claimed in claim 1 event-handling method, is characterized in that, by judging that the size of the residual memory space on storer is less than the size of the system event of described needs record, the memory space inadequate of determining storage device in described determining step.
4. the system as claimed in claim 1 event-handling method, is characterized in that, the system event stored in described renewal memory storage refers to delete the inessential or processed system event stored in memory storage, to upgrade the system event in memory storage.
5. a system event disposal system, run on the baseboard management controller BMC on server, it is characterized in that, this system comprises:
Request module, for send a configuration server memory storage the preceding paragraph storage space with the request of storage system event to server;
Judge module, for when server there being system event need BMC to record, judges that whether the storage space of the storer that BMC carries is not enough;
Memory module, for when the memory storage space judging that BMC carries is enough, this system event is stored in simultaneously in the storage space that storer and memory storage are asked, and when the memory storage space judging that BMC carries is not enough, this system event is stored to the storage space that memory storage is asked;
Notification module, for when the memory storage space judging that BMC carries is not enough, notifies that system manager upgrades the system event stored in memory storage.
6. system event disposal system as claimed in claim 5, it is characterized in that, this system also comprises:
Synchronization module, after having upgraded when the system event that memory storage stores, by the system event stores synchronized after upgrading in storage space that memory storage is asked in the storer of BMC.
7. system event disposal system as claimed in claim 5, is characterized in that, described judge module is by judging that the size of the residual memory space on storer is less than the size of the system event of described needs record, the memory space inadequate of determining storage device.
8. system event disposal system as claimed in claim 5, is characterized in that, the system event stored in described renewal memory storage refers to delete the inessential or processed system event stored in memory storage, to upgrade the system event in memory storage.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310526819.7A CN104598158B (en) | 2013-10-31 | 2013-10-31 | system event processing system and method |
| CN201711471272.XA CN108170577B (en) | 2013-10-31 | 2013-10-31 | Server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310526819.7A CN104598158B (en) | 2013-10-31 | 2013-10-31 | system event processing system and method |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711471272.XA Division CN108170577B (en) | 2013-10-31 | 2013-10-31 | Server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104598158A true CN104598158A (en) | 2015-05-06 |
| CN104598158B CN104598158B (en) | 2018-03-02 |
Family
ID=53123986
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711471272.XA Active CN108170577B (en) | 2013-10-31 | 2013-10-31 | Server |
| CN201310526819.7A Active CN104598158B (en) | 2013-10-31 | 2013-10-31 | system event processing system and method |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711471272.XA Active CN108170577B (en) | 2013-10-31 | 2013-10-31 | Server |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN108170577B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111611193A (en) * | 2019-02-22 | 2020-09-01 | 阿里巴巴集团控股有限公司 | Event processing method, device and equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100205600A1 (en) * | 2009-02-06 | 2010-08-12 | Inventec Corporation | Simulation method for realizing large batches and different kinds of baseboard management controllers using a single server |
| CN102073599A (en) * | 2009-11-23 | 2011-05-25 | 英业达股份有限公司 | System event log recording method |
| CN102262570A (en) * | 2010-05-28 | 2011-11-30 | 英业达股份有限公司 | Method for updating fan control table |
| CN102455950A (en) * | 2010-10-28 | 2012-05-16 | 鸿富锦精密工业（深圳）有限公司 | Firmware recovery system and method of base board management controller |
| CN102467399A (en) * | 2010-11-18 | 2012-05-23 | 鸿富锦精密工业（深圳）有限公司 | Firmware updating system and method for baseboard management controller |
| US20130212430A1 (en) * | 2012-02-09 | 2013-08-15 | Hon Hai Precision Industry Co., Ltd. | Electronic device with firmware recovery function and method for recovering firmware |
| CN103378986A (en) * | 2012-04-28 | 2013-10-30 | 鸿富锦精密工业（深圳）有限公司 | System event log recording system and method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100452725C (en) * | 2007-02-02 | 2009-01-14 | 杭州华三通信技术有限公司 | Log backup method and system unit and device for implementing the same |
| TWI414939B (en) * | 2009-10-22 | 2013-11-11 | Inventec Corp | Server monitoring method |
| JP4891388B2 (en) * | 2009-12-28 | 2012-03-07 | 株式会社エスディー | System event log system |
| CN102479162A (en) * | 2010-11-22 | 2012-05-30 | 英业达股份有限公司 | Computer system and method for recording system event log |
-
2013
- 2013-10-31 CN CN201711471272.XA patent/CN108170577B/en active Active
- 2013-10-31 CN CN201310526819.7A patent/CN104598158B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100205600A1 (en) * | 2009-02-06 | 2010-08-12 | Inventec Corporation | Simulation method for realizing large batches and different kinds of baseboard management controllers using a single server |
| CN102073599A (en) * | 2009-11-23 | 2011-05-25 | 英业达股份有限公司 | System event log recording method |
| CN102262570A (en) * | 2010-05-28 | 2011-11-30 | 英业达股份有限公司 | Method for updating fan control table |
| CN102455950A (en) * | 2010-10-28 | 2012-05-16 | 鸿富锦精密工业（深圳）有限公司 | Firmware recovery system and method of base board management controller |
| CN102467399A (en) * | 2010-11-18 | 2012-05-23 | 鸿富锦精密工业（深圳）有限公司 | Firmware updating system and method for baseboard management controller |
| US20130212430A1 (en) * | 2012-02-09 | 2013-08-15 | Hon Hai Precision Industry Co., Ltd. | Electronic device with firmware recovery function and method for recovering firmware |
| CN103378986A (en) * | 2012-04-28 | 2013-10-30 | 鸿富锦精密工业（深圳）有限公司 | System event log recording system and method |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111611193A (en) * | 2019-02-22 | 2020-09-01 | 阿里巴巴集团控股有限公司 | Event processing method, device and equipment |
| CN111611193B (en) * | 2019-02-22 | 2023-06-20 | 阿里巴巴集团控股有限公司 | Event processing method, device and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108170577A (en) | 2018-06-15 |
| CN108170577B (en) | 2021-11-26 |
| CN104598158B (en) | 2018-03-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8214823B2 (en) | Cluster system, process for updating software, service provision node, and computer-readable medium storing service provision program | |
| CN110535692B (en) | Fault processing method and device, computer equipment, storage medium and storage system | |
| CN103001809B (en) | Service node method for monitoring state for cloud storage system | |
| CN110830283B (en) | Fault detection method, device, equipment and system | |
| CN108572898B (en) | Method, device, equipment and storage medium for controlling interface | |
| CN108924202B (en) | Distributed cluster data disaster tolerance method and related device | |
| CN107453932B (en) | Distributed storage system management method and device | |
| CN103024065A (en) | System configuration management method for cloud storage system | |
| US8498214B2 (en) | Switching device, information processing device, and recording medium for failure notification control program | |
| US9697078B2 (en) | Method and device for auto recovery storage of JBOD array | |
| CN104346264A (en) | System and method for processing system event logs | |
| US20140156853A1 (en) | Computer and resource retrieval method | |
| US20120124221A1 (en) | Element terminal and communication system | |
| CN109218401B (en) | Log collection method, system, computer device and storage medium | |
| CN105516386A (en) | Media access control (MAC) address conflict detecting and processing method and system for server management system | |
| US9092396B2 (en) | Standby system device, a control method, and a program thereof | |
| CN104270434A (en) | Service state monitoring system based on cloud service | |
| CN106533751B (en) | SDN controller cluster merging method and device | |
| CN105530145A (en) | Agentless equipment monitoring network based on ZABBIX framework, networking method and monitoring method | |
| CN104598158A (en) | System and method for processing system event | |
| CN104182296A (en) | Data processing system, data processing apparatus, and storage medium | |
| CN111756800A (en) | Method and system for processing burst flow | |
| CN105338058A (en) | Application updating method and device | |
| CN110113187B (en) | Configuration updating method and device, configuration server and configuration system | |
| CN110888663B (en) | Application updating method, service server, transfer server, cluster and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20170921 Address after: 518000 Guangdong Province, Shenzhen New District of Longhua City, Dalang street, Longsheng Gold Dragon Road community e-commerce incubator exhibition Tao Commercial Plaza E block 706 Applicant after: Shenzhen step Technology Transfer Center Co., Ltd. Address before: 518109 Guangdong city of Shenzhen province Baoan District Longhua Town Industrial Zone tabulaeformis tenth East Ring Road No. 2 two Applicant before: Hongfujin Precise Industry (Shenzhen) Co., Ltd. Applicant before: Hon Hai Precision Industry Co., Ltd. |
|
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20180126 Address after: 066400 Hebei city of Qinhuangdao Province Economic and Technological Development Zone of the Yanghe River Road No. 12 e valley G-Net C district two floor No. 17 Applicant after: Hebei Zhongyan Technology Services Limited Address before: 518000 Guangdong Province, Shenzhen New District of Longhua City, Dalang street, Longsheng Gold Dragon Road community e-commerce incubator exhibition Tao Commercial Plaza E block 706 Applicant before: Shenzhen step Technology Transfer Center Co., Ltd. |
|
| TA01 | Transfer of patent application right | ||
| CB03 | Change of inventor or designer information |
Inventor after: Gao Yanjun Inventor before: Huang Yucheng |
|
| CB03 | Change of inventor or designer information | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20180131 Address after: The A District of the Yanghe River economic and Technological Development Zone, Road No. 12 e valley in Hebei province Qinhuangdao city G-Net 066000 three floor room 1301 Applicant after: Qinhuangdao forest Eagle Technology Co., Ltd. Address before: 066400 Hebei city of Qinhuangdao Province Economic and Technological Development Zone of the Yanghe River Road No. 12 e valley G-Net C district two floor No. 17 Applicant before: Hebei Zhongyan Technology Services Limited |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: Room 433, building 6, No. 78, Keling Road, high tech Zone, Suzhou, Jiangsu 215000 Patentee after: Suzhou Linying Technology Co.,Ltd. Address before: 066000 room 1301, 3rd floor, zone a, e valley creative space, 12 Yanghe Road, Qinhuangdao Economic and Technological Development Zone, Hebei Province Patentee before: QINHUANGDAO LINYING TECHNOLOGY CO.,LTD. |
|
| CP03 | Change of name, title or address |