It is impossible to create a new session because 'createSession' which takes HttpClient, - iphone

org.openqa.selenium.WebDriverException: It is impossible to create a new session because 'createSession' which takes HttpClient, InputStream and long was not found or it is not accessible
Build info: version: '3.12.0', revision: '7c6e0b3', time: '2018-05-08T14:04:26.12Z'
I am getting this error randomly i want to know the route cause for this issue in IOS

There are multiple reason behind this issue. There are multiple ways to resolve this issues, depending upon, where these issues are coming from.
1)One issue which occur to me was DesireCapabilities.setCapability() key/value was not correct type. I have resolved this issue by just
DesiredCapabilities.setCapability("capabilities_variable","capabilities_value");
setCapability("appWaitDuration", "600000"); here 600000 was String instead of long or int
Check your setCapability type whether it String/int/long.
2) Check USB Connection is Laptop or Computer, if not connected than same issue.
3) ADB Server might be problem. So adb kill-server and adb start-server
4) Try to change USB and try it out.
5) Sometimes, it might be a proxy issue(Laptop/Desktop may have some proxy setup
in organization, since for Desktop/Laptops are connected with Mobile via TCP/IP Connection).
6) Sometimes, there might be permission required to access PORT (sudo ufw allow portnumber (UBUNTU SYSTEM))
7) Environment variable required Android_SDK_Home and Android Platform Tools path

**> Solution 1st**
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability("deviceName", "xyz");
capabilities.setCapability("platformVersion", "6.0");
capabilities.setCapability("platformName", Platform.ANDROID);
capabilities.setCapability("appPackage", "com.hp.HPSupportAssistant");
capabilities.setCapability("appActivity", "com.hp.HPSupportAssistant.MainActivity");
capabilities.setCapability(MobileCapabilityType.NEW_COMMAND_TIMEOUT, 6000); capabilities.setCapability(AndroidMobileCapabilityType.AUTO_GRANT_PERMISSIONS,true);
//desiredCap.setCapability(MobileCapabilityType.AUTOMATION_NAME, AutomationName.ANDROID_UIAUTOMATOR2);
**Here comment below line and then run it will work**
desiredCap.setCapability(MobileCapabilityType.AUTOMATION_NAME, AutomationName.ANDROID_UIAUTOMATOR2);
**solution 2nd Or keep above line in desired capabilities but before that do
run 3 cmd on cmd promt**
adb shell pm list packages -f > D://t.txt
adb uninstall io.appium.uiautomator2.server
adb uninstall io.appium.uiautomator2.server
desiredCap.setCapability(MobileCapabilityType.AUTOMATION_NAME, AutomationName.ANDROID_UIAUTOMATOR2);

Related

Cannot send command IR with HotPI

