rschilling / websmsdroid

Automatically exported from code.google.com/p/websmsdroid
0 stars 0 forks source link

No connection to o2 #581

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. register at www.o2online.de
2. enter phone nummber and password in connector
3. start websms

What is the expected output? What do you see instead?
Instead of a beeing able to send sms and seeing how many you can still send 
this month you get the eror message 
"o2:java.net.unknownHostException:login.o2online.de

What version of the product are you using? On what operating system?
websms 3.7.4
websms 02 connector 1.7.2 
Android 2.2.1 

Please provide any additional information below.
check my password several times - it is correct. I can send sms via the o2-app 
or on the website. O2 is the only connector i use - the old version is no 
longer installed. I tried to de- and reinstall th connector and websms ... but 
the problem is still there.

Original issue reported on code.google.com by MariaMNe...@gmail.com on 14 Sep 2011 at 6:04

GoogleCodeExporter commented 9 years ago

Original comment by f...@ub0r.de on 16 Sep 2011 at 4:17

GoogleCodeExporter commented 9 years ago

Original comment by f...@ub0r.de on 16 Sep 2011 at 4:17

GoogleCodeExporter commented 9 years ago
Unfortunately, this is hard for me to debug. The message basically says that 
the Connector can not initiate a connection to the login server. But since the 
o2 app is working, we can discard this possibility.
Could you possibly collect some logs? I'm CC'ing the author of WebSMS, since I 
don't really know how this works.

Original comment by sca...@gmail.com on 16 Sep 2011 at 9:18

GoogleCodeExporter commented 9 years ago
Sure i can - just tell me how ...

I'm a little worried as no one other than me seeems to have these problems

Original comment by MariaMNe...@gmail.com on 16 Sep 2011 at 10:13

GoogleCodeExporter commented 9 years ago
the standard procedure is: reproduce the problem, open websms' preferences,
send logs (filtered logs)

for your problem it might be usefull. to see full logs. so please install
sendlog from market, reproduce the problem, send logs with sendlog.

just some checkup questions:
do you use a custom /etc/hosts file?
does the url work in android's browser?

Original comment by f...@ub0r.de on 16 Sep 2011 at 12:25

GoogleCodeExporter commented 9 years ago
I did reproduce the problem  and have sent the log via websms>settings

Which kind of log-format (long, raw, process, ... )do you need and to which 
emailadress shall i send it (same as the one websms sent its log to)?

Concerning your checkup questions:
I'm sorry but I don't have a clue what you are asking ... help! (natürlich 
gerne auch auf deutsch)

Original comment by MariaMNe...@gmail.com on 16 Sep 2011 at 4:50

GoogleCodeExporter commented 9 years ago
brief format should do the job.

do you use some kind of ad blocking app like adfree?
did you try to paste the hostname which can not be resolved into your
webbrowser of your phone, to try, if it can access the site?

which

Original comment by f...@ub0r.de on 16 Sep 2011 at 5:01

GoogleCodeExporter commented 9 years ago
Please send the Log to issue-581@trashmail.net . Its a temporary email that 
forwards to my main email account, I want to avoid spam as much as possible. 
I'll post the log here then.

Thanks!

Original comment by sca...@gmail.com on 16 Sep 2011 at 5:20

GoogleCodeExporter commented 9 years ago
Yes I am using adfree (but never had any problems like this before)

but I didn't  send sms via websms for the last month or so - which is why i 
can't tell you how long this problem has been there 

I was able to log into login.o2online.de via my mobile webbrowser (dolphin) - 
it uses https and there's a warning about an untrusted certificate (in websms 
o2-connector the "ignore invalid certificate"-option is checked)

Original comment by MariaMNe...@gmail.com on 16 Sep 2011 at 5:30

GoogleCodeExporter commented 9 years ago
Hi Maria,

Thanks for sending in the logs. Unfortunately, no WebSMS messages are present 
in them. Which steps did you use to collect the logs?

Original comment by sca...@gmail.com on 19 Sep 2011 at 5:26

GoogleCodeExporter commented 9 years ago
Well - I did as I was told (or at least I think I did):

"the standard procedure is: reproduce the problem, open websms' preferences,
send logs (filtered logs)[...] install sendlog from market, reproduce the 
problem, send logs with sendlog."

I've also just sent you the long version of the log - if this one also doesn't 
help please let me know and I will (try to) get some new ones

Original comment by MariaMNe...@gmail.com on 19 Sep 2011 at 5:59

GoogleCodeExporter commented 9 years ago
Thanks a lot, this one has the WebSMS messages.

The gist:

