Thanks, Michele! Even though the ping isn't particularly slow, adding the
entry to /etc/hosts does the trick for the web2py startup.
I'm still thinking that lookups might be slow for all sorts of reasons, and
the following bunch of lines should perhaps be moved from console()
into web2pyDialog.__init__(), right above the place where options.ips is
used (options.ips could become a local variable then):
try:
options.ips = list(set( # no duplicates
[addrinfo[4][0] for addrinfo in getipaddrinfo(socket.getfqdn())
if not is_loopback_ip_address(addrinfo=addrinfo)]))
except socket.gaierror:
options.ips = []
On Sunday, January 12, 2014 3:26:02 PM UTC+1, Michele Comitini wrote:
>
> try the following on the command line:
> $ ping $(hostname -f)
>
> if it takes long time and then it says something like "unkwown host" that
> your machine has a name that is neither resolvable by dns nor by /etc/hosts
> lookup. To fix the problem try to add the following line in your
> /etc/hosts:
>
> 127.0.0.1 <put here the name of your computer as given by hostname -f>
>
>
>
> 2014/1/12 Horst Horst <spamf...@gmail.com <javascript:>>
>
>> ...and guess what what: I've been working on my first web2py project
>> since almost three month, and thought this was normal! (I hear you
>> laughing.) Until yesterday when I had my WLAN turned off and web2py
>> launched almost instantly.
>>
>> I couldn't believe it, launched the debugger, and traced the problem down
>> to the line:
>>
>> gluon/widget.py:726
>> options.ips = list(set( # no duplicates
>> [addrinfo[4][0] for addrinfo in
>> getipaddrinfo(socket.getfqdn())
>>
>> Googling the culprit line gave me this post:
>>
>>
>> https://groups.google.com/forum/#!searchin/web2py/startup$20slow/web2py/Y0ybKPM4MzI/pWFVHj9_ynwJ
>>
>> but unfortunately the solution doesn't work for me. My /etc/hosts is in
>> virgin state (and commenting out any line(s) doesn't change anything):
>>
>> $ cat /etc/hosts
>> ##
>> # Host Database
>> #
>> # localhost is used to configure the loopback interface
>> # when the system is booting. Do not change this entry.
>> ##
>> 127.0.0.1 localhost
>> 255.255.255.255 broadcasthost
>> ::1 localhost
>> fe80::1%lo0 localhost
>>
>> Being rather clueless about network problems, I'm now lost. However, I
>> wonder if anyone else has this problem, since I remember web2py startup to
>> be as slow on my previous MacBook running 10.8.6.
>>
>> Looking at the code, I can work around the problem by simply setting
>>
>> options.ips = []
>>
>> However, I'd prefer a way to launch web2py without it looking up these
>> IPs. options.ips seems to be exclusively used in web2pyDialog, so I wonder
>> why the lookup can't be done there locally, and launching without the
>> dialog would be fast. Especially, running my unit test would then go
>> instantly (I hear you laughing...).
>>
>> --
>> Resources:
>> - http://web2py.com
>> - http://web2py.com/book (Documentation)
>> - http://github.com/web2py/web2py (Source code)
>> - https://code.google.com/p/web2py/issues/list (Report Issues)
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "web2py-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to web2py+un...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
