Hi there, I rebooted the system, because the process was killed but the socket wasn't closed. The Windows Operating System is awfull.
Solved now, thanks. Em 04-03-2011 00:26, Morty escreveu: > On Thu, Mar 03, 2011 at 03:12:33PM -0300, Rafael Henrique da Silva Correia > wrote: > >> Sorry... Portuguese... >> >> In English: >> >> \Socket.h:677: bind failed: 10048: Only one usage of each socket address >> (protocol>network address/port) is normally permitted. >> > Stop the daemon and run netstat in the mode that shows all sockets and > what processes are bound to them. Under linux, that's netstat -pan. > Under Windows, I think it's something like netstat -ban. > > - Morty > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > Nagios-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -- Rafael Henrique da Silva Correia http://abraseucodigo.blogspot.com Administrador de Sistemas Linux Certificado pela LPIC - 101 ID: LPI000160699 ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
