undef

**trevius** · #1 07-29-2009, 07:50 PM

Yeah, other than the one qglobal you are setting, I don't see anywhere that you are pulling qglobal information in those scripts, just a bunch of variables. If you do ever need to pull qglobal values, just make sure to use the $qglobals{killed_overlord_mata_muram} way to do it instead of $killed_overlord_mata_muram. For example:

This is the correct way:

Code:

if (defined($qglobals{killed_overlord_mata_muram})) {
  if ($qglobals{killed_overlord_mata_muram} == 1) {
    #Do what you want here
  }
}

This is the incorrect way to pull a qglobal value:

Code:

if ($killed_overlord_mata_muram == 1) {
    #Do what you want here
}

Though the second way may work most of the time, it will definitely cause major issues in many different scenarios. The defined check I did for the correct way is not required, but I added that in there as an extra example.

Also, if you think the memory problem might be quest related, try enabling quest logging in your log.ini file and then check out your quest logs. If the quest log is getting flooded by errors, that could definitely cause some issues.

eqwarrior · #2 07-30-2009, 02:53 AM

Thanks very much!

I will try using "my" outside of the sub and see if that makes a difference.

I'll probably have to revamp a lot of quest I have to use qglobal the right way now.

I learned a bit how to do stuff the right way now. I appreciate the help.

Yes, I agree that the aggro can be compiled with arrays and for loops.

I got lots of quest to edit now heh. More than just Anguish, but Anguish was biggest problem so I'll start there.

eqwarrior · #3 07-30-2009, 03:13 AM

Also, how important is undef? Or does "my" take care of everything for removing variable from memory?

eqwarrior · #4 07-30-2009, 03:40 AM

Quote:

Originally Posted by eqwarrior

Also, how important is undef? Or does "my" take care of everything for removing variable from memory?

Never mind, just saw the red text about undef, thanks much. Don't need it since I'm not calling a global.

eqwarrior · #5 07-30-2009, 04:54 AM

I just made the changes and test. First I cleared the respawn times table, and respawned the whole zone. Then I did a #reloadquest, then end process on the zone, then the (static) zone connected again 5 seconds later. I went in the zone and did a #repop many times, then #aggrozone and killed the whole zone. The Memory never went above 11 megs. Might be fixed, will have to wait until a guild raids it, cause it used to easy go over 1 gig of ram just for Anguish in one day. Might fix all my other custom quest in other zones if this works nicely. Appreciate your help.

eqwarrior · #6 07-30-2009, 09:22 PM

Users are raiding Anguish again, and the zone is already up to 250 megs of memory. I've already corrected the quest files and rebooted the server, so I don't know. Qvic is my 2nd biggest problem, but doesn't grow up to 1 gig ram like Anguish does. Sigh.

**trevius** · #7 07-30-2009, 10:24 PM

Have you tried enabling quest logging in your log.ini file?

Here is what I have my log.ini set to atm:

Code:

CHAT=on
CHAT__SAY=on
CHAT__EMOTE=off
CHAT__OOC=on
CHAT__GROUP=on
CHAT__GUILD=on

SPAWNS=off
SPAWNS__MAIN=off
SPAWNS__CONDITIONS=off
SPAWNS__LIMITS=off

AI=off
AI__ERROR=on
AI__WAYPOINTS=off
AI__BUFFS=off
AI__SPELLS=off

QUESTS=off
QUESTS__PATHING=off

SPELLS=off
SPELLS__LOAD=off
SPELLS__LOAD_ERR=off
SPELLS__CASTING_ERR=off
SPELLS__CASTING=off
SPELLS__EFFECT_VALUES=off
SPELLS__RESISTS=off
SPELLS__STACKING=off
SPELLS__BARDS=off
SPELLS__BUFFS=off
SPELLS__PROCS=off
SPELLS__MODIFIERS=off

FACTION=off

ZONE=off
ZONE__GROUND_SPAWNS=off
ZONE__INIT=on
ZONE__INIT_ERR=on
ZONE__WORLD=off
ZONE__WORLD_ERR=on
ZONE__WORLD_TRACE=off

TRADING=off
TRADING__ERROR=off
TRADING__CLIENT=off
TRADING__NPC=off
TRADING__HOLDER=off

INVENTORY=off
INVENTORY__ERROR=off
INVENTORY__SLOTS=off

TRADESKILLS=off
TRADESKILLS__IN=off
TRADESKILLS__OUT=off
TRADESKILLS__SQL=off
TRADESKILLS__TRACE=off

TRIBUTE=off
TRIBUTE__ERROR=off
TRIBUTE__IN=off
TRIBUTE__OUT=off

AA=off
AA__ERROR=off
AA__MESSAGE=off
AA__IN=off
AA__OUT=off


DOORS=off
DOORS__INFO=off

PETS=off
PETS__AGGRO=off

