New testing version... from previous testing is fixed active search leak and saved data counting.
1 ) With Lua 5.0.2 (http://www.ptokax.org/files/0.3.4.0k0.dbg.7z).
2 ) With Lua 5.1 (http://www.ptokax.org/files/0.3.4.0k1.dbg.7z).
Thanks PPK for the update.. Updating instanly...
I guess that when almost no one has replied to this thread, the latest test release is running nice and stable :)
Yes all ok here
------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.4.0k1 [debug] built on May 30 2006 15:07:10
Uptime: 0 days, 13 hours, 45 minutes
Users (Max/Actual Peak (Max Peak)/Logged): 8000 / 4775 (6272) / 4682
Users shared size: 135651152837386 Bytes / 123.37 TB
Chat messages: 4365 x
Unknown commands: 9986 x
PM commands: 3835 x
Key commands: 111833 x
Supports commands: 118357 x
MyINFO commands: 222063 x
ValidateNick commands: 89869 x
GetINFO commands: 10032 x
Password commands: 92 x
Version commands: 32157 x
GetNickList commands: 46030 x
Search commands: 636390 x
SR commands: 2878969 x
CTM commands: 6378022 x
RevCTM commands: 3120535 x
BotINFO commands: 8 x
------------------------------------------------------------
CPU usage (60 sec avg): 15.00%
CPU time: 1:19:02
Mem usage (Peak): 223.96 MB (232.38 MB)
VM size (Peak): 224.09 MB (232.54 MB)
------------------------------------------------------------
SendRests (Peak): 248 (260)
RecvRests (Peak): 1 (16)
Compression saved: 1.57 GB
Data sent: 54.50 GB
Data received: 937.50 MB
Tx (60 sec avg): 192.73 kB/s (1.70 MB/s)
Rx (60 sec avg): 14.23 kB/s (42.97 kB/s)
;)
Yes here too...
Hey, I was kidding.. Nothing is fine.. I have a damn 100/100 server and a rock stable 0.3.4.0k hub but only ~1000 users in it..
PPK, when are you going to supply some more users within the package?? ;D
then don't use test releases on big hubs, don't you have a small one to?
I don't have any problems with beta releases; especially with the latest one, only my hub has less users than its capacity.. I was joking about that; but you took it too serious :)
Reporting first bug (as fas as I know):
Addding user mode before description doesn't work for users which already have only "A" or "P" in their descriptions, with settings below:
(http://img284.imageshack.us/img284/9373/myinfo8aq.png)
Can be observed in my hub, as I did with a plain DC++ 0.674.
All descriptionless clients are 0.68 or 0.6811, other versions doesn't seem to create that bug.
So we know that those descriptionless clients are clients with MyINFO bug.
------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.4.0k0 [debug] built on May 30 2006 16:58:46
Uptime: 1 days, 15 hours, 33 minutes
Users (Max/Actual Peak (Max Peak)/Logged): 500 / 167 (169) / 155
Users shared size: 12738339938921 Bytes / 11.59 TB
Chat messages: 189 x
Unknown commands: 67891 x
PM commands: 288 x
Key commands: 3321 x
Supports commands: 3481 x
MyINFO commands: 18334 x
ValidateNick commands: 2813 x
GetINFO commands: 1034 x
Password commands: 1904 x
Version commands: 1648 x
GetNickList commands: 2268 x
Search commands: 32180 x
SR commands: 2656 x
CTM commands: 50572 x
RevCTM commands: 13128 x
BotINFO commands: 0 x
------------------------------------------------------------
CPU usage (60 sec avg): 0.95%
CPU time: 0:41:30
Mem usage (Peak): 58.80 MB (98.45 MB)
VM size (Peak): 58.08 MB (98.57 MB)
------------------------------------------------------------
SendRests (Peak): 0 (2)
RecvRests (Peak): 0 (9)
Compression saved: 168.02 kB
Data sent: 289.18 MB
Data received: 12.83 MB
Tx (60 sec avg): 0 B/s (3.36 kB/s)
Rx (60 sec avg): 79 B/s (176 B/s)
Running smooth here too? :D
//Edited
Added this information from the Windows Taskmanager for additional info
- Process Name : ptokax.exe
- CPU Time : 0:42:40
- Mem Usage: 65,676 K
- Peak mem : 103.684 K
- Page Faults : 95,226,133 and rising steadily
- VM size : 64,536 K
- I/O Reads : 88,129
- I/O Writes : 308,936
- I/O Others : 226,212
- I/O R Bytes : 60,086,653
- I/O W Bytes : 133,590,080
- I/O O Bytes : 7,169,816
---------------------------01.06.2006 18:08:48---------------------------
Exception 'EAccessViolation' in module PXLUA.DLL at 00005FE0
Access violation at address 00226FE0 in module 'PXLUA.DLL'. Read of address 10F80005
Call stack:
:00226FE0 [PXLUA.DLL] traversestack (lgc.c, line 245)
:00227128 [PXLUA.DLL] propagatemarks (lgc.c, line 279)
:0022773F [PXLUA.DLL] mark (lgc.c, line 465)
:002277C2 [PXLUA.DLL] luaC_collectgarbage (lgc.c, line 485)
:0022269E [PXLUA.DLL] lua_setgcthreshold (lapi.c, line 788)
:002322A7 [PXLUA.DLL] luaB_collectgarbage (lbaselib.c, line 197)
:00225A0D [PXLUA.DLL] luaD_precall (ldo.c, line 260)
:002300F6 [PXLUA.DLL] luaV_execute (lvm.c, line 631)
:0059E2C7 [Turkuaz.exe]
:0059E2DE [Turkuaz.exe]
:0053350A [Turkuaz.exe]
:7739C498 [USER32.dll]
:7739CF8D [USER32.dll]
:005220A1 [Turkuaz.exe]
:005BA585 [Turkuaz.exe]
:005BA61D [Turkuaz.exe]
:0060F0A1 [Turkuaz.exe]
:00225B95 [PXLUA.DLL] luaD_call (ldo.c, line 313)
:002223ED [PXLUA.DLL] f_call (lapi.c, line 672)
:002251F7 [PXLUA.DLL] luaD_rawrunprotected (ldo.c, line 88)
:002251E9 [PXLUA.DLL] luaD_rawrunprotected (ldo.c, line 87)
:00225F2A [PXLUA.DLL] luaD_pcall (ldo.c, line 416)
:002223D0 [PXLUA.DLL] lua_call (lapi.c, line 657)
:0022D294 [PXLUA.DLL] luaH_get (ltable.c, line 472)
:0022E2AF [PXLUA.DLL] luaV_gettable (lvm.c, line 158)
:00222455 [PXLUA.DLL] lua_pcall (lapi.c, line 685)
:002223D0 [PXLUA.DLL] lua_call (lapi.c, line 657)
:0048FCA7 [Turkuaz.exe] lua_OnTimer (luaInterface.cpp, line 5005)
:00492608 [Turkuaz.exe] LuaInterpret::ScriptTimerTimer (luaInterface.cpp, line 5800)
:005912D2 [Turkuaz.exe]
:005911B8 [Turkuaz.exe]
:0053350A [Turkuaz.exe]
:7739C3B7 [USER32.dll]
:7739C484 [USER32.dll]
:7739C43A [USER32.dll]
:7739C73C [USER32.dll]
:00536BEF [Turkuaz.exe]
:00536D83 [Turkuaz.exe]
:7738E406 [USER32.dll]
:0058DEEC [Turkuaz.exe]
:0058DF23 [Turkuaz.exe]
:0058E143 [Turkuaz.exe]
:0058E186 [Turkuaz.exe]
:00401B38 [Turkuaz.exe] WinMain (PtokaX.cpp, line 51)
:005D5AD7 [Turkuaz.exe]
:00400000 [Turkuaz.exe]
:77E523CD [kernel32.dll]
Modules:
$00400000 (00400000,00001000,0021E000) D:\Hubs\Turkuaz\Hub\Turkuaz.exe
$00220000 (00400000,00001000,00028000) D:\Hubs\Turkuaz\Hub\PXLUA.DLL
$77380000 (77380000,00001000,00060E00) C:\WINDOWS\system32\USER32.dll
$77E40000 (77E40000,00001000,00089C00) C:\WINDOWS\system32\kernel32.dll
Main Thread ID = 00000CA8, Current Thread ID = 00000CA8
Registers:
EAX = 05567D40? CS = 001B? EIP = 00226FE0? Flags = 00010202
EBX = 0B64207C? SS = 0023? ESP = 0012FA14? ? EBP = 0012FA20
ECX = 10F80000? DS = 0023? ESI = 005912C0? ? FS? = 003B
EDX = 05567D40? ES = 0023? EDI = 0012FE30? ? GS? = 0000
Code at CS:EIP
F6 41 05 11 75 11 8B 45 0C FF 70 42 FF 75 08 E8
Stack:
00000000 00000000 FFFFFFFF 0012FA40 00227128
00000000 77E523CD 0054D105 07032F34 0061570B
0C0B2D14 0121290B 00000000 0172ED08 77E523CD
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 00000001
Additional info:
Application Title : PtokaX DC Hub 0.3.4.0k0 [debug]
Major : 5
Minor : 2
Build : 3790
SP : 1
Type : 3
iJoins: 11598, iParts: 10111, iLogged: 1462
NicklistLen : 15940
OplistLen? ?: 74
MyInfosLen? : 69495
MyInfosTagLen? : 124690
Caused by bad script :(
ehm, what is the 'Turkuaz.exe' you have in that bug report GeceBekcisi?
Quote from: blackwings on 01 June, 2006, 20:46:39
ehm, what is the 'Turkuaz.exe' you have in that bug report GeceBekcisi?
Probably PtokaX.exe renamed.
If you had 4 different PtokaX hubs running on the same server, you'd guess quickly as -SkA- did; blackwings.
Yes, it's renamed PtokaX :)
Ehm....there is something wrong with uptime counter:
[08:36:41] <??????????> This hub is running PtokaX DC Hub 0.3.4.0k1 [debug] May 30 2006 15:07:21 (UpTime: 2 days, 23 hours, 37 minutes)
After ~2 hours:
[10:59:49] <??????????> This hub is running PtokaX DC Hub 0.3.4.0k1 [debug] May 30 2006 15:07:21 (UpTime: 2 days, 3 hours, 58 minutes)
:o
Hmm windows change time ??? Because PtokaX now use for uptime time_t (this value have time saved as seconds from 1.1.1970), in one have saved time of start, and 1x per minute get actual time and from this count minutes, hours and days of utime ::) I tried before to use for uptime ::GetTickCount (windows uptime in seconds), but this cause problems too. I tried to count uptime using second timer (is used to refresh PtokaX gui), but this not count if script take more than second for doing something :'(
Hmmm I think the problem is with days counter:
Yesterday:
[08:36:41] <????? ????> This hub is running PtokaX DC Hub 0.3.4.0k1 [debug] May 30 2006 15:07:21 (UpTime: 2 days, 23 hours, 37 minutes)
[10:59:49] <????? ????> This hub is running PtokaX DC Hub 0.3.4.0k1 [debug] May 30 2006 15:07:21 (UpTime: 2 days, 3 hours, 58 minutes)
Today:
[08:07:16] <??????????> This hub is running PtokaX DC Hub 0.3.4.0k1 [debug] May 30 2006 15:07:21 (UpTime: 3 days, 23 hours, 7 minutes)
[09:08:14] <??????????> This hub is running PtokaX DC Hub 0.3.4.0k1 [debug] May 30 2006 15:07:21 (UpTime: 3 days, 1 hours, 8 minutes)
PPK, could you change the following please ???
The !restart command will reset the hub's uptime to 00:00:00, but actually the hub didn't go "down"
And now i lost my uptime :'(
Uptime is counted from hub start, and restart stop and start it ::)
PPK have you resolved the uptime bug yet?
Maybe (http://www.ptokax.org/files/uptime.log) ::)