On Tue, Jul 31, 2012 at 7:16 PM, Steve Kieu msh.comput...@gmail.com wrote:
It could take a while for it to be pushed. I think if you run the
processes in debug mode the transfer will be logged. Running in debug
mode might be a good idea to see if it logs information on why the
agent.conf
On Wed, Aug 1, 2012 at 9:09 AM, dan (ddp) ddp...@gmail.com wrote:
On Tue, Jul 31, 2012 at 7:16 PM, Steve Kieu msh.comput...@gmail.com wrote:
It could take a while for it to be pushed. I think if you run the
processes in debug mode the transfer will be logged. Running in debug
mode might be a
: ossec-list@googlegroups.com [mailto:ossec-list@googlegroups.com] On
Behalf Of dan (ddp)
Sent: Wednesday, August 01, 2012 8:10 AM
To: ossec-list@googlegroups.com
Subject: Re: [ossec-list] Can nto have centralized agent config working
On Tue, Jul 31, 2012 at 7:16 PM, Steve Kieu msh.comput
Try blanking the merged.mg.
Looks like it does the trick. I cp /dev/null into it and then restart both
- after restarting the file is populated with datra again pushed from the
server in that section for the client name.
Need to wait or do some testing to see if it is actually using that
Try blanking the merged.mg.
Looks like it does the trick. I cp /dev/null into it and then restart both
- after restarting the file is populated with datra again pushed from the
server in that section for the client name.
Need to wait or do some testing to see if it is actually using that
Hello list,
I have tried many things until I just give up and ask for help. Basically
the centralized agent config not working.
At agent I remove the etc/shared/agent.conf
and etc/ossec.conf contains only
ossec_config
client
server-ip10.200.11.140/server-ip
/client
/ossec_config
And
AGENT_NAME is replace by my actual ossec client name
I tried to remove it it to be generic - replace name attr with os=Linux
and client is LInux - still does not do anything
On Tue, Jul 31, 2012 at 5:32 PM, bw bw.mail.li...@gmail.com wrote:
agent_config name=AGENT_NAME
do you need this
On Tue, Jul 31, 2012 at 2:11 AM, peace msh.comput...@gmail.com wrote:
Hello list,
I have tried many things until I just give up and ask for help. Basically
the centralized agent config not working.
At agent I remove the etc/shared/agent.conf
and etc/ossec.conf contains only
ossec_config
I did it and restart the server first and the client later. Should it be
picked up right away ?
I already checked permission. Not sure which process read the
etc/shared/agent.conf though as some process is run by root, other run by
ossec user (not remembered exactly the name as I am currently off
On Tue, Jul 31, 2012 at 7:31 AM, Steve Kieu msh.comput...@gmail.com wrote:
I did it and restart the server first and the client later. Should it be
picked up right away ?
It could take a while for it to be pushed. I think if you run the
processes in debug mode the transfer will be logged.
It could take a while for it to be pushed. I think if you run the
processes in debug mode the transfer will be logged. Running in debug
mode might be a good idea to see if it logs information on why the
agent.conf isn't being pushed.
I suppose that I change in the server and client as well
If you restart the client, it will get pushed within a minute - assuming
you had restarted the manager so it knows there was a change.
I had this problem with a large install of 4000+ agents in the beginning,
but in general, if the agent is restarted shortly after manager, the files
were
If you restart the client, it will get pushed within a minute - assuming
you had restarted the manager so it knows there was a change.
I had this problem with a large install of 4000+ agents in the beginning,
but in general, if the agent is restarted shortly after manager, the files
were
13 matches
Mail list logo
