On my machine it is 100% of the times. Strange. what calls uuidd? Perhaps the new CRYPT logic which calls web2py_uuid()
On Saturday, 1 September 2012 09:47:48 UTC-5, Marin Pranjić wrote: > > Maybe not so easy... I only got it twice and I have no idea what exactly > did I do. > This will take a while... It is hard to reproduce. > > On Sat, Sep 1, 2012 at 2:25 PM, Marin Pranjić > <marin....@gmail.com<javascript:> > > wrote: > >> Sure. First I need to find out what triggers it but that should be easy >> part. >> >> >> >> On Sat, Sep 1, 2012 at 2:13 PM, Massimo Di Pierro >> <massimo....@gmail.com<javascript:> >> > wrote: >> >>> Can you try figur out which web2py change introduced the problem? >>> >>> >>> On Saturday, 1 September 2012 00:12:57 UTC-5, Marin Pranjić wrote: >>> >>>> I have the same problem, but starting web2py with WingIDE debugger >>>> (rocket). It happens on ubuntu but not on windows (I do not use windows >>>> much so maybe I didn't notice yet). I change ~5 ports in one day. >>>> >>>> And this wasn't happening before. >>>> >>>> On Sep 1, 2012 12:02 AM, "Massimo Di Pierro" <massimo....@gmail.com> >>>> wrote: >>>> >>>> My web server started exhibiting a strange behavior: >>>> >>>> $ /etc/init.d/apache stop >>>> [ok] >>>> $ /etc/init.d/apache start >>>> * Starting web server apache2 >>>> >>>> (98)Address already in use: make_sock: could not bind to address [::]:80 >>>> (98)Address already in use: make_sock: could not bind to address >>>> 0.0.0.0:80 >>>> no listening sockets available, shutting down >>>> Unable to open logs >>>> [FAIL] >>>> $ netstat -tulpn| grep :80 >>>> (No info could be read for "-p": geteuid()=1000 but you should be root.) >>>> tcp6 0 0 :::80 :::* >>>> LISTEN >>>> >>>> The only way to restart it is by rebooting. Any idea what may cause >>>> this? I have not seen before and did not change the server config in a >>>> while. >>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> >>>> -- >>> >>> >>> >>> >> >> > --
