Ok, I ran 100, and sure enough, extra port 500s showed up with IDLE_WAIT.
Dropped that down to 99, and the extra port 500s slowly went away.
maxConnections = ## -- Two digits only.

[quote=IronBits;127240]Ok, I ran 100, and sure enough, extra port 500s showed up with IDLE_WAIT.
Dropped that down to 99, and the extra port 500s slowly went away.
maxConnections = ## -- Two digits only.[/quote]

What happens if you change that setting on llrserver.lua?

Carlos

Thanks guys.
The port info was what I was looking for.
I'll throw in some cycles as I can.

Well 99 didn't work, so now I'm at 60 to see what happens.
I haven't touched llrserver.lua, this is on windows.

Can I get everyone to put just one core on over here so I can find where the leak of sockets begins. I'll also get a feel for just how many of us are out there doing all the work. I suspect we have 6-12 people, but many cores per person. ;)

[quote=em99010pepe;127178]14 000 candidates need urgently to be tested on [COLOR=Blue][COLOR=Black][COLOR=Green][B]crus.dynip.telepac.pt port 100[COLOR=Black].
[/COLOR][/B][COLOR=Black]Those ones were left behind during last rally due to clients/server issues. Please help. Moved 6 cores to it. I can test them by myself in three days but [/COLOR][/COLOR][/COLOR][/COLOR]:help:needed.
[COLOR=Blue][COLOR=Black][COLOR=Green][COLOR=Black]
Carlos
[/COLOR][/COLOR][/COLOR][/COLOR][/quote]

[quote=BlisteringSheep;127194]em, you're welcome. :)

Is a day enough to help out? I'm having a lot of fun here, but I do have another project that the octocore is primarily used for (to help keep Free-DC from passing us in d.net OGR). So long as there is low-n work, I don't have any plans to move either of the other machines (P4 or P1) off of NPLB.[/quote]

We are almost done testing those missing 14 000 pairs from last rally race.
Free-DC won't pass Ars on OGR, believe me. Please keep your octo here for another 12 hours, thanks.

EDIT: Here's what I am talking about. Before my call of arms:

[code]
range pairs done miss
282200 2253 2252 1
282400 2215 2209 6
282600 2328 2231 97
282800 2351 1469 882
283000 2343 2234 109
283200 2239 2217 22
283400 2330 2292 38
283600 2263 2240 23
283800 2307 2301 6
284000 2386 690 1696
284200 2281 2191 90
284400 2311 2303 8
284600 2304 2283 21
284800 2262 1412 850
285000 2244 2194 50
285200 2265 2262 3
285400 2301 1985 316
285600 2305 226 2079
285800 2250 571 1679
286000 2320 547 1773
286200 2305 2131 174
286400 2295 2104 191
286600 2248 2217 31
286800 2259 1923 336
287000 2253 2119 134
287200 2280 1302 978
287400 2138 2056 82
287600 2277 2222 55
287800 2358 2344 14
288000 2225 2223 2
288200 2294 2288 6
288400 2236 2232 4
288600 2256 2227 29
288800 2345 2122 223
289000 2280 149 2131[/code]After

[code]
range pairs done miss
284000 2386 2383 3
284200 2281 2281 0
284400 2311 2311 0
284600 2304 2304 0
284800 2262 2261 1
285000 2244 2244 0
285200 2265 2263 2
285400 2301 2301 0
285600 2305 2305 0
285800 2250 2250 0
286000 2320 2320 0
286200 2305 2305 0
286400 2295 2295 0
286600 2248 2247 1
286800 2259 1923 336
287000 2253 2119 134
287200 2280 1302 978
287400 2138 2056 82
287600 2277 2222 55
287800 2358 2344 14
288000 2225 2223 2
288200 2294 2288 6
288400 2236 2232 4
288600 2256 2227 29
288800 2345 2337 8
289000 2280 2273 7
289200 2365 2355 10
289400 2282 2279 3
289600 2262 2257 5
289800 2327 2325 2
290000 2266 2264 2
290200 2292 2288 4
290400 2331 2331 0
290600 2286 2285 1
290800 2257 2257 0
291000 2186 2184 2
291200 2357 2354 3
291400 2360 2358 2
291600 2254 1642 612
291800 2258 404 1854[/code]PS (Thanks Karsten for the status update)

[QUOTE=em99010pepe;127282]Please keep your octo here for another 12 hours, thanks.[/QUOTE]

Okay, I think I can manage that. :)

[quote=BlisteringSheep;127284]Okay, I think I can manage that. :)[/quote]

I think we are done, if you want you can move the octo. Thanks.

What does this mean from the console as it went on by?
llrserver: Unknown command 311996
llrserver: Unknown command B328CF1622979A60
recv error res=-1, errno=0
connection closed (socket 1328)
I'm thinking the windows llrserver.exe has bugs or is broken.
I'm getting port/sockets holding on forever and not releasing.

Backing down to 30 connections to see if it goes away.

This is what goes across the console when I tell it to shutdown
connection closed (socket 1328)
net_signal called with code 2
shutting down listening socket
accept: errno=0
thread #30 exited
thread #31 exited
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
... It will keep repeating 'waiting for thread #0 exits' forever.
I have to force it closed (kill it) to make it go away.

[quote=IronBits;127353]What does this mean from the console as it went on by?
llrserver: Unknown command 311996
llrserver: Unknown command B328CF1622979A60
recv error res=-1, errno=0
connection closed (socket 1328)
I'm thinking the windows llrserver.exe has bugs or is broken.
I'm getting port/sockets holding on forever and not releasing.

Backing down to 30 connections to see if it goes away.[/quote]

[quote=IronBits;127354]This is what goes across the console when I tell it to shutdown
connection closed (socket 1328)
net_signal called with code 2
shutting down listening socket
accept: errno=0
thread #30 exited
thread #31 exited
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
waiting thread #0 exits
... It will keep repeating 'waiting for thread #0 exits' forever.
I have to force it closed (kill it) to make it go away.[/quote]
Hmm. Why don't you ask at the Riesel Sieve project forum, they might be able to help you. They should know what's going on--they developed LLRnet, after all. :smile: