Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Log files
System
We have an OD receiver Unix installation installed in /opt/opendeploy, with the log files configured to use /logs/opendeploy
A log file, "od.log" is created in /opt/opendeploy, and appended to at every deploy. This is in addition to the main log file /logs/opendeploy/[servername]_odrcvr.log. We need ALL the logs to go to /logs, and no writes to occur in the installation directory. How can this be accomplished?
After a week, we now have around a thousand log files in one directory, slowing down the server. As we do need to keep the logs, the solution is not as simple as to delete them.
Is there a way to remove the unique number from the deployment name so the receiver will really append to the log files instead of creating new files? We can live with four log files for each workflow, but not four new log files for each and every time something is deployed. In other
words, is there a way to configure the name used to not be unique for each and every deploy INSTANCE?
Find more posts tagged with
Comments
Migrateduser
W.R.T the od.log being updated with every deployment, it should not be, there should be only one update when the OD service/process is started. Moving this file out of the <od-home>directory though seems to be a feature request.
For the number of logs that are generated, I've confirmed that the receiver logs are appended, and the unique number described may be an artifact of the implementation. Can you confirm if the deployment configuration files are being generated on the fly with these unique identifiers in the definition name or config file name??