10 messages in com.googlegroups.android-beginnersRe: it seems too many emulator instan...| Subject: | Re: it seems too many emulator instances are running on this machine. Aborting |
|---|---|
| From: | D. Qiu (dieg...@gmail.com) |
| Date: | 12/22/2007 05:53:19 PM |
| List: | com.googlegroups.android-beginners |
Hi,
I am experiencing the same problem now with exactly the same output when try to run emulator. The machine I am running android is fedora 7 i386, with 2.6.23.1-21.fc7 kernel. Android SDK version is: android_sdk_linux_m3-rc37a.
I tried netstate -p -a -t -n and confirmed the ports are not occupied. Also I tried "adb kill-server" and then "emulator", and still get the same thing. When I try to do "adb get-status" it gives me:
[qiud@localhost bin]$ adb get-state * daemon not running. starting it now * cannot bind 'tcp:5037' ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon
Any help is appreciated.
d.
On Dec 22, 5:07 am, snowtiger <snow...@gmail.com> wrote:
...have you already tried a simple "adb kill-server" ?much
This always helps for me in my Windows environment, when i get the same error message.
On Dec 21, 11:01 am, Digit <digi...@gmail.com> wrote:
wow, thanks for the output, it seems that no other program is bound to these ports, which makes me perplex. can you tell me which distro/machine you're using ? I wonder if I can replicate this...
On Dec 20, 2007 11:26 PM, colin <Mr.C...@gmail.com> wrote:
Here is the output you requested
tcp 0 0 *:5800 *:* LISTEN 15687/kded tcp 0 0 *:5900 *:* LISTEN 15687/kded tcp 0 0 *:63342 *:* LISTEN 16633/java tcp 0 0 *:2864 *:* LISTEN 16633/java tcp 0 0 *:x11 *:* LISTEN - tcp 0 0 *:auth *:* LISTEN - tcp 0 0 *:ssh *:* LISTEN - tcp 0 0 *:postgresql *:* LISTEN - tcp 0 0 *:6942 *:* LISTEN 16633/java tcp 0 1 10.0.0.1:41753 10.0.0.1:2864 SYN_SENT 16633/java
I tried again right after running netstat...
colin@warthog ~ $ emulator it seems too many emulator instances are running on this machine. Aborting
Colin
On Dec 20, 10:27 pm, Digit <digi...@gmail.com> wrote:
hello,
when the emulator starts, it tries to bind to local TCP ports 5554 and 5555 (these are used for the control console and ADB). If this doesn't work, because at least one of the ports is already in use, it tries 5556/5557, then 5558/5559, etc... until it reaches 5584/5585. if this final port pair cannot be bound, then the emulator stops and dumps the dreaded "it seems too many emulator instances..." message.
this scheme allows for up to 16 concurrent emulator instances on a given development machine; taht is, unless these ports are already bound to a different program.
on Linux, you should be able to type "netstat -a -p tcp -n"; this will list all connected/bound TCP sockets on your machine, with the PID of the program that uses them.
could you send us the output of this command (only the first lines that start with "tcp" are needed) ?
On Dec 20, 2007 8:24 AM, colin <Mr.C...@gmail.com> wrote:
Hi
I've just installed android on a linux box and I get the message in the subject line when I try to run the emulator. I get the same message when I try running an activity from the idea-android plugin. Here is the output of emulator -verbose Does anyone have any idea how I can get around this.
Colin
colin@warthog ~ $ emulator -verbose emulator: Assuming: -sysdir /home/colin/apps/android_sdk_linux_m3- rc37a/tools/lib/images/ emulator: autoconfig: -kernel /home/colin/apps/android_sdk_linux_m3- rc37a/tools/lib/images/kernel-qemu emulator: autoconfig: -ramdisk /home/colin/apps/android_sdk_linux_m3- rc37a/tools/lib/images/ramdisk.img emulator: autoconfig: -image /home/colin/apps/android_sdk_linux_m3- rc37a/tools/lib/images/system.img emulator: autoconfig: -skindir /home/colin/apps/android_sdk_linux_m3- rc37a/tools/lib/images/skins emulator: autoconfig: -data /home/colin/.android/userdata.img emulator: warning: cannot load emulator configuration at '/home/ colin/.android/emulator.cfg'
emulator: parsing built-in skin layout file (size=3114) emulator: skin network speed: 'full' emulator: skin network delay: 'none' emulator: argv[00] = "emulator" emulator: argv[01] = "-kernel" emulator: argv[02] = "/home/colin/apps/android_sdk_linux_m3-rc37a/ tools/lib/images/kernel-qemu" emulator: argv[03] = "-initrd" emulator: argv[04] = "/home/colin/apps/android_sdk_linux_m3-rc37a/ tools/lib/images/ramdisk.img" emulator: argv[05] = "-nand" emulator: argv[06] = "system,size=0x4200000,initfile=/home/colin/apps/ android_sdk_linux_m3-rc37a/tools/lib/images/system.img" emulator: argv[07] = "-nand" emulator: argv[08] = "userdata,size=0x4200000,file=/home/ colin/.android/userdata.img" emulator: argv[09] = "-serial" emulator: argv[10] = "android-modem" emulator: argv[11] = "-append" emulator: argv[12] = "qemu=1 console=null android.checkjni=1 keycharmap=qwerty2 android.ril=ttyS0" emulator: reading read-only file '/home/colin/apps/ android_sdk_linux_m3-rc37a/tools/lib/images/system.img' (67584.0 KB) emulator: opening read/write file '/home/colin/.android/userdata.img' it seems too many emulator instances are running on this machine.