Another process is already running and attached to port 8080 most likely. You will see the same issue when starting other daemons twice when the first instance is still running and bound to the port. Maybe httpd was still running? I have done that many times myself. Scott Garry Taylor wrote: > Jason Henderson wrote: > >> can anyone tell me what this means please >> >> i ran the test config and this is the reply i got >> >> only one usage of each socket address(protocol/network address/port) >> is normally permitted : make_sock could not bind to address >> 192.168.1.100:8080 >> no listening sockets available shutting down >> unable to open logs >> >> thank you >> >> >> --------------------------------------------------------------------- >> The official User-To-User support forum of the Apache HTTP Server >> Project. >> See <URL:http://httpd.apache.org/userslist.html> for more info. >> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx >> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx >> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx >> > looks like some other demon is using port 8080. Try running a "lsof -n | > grep 8080" to find out what it is. > Giz > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > -- Scott Smyth, consultant ssmyth@xxxxxxxxxxxxxxxxxxxx 206-851-0979 --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|