search

jrossi / issue-migration-test

GNU General Public License v2.0
1 stars 0 forks source link

Agent.conf graceful failure #16

Open jrossi opened 10 years ago

jrossi commented 10 years ago

A mistake in agent.conf can cause ossec to not restart properly. In this case, ossec should attempt to fall back to ossec.conf or use a previous agent.conf, and log an informational message.

Note: This issue has been automatically migrated from Bitbucket Created by mstarks01 on 2012-09-01 21:26:18+00:00

jrossi commented 10 years ago

Refusing to start when a configuration file is wrong makes more sense to me. There's a better chance that the appropriate admin will see it and fix it.

Note: This comment has been automatically migrated from Bitbucket Created by ddpbsd on 2012-10-11 18:42:34+00:00

jrossi commented 10 years ago

I agree that a failure could be a good option for the manager. I am thinking of a situation with the agents in which they refuse to restart because of a bad agent.conf. With 500 or 1,000 agents, this could lead to a situation where they all stop working with no way to get them a correct agent.conf except for some ad-hoc out-of-band method.

Note: This comment has been automatically migrated from Bitbucket Created by mstarks01 on 2012-10-12 00:29:21+00:00