You can try running this command to kill port 5037:
*fuser -k tcp 5037*
Otherwise, read this article to get a better understanding of what's
running on your ports:
https://www.debian-administration.org/article/184/How_to_find_out_which_process_is_listening_upon_a_port
On Wednesday, June 10, 200
I'm having this same issue. Thinking the only solution may be to reinstall
the android sdk tools?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from
Hi.
I saw with the netstat -a command that the port 5037 was occupied.
It's OK now.
thanks
On 10 juin, 16:11, "H N Kavya-DXN738" wrote:
> Try killing the daemon many times. And again try starting it. It may
> help
>
> -Original Message-
> From: android-developers@googlegroups.com
>
> [
Hi.
I saw with the netstat -a command that the port 5037 was occupied.
It's OK now.
thanks
On 10 juin, 16:11, "H N Kavya-DXN738" wrote:
> Try killing the daemon many times. And again try starting it. It may
> help
>
> -Original Message-
> From: android-developers@googlegroups.com
>
> [
Try killing the daemon many times. And again try starting it. It may
help
-Original Message-
From: android-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] On Behalf Of jphdsn
Sent: Wednesday, June 10, 2009 7:36 PM
To: Android Developers
Subject: [android-develope
I will try in three or four hours I have to go now
I will send another post if it works or not
Thanks very much
2009/6/10 David Turner
> You should be able to use netstat -a to see which processes are bound to
> which ports
>
>
> On Wed, Jun 10, 2009 at 4:33 PM, jphdsn wrote:
>
>>
>> Precisio
You should be able to use netstat -a to see which processes are bound to
which ports
On Wed, Jun 10, 2009 at 4:33 PM, jphdsn wrote:
>
> Precision, I'm on macintosh...
>
> On 10 juin, 16:29, jphdsn wrote:
> > I don't think so but how can I be sure of that?
> >
> > thanks
> >
> > On 10 juin, 16:2
Precision, I'm on macintosh...
On 10 juin, 16:29, jphdsn wrote:
> I don't think so but how can I be sure of that?
>
> thanks
>
> On 10 juin, 16:22, David Turner wrote:
>
> > The ADB server binds and listen to port 5037. The error message seems to
> > indicate that another process is already usi
I don't think so but how can I be sure of that?
thanks
On 10 juin, 16:22, David Turner wrote:
> The ADB server binds and listen to port 5037. The error message seems to
> indicate that another process is already using this port.
> Do you have specific services / background programs running your
The ADB server binds and listen to port 5037. The error message seems to
indicate that another process is already using this port.
Do you have specific services / background programs running your machine ?
On Wed, Jun 10, 2009 at 4:06 PM, jphdsn wrote:
>
> Hi
> Coud anyone tell me if he had been
10 matches
Mail list logo
