If SmartLog is not active or failed to parse results from server, what commands can be run to re- enable the service?

Question

Options

• Asmartlogrestart and smartlogstart
• Bsmartlogstart and smartlogstop
• Csmartloginit and smartlogstop
• Dsmartlogstart and smartlogsetup

• A
  93% (42)
• B
  4% (2)
• C
  2% (1)

Explanation

Option A is correct because when SmartLog is inactive or failing to parse results, you need two recovery commands: smartlogstart to launch the service if it's not running, and smartlogrestart to cycle it if it's already running but malfunctioning - together they cover both failure scenarios.

Option B is wrong because smartlogstop disables the service rather than helping restore it - stopping SmartLog is the opposite of re-enabling it. Option C fails for the same reason: smartlogstop appears again and smartloginit is an initialization command, not a recovery tool for an already-configured service. Option D is wrong because smartlogsetup is used for initial configuration, not for recovering an active service that has stalled or lost its parse results.

Memory tip: Think of it as "restart or start" - if the service is stuck, restart it; if it never came up, start it. The two commands in option A map directly to those two states, making A the only pair that covers full recovery.

No community discussion yet for this question.