Sourceone job logs maintenance

Question

Hi

I have noticed a large number of logs in the Operations/Job Management, especially those related to Journaling (1 every minute).

I looked at the file level, but could not find any, so the jobs must be logged in the SQL database.

Question 1: is there a way to enable journaling logs let's say one per day, or one per hour, just to let us know that journaling is working OK.

Question 2: How do one removes/trim old logs? I noticed all the logs since the installation of Sourceone are still there, so there is no build-in process for it.

Thanks

Gary_Reardon · Answer

There is a logs in a log folder under the install directory that are used for troubleshooting.

Those automatically roll-off up to a maximum of 5 and then restart.

If you have detailed logging enabled in the task then logs are created in the designated joblogs folder.

The details of each task run is the Activity DB.

201001 · Answer

Thanks Garry

What do you mean by automatic roll-off up to a maximum of 5?

I have found the file ExJBJournal.exe (about 400Mb). I could not open it in Windows, so copied it to a Linux box to see what it looked like. Seems to be it.

I can see it has all the journalling logs from day 1.

Sourceone does not seem to trim/rotate it automatically.

If it was on Linux, I would know how to set a task to trim it let's say once a week, but I do not know how to do something similar on Windows

201001 · Answer

Well, I could not find any .log files (they all finished with .exe, via explorer) until I went to the command prompt, and yes all the logs are there, finishing with .exe.log

As you mentionned, I noticed a #000000001.log for the index service but the journal service log is still 400Mb and has not started splitting itself.

I might manually move it with a new 00000.1.log suffix to see if it gets recreated automatically and get split after 100Mb

Gary_Reardon · Answer

Each service has a log associated with it ServiceName .log extension. After it gets to 100 MB it creates a ServiceName#0000000001.log then when that one reaches 100 MB a 02 and so on up to 09.

SourceOne

Sourceone job logs maintenance

Was this post helpful?