Get the App
SLTechnology News&Howtos  ›  Network Security  › 

The method of dealing with the start-up Fault of OSSIM system

Shulou Source: shulou.com Published: 2022-06-01 04:14:34 10月06日 Update

The method of dealing with the start-up Fault of OSSIM system

1. Problem background

OSSIM is a system based on Debian Squeeze 6. Behind its strong processing power, its system is also relatively fragile and can not withstand serious accidental operations such as accidental power outage and illegal shutdown. This has a great or even devastating impact on the system. Of course, we should not be afraid of this kind of failure of Linux, learning is a process of finding and solving problems, as long as we master the basic ideas, all faults will be easily solved. There are many failures that cause Linux not to boot, such as / etc/initab,/etc/fstab configuration file loss or configuration error, root file system corruption, root partition corruption, grub loss or corruption, which can cause the system to fail to boot. The following example is a failure caused by a file system error caused by an accidental power failure of the server power supply. The main solution is to repair the file system by entering linux resuce mode through Linux LiveCD.

two。 Phenomenon

An OSSIM Server server in the computer room was running with an unexpected power outage and a large amount of data was not written back. Coincidentally, the Ext3 file system failed. Although it is a log file system with logging function, in the OSSIM system, ext3 files are in a high-load read-write mode all the time. This unexpected power failure is not just a simple loss of data for OSSIM. It is quite possible that there is an inconsistency in the internal structure of the file system, resulting in a file system failure, resulting in stopping at the interface shown in the following figure when the system starts again.

Ten minutes have passed and an hour has passed. The system has been parked on this interface.

Try to restart the system, then press F2 to view the system process and find that the system is prompted for the root password, as shown in the following figure.

No matter how many times you enter the correct password, the system just can't get in. ....

What are we going to do next?

3. Treatment method

Here is an analog video for reference only: http://www.tudou.com/programs/view/JrDFRHtlEiI

Tags: System file fault accident method processing that is problem password data log server mode interface process error service input configuration powerful Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Linux MariaDB Xiaomi OPPO Reno vpn