1 2 Previous Next 26 Replies Latest reply: Jan 10, 2013 6:13 AM by Michel Go to original post RSS
      • 15. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
        Honza
        Yes, I've tried cleaning IPC resources.

        I think I'm up to the point when I need to create a service request with Oracle.
        • 16. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
          Nicolas.Gasparotto
          Looks like it's a demo env in a VM, right ? Ultimately and before raising a ticket to the support, would it be possible to reboot the server itself ?

          Nicolas.
          • 17. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
            Honza
            Hello Nicolas,

            I have rebooted the server before recreating the scheduler domain.

            To sum this up I've tried to:
            - Recreate domain
            - Clear resources, clear cache
            - Reboot
            - startup application and scheduler domain
            App engines configured as Yes will cause the process to be stuck at initiated
            - Only thing I can find in the logs at this point is that RunAsync process not being able to find the queue. Only similar problems on metalink, very few and not quite this problem.
            Setting No option for application engines causes the process to error out with the "no longer running error"
            PSPRCSRV.11989 (0) [01/10/13 11:06:05](3)    Number of New Process Request(s) To Start: 1
            PSPRCSRV.11989 (0) [01/10/13 11:06:05](0)    Process Instance: 47606 started 
            PSPRCSRV.11989 (0) [01/10/13 11:06:05](3)    Starting process:  47606
            PSPRCSRV.11989 (0) [01/10/13 11:06:05](3)         Process Name: AEMINITEST 
            PSPRCSRV.11989 (0) [01/10/13 11:06:05](3)         Process Type: Application Engine
            PSPRCSRV.11989 (0) [01/10/13 11:06:05](3)        Command Line:  psae
            PSPRCSRV.11989 (0) [01/10/13 11:06:05](3)        Parm List:     -CT ORACLE -CD FC91DB -CO "VP1" -CP OPRPSWD -R 1 -I 47606 -AI AEMINITEST -OT 6 -FP "/home/fc91/psft/pt/8.52/appserv/prcs/FC91DB/log_output/AE_AEMINITEST_47606/" -OF 14 -TRACE 387 -TOOLSTRACEPC 3596
            PSPRCSRV.11989 (0) [01/10/13 11:06:05](3)        Working Dir:   
            PSPRCSRV.11989 (0) [01/10/13 11:06:05](3)         Session Id:   12145
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](3)    Server: PSUNX checking status...
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](3)    Server action mode: Ok (looking for requests)
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](3)    Server: PSUNX looking for work
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](3)    Checking Process cancels...
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](1) =================================Error===============================
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](1)    Process 47606 is marked 'Initiated' or 'Processing' but can not detect status of PID
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](3)    Updating process instance's status to Error.
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](2)         Process Name: AEMINITEST
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](2)         Process Type: Application EnginePSPRCSRV.11989 (0) [01/10/13 11:06:20](2)         Session Id:   12145
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](2) =====================================================================
            PSPRCSRV.11989 (0) [01/10/13 11:06:20](3)   Number of requests removed from Task Active List:  1
            Hm, I can try running these manually from the command line like with reports ..
            • 18. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
              Nicolas.Gasparotto
              I'm still wondering why traces options are appended. Is it configured in process definition, apps or prcs config file ?

              Nicolas.
              • 19. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
                Honza
                In that case it was appended for the process definition, same output without trace append:
                PSPRCSRV.11989 (0) [01/10/13 12:09:12](3)    Server: PSUNX looking for work
                PSPRCSRV.11989 (0) [01/10/13 12:09:12](3)    Checking Process cancels...
                PSPRCSRV.11989 (0) [01/10/13 12:09:12](3)      Requests found in Process Request table         1
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)    Server: PSUNX checking status...
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)    Server action mode: Submitting request
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)    Number of New Process Request(s) To Start: 1
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](0)    Process Instance: 47607 started 
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)    Starting process:  47607
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)         Process Name: AEMINITEST
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)         Process Type: Application Engine
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)        Command Line:  psae
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)        Parm List:     -CT ORACLE -CD FC91DB -CO "VP1" -CP OPRPSWD -R 1 -I 47607 -AI AEMINITEST -OT 6 -FP "/home/fc91/psft/pt/8.52/appserv/prcs/FC91DB/log_output/AE_AEMINITEST_47607/" -OF 14
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)        Working Dir:   
                PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)         Session Id:   12571
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Server: PSUNX checking status...
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Server action mode: Ok (looking for requests)
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Server: PSUNX looking for work
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Checking Process cancels... 
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](1) =================================Error===============================
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](1)    Process 47607 is marked 'Initiated' or 'Processing' but can not detect status of PID
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Updating process instance's status to Error.
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](2)         Process Name: AEMINITEST
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](2)         Process Type: Application Engine
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](2)         Session Id:   12571
                PSPRCSRV.11989 (0) [01/10/13 12:09:28](2) =====================================================================
                PSPRCSRV.11989 (0) [01/10/13 12:09:29](3)   Number of requests removed from Task Active List:  1
                PSPRCSRV.11989 (0) [01/10/13 12:09:44](3)    Server: PSUNX checking status...PSPRCSRV.11989 (0) [01/10/13 12:09:44](3)    Server action mode: Ok (looking for requests)
                PSPRCSRV.11989 (0) [01/10/13 12:09:44](3)    Server: PSUNX looking for work
                The reason why there was an append was probably just testing, or showing someone how to accomplish this.
                • 20. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
                  Honza
                  In that case it was appended for the process definition, same output without trace append:
                  PSPRCSRV.11989 (0) [01/10/13 12:09:12](3)    Server: PSUNX looking for work
                  PSPRCSRV.11989 (0) [01/10/13 12:09:12](3)    Checking Process cancels...
                  PSPRCSRV.11989 (0) [01/10/13 12:09:12](3)      Requests found in Process Request table         1
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)    Server: PSUNX checking status...
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)    Server action mode: Submitting request
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)    Number of New Process Request(s) To Start: 1
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](0)    Process Instance: 47607 started 
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)    Starting process:  47607
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)         Process Name: AEMINITEST
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)         Process Type: Application Engine
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)        Command Line:  psae
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)        Parm List:     -CT ORACLE -CD FC91DB -CO "VP1" -CP OPRPSWD -R 1 -I 47607 -AI AEMINITEST -OT 6 -FP "/home/fc91/psft/pt/8.52/appserv/prcs/FC91DB/log_output/AE_AEMINITEST_47607/" -OF 14
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)        Working Dir:   
                  PSPRCSRV.11989 (0) [01/10/13 12:09:13](3)         Session Id:   12571
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Server: PSUNX checking status...
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Server action mode: Ok (looking for requests)
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Server: PSUNX looking for work
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Checking Process cancels... 
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](1) =================================Error===============================
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](1)    Process 47607 is marked 'Initiated' or 'Processing' but can not detect status of PID
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](3)    Updating process instance's status to Error.
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](2)         Process Name: AEMINITEST
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](2)         Process Type: Application Engine
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](2)         Session Id:   12571
                  PSPRCSRV.11989 (0) [01/10/13 12:09:28](2) =====================================================================
                  PSPRCSRV.11989 (0) [01/10/13 12:09:29](3)   Number of requests removed from Task Active List:  1
                  PSPRCSRV.11989 (0) [01/10/13 12:09:44](3)    Server: PSUNX checking status...PSPRCSRV.11989 (0) [01/10/13 12:09:44](3)    Server action mode: Ok (looking for requests)
                  PSPRCSRV.11989 (0) [01/10/13 12:09:44](3)    Server: PSUNX looking for work
                  The reason why there was an append was probably just testing, or showing someone how to accomplish this.
                  • 21. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
                    Honza
                    At his point I'm not sure which to troubleshoot: case with or without the Yes option in interactive psadmin setup. Although the cause is probably the same thing.
                    • 22. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
                      Michel
                      That's a difficult question. For me the evidence points towards Tuxedo. There might be something wrong with Tuxedo what could be the cause of both error messages, but I'm not entirely convinced that both errors are because of the exact same reason. Either way in both situations Application Engines do not work.

                      Were you able to run the psae via command line without problems?

                      You can also check the stderr and stdout logs by the way. Those should mention any Tuxedo errors as well.
                      • 23. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
                        Honza
                        I'm getting "Segmentation fault" when running the parameter list from the command line. Been trying to figure it out for some time now, what exactly that might point to. Maybe just can't get the right syntax, but I get "segmentation fault" even when invoking only psae alone.
                        • 24. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
                          Nicolas.Gasparotto
                          Is there anything in stderr and stdout files ? Have you tried to remove all the unsuccessfull (error/not success) runs of AE ?

                          Nicolas.
                          • 25. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
                            Honza
                            Only in stdout:
                            =================================Error===============================
                             Message:     Process 47608 is marked 'Initiated' or 'Processing' but can not detect status of PID
                                    Process Name: AEMINITEST
                                    Process Type: Application Engine
                                    Session Id:   3214
                            =====================================================================
                            And yes, unsuccessful processes have been cleared.
                            • 26. Re: Application Engine initiated: Tuxedo cannot find RunAeAsync
                              Michel
                              That's a bit strange. A segmentation fault would be an error from the OS and not PeopleSoft.
                              1 2 Previous Next