A
andrerca12
Hello, good night.
I'm with an peculiar issue in my environment.
I already noticed this behavior in three servers, with three different services.
Whenever I try to restart a service, Windows will not let me start it again, and in the logs I find that the port is already being used. The only way to start the service is restarting the server or changing the port application.
Real example:
I stopped Zabbix Agent service, running on port 10050. I'm unable to start the service again if i don't boot the server or change the port. With the service currently stopped, this 10050 port is not showing up in NETSTAT nor TCP VIEW, so theoretically there is no application using it. Also, there are no proccesses running for Zabbix Agent.
I have no clue on how to solve this. Im suspicious Windows Update may be the cause, but i haven't seen other people with this problem.
Continue reading...
I'm with an peculiar issue in my environment.
I already noticed this behavior in three servers, with three different services.
Whenever I try to restart a service, Windows will not let me start it again, and in the logs I find that the port is already being used. The only way to start the service is restarting the server or changing the port application.
Real example:
I stopped Zabbix Agent service, running on port 10050. I'm unable to start the service again if i don't boot the server or change the port. With the service currently stopped, this 10050 port is not showing up in NETSTAT nor TCP VIEW, so theoretically there is no application using it. Also, there are no proccesses running for Zabbix Agent.
I have no clue on how to solve this. Im suspicious Windows Update may be the cause, but i haven't seen other people with this problem.
Continue reading...