D/WebSMS  (20853): de.ub0r.android.websms.connector.common.WebSMSException: 
java.net.UnknownHostException: login.o2online.de
D/WebSMS  (20853):  at 
com.websms.connector.o2.ConnectorO2.getHttpClient(ConnectorO2.java:550)
D/WebSMS  (20853):  at 
com.websms.connector.o2.ConnectorO2.sendData(ConnectorO2.java:428)
D/WebSMS  (20853):  at 
com.websms.connector.o2.ConnectorO2.doUpdate(ConnectorO2.java:517)
D/WebSMS  (20853):  at 
de.ub0r.android.websms.connector.common.ConnectorService.doInBackground(Connecto
rService.java:302)
D/WebSMS  (20853):  at 
de.ub0r.android.websms.connector.common.ConnectorService.onHandleIntent(Connecto
rService.java:270)
D/WebSMS  (20853):  at 
android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:59)
D/WebSMS  (20853):  at android.os.Handler.dispatchMessage(Handler.java:99)
D/WebSMS  (20853):  at android.os.Looper.loop(Looper.java:143)
D/WebSMS  (20853):  at android.os.HandlerThread.run(HandlerThread.java:60)
D/WebSMS  (20853): Caused by: java.net.UnknownHostException: login.o2online.de
D/WebSMS  (20853):  at 
java.net.InetAddress.lookupHostByName(InetAddress.java:513)
D/WebSMS  (20853):  at 
java.net.InetAddress.getAllByNameImpl(InetAddress.java:278)
D/WebSMS  (20853):  at java.net.InetAddress.getAllByName(InetAddress.java:242)
D/WebSMS  (20853):  at 
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(Default
ClientConnectionOperator.java:136)
D/WebSMS  (20853):  at 
org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
D/WebSMS  (20853):  at 
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapt
er.java:119)
D/WebSMS  (20853):  at 
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirecto
r.java:348)
D/WebSMS  (20853):  at 
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:5
55)
D/WebSMS  (20853):  at 
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:4
87)
D/WebSMS  (20853):  at 
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:4
65)
D/WebSMS  (20853):  at 
de.ub0r.android.websms.connector.common.Utils.getHttpClient(Utils.java:786)
D/WebSMS  (20853):  at 
com.websms.connector.o2.ConnectorO2.getHttpClient(ConnectorO2.java:545)
D/WebSMS  (20853):  ... 8 more

I'm not quite sure what to make of this. If this was a problem on AdFree's 
part, we prob. wouldn't see an UnknownHostException, since login.o2online.de 
should resolve to localhost. On the other hand Dolphin seems to do fine...
Also, no Exceptions regarding insufficient permissions, etc.

Maria, could you try disabling AdFree and then try update your balance again? 
Just to be sure. Do you have your telephone rooted?

Thanks

Thanks

Original comment by sca...@gmail.com on 19 Sep 2011 at 6:19

Attachments:

GoogleCodeExporter commented 9 years ago
may be this is related to ipv4/ipv6 issues, just a wild guess

Original comment by f...@ub0r.de on 19 Sep 2011 at 6:22

GoogleCodeExporter commented 9 years ago
Login.o2online.de doesn't have any AAAA entries, so no IPv6. I'll take you out 
of CC while trying to narrow down the problem, that way you wont get spammed 
all the time. Sound okay?

Original comment by sca...@gmail.com on 19 Sep 2011 at 6:28

GoogleCodeExporter commented 9 years ago
done myself ;)

Original comment by f...@ub0r.de on 19 Sep 2011 at 6:31

GoogleCodeExporter commented 9 years ago
I restored the hosts via adfree ... no change ... i deinstalled adfree ... 
rebooted ... no change
I deinstalled websms and the connector ... rebooted ... reinstalled websms and 
the connector ... marked both as trusted aps with LBE Security (=granted all 
rights) ...  but still no change

I did root my phone via oneclickroot about 6 months ago ... and am using 
superuser to grant su-rights. ... I do have several root-apps (as you can 
probebly tell from the log) und am using the LBE Security app to restrict and 
monitor some apps

I'll send you a new log (after all of that deinstalling, rebooting, 
reinstalling etc.) 

Original comment by MariaMNe...@gmail.com on 20 Sep 2011 at 9:41

GoogleCodeExporter commented 9 years ago
I think your problem is related to the LBE Security Manager. Just installed
it on my phone and told it to deny access to the internet for the o2
connector. Gives me the same error message you describe. Please check you
settings under "Internet Access Manager".

Original comment by sca...@gmail.com on 20 Sep 2011 at 12:02

GoogleCodeExporter commented 9 years ago
Only problem is ... everything related to websms and and the connector is 
marked as "trusted" and isn't even monitored by LBE 

But I deinstalled LBE (just in case) ... evn rebooted ... but still the same 
java message

I even downloaded (and activated) the cherry-sms connector to test ... it tells 
me "verbindung abgebrochen" 

Well I fear that i will have to do without websms in futur :(

Original comment by MariaMNe...@gmail.com on 20 Sep 2011 at 12:54

GoogleCodeExporter commented 9 years ago
Very weird. Can you try to execute (in a terminal app) and send me the
output of the following command?

nslookup login.o2online.de

Original comment by sca...@gmail.com on 20 Sep 2011 at 1:03

GoogleCodeExporter commented 9 years ago
I found the problem ...
or to be more precise the app causing trouble

I started to uninstall one app after another to find out which app was the 
troublemaker ... I started with the most recently installed apps ... after each 
uninstall i tried to use websms ... then I uninstalled the root-apps ...

After the uninstall of droidwall websms worked fine.

But there is one weird thing about this ... websms and the connectors were on 
the white list (= able to use 3g/wifi) and the firewall wasn't even activated.

I reinstalled several of the other apps (e.g. LBE) and none of them interfered 
with websms.

However - I'm so sorry for causing all this trouble and thanks ever so much for 
you help and patience. Thank you :-*

Original comment by MariaMNe...@gmail.com on 20 Sep 2011 at 3:06

GoogleCodeExporter commented 9 years ago
No worries, you're welcome :) Good of you to go through the hassle of trying
to narrow down the problem. I'm closing this issue.

Original comment by sca...@gmail.com on 20 Sep 2011 at 3:35

GoogleCodeExporter commented 9 years ago

Original comment by sca...@gmail.com on 20 Sep 2011 at 3:36