Problem with log file getting too big...

[Guest fsoudbakhsh]

Suddenly VG used 99% of CPU and this cause our system to crash.

I can not finger out why all the sudden VG act link this.

My system has 1G RAM,

250 G hard drive,

2.3 GHZ CPU.

 

Please see attached pictures for this problem.

Thanks

[SupportTeam]

Which version of VoiceGuide are you using?

 

What was the system doing at the time?

 

Please provide traces (from VG's \log\ subdirectory) from the time you saw this happen.

[Guest fsoudbakhsh]

I can not attache the log file which contain the problem with no answer when the log file is too big in memory size.

 

the file is rar file.

 

here is the error I get from Forum:

 

THE FOLLOWING ERROR(S) WERE FOUND

You cannot upload this type of file

 

I can not open this file because it is too big, no application including Ms word could open this file for me.

 

Perhaps in this file you would see why VG will take more then 97% of CPU suddenly too.

 

please let me know how can I send this file to you??

 

Thanks

[SupportTeam]

How big is the log file (unzipped and .zipped)?

 

On our test systems we get log files over 1GB+ (1024MB+) regularly with no problems...

[SupportTeam]

Had a look at the log file you emailed to us directly.

 

The 'vgm' log is about 800MB and covers the operation of the system from 6AM till about 6:30AM.

 

Why is it so big?

Well it shows that your script after answering the call and getting all the info from caller is then starting a Database query in module [LookForFarzadRateForOrgenateCall], and the query ran is:

 

Select FarzadRate From 2 Where Code = ""

 

That query does not return any data - and it looks like you have designed your script to now go into an infinite loop continually calling module [LookForFarzadRateForOrgenateCall], and adding Result Variables to VG and this infinite Database query loop is what's causing all the problems... you have a tight loop which all that it does is make one database query after another, as fast as VoiceGuide can make them... that is why you're seeing CPU usage so high - you’ve got an infinite loop doing database queries and VoiceGuide is working as had as it can executing these queries one after another...

 

You should fix your script so that such loops don't happen...

 

 

And next time you have a situation where you see unnaturally large log files or large CPU usage then just have a look inside the log file to see what is causing so much logging/work... you will be able to see the answer there yourself immediately...

 

You will usually be able to quickly spot what modules are going round and round in circles by looking at the log file entries starting with "rvns " or "rv ns" (after the timestamp and LineID).

The "rvns " (or "rv ns") line shows the RVs created by the script and if you see some RVs created over and over then you know you have a problem with the script going round and round in some infinite loop....