Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »


When the disk starts to get full (less than 100MB) the system shutdowns down into readonly mode (you can see the threshold settings and memory heap space in the Info App).

We created a Create Heap Usage Alert tool that will send you an email alert once a certain percentage has been reached.

What to do

Below are a few things the user can do. It can be a handful of things. It might be that you have so many snapshots and don't have a job to maintain them. Another thing is maybe not allocating enough memory heap to handle it. Having Audit Settings enabled can sometimes pile up and take a lot of space. Histories can be another source of that can consume space depending on how many points are being trend.

Increase Memory Heap

One way is to increase the memory heap for the service.

  1. Go to your FIN Stack notification icon in the tray
  2. Right click and select Stop to stop the service
  3. Right click again and select Configure...
  4. Once open, select the Java tab
  5. There, the user will increase the "Maximum memory pool" to something their system is capable of handling depending on space available
  6. Apply and right click again to Start the service for it to take effect

Add Snapshot Control job

Another thing that can be taking a lot of resources is snapshots (backups of project). If there is no job that maintains a certain amount of snapshots, then they will keep on getting generated and consume a lot of space. To avoid this, add the job below that runs every day at midnight and maintains at least 4 snapshots.

  1. Download the below job which is a copy of "Snapshots Control" we have in our demo (leave it zipped)
  2. Once downloaded, go to your Jobs app and select to Restore that zipped file
  3. You should now see a new job called "Snapshots Control"
  4. Select the job and run it and thats it

Check logs

Another thing to check would be logs to see if you have a lot of them or if any are large. If you have Audit Settings enabled, that will add extra logs. Its ok to have them enabled if not make huge amount of changes that get recorded.

  1. Go to Debug app
  2. Check count on logs
  3. Inspect a few to see what they might be about to see if some can be resolved or what issues there might be
  4. If they aren't important, they can also be deleted by doing to the directory (can also be checked this way). Here is example path of where to find them: C:\Program Files (x86)\FIN Stack\FIN Stack 4.0.2925\db\demo\logs
  5. System logs would be here: C:\Program Files (x86)\FIN Stack\FIN Stack 4.0.2925\service_logs
  6. Basically just want to check if you have a lot of logs and if any are large files, if you don't seem to have a lot, then it should be fine.
  7. Audit Settings can be found if you go to Menu > Settings > Audit Settings. This would be best to enable once the job is done since not many changes will be made if wanted.

Points Historized

Points being historized is another thing the user needs to take into account. If you have thousands of points and all being historized, then that can be something to look into. A question would be if all need to be trended or can some not be trended? If all are wanted, just make sure you have enough space to handle them.

  • No labels