Error No Remote Connection Configured. Exiting
Contents |
tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the ossec auth key workings and policies of this site About Us Learn more about Stack ossec duplicated counter Overflow the company Business Learn more about hiring developers or posting ads with us Information Security Questions Tags Users ossec manage_agents Badges Unanswered Ask Question _ Information Security Stack Exchange is a question and answer site for information security professionals. Join them; it only takes a minute: Sign up Here's how ossec add agent automatically it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top OSSEC error “agent_control(1750): ERROR: No remote connection configured. Exiting” up vote 0 down vote favorite I am new to OSSEC and trying to figure the tool to deploy it. I have an ubuntu server where I downloaded and installed
Error: Queue '/var/ossec/queue/ossec/queue' Not Accessible: 'connection Refused'.
the security onion packages. I have a few windows systems which I would like to monitor. On the server I used the sudo /var/ossec/bin/manage_agent command to add the windows agent's IP address and other information. I installed the windows agent on my systems along with ssh putty client. I got the key from the server for the agent and added it to the agent. The log file in the agent shows connected to IP XX.XX.XX.XX which is the server's IP. When I try to extract information from the agent from the server side using the command sudo ossec/bin/agent_control I get the error agent_control(1750): ERROR: No remote connection configured. Exiting. On the server side, all the firewall rules are default to allow connections from all IPs and ports on my internal network. Would anyone be able to tell me what I am doing wrong or what I need to do have a proper connection between the agent and the server? When I list the connections -l, it replies: "Never Connected". On the server side, I used tcpdump on the port
Blogs ยป eth00's blog Recent blog posts OpenSSL
Ossec Firewall Ports
updates for ALL versions Barnyard2 error Suricata build error Archipel build error - sqlalchemy Archipel build error - numpy Archipel build error - python-setuptools Ossec ar.conf issue Linksys 0-day Exploit Red October Malware Campaign 0-Day in Java 1.7 More Custom Search http://security.stackexchange.com/questions/113414/ossec-error-agent-control1750-error-no-remote-connection-configured-exitin User login Username * Password * Request new password OSSEC start problem due to keys Submitted by eth00 on Sun, 07/08/2012 - 19:02 The following is an error I got after starting ossec as an agent that is supposed to connect back http://eth0.us/node/216 to a central server: #/var/ossec/bin/ossec-control start Starting OSSEC HIDS v2.5.1 (by Trend Micro Inc.)... Started ossec-execd... ossec-agentd(1402): ERROR: Authentication key file '/var/ossec/etc/client.keys' not found. ossec-agentd(1750): ERROR: No remote connection configured. Exiting. ossec-agentd(4109): ERROR: Unable to start without auth keys. Exiting. The server (the one that ossec connects to) needs to have a key created for this agent, you can do so via: # /var/ossec/bin/manage_agents On the client (the one that got the error message) you need to add the key via the same command. Finally you can start ossec on the client: # /var/ossec/bin/ossec-control start That should do it! eth00's blog Everything provided is provided without any warranty, if you are not sure what something does test it in a development environment first!
a GitHub account Sign in Create a gist now Instantly share code, notes, and snippets. https://gist.github.com/1387701/5e29c8181be00d29aeed4be7a4b79a460bec1ca4 Star 0 Fork 0 cjs226span/gist:1387701 Created Nov 23, 2011 Embed What would you like to do? Embed Embed this gist in your website. Embed Share Copy sharable URL for this gist. Share Clone via HTTPS Clone with Git or checkout with SVN using the repository's web address. HTTPS Learn more about error no clone URLs Download ZIP Code Revisions 3 Problem starting OSSEC agent using Chef ossec cookbook Raw gistfile1.txt 2011/11/23 01:49:22 ossec-execd: INFO: Started (pid: 21856). 2011/11/23 01:49:22 ossec-agentd(1410): INFO: Reading authentication keys file. 2011/11/23 01:49:22 ossec-agentd(1750): ERROR: No remote connection configured. Exiting. 2011/11/23 01:49:25 ossec-syscheckd(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection error no remote refused'. 2011/11/23 01:49:25 ossec-rootcheck(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2011/11/23 01:49:31 ossec-logcollector(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2011/11/23 01:49:31 ossec-logcollector(1211): ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue'. Giving up.. 2011/11/23 01:49:33 ossec-syscheckd(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2011/11/23 01:49:33 ossec-rootcheck(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2011/11/23 01:49:46 ossec-syscheckd(1210): ERROR: Queue '/var/ossec/queue/ossec/queue' not accessible: 'Connection refused'. 2011/11/23 01:49:46 ossec-rootcheck(1211): ERROR: Unable to access queue: '/var/ossec/queue/ossec/queue'. Giving up.. Owner cjs226span commented Nov 23, 2011 I verified the client can communicate with the server as the server has a copy of the agent's key in /var/ossec/etc/client.keys Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Terms Privacy Security Status Help You can't perform that action at this time. You signed in with another tab or windo