*# ./wildifre start
Starting wildfire
nohup: appending output to `nohup.out’’
but wildire not run
NOTE: nohup.out is empty
Message was edited by: urgido
*# ./wildifre start
Starting wildfire
nohup: appending output to `nohup.out’’
but wildire not run
NOTE: nohup.out is empty
Message was edited by: urgido
Hey urgido,
It is ok for nohup.out to be empty. Is the server not working for you? Have you tried executing netstat -a to check that wildfire’'s process is listening on ports 9090 and 9091? You should be able to open a browser and connect to http://localhost:9090/login.jsp where localhost is the name of the machine running Wildfire. Also check out the log files and let us know if you see something there.
Thanks,
– Gato
IT2000 once told me to use the command :
sh -x ./wildfire start
to start wildfire. this will give you alot of info on what is going on with the script. if it is erroring due to misconfig, or directory path issues that will show you the place it fails… Hope this helps.
Jeff
Message was edited by: jeff_garner