Oracle OBIEE 12c. We have log rotation set up for the bi_server logs. They are set to 5MB, and rotate accordingly. However, we have a log file called bi_server.out which is 24GB and doesn't rotate for some reason. I don't see any settings in the WLS Admin Console to change the rotation settings for this log file.
Hoping someone could tell me where to look for the settings of this specific log to ensure that it rotates at a certain size, or creates a new log beyond logging so many queries.
.out isn't technically one of the log files which are governed by the log rotation. The .out is the file where the detailed outputs get piped to.
Update: If your .out file grows to those sizes then you definitely have an issue somewhere. You have to find out what's duping into the .out all the time and why.
Rename the file to bi_server1_0001.out when the obis1 component is stopped and then the system will create a new, empty one.
Related
I'm building an app that must visualize a large point cloud on HoloLens 1st gen. As performance is an issue wit large clouds, I'm using Potree, an octree that takes care that only a preset number of points from the cloud are rendered.
The solution works in the editor, but, you guessed it, not when deployed on HL.
The point cloud in the Potree format is a set of couple of .json and hundreds of .bin files stored in hundreds of subfolders following the octree structure, all of that stored within a single folder, and the path to this folder is accessed by the renderer at runtime. However, I don't know how to include this folder in the HL app. Using Resources doesn't work as it's not really a standard resource. I've seen Asset Bundle suggested elsewhere, but according to this post asset bundling doesn't work on HL.
Is there a way to simply put this complex file structure in an accessible directory on HoloLens?
I feel completely stuck here and any help would be much appreciated.
Some of the things I've tried:
Keijiro Pcx doesn't work here. If rendered as single pixels, points cannot be seen in AR, and if rendered as meshes, the performance is abysmal (which led me to a conclusion octree structure should be used)
the solution here shows how to load one .xml file, but I have hundreds of files so I don't think it would work for me
similarly, this post deals with one .obj file
Unity 2019.4
HoloLens 1st gen
For anyone stumbling upon this - I ended up using Unity StreamingAssets and accessing the folder with Application.streamingAssetsPath - works beautifully!
Using pcx needs to be adjusted to binocular rendering in publishing settings. Please uncheck "Enable Depth Buffer Sharing" in XR Settings, and change "Single Pass" to "Multi Pass", as shown in the figure.enter image description here
I would like to find the reason for a bug with an application and the Google Drive on Mac. With FSMonitor, I see that drive writes many logs in a structured_log_* file at ~/Library/Application Support/Google/DriveFS/Logs/ when I have the issue. But when I open the file it's not really readable in editor and toolbox.googleapps.com/apps/loggershark need drive_fs*.txt file and it does not contain any related log.
I see that structured_log_* are logs related to the file I open fichier test dsi2, but it is not readable.
How can I decode and read the file ?
Did you ever find an answer?
I'm looking to view the structured_log_* logs to see if it contains information on files uploaded and removed from a google drive account. Basically for auditing proposes...
But unfortunately, I can't make anything out. I have passed it through strings and sorted and it looks like the file names are contained within these logs and possibly the hashes of the files.
It would be nice to be able to decode the log properly to see whats the activity on in the log.
Thanks
I'm using R/RStudio on CentOS platform. I need to see if the binary log file (/var/log/messages) contains further information regarding a graphics device plotting issue, but I cannot read it from within RStudio.
I cannot find any information on the community support troubleshooting pages. The Help Menu -> Diagnostics -> ... does not indicate a 'Show Log Files' option. Can someone advise how this file can be accessed, preferably from within RStudio?
By default /var/log/messages is not readable by all users, so the first thing you need to do is make it accessible to whatever user you're logged in as in RStudio. This question has details and ideas:
https://serverfault.com/questions/258827/what-is-the-most-secure-way-to-allow-a-user-read-access-to-a-log-file
Once your user account has permissions to /var/log/messages, you can use something like the following to show it in RStudio:
> readLines("/var/log/messages")
(You could also try file.edit("/var/log/messages") to open it in an editor buffer, but that is less likely to succeed.)
I am using CocoaLumberjack for my logging as it seems a very versatile logging framework.
In my application, I need to log to a file, and have the contents of that file displayed in the app itself: this is for diagnostics purposes for the user of the app (mainly so they can see how much the app is accessing their network, which I log to file).
There is the DDFileLogger and DDLogFileManager classes. I can see how I can use the DDLogFileManager class to access a file once it's wrapped, but what I want to do is display the contents of the file in a UITextView - so that it shows the current contents.. not just when it's wrapped.
Either way, I can't see how to access the log file within the app itself - can anyone shed some light on how to do this please?
thanks!
See my answer here:
https://stackoverflow.com/a/11544657/620577
And these characters are just to reach the 30 minimum.
I need to prevent a document from being saved / saved as (say from ms word). I've looked around and I havn't quite found a satifying answer. I've considered EFS... but I don't think it prevents the user from saving the document as... (though it prevents access to the original source file). Any ideas outthere?
Run it on completely locked-down system with read-only disk, no network and no removable drives. Access to the computer must be phisically restricted as well.
This should prevent Save As from working, but still won't prevent document from being copied (someone may take photo of the screen and OCR it).
It usually isn't worth it to disable Save As, because you need access to the original in order to open it in the first place. There are always ways to copy a file.
I had the same issue come up when someone asked me to disable Save As for a PDF.
There is no way take an arbitrary document and modify it in such a way that it cannot be saved. You could modify a program such as Word not to allow Save or Save As but that would still allow someone to open and save the document with a different program or on a different machine.