Hey, That's very unusual... At that stage in the install it is just copying the files over and restarting OSSEC. First time I heard of it hanging in there.
Do you mind re-trying the install to see if it happens again? If it happens, if you can try it with debug enabled ( bash -x ./install.sh ) that might give us some hints of what is going on. Thanks, -- Daniel B. Cid dcid ( at ) ossec.net On Thu, Dec 10, 2009 at 1:52 PM, jplee3 <[email protected]> wrote: > Nevermind. I just had to let it sit [for a really long time!] before > it eventually finished. Kind of annoying but it turned out to be fine. > > On Dec 9, 1:40 pm, jplee3 <[email protected]> wrote: >> I've attempted both agent and local installations on a couple of >> identical 2.6.23.1-42.fc8 servers and cannot get OSSEC to successfully >> install. The install always hangs at >> >> make[1]: Leaving directory `/home/jlee/ossec-hids-2.2/src/monitord' >> >> Here is a snippet of the last of the install process: >> >> cp -pr manage_agents ../../bin >> cp -pr manage_agents ../../bin >> make[1]: Leaving directory `/home/jlee/ossec-hids-2.2/src/addagent' >> make[1]: Entering directory `/home/jlee/ossec-hids-2.2/src/util' >> cp -pr syscheck_update clear_stats list_agents syscheck_control >> rootcheck_control agent_control ../../bin >> make[1]: Leaving directory `/home/jlee/ossec-hids-2.2/src/util' >> make[1]: Entering directory `/home/jlee/ossec-hids-2.2/src/rootcheck' >> make[1]: Nothing to be done for `build'. >> make[1]: Leaving directory `/home/jlee/ossec-hids-2.2/src/rootcheck' >> make[1]: Entering directory `/home/jlee/ossec-hids-2.2/src/syscheckd' >> cp -pr ossec-syscheckd ../../bin >> make[1]: Leaving directory `/home/jlee/ossec-hids-2.2/src/syscheckd' >> make[1]: Entering directory `/home/jlee/ossec-hids-2.2/src/monitord' >> cp -pr ossec-monitord ../../bin >> cp -pr ossec-reportd ../../bin >> make[1]: Leaving directory `/home/jlee/ossec-hids-2.2/src/monitord' >> >> Does anybody know what the problem is here? >
