Vandaag zet ik de proxy aan terwijl ik op m'n werk ben. Totdat mijn oog valt op het aantal blokjes dat nog ter verzending klaarstaat. 1700? Ik had gisteren toch 't ding leeggegooid? Vreemd.
Kijken op de statspagina van CC. Idd. Blokjes zijn netjes aangekomen. Maar 1700 in 24 uur is niet mijn reguliere output. Verre van.
Kijkt u vervolgens eens naar deze (ge-editte) logfile.
Code: Select all
2004-01-05 12:35:59,rc5-72 r=1876/2000, d=1402/1, 0.0 Mkeys/sec, tot=0/0 blocks
2004-01-05 12:35:59,ogr r=0/0, d=0/3, 0.0 Mnodes/sec, tot=0/0 stubs
2004-01-05 12:35:59,Status: Uptime: 0.00:00:01, 1 listener, 0 uplinks
2004-01-05 12:35:59,Status: 0 active clients (peak: 0, mean: 0.00)
2004-01-05 12:36:02,Uplink: [1] Server is running version 333.
2004-01-05 12:36:02,Uplink: [1] Server is running version 333.
2004-01-05 12:36:02,Uplink: [1] Server does not have ogr packets available
2004-01-05 12:35:47,server: --> uplink rc5-72 packet CA:71B0BE4C:00000000 iter 1
2004-01-05 12:35:47,server: Queueing rc5-72 request.
****<knipperdeknip>****
2004-01-05 12:37:19,server: <-- ack OK rc5-72 packet CA:72BAD0B2:00000000 iter 1
2004-01-05 12:37:20,server: <-- ack OK rc5-72 packet CA:7F4C87F4:00000000 iter 1
2004-01-05 12:37:20,server: <-- ack OK rc5-72 packet CA:7F4C6E3C:00000000 iter 1
2004-01-05 12:37:20,server: <-- ack OK rc5-72 packet CA:7203870F:00000000 iter 1
****************** Uplink klaar. Blokjes gefetched en geflushed.
2004-01-05 12:37:52,rc5-72 r=2000/2000, d=0/1, 0.0 Mkeys/sec, tot=0/0 blocks
2004-01-05 12:37:52,Status: rc5-72: Last uplink sent 1402 and received 124
2004-01-05 12:37:52,ogr r=0/0, d=0/3, 0.0 Mnodes/sec, tot=0/0 stubs
2004-01-05 12:37:52,Status: ogr: Last uplink sent 0 and received 0
2004-01-05 12:37:52,Status: Uptime: 0.00:01:54, 1 listener, 0 uplinks
2004-01-05 12:37:52,Status: 0 active clients (peak: 0, mean: 0.00)
2004-01-05 12:41:35,192.168.0.1: assigned rc5-72 CA:735324B6:00000000 iter 1
2004-01-05 12:41:35,192.168.0.1: completed rc5-72 CA:72038710:00000000 iter 1
****************** WTF?????? In 1 keer weer gewoon ongefetched en ongeflushed?
2004-01-05 12:43:04,rc5-72 r=1875/2000, d=1403/10001, 252.2 Mkeys/sec, tot=107/106 blocks
2004-01-05 12:43:04,ogr r=0/0, d=0/3, 0.0 Mnodes/sec, tot=0/0 stubs
2004-01-05 12:43:04,Status: Uptime: 0.00:30:04, 1 listener, 0 uplinks
****************** En vervolgens weer vrolijk fetchen??????
2004-01-05 12:43:04,Status: 0 active clients (peak: 2, mean: 0.00)
2004-01-05 12:43:07,Uplink: [1] Server is running version 333.
2004-01-05 12:43:07,Uplink: [1] Server is running version 333.
2004-01-05 12:43:07,Uplink: [1] Server does not have ogr packets available
2004-01-05 12:42:52,server: Queueing rc5-72 request.
****<knipperdeknip>****
2004-01-05 12:42:52,server: Queueing rc5-72 request.
2004-01-05 12:42:52,server: Received rc5-72 packet CA:7535C117:00000000 iter 1
****<knipperdeknip>****
2004-01-05 12:42:52,server: Received rc5-72 packet CA:7535C337:00000000 iter 1
****<knipperdeknip>****
2004-01-05 12:42:53,server: Received rc5-72 packet CA:7535CA20:00000000 iter 1
2004-01-05 12:42:53,server: Queueing rc5-72 request.
2004-01-05 12:42:53,rc5-72 r=1890/2000, d=1403/10001, 251.7 Mkeys/sec, tot=107/106 blocks
2004-01-05 12:42:53,ogr r=0/0, d=0/3, 0.0 Mnodes/sec, tot=0/0 stubs
2004-01-05 12:42:53,Status: Uptime: 0.00:29:53, 1 listener, 1 uplink
2004-01-05 12:42:53,Status: 0 active clients (peak: 2, mean: 0.00)
2004-01-05 12:42:53,server: Received rc5-72 packet CA:7535D0FF:00000000 iter 1
2004-01-05 12:42:58,server: Received rc5-72 packet CA:753BB61F:00000000 iter 1
****<knipperdeknip>****
2004-01-05 12:42:59,server: Received rc5-72 packet CA:72E82685:00000000 iter 1
2004-01-05 12:42:59,server: Received rc5-72 packet CA:72E82686:00000000 iter 1
2004-01-05 12:43:30,rc5-72 r=2000/2000, d=1403/10001, 246.6 Mkeys/sec, tot=107/106 blocks
2004-01-05 12:43:30,Status: rc5-72: Last uplink sent 0 and received 125
2004-01-05 12:43:30,ogr r=0/0, d=0/3, 0.0 Mnodes/sec, tot=0/0 stubs
2004-01-05 12:43:30,Status: ogr: Last uplink sent 0 and received 0
2004-01-05 12:43:30,Status: Uptime: 0.00:30:30, 1 listener, 0 uplinks
2004-01-05 12:43:30,Status: 0 active clients (peak: 2, mean: 0.00)
2004-01-05 12:45:50,rc5-72 r=2000/2000, d=0/1, 0.0 Mkeys/sec, tot=0/0 blocks
2004-01-05 12:45:50,ogr r=0/0, d=0/3, 0.0 Mnodes/sec, tot=0/0 stubs
2004-01-05 12:45:50,Status: Uptime: 0.00:09:52, 1 listener, 0 uplinks
2004-01-05 12:45:50,Status: 0 active clients (peak: 0, mean: 0.00)
2004-01-05 12:47:09,192.168.0.3: assigned rc5-72 CA:735324B7:00000000 iter 1
2004-01-05 12:47:09,192.168.0.3: completed rc5-72 CA:71E23643:00000000 iter 1
2004-01-05 12:52:24,192.168.0.1: assigned rc5-72 CA:735324B8:00000000 iter 1
2004-01-05 12:52:24,192.168.0.1: completed rc5-72 CA:72038721:00000000 iter 1
2004-01-05 12:52:29,Uplink: [1] Server is running version 333.
2004-01-05 12:52:29,Uplink: [1] Server is running version 333.
2004-01-05 12:52:29,Uplink: [1] Server does not have ogr packets available
2004-01-05 12:52:29,server: Queueing rc5-72 request.
2004-01-05 12:52:29,server: Queueing rc5-72 request.
2004-01-05 12:52:29,server: Received rc5-72 packet CA:72E82689:00000000 iter 1
2004-01-05 12:52:29,server: Received rc5-72 packet CA:72E8268A:00000000 iter 1
2004-01-05 12:52:54,rc5-72 r=2000/2000, d=1405/10001, 192.5 Mkeys/sec, tot=109/108 blocks
2004-01-05 12:52:54,ogr r=0/0, d=0/3, 0.0 Mnodes/sec, tot=0/0 stubs
2004-01-05 12:52:54,Status: Uptime: 0.00:39:54, 1 listener, 1 uplink
2004-01-05 12:52:54,Status: 0 active clients (peak: 2, mean: 0.00)
****************** En hier gaf ik pas de CTRL-BREAK
2004-01-05 12:52:57,*Signal* Re-reading configuration.
2004-01-05 12:52:57,Doing .ini reload now.
2004-01-05 12:52:57,Verbosity set to: general stats keyblock buffers timestamp attention errlow errsevere (3495)
2004-01-05 12:52:57,Notice: connectivity mode is normal
2004-01-05 12:52:57,Notice: Loaded 0 ignoredip addresses from ini file
2004-01-05 12:52:57,Notice: Loaded 0 allowedip addresses from ini file
2004-01-05 12:52:57,Notice: Primary listener bound to (all devices):2313
2004-01-05 12:52:57,rc564-in: limits adjusted to min 1, max 0
2004-01-05 12:52:57,rc564-dupe: resized to dupe history size of 31
2004-01-05 12:53:45,rc5-72 r=2000/2000, d=0/10001, 0.0 Mkeys/sec, tot=0/0 blocks
2004-01-05 12:53:45,Status: rc5-72: Last uplink sent 0 and received 0
2004-01-05 12:53:45,ogr r=0/0, d=0/3, 0.0 Mnodes/sec, tot=0/0 stubs
2004-01-05 12:53:45,Status: ogr: Last uplink sent 0 and received 0
2004-01-05 12:53:45,Status: Uptime: 0.00:17:47, 1 listener, 0 uplinks
2004-01-05 12:53:45,Status: 0 active clients (peak: 0, mean: 0.00)
2004-01-05 12:54:30,rc5-72 r=2000/2000, d=1405/10001, 185.1 Mkeys/sec, tot=109/108 blocks
2004-01-05 12:54:30,Status: rc5-72: Last uplink sent 0 and received 2
2004-01-05 12:54:30,ogr r=0/0, d=0/3, 0.0 Mnodes/sec, tot=0/0 stubs
2004-01-05 12:54:30,Status: ogr: Last uplink sent 0 and received 0
2004-01-05 12:54:30,Status: Uptime: 0.00:41:30, 1 listener, 0 uplinks
2004-01-05 12:54:30,Status: 0 active clients (peak: 2, mean: 0.00)
Code: Select all
ppdone.r72 290,312 bytes
ppready.r72 284936 bytes
pprc5out.rc5 8 bytes
pprc5in.rc5 8 bytes
Ik flush mijn proxy op gezette tijden met de hand (omdat ik een dynamisch IP heb, en CC heeft maar 1 proxy, dus ik moet 't IP doorgeven aan ubercow Hemz) Hiervoor hanteer ik de volgende procedure.
- Ik open de INI file in kladblok (windows 98) en zet Maxkeysdone=1 en minkeysdone=0. Ik sla het bestand op. Kladblok blijft openstaan.
- Ik start de proxy
- Ik edit: Maxkeysdone=10001 en minkeysdone=100009 en sla deze op en sluit kladblok af. Proxy is nu nog steeds fetchende/flushende.
- Ik wacht totdat de proxy leeg is. Als die klaar is druk ik op CTRL-BREAK om de INI opnieuw door de proxy te laten inlezen.