Unable to logging with the new beta client for Linux

Hello,

Before upgrading, I was able to run SecondLife with Ubuntu 9.10 without problem, then when the version for linux changed, the SecondLife client forced to installed the new version, the one currently available (it didn't run othewise). Since upgrading to this new version, it doesn't work.

After the message of "Logging", it takes quite a while, before another message saying "Unable to loggin in SecondLife. Unexpecte error. Please checke at secondlife.com/status".

I have tried deleting the .secondlife folder but nothing happens.

I run SecondLife clicking on the sh file SecondLife, run on terminal, and this is the text that appears on terminal before crashing:

2010-01-24T18:45:03Z INFO: authenticate: Authenticating: Shariputra Martian,
2010-01-24T18:45:03Z INFO: authenticate: Options: inventory-root, inventory-skeleton, inventory-lib-root, inventory-lib-owner, inventory-skel-lib, initial-outfit, gestures, event_categories, event_notifications, classified_categories, buddy-list, ui-config, tutorial_setting, login-flags, global-textures, END
2010-01-24T18:45:03Z INFO: authenticate: LLUserAuth::authenticate: uri=https://login.agni.lindenlab.com/cgi-bin/login.cgi
2010-01-24T18:45:03Z INFO: setStartupState: Startup state changing from STATE_LOGIN_AUTHENTICATE to STATE_LOGIN_NO_DATA_YET
2010-01-24T18:45:43Z WARNING: process: LLXMLRPCTransaction CURL error 28: Connection time-out after 40001 ms
2010-01-24T18:45:43Z WARNING: process: LLXMLRPCTransaction request URI: https://login.agni.lindenlab.com/cgi-bin/login.cgi
2010-01-24T18:45:43Z INFO: authResponse: Processed response: 28
2010-01-24T18:45:43Z INFO: setStartupState: Startup state changing from STATE_LOGIN_NO_DATA_YET to STATE_LOGIN_DOWNLOADING
2010-01-24T18:45:43Z INFO: setStartupState: Startup state changing from STATE_LOGIN_DOWNLOADING to STATE_LOGIN_PROCESS_RESPONSE
2010-01-24T18:45:43Z INFO: LLNotificationHistoryChannel:avePersistentNotifi cations: Saving open notifications to /home/mcgarcia/.secondlife/user_settings/open_notifications.xml
2010-01-24T18:45:43Z WARNING: LLAlertDialog: Alert: Unable to connect to Second Life.
Despite our best efforts, something unexpected has gone wrong.

Please check secondlife.com/status
to see if there is a known problem with the service.


Any suggestions would be much appreciate.

Thank you very much

Try the Emerald Linux client.

Buy a Mac

P.S. looks like a network problem

hah. I'm telling Fmeh.

Hello.

Thanks for your suggestions. I tried with the Emerald viewer but I got exactly the same problem:

2010-01-25T21:34:46Z WARNING: process: LLXMLRPCTransaction CURL error 28: Connection time-out after 40033 ms
2010-01-25T21:34:46Z WARNING: process: LLXMLRPCTransaction request URI: https://login.agni.lindenlab.com/cgi-bin/login.cgi
2010-01-25T21:34:46Z INFO: authResponse: Processed response: 28
2010-01-25T21:34:46Z INFO: setStartupState: Startup state changing from STATE_LOGIN_NO_DATA_YET to STATE_LOGIN_DOWNLOADING
2010-01-25T21:34:46Z INFO: setStartupState: Startup state changing from STATE_LOGIN_DOWNLOADING to STATE_LOGIN_PROCESS_RESPONSE
2010-01-25T21:34:46Z INFO: LLNotificationHistoryChannel:avePersistentNotifications: Saving open notifications to /home/mcgarcia/.secondlife/user_settings/open_notifications.xml
2010-01-25T21:34:46Z WARNING: LLAlertDialog: Alert: Unable to connect to Emerald Viewer.
Despite our best efforts, something unexpected has gone wrong.

Please check secondlife.com/status
to see if there is a known problem with the service.


Yes, it seems to be a network problem definitively.

I assume you have internet access, otherwise you could not post here .

I see 2 potential causes, first your DNS has problems to resolve some addresses or you have required ports blocked.

1) Try a different DNS server. I like Google DNS, very easy to remember and just works. IPs: 8.8.8.8 and 8.8.4.4 http://code.google.com/speed/public-dns/

2) SL requires the following ports to be open: 443/TCP, 12035/UDP, 12036/UDP, 12043/TCP, and 13000-13050/UDP (thanks Sue http://suezannecbaskerville.wordpress.com/second-life-firewalls-routers-ports-udp-tcp/)

Hope that helps

Thank you very much for your help, Boy. I tried both suggestions, but still not working.
The only thing is that I don't know if I am opening the ports in the right way.

I am using a wireless connection to an ADSL router. Is this what I should write:

sudo iptables -A INPUT -p udp -d 0/0 -s 0/0 --dport 13000:13050 -j ACCEPT
sudo iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport 443 -j ACCEPT


I also tried netstat -a|grep "LISTEN" although, to be honest, I didn't understand much the input. What I noticed is that the SecondLife client application didn't appear among the things that are being "listening". Maybe that is the problem.

@Shari
If you use a standard Ubuntu installation you should have a "Firewall configuration" entry in the System/Administration menu. That's a simple to use frontend for iptables. If it is not there you can simply install it with synaptic or "sudo apt-get install gufw". I think it is enabled by default, so you may want to disable it to see if this is causing connection problems for SL.

Hello Boy,

I checked that the firewall is disabled. I installed Snowglobe just to see if it makes any different, but the error message is the same.

I can only think that there may be any application/software which is blocking the ports, since I was able to use the viewer months ago with Ubuntu 9.10. The only application that I have installed in Google Earth, though.

That's all pretty strange, maybe some coincidence with your modem getting mad or your ISP insane . Who knows...

One thing I'd try is to boot from a life CD (Ubuntu, Debian, Knoppix etc.) and download and run a fresh viewer copy on that. So you can make sure it's not your network connection but something is screwed up inside your Ubuntu installation.

I'm seeing the same behaviour. I've not been able to delve too deeply into the problem, but it looks like libcurl is no longer communicating correctly with the resolver.

As a workaround, so an nslookup (or dig) of login.agni.lindenlab.com to get an IP number and sick it in the hosts file. That worked for me.

This doesn't make sense, an update of the viewer will not screw around with your libs or DNS. Or it should not .

A fresh official viewer works just fine on Ubuntu 9.10.

It looks like the libdns security updates, from about a week ago, have broken something. Most likely to do with the caching of names, since that is the behaviour which changed. I'd guess that, for some people, the IP they get when logging in now changes half way through the process.

I've reinstalled the previous versions of the following packages:

libisc50 libisccc50 libisccfg50 libbind9-50 liblwres50 bind9-host dnsutils

Also, libdns50 needs to be reinstalled, as it was replaced by libdns53 during the update.

I can now login again without hard coding a login server in the hosts file.

Thanks to both for your suggestions.

I am going to try first reinstalling previous versions of the file you mentioned.

How can I do that?

I am just a beginner in Ubuntu and it doesn't allow me through the psynaptic manager.

I don't have Subversion installed or other VCS

Regards

In order to revert to the previous version of libdns, I ran the following command:

sudo apt-get install libisc50=1:9.6.1.dfsg.P1-3 libdns50=1:9.6.1.dfsg.P1-3 libisccc50=1:9.6.1.dfsg.P1-3 libisccfg50=1:9.6.1.dfsg.P1-3 libbind9-50=1:9.6.1.dfsg.P1-3 liblwres50=1:9.6.1.dfsg.P1-3 bind9-host=1:9.6.1.dfsg.P1-3 dnsutils=1:9.6.1.dfsg.P1-3

Note that this should be all on one line. It would be better to copy it into gedit first, because the forum will probably insert line breaks.

If you are unsure about what version you currently have installed, you should also use the apt-cache command to confirm that the update was applied. The newer ones had the version 1:9.6.1.dfsg.P1-3ubuntu0.3 (i.e. "ubuntu0.3" was added to the version)

Thank you very much for your help and suggestions. Installing the old library versions didn't solve my problem, so I am going to try now to boot from a life CD.

Regards

Just to keep updated, I have re-applied the DNS updates along with the latest kernel revision and I'm no longer having a problem logging in.