OnDemand User Group
Support Forums => MP Server => Topic started by: jsquizz on July 02, 2020, 09:57:53 AM
-
We are running trace, and I'm trying to figure out where the file is output to. It's set to -
[TRACE]
TRACE_FILE=ARCHIVE.trace.log
TRACE_LEVELS=DB=3,SOCKET=3,SRVR=3
I verified it's running. But Can't find the file. In reading the documentation (if i understand it correctly), it shold goto ARS_TMP..which It's not.
It's also not in /config and /bin .. My thoughts are its writing somewhere and it might fill up a file system. We have to run arsmaint to purge 100mil+ docs, and that smells like trouble to me.
anyone have any thoughts?
-
Did you search in /tmp ?
Usually the trace files is wrote in /tmp when is not set on trace.settings
Lair Martins
IBM Brazil
-
Did you search in /tmp ?
Usually the trace files is wrote in /tmp when is not set on trace.settings
Lair Martins
IBM Brazil
Yeah, It's not there. I thought the same thing. There's no trace file at all being generated.
-
if you have root access, maybe:
find / -type f | grep "trace.log"
....or some variant of this command could help to traverse all directories.
-
Without specifying a full path, I would expect the trace log to be generated in the directory you were in when you ran the arssockd command.
Why not just change the file to include a full path? :) Somewhere with wide open permissions like /arstmp or /tmp.
If it's not able to create the trace file, it probably doesn't have permissions to write the file there.
-JD.
-
Without specifying a full path, I would expect the trace log to be generated in the directory you were in when you ran the arssockd command.
Why not just change the file to include a full path? :) Somewhere with wide open permissions like /arstmp or /tmp.
If it's not able to create the trace file, it probably doesn't have permissions to write the file there.
-JD.
I figured that too. We need to turn trace off because for some reason it's been running in production. I'm just really curious as to where the trace file is being generated.