Jump to content

chriser

Members
  • Posts

    94
  • Joined

  • Last visited

  • Days Won

    1

chriser last won the day on September 30 2014

chriser had the most liked content!

About chriser

  • Birthday 12/17/1992

Profile Information

  • Gender
    Male
  • Location
    Germany
  • Interests
    Gaming
    Programming
    Driving

Recent Profile Visitors

3774 profile views

chriser's Achievements

Poring

Poring (1/15)

4

Reputation

2

Community Answers

  1. I have a slightly easier implementation, but it is not always correct. ShowWarning("pc_bonus: unknown type %d %d, possible item %d or card %d !\n",type,val,sd->inventory_data[current_equip_item_index]->nameid, current_equip_card_id); you only need to change one line of code, but yeah, it's not perfect (of couse, change the implemetation for pc_bonus(2/3/4/5) as well )
  2. map-server load is at ~80% right now, still the same amount of players online. The performance analysis with gprof did not work because the map-server stopped accepting logins after some minutes, so basically the server hung up. I haven't found an issue in the scripts...
  3. maybe that fixes the problem http://rathena.org/board/tracker/issue-9130-cpu-usage-goes-to-100/
  4. i will try and find stuff that looks like something than can build up. my ram usage stays the same most of the time (at about 10% constantly +-1%), only cpu usage goes up. right now, the load is at 20% again. thanks for your feedback so far EDIT: my asrpika does the following script: while(isequipped(2383, 2541)) { specialeffect2 546; sleep2 1000; }; but we have that since over one year and we didn't have any problems with that... could that cause the problem somehow? for me it seems that some code is starting to run when a char logs in and does not stop when he logs out. it could be that one, but i could be wrong...
  5. https://github.com/rathena/rathena/commit/1d1a58cdcb88fb0ba294d3ba827a1da653598cbe#commitcomment-6061944 the issue was fixed here: https://github.com/rathena/rathena/commit/f7c09d95fdf0825f2c10fab8b516681797fa4f44#diff-d96b6365b4bdad78139e676d6e7e3295
  6. I have currently an iowait of 0-50%. mainly caused by jdb2/sda3-8 (according to top, htop and iotop). I had lots of issues with this process (sometimes it has 100% iowait for minutes) but i could not figure out why. it's fine now, and i hope this will not change iostat output: Linux 3.2.0-60-generic 26/10/14 _x86_64_ (2 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 35.61 0.00 3.00 14.85 0.00 46.54 Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn sda 36.34 150.25 2906.64 2696456238 52162671636 uptime: 13:07:54 up 207 days, 17:14, 10 users, load average: 0.69, 0.79, 0.66 i am not being attacked, also i would notice that currently the load is totally fine, the map-server was restarted about 10 hours ago. i will assume that in about 4 days the load will go up to 40-50% with the same playerbase. this is a dedicated machine, no virtualization. (btw, harddrive is one 1TB drive, so no RAID, i edited hdd info to the first post)
  7. Hi guys, I am facing a really strange problem. After restarting my server, the usage of the map server is at <5% for some hours, which is normal for my playerbase. After some days, the usage of the map server is at 50%, and after about 2 weeks at 100% permanently, including heavy lags. Even when I start my test server and leave it running for some days, the cpu usage increases without anyone playing on the server. Specs: CPU: Intel Celeron G530 (2x 2,4 GHz) 64bit RAM: 4GB (3,81GB total, 3,64GB used, 1,22GB cached, 64% usage) System: Ubuntu 12.04.5 LTS HDD: 1TB hard drive @ 7200rpm, no RAID, SMART says few bad sectors, but still green (warnings are: reallocated secor count @ 28 secotrs, current pending sector count @ 24 secotrs, both not under threshhold, so not an error, only a warning) My rathena is currently on commit f7d40ba71c57945a26a621f0c6178f9e1f26197a (Date: Thu Mar 27 01:47:51 2014 -0400) with custom modifications. Does anyone have the same problem or does anyone know how to resolve this issue? Are there some kind of methods to see from which part of the code the most execution time is comming? EDIT: i am using gprof right now on the testserver to hopefully find the issue...
  8. does noone have a clue about this? o.o it seems that this functionality causes the crash: L_Again: sleep2 1; .@sth = rand(10); if(.@sth == 0) goto L_Again; If .@sth is 0, the server crashes...
  9. bump. getting this error again on a different script now, but i don't know which one. Program terminated with signal 11, Segmentation fault. #0 0x00000000004e3149 in get_val.part.41 (data=0x7f76b7074b4c, st=0x7f76b60111ec) at script.c:2733 2733 data->u.num = (int)idb_iget(n,reference_getuid(data)); (gdb) bt full #0 0x00000000004e3149 in get_val.part.41 (data=0x7f76b7074b4c, st=0x7f76b60111ec) at script.c:2733 n = 0xfdfdfdfdfdfdfdfd name = 0x99e118a ".@id" prefix = 46 '.' postfix = 100 'd' sd = 0x0 #1 get_val (st=0x7f76b60111ec, data=0x7f76b7074b4c) at script.c:2605 __FUNCTION__ = "get_val" __FUNCTION__ = "get_val" #2 0x00000000004e28f5 in conv_num (st=0x7f76b60111ec, data=0x7f76b7074b4c) at script.c:2916 p = 0x7fff89f18c80 " \215\361\211\377\177" num = 6340990 __FUNCTION__ = "conv_num" __FUNCTION__ = "conv_num" #3 0x00000000004ddbf3 in buildin_jump_zero (st=0x7f76b60111ec) at script.c:13418 sel = 0 #4 0x00000000005ee40d in run_func (st=0x7f76b60111ec) at script.c:3584 data = 0x7f76b7074b1c i = 2 start_sp = 1 end_sp = 5 func = 349 #5 0x0000000000528f16 in run_script_main (st=0x7f76b60111ec) at script.c:3819
  10. Hi guys, I updated to the latest version last weekend, and i launched the update yesterday. The server always crashes when this script is executed: for(.@i=0;.@i<5;.@i=.@i+1) { L_Again: sleep2 1; .@rnd = rand(1,10); if(callfunc("inarray",.@rnd,.@qu)) goto L_Again; .@qu[.@i] = .@rnd; mes "........."; } Here is my full bt: Program received signal SIGSEGV, Segmentation fault. 0x00000000004e1f9c in get_val.part.41 (data=0x7fffe1ebfc5c, st=0x7fffe66bbea4) at script.c:2732 2732 data->u.num = (int)idb_iget(n,reference_getuid(data)); (gdb) bt full #0 0x00000000004e1f9c in get_val.part.41 (data=0x7fffe1ebfc5c, st=0x7fffe66bbea4) at script.c:2732 n = 0xfdfdfdfdfdfdfdfd name = 0x7dec619 ".@rnd" prefix = 46 '.' postfix = 100 'd' sd = 0x0 #1 get_val (st=0x7fffe66bbea4, data=0x7fffe1ebfc5c) at script.c:2604 __FUNCTION__ = "get_val" __FUNCTION__ = "get_val" #2 0x00000000004e1748 in conv_num (st=0x7fffe66bbea4, data=0x7fffe1ebfc5c) at script.c:2915 p = 0x7fffffffdd80 " \336\377\377\377\177" num = 6336753 __FUNCTION__ = "conv_num" __FUNCTION__ = "conv_num" #3 0x00000000004dca46 in buildin_jump_zero (st=0x7fffe66bbea4) at script.c:13414 sel = 0 #4 0x00000000005dddf1 in run_func (st=0x7fffe66bbea4) at script.c:3583 data = 0x7fffe1ebfc2c i = 1 start_sp = 0 end_sp = 4 func = 341 #5 0x00000000005382a4 in run_script_main (st=0x7fffe66bbea4) at script.c:3818 c = C_FUNC cmdcount = 655273 gotocount = 655357 sd = 0x7fffffffdfb0 stack = 0x7fffe1c88d0c #6 0x0000000000537cc7 in run_script_timer (tid=69, tick=77311478, id=150086, data=140737059208868) at script.c:3700 st = 0x7fffe66bbea4 node = 0x7fffe1c8904c sd = 0x7ec0170 #7 0x0000000000516fda in do_timer (tick=77311528) at timer.c:371 tid = 69 diff = -50 __FUNCTION__ = "do_timer" #8 main (argc=1, argv=0x7fffffffe408) at core.c:375 next = 50 I temporarly removed the random array filling and just filled the .@qu array with fixed values, but that can't be the final solution, because this is the index list of questions, which should be random. My script.c is almost completely stock, i only added one function which is working properly and has nothing to do with that. Any ideas?
  11. i am using this system since some time on my server, and i noticed one thing. you can mine mines as long as you want (not quite that much, but close to that), if you mine, close, move one cell, mine again, and so on... maybe you should make an extra column for each mine which saves how often the mine was mined, and if it exceedes a given value, destroy the mine. i could do this on my own, but i think other people can have the same problem, so fixing this issue in general would be nice.
×
×
  • Create New...