18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

What to do if the<br />

boot process<br />

fails<br />

Appendix F: Basic Troubleshooting<br />

What to do if the boot process fails<br />

4 Obtain the license by doing one <strong>of</strong> the following:<br />

• If DNS is resolving, enter cf license get.<br />

• If DNS is not resolving, you will need to get the license using the Secure<br />

Computing activation server’s IP address by entering the following on a<br />

single line:<br />

cf license get activation_url=https://66.45.10.76/cgibin/sidewinder-activation.cgi<br />

5 Reboot the system to the operational kernel by entering:<br />

shutdown -r now<br />

The <strong>Sidewinder</strong> <strong>G2</strong> should now be correctly licensed and fully functional.<br />

Boot failure may be caused by the fsck command. This command is run as<br />

part <strong>of</strong> the system boot process. If this command fails, the <strong>Sidewinder</strong> <strong>G2</strong> will<br />

not boot properly. If the boot process fails, you will need to attach a keyboard<br />

and monitor and repower the system. If you see a # prompt (indicating that the<br />

fsck command failed), type the following at the # prompt to fix any disk<br />

problems:<br />

ind Kern /sbin/fsck -p<br />

Then restart the system by entering shutdown -r now at the command<br />

prompt.<br />

System reboot messages<br />

During a system reboot, certain system events will cause messages to be<br />

stored in the audit holding area prior to auditd being started. When auditd<br />

starts, one or more blue messages stating “sacopen: transferred 1<br />

records from hold” may appear on the console’s display. This merely<br />

indicates that the messages stored in the audit holding area were transferred<br />

to the audit stream. Normally, these messages can be ignored.<br />

651

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!