Logging on the rapidminer server

Artm

Just playing around as a newbie with the rapidminer server.
I have some questions on logging.

When I run a process on the sever, I get less logging then when running locally.

For instance : 
When I run a process with an exeute script step, I do not see any operator.getLog().log("whatever") entries.
Also when using the Print to Console operator, I do not see any of those results in the Log.

Any thoughts about this ?

I was also wondering about how to configure a relative path in the process attrbitue  (logfile).
And then specifically, relative to the process definition location.

mmichel

Hi Artm,

have you tried using 

operator.getLogger().info("foo")

This will re-use the logger of the process instead of creating a new one.

Cheers

Marcel

MartinLiebig

Hi @Artm ,

did you try to increase the severity level? Like

operator.getLog().log("whatever",5)

Best,

Martin

Artm

@mschmitz, I did not use the additional parameter yet. But I did set the log level to all in the process.

Artm

@mschmitz, I tried also with the ,5 (warning) addition, but process on server just mentions : 

Dec 18, 2019 2:39:09 PM com.rapidminer.execution.jobcontainer.execution.SimpleExecutor

INFO: Execution of job '6d62d0ec-bc43-4a46-af9f-3cd389b9cab0' finished successfully.

Locally it (only) says :

Dec 18, 2019 3:40:15 PM WARNING: whatever

Edin_Klapic

Hi @Artm ,

Which log file did you check - server.log?

If you run a process on RapidMiner Server it is usually executed in a JobContainer on a JobAgent.

You should be able to see the same log output compared to RapidMiner Studio when you take a look at the process execution log which can be found in the RapidMiner Server Webinterface => Executions.

Happy Mining,

Edin

Artm

Hi @Edin, I in fact did look only at the process execution log.

Locally 

Dec 20, 2019 3:42:12 PM INFO: Process starts

Dec 20, 2019 3:42:12 PM WARNING: whatever

Dec 20, 2019 3:42:12 PM INFO: Saving results.

Dec 20, 2019 3:42:12 PM INFO: Process finished successfully after 0 s

Server

Dec 20, 2019 2:42:49 PM com.rapidminer.tools.ResultService init

INFO: No filename given for result file, using stdout for logging results!

Dec 20, 2019 2:42:49 PM com.rapidminer.execution.jobcontainer.execution.ExecutionProcessListener processStarts

INFO: Execution of process started

Dec 20, 2019 2:42:49 PM com.rapidminer.Process execute

INFO: Process //_LOCAL/home/artm/processes/dummy starts

Dec 20, 2019 2:42:49 PM com.rapidminer.execution.jobcontainer.execution.ExecutionProcessListener processStartedOperator

INFO: Started operator : Process

Dec 20, 2019 2:42:49 PM com.rapidminer.execution.jobcontainer.execution.ExecutionProcessListener processStartedOperator

INFO: Started operator : Execute Script

Dec 20, 2019 2:42:49 PM com.rapidminer.execution.jobcontainer.execution.ExecutionProcessListener processFinishedOperator

INFO: Finished operator : Execute Script

Dec 20, 2019 2:42:49 PM com.rapidminer.execution.jobcontainer.execution.ExecutionProcessListener processFinishedOperator

INFO: Finished operator : Process

Dec 20, 2019 2:42:49 PM com.rapidminer.Process execute

INFO: Process //_LOCAL/home/artm/processes/dummy finished successfully after 0 s

Dec 20, 2019 2:42:49 PM com.rapidminer.execution.jobcontainer.execution.ExecutionProcessListener processEnded

INFO: Execution of process stopped

Dec 20, 2019 2:42:49 PM com.rapidminer.execution.jobcontainer.execution.SimpleExecutor

INFO: Execution of job 'df93adee-5e98-41c5-aaf9-50b27cf6b72e' finished successfully.

Edin_Klapic

Hi @Artm ,

that is very strange. I get the same output in all execution environments (logverbosity on Process level has been kept to "init").

Can you post your process so we can check that?

Happy Mining,

Edin

Studio:

Server:

JobAgent:

Artm

Hi Edin, 

Find attached, nothing special I'd say.

mmichel

Hi Artm,

have you tried using 

operator.getLogger().info("foo")

This will re-use the logger of the process instead of creating a new one.

Cheers

Marcel

Artm

Hi @mmichel
Actually that made the server log foo.

Thanks for this.