I have been running my workspace (which unfortunately I cannot easily share) that uses a number of PythonCallers which each writes to the log file via the FMEObjects calls. What I have found is that when running the workspace from the GUI all the log messages are written to the log file. But when running the workspace from the command line I have found that some installations of FME will log all the details while others will not. Is there some configuration file or command line option that would force FME to record all log messages to the log file?
Solved
Execution from command line sometimes doesn't write data to log file
+1
Can you give more details about the installations that are logging correctly versus the ones that are not?
+1All installations should be Build 16674, which should have been installed as standard from the installer. Are there any more specific details you would like to know about the machines in question?
jstanger wrote:
All installations should be Build 16674, which should have been installed as standard from the installer. Are there any more specific details you would like to know about the machines in question?
+13- Safer
stalknecht wrote:
You can configure it in workbench:
+13- Safer
>What I have found is that when running the workspace from the GUI all the log messages are written to the log file.
Do all installations correctly log out, when the workspace is run from the FME Workbench GUI?
+1stalknecht wrote:
You can configure it in workbench:
+1rylanatsafe wrote:
>What I have found is that when running the workspace from the GUI all the log messages are written to the log file.
Do all installations correctly log out, when the workspace is run from the FME Workbench GUI?
+1I have had the client confirm that the Build numbers are the same.
They report that the command line console shows the required log information coming from the PythonCaller but these same details don't get written to the log file specified.
+13- Safer
jstanger wrote:
I have had the client confirm that the Build numbers are the same.
They report that the command line console shows the required log information coming from the PythonCaller but these same details don't get written to the log file specified.
For FME Server Engines, Python is not typically logged to the Job Log file, rather it is recorded to the fmeprocessmonitorengine.log file. (See this Q&A; Post) That wouldn't explain why some do and some don't.. Please check that log file on FME Server and see if that is where the missing messages are found!
+1rylanatsafe wrote:
Hmm, I may have misunderstood your initial report. The logging is coming from PythonCaller transformers. Is that correct?
For FME Server Engines, Python is not typically logged to the Job Log file, rather it is recorded to the fmeprocessmonitorengine.log file. (See this Q&A; Post) That wouldn't explain why some do and some don't.. Please check that log file on FME Server and see if that is where the missing messages are found!
Indeed the logging was coming from a PythonCaller but with the default logging status of Inform. Therefore, I'm going to accept the answer given because of the possible configuration differences that could have caused the issue.
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.