CN106776090A - A kind of method for collecting information when RHEL operating systems are without response - Google Patents
A kind of method for collecting information when RHEL operating systems are without response Download PDFInfo
- Publication number
- CN106776090A CN106776090A CN201611072689.4A CN201611072689A CN106776090A CN 106776090 A CN106776090 A CN 106776090A CN 201611072689 A CN201611072689 A CN 201611072689A CN 106776090 A CN106776090 A CN 106776090A
- Authority
- CN
- China
- Prior art keywords
- rhel
- operating systems
- kdump
- response
- vmcore
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3452—Performance evaluation by statistical analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computer Hardware Design (AREA)
- Bioinformatics & Computational Biology (AREA)
- Probability & Statistics with Applications (AREA)
- Evolutionary Biology (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Life Sciences & Earth Sciences (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Computing Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
A kind of method for collecting information during the invention discloses RHEL operating systems without response, belongs to computer operating system technical field.The method of information is collected when RHEL operating systems of the invention are without response to RHEL operating systems configuration kdump, installation sosreport and sysstat is installed, wherein setting sysrq magic keys when kdump is configured；Judge the state of RHEL operating systems, when RHEL operating systems can respond part interrupt signal, the status information of system is obtained by sysrq magics key, is triggered by kdump and is produced vmcore files, by the comprehensive daily record of sosreport collection systems and configuration information.The problem of the method energy precise positioning operation system without response of information is collected when the RHEL operating systems of the invention are without response, accident analysis personnel fast and effectively orientation problem reason is helped, with good application value.
Description
Technical field
The present invention relates to computer operating system technical field, collected when specifically providing a kind of RHEL operating systems without response
The method of information.
Background technology
Computer has information memory capacity big, user obtain information it is convenient and swift the advantages of, application field is widely.
With the fast development of internet economy, the need for minicom can not meet some large enterprises, with higher
The server of stability, security and performance is developed rapidly and come.Server plays the effect of key for enterprise, once
Server is damaged can bring huge loss to enterprise, it is therefore desirable to which the properties to server are tested accordingly.Behaviour
It is the core of server as system, RHEL is the abbreviation of Red Hat Enterprise Linux, is Red Hat companies
Linux system.When performance test is carried out to server, system is one in server test, production environment without response
Common serious problems, especially for production environment, often cause heavy losses to client.In situation of the system without response
Under, how fast and accurately the basic reason of orientation problem is client, soft so as to solve, thoroughly evade the generation of problems
The problem that hardware supplier, integrator pay close attention to the most.But, quick and precisely alignment system is still lacked in the prior art and is asked without response
The method of topic.
The content of the invention
Technical assignment of the invention is directed to above-mentioned problem, there is provided one kind can be accurately positioned and collect operating system
Problem without response, receives when helping the RHEL operating systems of accident analysis personnel fast and effectively orientation problem reason without response
The method of collection information.
To achieve the above object, the invention provides following technical scheme：
A kind of method for collecting information when RHEL operating systems are without response, to RHEL operating systems configuration kdump, installs
Sosreport and installation sysstat, wherein setting sysrq magic keys when kdump is configured；Judge the shape of RHEL operating systems
State, when RHEL operating systems can respond part interrupt signal, the state of system is obtained by the sysrq magics key for setting
Information, is triggered by the kdump that configures and produces vmcore files, by the comprehensive daily record of sosreport collection systems and is matched somebody with somebody
Confidence ceases, by sysstat collection systems without the systematic function before response and system resource service condition, according to vmcore files
The failure of document alignment and analysis RHEL operating systems without response collected with sosreport；When RHEL operating systems cannot ring
When answering any interrupt signal, wait kdump set trigger condition produce vmcore files, according to vmcore document alignments and point
Failure of the analysis RHEL operating systems without response.
The Kdump is to utilize kexec（From one in the kernel context of operation, checked without BIOS, quickly
Start the mechanism of another kernel）A kind of reliable Kernel Panic dump mechanism realized, when system crash, kdump is utilized
Kexec quickly starts to second kernel, and second kernel captures crash dump image.
The sysrq is a magic key combination, except system is lockable completely（Generation can not interruption pending）Outward, in nothing
In the case of the machine etc. that responds or delay is every other, kernel can respond the Macintosh, permanent and come into force：
#vi/etc/sysctl.conf increases kernel.sysrq=1
#sysctl –p
The information that Sysrq is produced is stored in/var/log/messages
Several important sysrq Macintosh
The information of Alt+sysrq+m dump Memory Allocations；
Alt+sysrq+t dump thread state informations；
Alt+sysrq+p:The current CPU registers of dump and flag information；
Alt+sysrq+w:Dump can not masked state mission bit stream；
Alt+sysrq+c: crash the kernel。
Operation yum install sos install sosreport.Sosreport is that collection system matches somebody with somebody confidence in RHEL systems
One kit of breath and log information, runs the kit, can be collected into very full system information.
The sysstat software kits provide the order such as sar and iostat, can be to disk, network and other I/O resources
Operation carry out system monitoring and statistics, the instrument contributes to analysis system resource service condition before going wrong to become
Gesture.Operation #yum install sysstat carry out installation sysstat, journal file is stored in/var/log/sa/ under, by #
Sar-f/var/log/sa/saXX orders can check monitoring and the statistical information of system.
The RHEL operation system states of the inspection include：
（1）Whether can ssh/telnet Telnets；
（2）Whether can be by console login systems；
（3）Whether can ping way systems；
（4）Whether system can respond local keyboard and mouse.
If aforesaid operations have what can be run succeeded, illustrate that RHEL operating systems can also respond a part of interruption at present
Signal, in the case of this kind, RHEL operation system informations is obtained using such as issuing orders：
（a）In the case where sysrq magic keys have been configured with, system mode is obtained by sysrq magics key：Alt+Sysrq+
M, Alt+sysrq+t, Alt+sysrq+p Alt+sysrq+w are performed 3 times, every time interval 3 minutes or so；
（b）In the case where kdump has been configured with, crash is triggered by Alt+sysrq+c, derive vmcore files；
（c）After system reboot, operation sosreport collects sosreport files；
（d）Vmcore files, the derivation of sosreport files that will be collected, according to vmcore files, sosreport document alignments
With failure of the analysis RHEL operating systems without response.
If aforesaid operations not can perform, illustrate that RHEL operating systems cannot respond to these interrupt signals, this kind of situation
Under, the cooperation of kdump and nmi_watchdog by configuring, RHEL operating systems trigger kernel panic collections automatically
Core dump file vmcore, according to the failure of vmcore document alignments and analysis RHEL operating systems without response.
Preferably, the method that information is collected when the RHEL operating systems are without response specifically includes following steps：
S1：To RHEL operating systems configuration kdump, sosreport and installation sysstat is installed, is set during configuration kdump
Sysrq magic keys；
S2：RHEL operation system states are checked, step is performed successively when RHEL operating systems can respond part interrupt signal
S3, S4, S5, S6, S7, step S8, S9 is performed when RHEL operating systems cannot respond to any interrupt signal successively；
S3：The status information of system is obtained by the sysrq magics key for setting；
S4：Triggered by the kdump for configuring and produce vmcore files；
S5：By the comprehensive daily record of sosreport collection systems and configuration information；
S6：By sysstat collection systems without the systematic function before response and system resource service condition；
S7：According to the failure of document alignment and analysis RHEL operating systems without response that vmcore files and sosreport are collected；
S8：The trigger condition for waiting kdump to set produces vmcore files；
S9：According to the failure of vmcore document alignments and analysis RHEL operating systems without response.
Preferably, in step S1, the process for configuring kdump is：Install kexec tool, configuration kdump trigger conditions,
Configuration crashkernel sizes, configuration vmcore deposit positions, the compression that vmcore files are set, setting kdump service starts
From opening, arrangement above is when changing, restart kdump services, set sysrq magics key, restart computer, test kdump configurations whether
Come into force and core dump caused by downtime.
The installation kexec tool are by #rpm-q kexec-tools or #yum install kexec-
tools。
The process of the configuration kdump trigger conditions is：
（1）System hang are detected by NMI watchdog:Increase nmi_ in the kernel rows of grub or start-up parameter
Watchdog=1 (or nmi_watchdog=2), checks whether by cat/proc/interrupts to come into force after restarting；
（2）Configuration hardware NMI button trigger kdump when being pressed:Increase in/etc/sysctl.conf
kernel.unknown_nmi_panic=1；
（3）When " unrecovered " NMI occurs, kernel.panic_on_ is increased in/etc/sysctl.conf
unrecovered_nmi=1；
（4）When there is softlockup, kernel.softlockup_panic=1 is increased in/etc/sysctl.conf；
（5）When out of memory killer are triggered, vm.panic_on_oom is increased in/etc/sysctl.conf
=1。
The process of the configuration crashkernel sizes is the kernel rows increase in the grub of RHEL6/7：
Crashkernel=XM or crashkernel=auto (version after RHEL6.3, RAM>2GB), maximum crashkernel=
896M。
Configuration vmcore deposit positions (/etc/kdump.conf), if be not provided with, vmcore files can be saved
Under to/var/crash catalogues, it is desirable to have enough memory spaces：
（1）Directly it is dumped to an equipment：raw <devicename>；
（2）It is dumped to a file on disk：
<filesystemtype><filesystem>:Filesystem can be mounted to the type of filesystemtype/
Mnt, and vmcore files can be stored in/mnt/var/crash catalogues under,
For example：ext4 /dev/sdb1；
（3）It is dumped to and uses the network equipment of NFS：
Kexec_tools versions before 2.0.0-232, net<nfs server>:</nfs/mount>,
Kexec_tools versions in 2.0.0-232 and afterwards, nfs<nfs server>:</nfs/mount>；
（4）It is dumped to and uses the network equipment of SSH：
Kexec_tools versions before 2.0.0-232, net<user>@<ssh server>,
Kexec_tools versions in 2.0.0-232 and afterwards, ssh<user>@<ssh server>,
Vmcore be stored in ssh server /var/crash catalogues under；
（5）It is dumped to SAN equipment：https://access.redhat.com/node/6038.
The compression of the setting vmcore files, removes unnecessary page（/etc/kdump.conf）
- the c of core_collector makedumpfile-d 31, remove all blank pages and compress.
Setting kdump service start from open for：
RHEL6:
# service kdump start
#chkconfig kdump on
RHEL7:
#systemctl start kdump
#systemctl enable kdump。
When the arrangement above changes, restarting kdump services is：
RHEL6：#service kdump restart
RHEL7: #systemctl restart kdump。
The setting sysrq magic keys are：#vi /etc/sysctl.conf kernel.sysrq=1.
It is described to restart computer for #reboot.
Test kdump configuration whether come into force and core dump caused by downtime be #echo c> /proc/
sysrq-trigger。
Preferably, in step S3, the system status information that the sysrq magics key is obtained include CPU register informations,
Internal memory service condition, process status, thread state information.
Compared with prior art, the method for collection information has following prominent when RHEL operating systems of the invention are without response
Beneficial effect：The method that information is collected during by the RHEL operating systems without response can fast and effectively collect operating system
Problem without response, and the effective information collected is more comprehensive, is system manager, after-sale service personnel's analyzing and positioning system
Failure cause provides support.
Brief description of the drawings
Fig. 1 is flow chart of the RHEL operating systems of the present invention without the method that information is collected when responding.
Specific embodiment
Below in conjunction with drawings and Examples, the method that information is collected during to RHEL operating systems of the invention without response is made
Further describe.
Embodiment
As shown in figure 1, the method for collecting information when RHEL operating systems of the invention are without response, operates system to RHEL first
System is pre-configured with kdump, installs sosreport and installs sysstat, and sysrq magic keys are set during configuration kdump.Judge again
The state of RHEL operating systems, when RHEL operating systems can respond part interrupt signal, by the sysrq magics for setting
Key obtains the status information of system, is triggered by the kdump for configuring and produces vmcore files, and system is collected by sosreport
Unite comprehensive daily record and configuration information, feelings are used without the systematic function and system resource before response by sysstat collection systems
Condition, according to the failure of document alignment and analysis RHEL operating systems without response that vmcore files and sosreport are collected；When
When RHEL operating systems cannot respond to any interrupt signal, the trigger condition for waiting kdump to set produces vmcore files, according to
The failure of vmcore document alignments and analysis RHEL operating systems without response.
The method that information is collected when the RHEL operating systems are without response specifically includes following steps：
S1：To RHEL operating systems configuration kdump, sosreport and installation sysstat is installed, is set during configuration kdump
Sysrq magic keys.
Kdump is to utilize kexec（Checked without BIOS in the kernel context of operation from one, it is quick to start
The mechanism of another kernel）A kind of reliable Kernel Panic dump mechanism realized, when system crash, kdump utilizes kexec
Second kernel quickly is started to, second kernel captures crash dump image.
Configure kdump process be：
（One）Kexec tool are installed：By #rpm-q kexec-tools or #yum install kexec-tools.
（Two）Configuration kdump trigger conditions：
（1）System hang are detected by NMI watchdog:Increase nmi_ in the kernel rows of grub or start-up parameter
Watchdog=1 (or nmi_watchdog=2), checks whether by cat/proc/interrupts to come into force after restarting；
（2）Configuration hardware NMI button trigger kdump when being pressed:Increase in/etc/sysctl.conf
kernel.unknown_nmi_panic=1；
（3）When " unrecovered " NMI occurs, kernel.panic_on_ is increased in/etc/sysctl.conf
unrecovered_nmi=1；
（4）When there is softlockup, kernel.softlockup_panic=1 is increased in/etc/sysctl.conf；
（5）When out of memory killer are triggered, vm.panic_on_oom is increased in/etc/sysctl.conf
=1。
（Three）Configuration crashkernel sizes：Increase in the kernel rows of the grub of RHEL6/7：crashkernel=XM
Or crashkernel=auto (version after RHEL6.3, RAM>2GB), maximum crashkernel=896M.
（Four）Configuration vmcore deposit positions（1）System hang are detected by NMI watchdog:In grub or open
The kernel rows of dynamic parameter increase nmi_watchdog=1 (or nmi_watchdog=2), and cat/proc/ is passed through after restarting
Interrupts checks whether to come into force；
（2）Configuration hardware NMI button trigger kdump when being pressed:Increase in/etc/sysctl.conf
kernel.unknown_nmi_panic=1；
（3）When " unrecovered " NMI occurs, kernel.panic_on_ is increased in/etc/sysctl.conf
unrecovered_nmi=1；
（4）When there is softlockup, kernel.softlockup_panic=1 is increased in/etc/sysctl.conf；
（5）When out of memory killer are triggered, vm.panic_on_oom is increased in/etc/sysctl.conf
=1。
The process of the configuration crashkernel sizes is the kernel rows increase in the grub of RHEL6/7：
Crashkernel=XM or crashkernel=auto (version after RHEL6.3, RAM>2GB), maximum crashkernel=
896M。
（Five）The compression of vmcore files is set, removes unnecessary page（/etc/kdump.conf）
- the c of core_collector makedumpfile-d 31, remove all blank pages and compress.
（Six）Kdump service starts are set to open certainly：
RHEL6:
# service kdump start
#chkconfig kdump on
RHEL7:
#systemctl start kdump
#systemctl enable kdump。
（Seven）When arrangement above changes, kdump services are restarted：
RHEL6：#service kdump restart
RHEL7: #systemctl restart kdump。
（Eight）Sysrq magic keys are set：#vi /etc/sysctl.conf kernel.sysrq=1.
（Nine）Restart computer：#reboot.
（Ten）Test kdump configuration whether come into force and core dump caused by downtime：#echo c > /proc/
sysrq-trigger。
Sysrq is a magic key combination, except system is lockable completely（Generation can not interruption pending）Outward, without response
It is permanent and come into force or in the case of machine of delaying etc. is every other, kernel can respond the Macintosh.#vi /etc/
Sysctl.conf increases kernel.sysrq=1
#sysctl –p
The information that Sysrq is produced is stored in/var/log/messages
Several important sysrq Macintosh
The information of Alt+sysrq+m dump Memory Allocations；
Alt+sysrq+t dump thread state informations；
Alt+sysrq+p:The current CPU registers of dump and flag information；
Alt+sysrq+w:Dump can not masked state mission bit stream；
Alt+sysrq+c: crash the kernel。
Sysrq magics key obtain system status information include CPU register informations, internal memory service condition, process status,
Thread state information.
Sosreport is a kit of collection system configuration information and log information in RHEL systems, runs the work
Tool bag, can be collected into very full system information, and operation yum install sos install sosreport.
Sysstat software kits provide the order such as sar and iostat, can be to the behaviour of disk, network and other I/O resources
System monitoring and statistics are carried out, the instrument contributes to the trend of analysis system resource service condition before going wrong.Fortune
Row #yum install sysstat carry out installation sysstat, journal file is stored in/var/log/sa/ under, by #sar-
F/var/log/sa/saXX orders can check monitoring and the statistical information of system.
S2：RHEL operation system states are checked, is performed successively when RHEL operating systems can respond part interrupt signal
Step S3, S4, S5, S6, S7, step S8, S9 is performed when RHEL operating systems cannot respond to any interrupt signal successively.
The RHEL operation system states of inspection include：
（1）Whether can ssh/telnet Telnets；
（2）Whether can be by console login systems；
（3）Whether can ping way systems；
（4）Whether system can respond local keyboard and mouse.
If aforesaid operations have what can be run succeeded, illustrate that RHEL operating systems can also respond a part of interruption at present
Signal, in the case of this kind, performs step S3, S4, S5, S6, S7 successively.
If aforesaid operations not can perform, illustrate that RHEL operating systems cannot respond to these interrupt signals, in the case of this kind,
Step S8, S9 is performed successively.
S3：The status information of system is obtained by the sysrq magics key for setting.It is being configured with sysrq magic keys
In the case of, system mode is obtained by sysrq magics key：Alt+Sysrq+m, Alt+sysrq+t , Alt+sysrq+p
Alt+sysrq+w is performed 3 times, every time interval 3 minutes or so.
S4：Triggered by the kdump for configuring and produce vmcore files.In the case where kdump has been configured with, pass through
Alt+sysrq+c triggers crash, derives vmcore files.
S5：By the comprehensive daily record of sosreport collection systems and configuration information.After system reboot, sosreport is run
Collect sosreport files.
S6：By sysstat collection systems without the systematic function before response and system resource service condition；
S7：According to the failure of document alignment and analysis RHEL operating systems without response that vmcore files and sosreport are collected.
Vmcore files, the derivation of sosreport files that will be collected, according to vmcore files, sosreport document alignments
With failure of the analysis RHEL operating systems without response.
S8：The trigger condition for waiting kdump to set produces vmcore files.
The cooperation of the kdump and nmi_watchdog that have configured, RHEL operating systems trigger kernel panic receipts automatically
Collection core dump file vmcore.
S9：According to the failure of vmcore document alignments and analysis RHEL operating systems without response.
Embodiment described above, the simply present invention more preferably specific embodiment, those skilled in the art is at this
The usual variations and alternatives carried out in the range of inventive technique scheme all should be comprising within the scope of the present invention.
Claims (4)
1. a kind of method of collection information when RHEL operating systems are without response, it is characterised in that：RHEL operating systems are configured
Kdump, installation sosreport and installation sysstat, wherein setting sysrq magic keys when kdump is configured；Judge that RHEL is grasped
Make the state of system, when RHEL operating systems can respond part interrupt signal, obtained by the sysrq magics key for setting
The status information of system, is triggered by the kdump for configuring and produces vmcore files, comprehensive by sosreport collection systems
Daily record and configuration information, by sysstat collection systems without the systematic function before response and system resource service condition, according to
The failure of document alignment and analysis RHEL operating systems without response that vmcore files and sosreport are collected；When RHEL operations
When system cannot respond to any interrupt signal, the trigger condition for waiting kdump to set produces vmcore files, according to vmcore texts
Part is positioned and failure of the analysis RHEL operating systems without response.
2. the method for collection information when RHEL operating systems according to claim 1 are without response, it is characterised in that：It is described
The method that information is collected when RHEL operating systems are without response specifically includes following steps：
S1：To RHEL operating systems configuration kdump, sosreport and installation sysstat is installed, is set during configuration kdump
Sysrq magic keys；
S2：RHEL operation system states are checked, step is performed successively when RHEL operating systems can respond part interrupt signal
S3, S4, S5, S6, S7, step S8, S9 is performed when RHEL operating systems cannot respond to any interrupt signal successively；
S3：The status information of system is obtained by the sysrq magics key for setting；
S4：Triggered by the kdump for configuring and produce vmcore files；
S5：By the comprehensive daily record of sosreport collection systems and configuration information；
S6：By sysstat collection systems without the systematic function before response and system resource service condition；
S7：According to the failure of document alignment and analysis RHEL operating systems without response that vmcore files and sosreport are collected；
S8：The trigger condition for waiting kdump to set produces vmcore files；
S9：According to the failure of vmcore document alignments and analysis RHEL operating systems without response.
3. the method for collection information when RHEL operating systems according to claim 1 and 2 are without response, it is characterised in that：Step
In rapid S1, the process for configuring kdump is：Kexec tool, configuration kdump trigger conditions are installed, crashkernel is big for configuration
Small, configuration vmcore deposit positions, the compression that vmcore files are set, set kdump services start from opening, arrangement above changes
When, restart kdump services, sysrq magics key is set, is restarted computer, tested whether kdump configurations come into force and core dump causes
Downtime.
4. the method for collection information when RHEL operating systems according to claim 3 are without response, it is characterised in that：Step S3
In, the system status information that the sysrq magics key is obtained include CPU register informations, internal memory service condition, process status,
Thread state information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611072689.4A CN106776090A (en) | 2016-11-29 | 2016-11-29 | A kind of method for collecting information when RHEL operating systems are without response |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611072689.4A CN106776090A (en) | 2016-11-29 | 2016-11-29 | A kind of method for collecting information when RHEL operating systems are without response |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106776090A true CN106776090A (en) | 2017-05-31 |
Family
ID=58904362
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611072689.4A Pending CN106776090A (en) | 2016-11-29 | 2016-11-29 | A kind of method for collecting information when RHEL operating systems are without response |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106776090A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108647103A (en) * | 2018-05-14 | 2018-10-12 | 上海泰砚通信技术有限公司 | A kind of the hot key interactive system and method for linux system |
| CN108923965A (en) * | 2018-06-27 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of Remote triggering server system generates the system and method for Kernel Panic log |
| CN109062627A (en) * | 2018-07-12 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of configuration method of Linux server system kdump service |
| CN113742120A (en) * | 2021-08-06 | 2021-12-03 | 苏州浪潮智能科技有限公司 | Method, system, device and medium for kdump triggering |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102929747A (en) * | 2012-11-05 | 2013-02-13 | 中标软件有限公司 | Method for treating crash dump of Linux operation system based on loongson server |
| US20140172924A1 (en) * | 2012-12-19 | 2014-06-19 | Red Hat, Inc. | Crash recovery for attended operating system installations |
| CN104714863A (en) * | 2015-02-06 | 2015-06-17 | 浪潮电子信息产业股份有限公司 | Method for completely storing Raid card logs on basis of Linux operation system after system crashes |
| CN105242981A (en) * | 2015-10-30 | 2016-01-13 | 浪潮电子信息产业股份有限公司 | Configuration method of Kdump and computer device |
| CN105512015A (en) * | 2015-12-15 | 2016-04-20 | 北京奇虎科技有限公司 | Android target application crash calculation method and device |
| CN105718340A (en) * | 2016-01-13 | 2016-06-29 | 浪潮电子信息产业股份有限公司 | Crontab based CPU stability testing method |
-
2016
- 2016-11-29 CN CN201611072689.4A patent/CN106776090A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102929747A (en) * | 2012-11-05 | 2013-02-13 | 中标软件有限公司 | Method for treating crash dump of Linux operation system based on loongson server |
| US20140172924A1 (en) * | 2012-12-19 | 2014-06-19 | Red Hat, Inc. | Crash recovery for attended operating system installations |
| CN104714863A (en) * | 2015-02-06 | 2015-06-17 | 浪潮电子信息产业股份有限公司 | Method for completely storing Raid card logs on basis of Linux operation system after system crashes |
| CN105242981A (en) * | 2015-10-30 | 2016-01-13 | 浪潮电子信息产业股份有限公司 | Configuration method of Kdump and computer device |
| CN105512015A (en) * | 2015-12-15 | 2016-04-20 | 北京奇虎科技有限公司 | Android target application crash calculation method and device |
| CN105718340A (en) * | 2016-01-13 | 2016-06-29 | 浪潮电子信息产业股份有限公司 | Crontab based CPU stability testing method |
Non-Patent Citations (1)
| Title |
|---|
| PAUL NOVARESE: "Red Hat Enterprise Linux Kernel Crash Capture and Analysis", 《HTTPS://WWW.SLIDESHARE.NET/PAULVNOVARESE/LINUX-CRASH-DUMP-CAPTURE-AND-ANALYSIS》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108647103A (en) * | 2018-05-14 | 2018-10-12 | 上海泰砚通信技术有限公司 | A kind of the hot key interactive system and method for linux system |
| CN108923965A (en) * | 2018-06-27 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of Remote triggering server system generates the system and method for Kernel Panic log |
| CN109062627A (en) * | 2018-07-12 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of configuration method of Linux server system kdump service |
| CN113742120A (en) * | 2021-08-06 | 2021-12-03 | 苏州浪潮智能科技有限公司 | Method, system, device and medium for kdump triggering |
| CN113742120B (en) * | 2021-08-06 | 2023-07-14 | 苏州浪潮智能科技有限公司 | Kdump triggering method, system, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11070444B2 (en) | SDN control plane performance testing | |
| CN106776090A (en) | A kind of method for collecting information when RHEL operating systems are without response | |
| CN107544832B (en) | Method, device and system for monitoring process of virtual machine | |
| CN109144813B (en) | System and method for monitoring server node fault of cloud computing system | |
| CN111046011B (en) | Log collection method, system, device, electronic equipment and readable storage medium | |
| WO2006077247A1 (en) | Predictive method for managing, logging or replaying non-deterministic operations within the execution of an application process | |
| EP2300920A1 (en) | Method and apparatus for cause analysis involving configuration changes | |
| US11706080B2 (en) | Providing dynamic serviceability for software-defined data centers | |
| Gupta et al. | Context-aware time series anomaly detection for complex systems | |
| EP4030728A1 (en) | Software defined networking control plane resiliency testing | |
| CN104391777B (en) | Cloud platform and its operation and monitoring method and device based on (SuSE) Linux OS | |
| CN108984332A (en) | A kind of device and method of location-server delay machine failure | |
| CN115858221A (en) | Management method and device of storage equipment, storage medium and electronic equipment | |
| CN114138483B (en) | Virtualized resource management method, device, server, system and medium | |
| US20220353589A1 (en) | Systems and methods for enabling smart network interface card as an advanced telemetry appliance | |
| US9922539B1 (en) | System and method of telecommunication network infrastructure alarms queuing and multi-threading | |
| CN109189652A (en) | A kind of acquisition method and system of close network terminal behavior data | |
| CN110674008B (en) | Problem disk log information collection method, device, equipment and medium of SSD | |
| CN112714022A (en) | Control processing method and device for multiple clusters and computer equipment | |
| Leangsuksun et al. | A failure predictive and policy-based high availability strategy for linux high performance computing cluster | |
| CN109660392A (en) | Hardware unitizes adaptive management dispositions method and system under a kind of linux system | |
| CN110569172B (en) | Performance monitoring system of service level | |
| CN113553243A (en) | Remote error detection method | |
| CN112613931A (en) | Method and system for real-time storage and large-scale parallel access of mass billing data | |
| Kavulya et al. | Gumshoe: Diagnosing performance problems in replicated file-systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170531 |