I bought a HotPi a while ago, and decided to use it. So I followed the procedure to configure the IR and after a few hours I was able to IR signals on my Raspberry 1.
But my purpose here is to send IR signals, which I tried, without any luck.
So this is the command I try to do (just for test):
irsend SEND_START devinput KEY_POWER ; sleep 3
And this is what lircd tells me:
lircd-0.9.4c[907]: Notice: accepted new client on /var/run/lirc/lircd
lircd-0.9.4c[907]: Info: Cannot configure the rc device for /dev/lirc0
lircd-0.9.4c[907]: Error: invalid send buffer
lircd-0.9.4c[907]: Error: this remote configuration cannot be used to transmit
lircd-0.9.4c[907]: Error: error processing command: SEND_START devinput KEY_POWER
lircd-0.9.4c[907]: Error: transmission failed
lircd-0.9.4c[907]: Info: removed client
Edit:
It seems I'm not using the good drivers. According to the HotPi documentation, I'm suppose to use lirc-rpi, which I'm suppos to install with
sudo modprobe lirc-rpi
Which, at least, doesn't return an error. But trying to configure the interface tells me that the driver doesn't exist:
pi#raspberrypi:~ $ mode2 --driver lirc-rpi --device /dev/lirc0
Driver `lirc-rpi' not found. (Missing -U/--plugins option?)
Available drivers:
accent
alsa_usb
asusdh
atilibusb
atwf83
audio
audio_alsa
awlibusb
bte
bw6130
commandir
creative
creative_infracd
default
devinput
dfclibusb
dsp
dvico
ea65
file
ftdi
ftdi-exp
ftdix
girs
i2cuser
irlink
irtoy
livedrive_midi
livedrive_seq
logitech
macmini
mouseremote
mouseremote_ps2
mp3anywhere
mplay
mplay2
pcmak
pinsys
pixelview
samsung
sb0540
silitek
slinke
sonyir
srm7500libusb
tira
tira_raw
udp
uirt2
uirt2_raw
usb_uirt_raw
usbx
zotac
Here is no info what lirc version you are using. There are vast differences between the legacy 0.9.0 still used in some distros and modern lirc.
That said, the logs seems pretty clear. You are using the devinput driver, right? This driver does not support sending data, reflecting the fact that also the kernel doesn't.
You then need to use another driver - first stop might be the default one. If/when using this other driver, you need another lircd.conf.
Please refer to http://lirc.org/html/configuration-guide.html
EDIT: Ah, lirc-0.9.4c says the log. Sorry, my bad. The reply should still be valid, though.
When you record the remote, use:
irrecord -d /dev/lirc0 -f name.conf
The -f uses raw mode. This then worked for me on the transmit side, before I got same error as you.

Connect Beaglebone black to Internet via Fona and a Sim needing APN authentication

I have a BBB, a Fona from Adafruit and a LycaMobile 3G Sim card and I wanted to connect BBB to internet using this 3G sim. I followed : this tutorial from adafruit to do so.
But to connect to my APN I need to set username and password. SO I did this :
in my /etc/ppp/peers/fona :
Instead of
noauth
I put :
auth
user lmfr
name lycamobile
and in my /etc/ppp/chap-secrets as well as in my etc/ppp/pap-secrets I put :
"lmfr" * "plus"
But I have the following error when i do this :
sudo pon fona
/usr/sbin/pppd: The remote system is required to authenticate itself
/usr/sbin/pppd: but I couldn't find any suitable secret (password) for it to use to do so
/usr/sbin/pppd: (None of the available passwords would let it use an IP address)
Does anyone knows how to fix this or another way to connect to Fona with APN authentication ?
Struggling with authentication using FONA on either Raspberry Pi 2 and 3 even while strictly following the Adafruit FONA setup instructions, the following steps helped me to get it work on both Pi's - based on a freshly installed raspbian/debian stretch OS. Adopt the following to your BBB:
update OS:
sudo apt-get update
sudo apt-get dist-upgrade
install neccessary packages:
sudo apt-get install ppp screen
connect FONA board to Pi/BBB as described within Adafruit FONA setup instructions
ensure you disabled kernel's use of hardware serial connection!
Pi2: follow Adafruit description
Pi3: "sudo raspi-config" > "Interfacing Options" > "Serial"
> "...login shell... over serial?" NO
> "...serial port hardware enabled?" YES
exit/finish raspi config and
check
sudo nano /boot/config.txt
if line enable_uart=1 is included. If not, add this as new line and save
[Ctrl]+[x], [y], [Enter] > reboot!
find the correct serial port for your Pi/BBB. This command might help - it shows all available ports:
ls /dev
Examples:
Pi2: "/dev/ttyAMA0"
Pi3: "/dev/serial0"
BBB: "/dev/tty04" (as stated at Adafruit)
Ensure that the FONA is answering on the corresponding serial port - in this example on Pi3:
screen /dev/serial0 115200
A black screen (terminal window) should occur. Write
AT [Enter]
and you should get OK as response. If you don't get the "OK", just disconnect the battery, reconnect it afterwards and give it another try! You can exit the terminal window at any time through
[Ctrl]+[A]
:quit [Enter]
As soon as the FONA board is answering over serial connection, the cellular connection (especially authentication) is the target.
Changing noauth to auth within "fona" did not help me, neither editing "chap-secrets" and/or "pap-secrets". Have the 3 APN values included within the "fona" file:
sudo -i
cd /etc/ppp/peers
nano fona
Enter the correct APN name within the "connect" line, like Adafruit mentioned:
connect "/usr/sbin/chat ... -T T-Mobile"
and replace "T-Mobile" with your APN name. Ensure to uncomment only one line within the next block, having the exact same serial port included as above when successfully testing the serial connection (in this example again the Pi3 port)
/dev/serial0
Now add the following section at the end of the file for fona-file authentication:
#Authentication
user abcd#efgh.dom << here goes the providers APN user name
password 1a2b3d4e << here goes the providers APN password
Save and exit the file and exit the superuser mode
[Ctrl]+[x], [Y], [Enter]
exit [Enter]
At least give it a try, as stated at Adafruit
sudo pon fona
If the red LED starts blinking twice every second you're done! If not, please follow the Adafruit troubleshooting section, which should solve the missing bits and pieces.
The essential parts are propper serial connection and - as soon as that works - the authentication within the "fona" file!
Especially the cellular connection and authentication should be adoptable to BBB, once the serial connection is established.
Here is what I did :
I made sure that I could see /dev/ttyO4 after adding capemgr.enable_partno=BB-UART4 to uEnv.txt
I installed ppp, screen, elinks, jdk1.8-linux-arm and librxtx-java
I used the fona library from angryelectron. So I downloaded the library on my PC and build it via "ant jar" and it generated some jar files.
I created a Main.java file in which I put this :
public class Main {
//Make sure You can see /dev/ttyO4 on your Beagle Bone Black or /dev/ttyAMA0 on raspberryPi
private static final String PORT = "/dev/ttyO4";
private static final Integer BAUD = 115200;
//Credentials for Lycamobile Wireless required for testing GPRS.
private static final String APN = "data.lycamobile.fr";
private static final String USER = "lmfr";
private static final String PWD = "plus";
private static final String SMTP = "smtp.lycamobile.fr";
public static void main(String[] args)
{
try
{
fona.open(PORT, BAUD);
testGprsHttpGet();
fona.close();
}
catch(Exception e)
{
System.out.println("exception " + e);
}
}
public static void testGprsHttpGet() throws FonaException {
System.out.println("gprsHttpGet");
fona.gprsEnable(APN, USER, PWD);
String response = fona.gprsHttpGet("http://httpbin.org/user-agent");
if (!response.contains("SIMCOM_MODULE")) {
System.out.println("Fails");
}
else{
System.out.println(response);
}
}
}
Also created a simple exec.sh file :
JAVA_OPT="-Djava.library.path=/usr/lib/jni -Dgnu.io.rxtx.SerialPorts=/dev/ttyO4"
javac -cp .:fona-0.92.jar:fona.jar:RXTXcomm-2.2pre2.jar:fona-0.92-sources.jar Main.java
java $JAVA_OPT -cp .:fona-0.92.jar:fona.jar:RXTXcomm-2.2pre2.jar:fona-0.92-sources.jar Main
I put all those files in a folder :
fona-0.92.jar fona.jar RXTXcomm-2.2pre2.jar fona-0.92-sources.jar Main.java and copied the folder on BBB
launched my script exec.sh and thats it. In the output I can see :
{
"user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36"
}
And the NET led blinks like twice a second.
Hope this helps someone else.

python-memcache memcached -- I installed on centos virtualbox but it get/set never seem to work

I'm using python. I did a yum install memcached followed by a easy_install python-memcached
I used the simple test program from the Help(memcache). When I wasn't getting the proper answers I threw in some print statements:
[~/test]$ cat m2.py
import memcache
mc = memcache.Client(['127.0.0.1:11211'], debug=0)
x = mc.set("some_key", "Some value")
print 'Just set a key and value into the cache (suposedly)'
value = mc.get("some_key")
print 'Just retrieved that value from the cache using the key'
print 'X %s' % x
print 'Value %s' % value
[~/test]$ python m2.py
Just set a key and value into the cache (suposedly)
Just retrieved that value from the cache using the key
X 0
Value None
[~/test]$
The question now is, what have I failed to do in my installation? It appears to be working from an API perspective but it fails to put anything into the memcache share area.
I'm using a virtualbox vm running centos
[~]# cat /proc/version
Linux version 2.6.32-358.6.2.el6.i686 (mockbuild#c6b8.bsys.dev.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Thu May 16 18:12:13 UTC 2013
Is there a daemon that is supposed to be running? I don't see an obvious named one when I do a ps.
I tried to get pylibmc installed on my vm but was unable to find a working installation so for now will see if I can get the above stuff working first.
I discovered if i ran straight from the python console GUI i get a bit more output if I set debug=1
>>> mc = memcache.Client(['127.0.0.1:11211'], debug=1)
>>> mc.stats
{}
>>> mc.set('test','value')
MemCached: MemCache: inet:127.0.0.1:11211: connect: Connection refused. Marking dead.
0
>>> mc.get('test')
MemCached: MemCache: inet:127.0.0.1:11211: connect: Connection refused. Marking dead.
When I try to use per the example telnet to connect to the port i get a connection refused:
[root#~]# telnet 127.0.0.1 11211
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
[root#~]#
I tried the instructions I found on the net for configuring telnet so localhost wouldn't be disabled:
vi /etc/xinetd.d/telnet
service telnet
{
flags = REUSE
socket_type = stream
wait = no
user = root
server = /usr/sbin/in.telnetd
log_on_failure += USERID
disable = no
}
And then ran the commands to restart the service(s):
service iptables stop
service xinetd stop
service iptables start
service xinetd start
service iptables stop
I ran with both cases (iptables started and stopped) but it has no effect. So I am out of ideas. What do I need to do to make it so the PORT will be allowed? if that is the problem?
Or is there a memcached service that needs to be running that needs to open up the port ?
well this is what it took to get it working: ( a series of manual steps )
1) su -
cd /var/run
mkdir memcached # this was missing
In the memcached file I added "-l 127.0.0.1" to the OPTIONS statement. It's apparently a listen option. Do this for steps 2 & 3. I'm not certain which file is actually used at runtime.
2) cd /etc/sysconfig
cp memcached memcached.old
vi memcached
3) cd /etc/init.d
cp memcached memcached.old
vi memcached
4) Try some commands to see if the server starts now
/etc/init.d/memcached start
/etc/init.d/memcached status
/etc/init.d/memcached stop
/etc/init.d/memcached restart
I tried opening a browser, but it never seemed to actually display anything so I don't really know how valid this approach is. I'm not running apache or anything like this so perhaps its not relevant to my cause. Perhaps I would have to supply a ?key=blah or something.
5) http://127.0.0.1:11211
6) Now it should be ready to go. If one runs the test shown with the following it should work. At least it did for me. doing the help(memcache) will display a simple program. just paste that in and it should work just fine.
[~]$ python
>>> import memcache
>>> help(memcache)

Error with "Get Started" on Oracle Express 11g

this is my first post so I will try to be as descriptive as possible. Please let me know if there is anything missing:
So I am trying to install Oracle Express 11g, after I download the zip file "OracleXE112_Win32" - I unzip it, and open Disk 1 then setup. I go through the entire installation process without any problems. However when I go to open "Get Started" I come across the following error:
"Windows cannot find 'http:/.127.0.0.1:%HTTPPORT%/apex/f?p=4950'. Make sure you typed the name correctly, and then try again. -- After googling this, I was told to change %HTTPPORT% to 8080.
If I do this when I click on "Get Started" the following error shows up:
"Firefox can' establish a connection to the server at 127.0.0.1:8080."
I need this to work, so that I can sooner or later connect this to my eclipse, so that I can start doing my homework for my Java Programming class. Any help is greatly appreciated, thank you so much!
I have found one solution for this problem. In order to explain my solution, I have used some aliases referring to my real parameters. These are:
[ME] = my user name
[MYHOST] = my current workstation hostname (netbios name as well)
[MYHOST.mycompany.com] = my worksation's fully qualified domain name
At the beginning I had the same situation as mentioned above: I was unable to connect to the apex service even after successful installation.
First I have used the tnsping oracle utility:
C:\Users\ME>tnsping MYHOST
This was the answer:
TNS Ping Utility for 32-bit Windows: Version 11.2.0.2.0 - Production
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
C:\oraclexe\app\oracle\product\11.2.0\server\network\admin\sqlnet.ora
Used HOSTNAME adapter to resolve the alias
Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=
(PROTOCOL=TCP)(HOST=fe80::5d34:78a:5862:64%20)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=fe80::c27:54a4:1600:86a4%26)(PORT=1521))(ADDRESS=
(PROTOCOL=TCP)(HOST=fe80::38ab:cdb4:dd77:7ed9%12)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)
(HOST=10.9.32.208)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.56.1)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.106)(PORT=1521)))
TNS-12541: TNS:no listener
You see above a lot of currently active different IP addresses. Only the most important 127.0.0.1 is missing. I work on notebook so the network is "almost always" changing (WLAN, 3G, HSDPA, Ethernet etc.) only the localhost is fixed. And that was the real case of the trouble. (When I was working at the office environment connected to the office network it was also working.)
When I was in this situation I also started to use the lsnrctl oracle utility.
I have seen the following:
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 11.2.0.2.0 - Production
Default Service XE
Listener Parameter File /oraclexe/app/oracle/product/11.2.0/server\network\admin\listener.ora
Listener Log File C:\oraclexe\app\oracle\diag\tnslsnr\MYHOST\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=MYHOST.mycompany.com)(PORT=1521)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
You can see that the service for the apex at 8080 port is missing !!!
I have tried also the normal ping which worked perfectly:
C:\Users\ME>ping MYHOST.mycompany.com
The result was:
MYHOST.mycompany.com [fe80::c27:54a4:1600:86a4%26] ping
response fe80::c27:54a4:1600:86a4%26: time<10 ms
...
You can realize the IPv6 address also exists in my tnsping trial as well.
So I have decided to define MYHOST in my local hosts file directly:
127.0.0.1 localhost MYHOST MYHOST.mycompany.com
Testing now with ping:
C:\Users\ME>ping MYHOST
And the answer:
MYHOST.mycompany.com [127.0.0.1] ping:
response 127.0.0.1: byte=32 time<10 ms. TTL=128
...
At this point I have restarted (stopped and started again) the both running Oracle services (just for sure):
OracleServiceXE
OracleXETNSListener
And look the miracle:
C:\Users\ME>lsnrctl
LSNRCTL for 32-bit Windows: Version 11.2.0.2.0 - Production
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 11.2.0.2.0 - Production
Default Service XE
Listener Parameter File /oraclexe/app/oracle/product/11.2.0/server\network\admin\listener.ora
Listener Log File C:\oraclexe\app\oracle\diag\tnslsnr\MYHOST\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=MYHOST.mycompany.com)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=MYHOST.mycompany.com)(PORT=8080))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL>
You can see the important line with PORT=8080 and service XE instance.
So I am happy the getting started URL is working again.
What browser are you using? I experienced the same issue with Chrome. Download firefox, Right click the "Get Started With Oracle Database 11g Express Edition" icon and change the "opens with" option to firefox.
Simple solution:
You need to directly tell where your http port is. To do so; open up the folder where your Oracle is stored and navigate to server folder( in my case C:\Oracle\oraclexe\app\oracle\product\11.2.0\server) in that folder right click to Get_Started file and choose properties. There you can hand type your http port which is usually 8080 in my case: ....127.0.0.1:8080/apex/f?p=4950
The problem should be solved.
Hope this helps you get through it..
Pinar U.S.
Right Click on the "Get Started" icon and click on the properties and select General tab. Click on change button and select other browser installed in your system other than the current one . after setting this up, you'll be able to open the panel.
I also experienced the same problem for this go to start-> all programs -> Oracle Database 11g Express Edition and right click on get started and click open file location and drag and drop the "Get_Started" to your browser
Ok, I found the solution. Right click on icon of "Get Started With Oracle Database 11g Express Edition", then "properties". Then click "General tab" and then you will see option "change", click on that and then select your browser, click "apply" and "ok". And then start the Database again.
Drag and drop get started link into browser address bar worked great for me, I tried EVERYTHING else, adding port to hosts, changing port in properties etc. nothing worked, until I dragged and dropped... So damn simple, wish I did that hours ago
Your solution is partially correct buddy. You need to match the entries in the file:
C:\oraclexe\app\oracle\product\11.2.0\server\network\ADMIN\listener.ora
(the entries with the --> mark)
:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
--> (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
--> (ADDRESS = (PROTOCOL = TCP)(HOST = myserver.company.com)(PORT = 1521))
)
)
:
With the entries in the file:
C:\Windows\System32\drivers\etc\hosts
(the entries with the --> mark)
:
--> 127.0.0.1 localhost
--> 1.2.3.4 myserver myserver.company.com
:
Finally, under Administrator account do:
C:> lsnrctl stop
C:> lsnrctl start
Solved. No need for changing name, no drag & drop either.

Should I worry about DDMS console log messages "Can't bind to local nnnn for debugger"?

I'm new to Android programming (and Eclipse IDE and Android emulator). I've got Hello World and some of Notepad working, but I'm still constantly getting quite a few DDMS console log messages (shown below) about not being able to bind locals for debugger.
[2010-05-29 21:03:16 - ddms] Can't bind to local 8601 for debugger
[2010-05-29 21:05:26 - Device] Failed to delete temporary package: device (emulator-5556) request rejected: device not found
[2010-05-29 21:06:47 - ddms] Can't bind to local 8600 for debugger
[2010-05-29 21:07:05 - ddms] Can't bind to local 8601 for debugger
[2010-05-29 21:07:05 - ddms] Can't bind to local 8602 for debugger
And so on. Is this a problem? Can I get rid of these messages somehow?
In Eclipse, goto
1) Windows->Preference
2) Expand Android menu in the side of the Preference Window.
3) Now select DDMS from it.
4) Then Set the Base local debugger port to "8601" and enable "Use ADBHOST" checkbox and the ABDHOST value should be "127.0.0.1".
5) Click apply and ok.
6) Now you have to restart your ADB, for this you have to login as root user(Assuming linux user) and navigate to Platfrom tools folder of your Android SDK. Then execute,
./adb kill-server
./adb start-server
You will be able to see the message "Daemon started Successfully" . If not repeat step 6 once again until you see the success message.
You can get rid of the the messages by adding following to your hosts file:
127.0.0.1 localhost
ps. hosts file can be found from c:\windows\system32\drivers\etc\hosts
or if you are on linux /etc/hosts
In my situation the problem has been solved by a uninstalling all Java 7. The debugger is now working again!