In my "date" tests for the process service, I did get this to show up in
nohup.out:

20100203-12:52:28;3856;00000100;Caught unknown exception in
STAFProcessService::sendNotificationCallback()
date: 0551-402 Invalid character in date/time specification.
Usage: date [-n][-u] [mmddHHMM[[cc]yy]] [+"Field Descriptors"]
Usage: date [-n][-u] [mmddHHMM[.SS[cc]yy]] [+"Field Descriptors"]
Usage: date [-a] [[+|-]sss.fff].

I've seen that error (in sendNotificationCallback()) before, too.  It
doesn't get put into nohup.out everytime I run a command through the
process service though...

Paul


                                                                       
  From:       Paul Ellsworth/San Jose/IBM                              
                                                                       
  To:         Paul Ellsworth/San Jose/i...@ibmus                        
                                                                       
  Cc:         David Bender/Austin/i...@ibmus, Sharon Lucas/Austin/i...@ibmus, 
staf-users@lists.sourceforge.net
                                                                       
  Date:       02/03/2010 01:03 PM                                      
                                                                       
  Subject:    Re: [staf-users] STAF running but does not return command output
                                                                       




(trimmed history off)

Hello,

It looks like this issue is still happening.  This time I did *not* reboot
the system and it showed up.  This is with staf 3.3.5 (fresh installation),
and there were no tty errors.  I haven't looked for java errors in any logs
yet...

The test was running along fine and unmounting some filesystems.  Then it
got to a cmp -l [two devices] command.  This command was usually taking 3
minutes.  After about 15 minutes, I decided it had died.  I killed the job,
which in turn killed the process on the system (the process still
existed...).  This particular system is an AIX one, which seems to get the
problem more often than any of the other systems.

And, sure enough, the process service is "unresponsive" again:

# staf local process start shell returnstdout returnstderr wait command
"date" STDIN /tmp/empty
Response
--------
{
  Return Code: 0
  Key        : <None>
  Files      : [
    {
      Return Code: 0>
      Data       :
    }
    {
      Return Code: 0>
      Data       :
    }
  ]
}
# staf local ping ping
Response
--------
PONG

I will update if I find anything else in any logs (anwhere I should look in
particular?).

Thanks,
Paul

<<inline: graycol.gif>>

<<inline: ecblank.gif>>

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users

Reply via email to