COMBAT=off
COMBAT__ATTACKS=off
COMBAT__TOHIT=off
COMBAT__MISSES=off
COMBAT__DAMAGE=off
COMBAT__HITS=off
COMBAT__RANGED=off
COMBAT__SPECIAL_ATTACKS=off
COMBAT__PROCS=off

GUILDS=off
GUILDS__ERROR=off
GUILDS__ACTIONS=off
GUILDS__DB=off
GUILDS__PERMISSIONS=off
GUILDS__REFRESH=off
GUILDS__IN_PACKETS=off
GUILDS__OUT_PACKETS=off
GUILDS__IN_PACKET_TRACE=off
GUILDS__OUT_PACKET_TRACE=off

CLIENT=off
CLIENT__ERROR=on
CLIENT__DUELING=off
CLIENT__SPELLS=off
CLIENT__NET_ERR=on
CLIENT__NET_IN_TRACE=off

SKILLS=off
SKILLS__GAIN=off

RULES=off
RULES__ERROR=on
RULES__CHANGE=on

NET=off
NET__WORLD=on
NET__OPCODES=on
NET__IDENTIFY=off
NET__IDENT_TRACE=off
NET__STRUCTS=off
NET__STRUCT_HEX=off
NET__ERROR=off
NET__DEBUG=off
NET__APP_TRACE=off
NET__APP_CREATE=off
NET__APP_CREATE_HEX=off
NET__NET_TRACE=off
NET__NET_COMBINE=off
NET__FRAGMENT=off
NET__FRAGMENT_HEX=off
NET__NET_CREATE=off
NET__NET_CREATE_HEX=off
NET__NET_ACKS=off
NET__RATES=off

DATABASE=off

COMMON=off
COMMON__ERROR=on
COMMON__THREADS=off

LAUNCHER=on
LAUNCHER__ERROR=on
LAUNCHER__INIT=on
LAUNCHER__STATUS=on
LAUNCHER__NET=on
LAUNCHER__WORLD=on

WORLD=off
WORLD__CONFIG=on
WORLD__INIT=on
WORLD__INIT_ERR=on
WORLD__CLIENT=off
WORLD__ZONE=on
WORLD__LS=on
WORLD__CLIENT_ERR=on
WORLD__ZONE_ERR=on
WORLD__LS_ERR=on
WORLD__SHUTDOWN=on
WORLD__CLIENTLIST=off
WORLD__CLIENTLIST_ERR=on
WORLD__ZONELIST=on
WORLD__ZONELIST_ERR=on
WORLD__CLIENT_TRACE=off
WORLD__ZONE_TRACE=off
WORLD__LS_TRACE=on
WORLD__CONSOLE=on
WORLD__HTTP=off
WORLD__HTTP_ERR=on
WORLD__PERL=off
WORLD__PERL_ERR=on
WORLD__EQW=on
WORLD__LAUNCH=on
WORLD__LAUNCH_ERR=on
WORLD__LAUNCH_TRACE=on

LOG_CATEGORY( MAIL )
LOG_TYPE( MAIL, INIT, ENABLED )
LOG_TYPE( MAIL, ERROR, ENABLED )
LOG_TYPE( MAIL, CLIENT, DISABLED )
LOG_TYPE( MAIL, TRACE, DISABLED )
LOG_TYPE( MAIL, PACKETS, DISABLED)

LOG_CATEGORY( CHANNELS )
LOG_TYPE( CHANNELS, INIT, ENABLED )
LOG_TYPE( CHANNELS, ERROR, ENABLED )
LOG_TYPE( CHANNELS, CLIENT, DISABLED )
LOG_TYPE( CHANNELS, TRACE, DISABLED )
LOG_TYPE( CHANNELS, PACKETS, DISABLED)

LOG_CATEGORY( UCS )
LOG_TYPE( UCS, INIT, ENABLED )
LOG_TYPE( UCS, ERROR, ENABLED )
LOG_TYPE( UCS, CLIENT, ENABLED )
LOG_TYPE( UCS, TRACE, ENABLED )
LOG_TYPE( UCS, PACKETS, DISABLED )

If you set "QUESTS=on", it might help to show if you have any quest issues that could be causing weird issues.

Other than that, a work-around for your problem might be to set the zone to do a daily reset using my Zone Reset Script posted in the custom quest section of the forums. Resetting the zone should clear out any RAM usage.

thepoetwarrior · #8 07-31-2009, 08:53 AM

I'll set the logs on, thanks much!

I was thinking last resort is rebooting Anguish with that quest we used when we were on windows. I still have it.

The raid is set up that trash and bosses are all 24 hour respawn, and they can't skip around since higher bosses will aggro a lower boss. So its basically a 24 hour raid. So I wouldn't want to reboot every two hours. Maybe every 12 or 24 hours.

Since I did the quest edits, and similar to qvic, our 2nd worst memory hog, after being up all night, Anguish is only taking up 507 megs, not over 1 gig, and Anguish is only taking up 87 megs, not 150-450 megs. So looks to be a bit better. Will check out the logs.

I appreciate the help.

-Hunter