error

Juan,

There should be more information in the gem log for that process. By default the pid (18503) should be in the name of the gem log file.

With this type of error showing up in the pcmon log, it implies that the gem may have had an error that didn't allow it to do it's normal shutdown process which includes writing information to the gem log:(

So, there may not necessarily be info in the gem log. The other place to look is the stone log ... the stone will sometimes kill processes that it thinks are misbehaving (not responding to signals) and the stone should record that information in the stone.log.

Dale

On 11/26/2010 08:59 AM, Juan wrote:

folks

i have the follow error

[11/26/10 13:33:03.811 ART]: Client died
 vcid 12 clientId 10 ptSlot 11 processId 18503 lostOtTimeout 0,
processName Topaz478
   [Info]: Cleaned up locked/pinned frame 6958 for crashed process 18503

the error was collected with:

 tail -f seaside_13556pcmon.log

there any way to make more verbose the log error?
any clue?
best regards

Juan,

Given this list it is probably one of the FastCGI logs (you can grep for the pid 18503 to figure out which one. The stone log is the seaside.log file

Dale

On 11/26/2010 09:26 AM, Juan wrote:

DAle

thanks for responses.
Dale the gem log what your are talking about what file is?
this my list of log's file.

FastCGI_server-9001.log         seaside_13578admingcgem.log
seaside_4743pgsvrff.log        seaside_4768admingcgem.log
FastCGI_server-9002.log         seaside_13581symbolgem.log
seaside_4744pgsvrff.log        seaside_4770symbolgem.log
FastCGI_server-9003.log         seaside_4649pcmon.log
seaside_4745pgsvraio.log       seaside_4774reclaimgcgem0.log
gs64ldi.log                     seaside_4659pgsvrff.log
seaside_4745reclaimgcgem0.log  seaside_4775admingcgem.log
maintenance_gem.log             seaside_4661pgsvraio.log
seaside_4746admingcgem.log     seaside_4776symbolgem.log
seaside_13556pcmon.log          seaside_4677pcmon.log
seaside_4746pgsvraio.log       seaside_4790pagemanager.log
seaside_13560pgsvrff.log        seaside_4679pcmon.log
seaside_4751symbolgem.log      seaside_4817symbolgem.log
seaside_13561pgsvraio.log       seaside_4683pcmon.log
seaside_4754pagemanager.log    seaside.log
seaside_13571pagemanager.log    seaside_4714pcmon.log
seaside_4762pagemanager.log
seaside_13576reclaimgcgem0.log  seaside_4733pagemanager.log
seaside_4766reclaimgcgem0.log


 best
mdc

On Fri, Nov 26, 2010 at 2:19 PM, Dale Henrichs <[hidden email]

<mailto:[hidden email]>> wrote:

   Juan,

   There should be more information in the gem log for that process. By
   default the pid (18503) should be in the name of the gem log file.

   With this type of error showing up in the pcmon log, it implies that
   the gem may have had an error that didn't allow it to do it's normal
   shutdown process which includes writing information to the gem log:(

   So, there may not necessarily be info in the gem log. The other
   place to look is the stone log ... the stone will sometimes kill
   processes that it thinks are misbehaving (not responding to signals)
   and the stone should record that information in the stone.log.

   Dale


   On 11/26/2010 08:59 AM, Juan wrote:

       folks

       i have the follow error

       [11/26/10 13:33:03.811 ART]: Client died
         vcid 12 clientId 10 ptSlot 11 processId 18503 lostOtTimeout 0,
       processName Topaz478
           [Info]: Cleaned up locked/pinned frame 6958 for crashed
       process 18503

       the error was collected with:

         tail -f seaside_13556pcmon.log

       there any way to make more verbose the log error?
       any clue?
       best regards