restart OengineServer V10.0(OpenJDK) (OEngine Server)
At 17 FEB 2022 06:12:22PM Barry Stevens wrote:
In Task Manger when I restart restart OengineServer V10.0(OpenJDK) I then see the following .log files created.
Can you please tell me if this indicates I have issues.
FileName = eserver_SystemMonitor.log
Content = 2
FileName = eserver_SystemMonitor_1.log
Content:
Process started at 2022-02-18 09:56:13 About to process *1**SYSPROG3REVCMD_LISTENER at 2022-02-18 09:56:13 login to account 'SYSPROG', user '*': 00\\.\L_18088_5688213256600Q_18088_5688213256600SYSPROG651*REVCMD_LISTENER0W14104336 About to process *3DO_LOGINPROC (. at 2022-02-18 09:56:16 login process: 00 About to process *3RTI_OEMONITOR_CLEANUP at 2022-02-18 09:56:16 command 'RTI_OEMONITOR_CLEANUP': 00 Process finished at 2022-02-18 09:56:16FileName = eserver_SystemMonitor_2.log
Content:
Process started at 2022-02-18 09:56:13 About to process *1**SYSPROG3REVCMD_LISTENER at 2022-02-18 09:56:13 login to account 'SYSPROG', user '*': 00\\.\L_18088_5688211137600Q_18088_5688211137600SYSPROG651*REVCMD_LISTENER0W14104336 About to process *3DO_LOGINPROC (. at 2022-02-18 09:56:16 login process: 00 About to process *3RTI_OEMONITOR_INDEX at 2022-02-18 09:56:16 command 'RTI_OEMONITOR_INDEX': 03Invalid request for input during phantom processing (1): *5* Process finished at 2022-02-18 09:56:16FileName = eserver_SystemMonitor_2.err
Content:
Error during command 'RTI_OEMONITOR_INDEX' at 2022-02-18 09:56:16: 03Invalid request for input during phantom processing (1): *5*
At 18 FEB 2022 07:40AM bshumsky wrote:
Hi, Barry.
The first maintenance task (RTI_OEMONITOR_CLEANUP) has run successfully; the output in the log file shows that. The second task, however (RTI_OEMONITOR_INDEX) has encountered an error (as you can see in the log, and preserved as well in the err file).
I believe we've already tracked that down and fixed it for the next release.
- Bryan Shumsky
At 18 FEB 2022 02:37PM Barry Stevens wrote:
Hi, Barry.
The first maintenance task (RTI_OEMONITOR_CLEANUP) has run successfully; the output in the log file shows that. The second task, however (RTI_OEMONITOR_INDEX) has encountered an error (as you can see in the log, and preserved as well in the err file).
I believe we've already tracked that down and fixed it for the next release.
- Bryan Shumsky
Thank you.
Any idea what sort of issue this causes?
At 18 FEB 2022 03:37PM bshumsky wrote:
Do you have "update before query" set in your application environment settings? If so, then this won't cause any issues. It just prevents the engine server from acting as an indexing server at this time.
- Bryan Shumsky
At 18 FEB 2022 03:49PM Barry Stevens wrote:
Do you have "update before query" set in your application environment settings? If so, then this won't cause any issues. It just prevents the engine server from acting as an indexing server at this time.
- Bryan Shumsky
Thanks - yes it is set