Disk is full

Owned by Ricky Villa
Last updated: Jan 19, 2021 by Kimberly Cruz (Unlicensed)
4 min read

When the disk starts to get full (less than 100MB) the system shutdowns down into readonly mode (this can be seen in the Diagnosed section in Debug, for more information: https://finproducts.atlassian.net/wiki/spaces/FINFramework/pages/770709374#HomeDebug-Diagnostics )

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

Below are a few things the user can do:

Increase Memory Heap

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

1. Go to your FIN 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

  • Increase the Maximum memory pool to something the system is capable of handling depending on the space available

5. Select the Apply button to change the maximum memory pool.

6. Close the window by selecting the Okay button

7. Right click the FIN icon and select Start Service

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 that is in the default demo (leave it zipped)

2. Once downloaded, select the App Launcher menu icon then select the Job tile under Advanced Apps

3. Select the Restore button to upload a file

4. Select the Choose File button to upload the SnapshotControl.zip

5. Select the Upload button to upload the file in FIN

6. There should be a new job called Snapshot Control

7. Select the Snapshots Control job then click on the Run button

Check logs

Another thing to check would be logs to see if you have a lot of them or if any are large.

Only the superuser (su) is able to view the logs

1. Click on the App Launcher menu icon, this will open a set of apps available

2. Select on the Host tile under Advanced Apps

3. This will open the landing page. This page will look different for each user depending on their user type.

4. Select on the Debug icon

5. Select on the Log option, this is where the superuser can view the logs about the system and what is occurring

  • Inspect a few to see what they might be about to see if some can be resolved or what issues there might be

Note

If issues continue to arise, check the logs in the directory to see if there are any large files or a lot of logs. If it has either large files or there are a lot of logs, go ahead and delete the logs.

  • Make sure to stop running FIN before accessing the directory, otherwise it will not allow the user to delete any logs.

  • Example path: C:\Program Files (x86)\FIN Framework\FIN Framework 5.0.7.3410\var\log

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.