4.11.3 Pro only 2 ultrapeers

[birdy]

I realise it's normal for LW to drop ultrapeers when in idle mode but mine couldn't seem to reconnect to more u/ps. It was connected to 2 u/ps & attempting to connect to another 3 for more than an hour.
No error message. Only a "good" connection. No uploads during that time. Tried downloading a couple of files but didn't kickstart any connections.
In the end I restarted & went straight back up to "turbocharged".

This isn't normal, is it?

Same thing happened with 4.11.2 yesterday, that's the first time I've ever seen it.

[Sam]

Does this happen after every time it goes Idle and comes back to sleep? Can anyone else reproduce this?

[jum]

I get that one always on my windows box. My mac is a bit ill right now, so I did not check.

[birdy]

No Sam, it doesn't happen every time. Hasn't happened since I started the thread. But I am missing the "Waking up connection" message that usually shows up after being idle for a long time.

[birdy]

Dropped 3 ultrapeers again this afternoon but this time when I was actively using LW... just finished a download. One upload in progress at 6KB/s. No error message. Again, file > disconnect & connect was no use... had to restart LW.

[jum]

My problem appears to be gone with todays svn update. After fixing my repo again I got a few updates to core and the problem is gone.

[Sam]

That sounds great, Jens. Sorry again about the SVN problems. We're hoping to move to SVN as quickly as possible -- we've got a test FishEye SVN instance going, but it's dreadfully slow. I'm going to experiment with it and see if I can speed it up at all, and if it gets any faster, then maybe I'll just live with the different display it has.

[Sam]

It will only show the "Waking Up" message if it is in Poor or Fair state. If it goes immediately to Excellent or Turbo-Charged, it won't show Waking Up.

[jum]

After letting it run for a while it started resuming one or two old downloads. After a while it lost connection to a few ultrapeers and now I have three stuck outgoing connection attempts in the connection window and quite a few in the old downloads window. So the problem is not solved entirely.