18.07.2013 Views

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

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

Sidewinder G2 6.1.1 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.

Additional <strong>Sidewinder</strong> <strong>G2</strong> operating characteristics<br />

There are four key components that must be enabled and running<br />

before daemond will successfully boot the <strong>Sidewinder</strong> <strong>G2</strong>. These are:<br />

auditd, auditsql, aclsql, and acld.<br />

Whether running in normal or failure mode, daemond will fail to bring<br />

the <strong>Sidewinder</strong> <strong>G2</strong> up completely if any <strong>of</strong> the following situations<br />

occur:<br />

a configuration file error exists in any <strong>of</strong> the three files daemond<br />

parses: /etc/daemond.conf, /etc/server.conf, and<br />

/etc/sidewinder/nss.common.conf<br />

the system has not been properly licensed or activated<br />

a key component failed to start up or was not properly enabled<br />

a patch installation failed<br />

If one <strong>of</strong> these error conditions occur, a message appears notifying<br />

you that your system has booted to failure mode along with the<br />

reason why it booted to failure mode. The reason for the failure will<br />

be logged in /var/log/daemond.log. If none <strong>of</strong> the above situations<br />

occur, daemond will bring the system up without error.<br />

Once the <strong>Sidewinder</strong> <strong>G2</strong> has finished booting and the system is<br />

operational, daemond becomes responsible for monitoring, stopping<br />

and starting all the components in /etc/server.conf and<br />

/etc/sidewinder/nss.common.conf. While daemond is monitoring the<br />

enabled and running components, it is also responsible for keeping<br />

an instance <strong>of</strong> that component running.<br />

Restarting processes<br />

If a component dies unexpectedly, daemond will restart that<br />

component and audit the event in both the audit log and the daemond<br />

log. The message in /var/log/daemond.log will look similar to this:<br />

Nov 7 16:05:22 fiji : restarting /usr/libexec/syncd<br />

(2686) due to unexpected death<br />

If a component quits within five seconds <strong>of</strong> starting three times in a<br />

row, daemond will not attempt to restart it until the next time daemond<br />

rereads its configuration files. This event will also be audited to both<br />

the audit log and the daemond log. The message in /var/log/<br />

daemond.log will look similar to this:<br />

Nov 5 18:13:03 fiji : /usr/contrib/sbin/sshd will<br />

not be restarted due to possible startup errors<br />

Introduction 1-15

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

Saved successfully!

Ooh no, something went wrong!