Troubleshooting Storage Gateway

1. Add the docker group to the existing groups in your host:

   sudo groupadd docker

2. Add your user id to the docker group:

   usermod -a -G docker user

3. Shut down your host:

   shutdown –r now

4. Log in to your host and run the Storage Gateway installation script:

   sudo ./ocisg-install.sh

1. Run the ocisg info command:

   sudo ocisg info

   If Storage Gateway is not running, start Storage Gateway:

   sudo ocisg up

2. Make a note of the management console port number from the output:

   Management Console: https://myStorageGatewayHost.example.com:32775
   
   If you have already configured a OCISG File System via the Management Console, you can access the NFS share using the following port.
   
   NFS Port: 32774
   
   Example: mount -t nfs -o vers=4,port=32774 myStorageGatewayHost.example.com:/ocisg_file_system_name/local_mount_point

   In the example, myStorageGatewayHost.example.com is the Storage Gateway host name and 32775 is the management console port number.

3. Ensure that Storage Gateway is running docker on the Storage Gateway host.

4. Check that the management console port number in the output from ocisg info matches the port you’re using to access the management console.

5. Ensure that you are using HTTPS if you have enabled SSL. SSL is enabled by default.

1. Run the ocisg info command:

   sudo ocisg info

   If Storage Gateway is not running, start Storage Gateway:

   sudo ocisg up

2. Make a note of the management console port number and NFS port number from the output:

   Management Console: https://myStorageGatewayHost.example.com:32775
   
   If you have already configured a OCISG File System via the Management Console, you can access the NFS share using the following port.
   
   NFS Port: 32774
   
   Example: mount -t nfs -o vers=4,port=32774 myStorageGatewayHost.example.com:/ocisg_file_system/local_mount_point

   In the sample output:

   • myStorageGatewayHost.example.com is the Storage Gateway host.

   • 32775 is the management console port number.

   • 32774 is the NFS port number.

   • Log in to the NFS client from which you want to access your service instance through Storage Gateway.

   • Create a directory on the NFS client.

   • Mount the file system on the directory that you created on the NFS client:

     sudo mount -t nfs -o vers=4,port=NFS_port storage_gateway_host:/ocisg_file_system/local_mount_point

     In this command:

     • Replace NFS_port with the NFS port number.

     • Replace storage_gateway_host with the server name or IP address of the server on which Storage Gateway is installed.

     • Replace ocisg_file_system with the name of the file system you want to mount.

     • Replace local_mount_point with the path to the directory you created on the NFS client.

     For example:

     sudo mount -t nfs -o vers=4,port=32774 myStorageGatewayHost.example.com:/myFirstFS /home/xyz/abc

     In this example,

     • 32774 is the NFS port number.

     • myStorageGatewayHost.example.com is the Storage Gateway host name.

     • myFirstFS is the file system name.

     • /home/xyz/abc is the path to the directory abc on the NFS client.

   • Ensure that Storage Gateway is running docker on the Storage Gateway host.

   • Ensure that the NFS protocol is running:

     sudo systemctl enable nfs-server

   • Check that the NFS port number in the output from ocisg info matches the port you’re using to connect to with your NFS client.

If you cancel an active or stalled Cloud Sync job and disconnect the file system, you might not be able to delete the associated Object Storage bucket. If file uploads were in progress when you canceled the job, the Object Storage service might expect a commit that never completed. In this case, the service does not allow bucket deletion and returns the error "multipart upload pending". You can use the CLI to resolve the issue.

1. List the bucket's pending multipart uploads:

   oci os multipart list -bn bucket_name

   Be sure to note the relevant object names and upload IDs.

2. Delete all pending uploads:

   oci os multipart abort -bn bucket_name --object-name object_name --upload-id upload_id

3. Delete the bucket:

   oci os bucket delete -ns object_storage_namespace> --name bucket_name

The Storage Gateway installation software installs the NFS, if needed, and automatically configures it. After the installation, the NFS is configured and a file system created. You can then mount the filesystem from a remote client. Sometimes this mount can fail.

To troubleshoot a mount failure:

1. Ensure that the NFS port is included in the Storage Gateway's subnet security list and that it is available there. If the port does not appear in the subnet security list, add it and retry the mount.

2. Run rpcinfo -p. The command should return:

   100003 4 tcp 2049 nfs

   This result means that NFS is ready, available, and the mount succeeds.

3. If nfs does not appear in the response to the rpcinfo -p command, enable and restart both rpcbind and NFS:

   sudo systemctl enable rpcbind
   sudo systemctl enable nfs
   sudo systemctl start rpcbind
   sudo systemctl start nfs

4. Run the rpcinfo -p command again to verify that NFS is now available.

   1. If NFS still is not available, reboot the Storage Gateway.
   2. Run the rpcinfo -p command again to confirm.
5. If you remain unable to mount the file system, contact Oracle Support.

You can increase the size of your cache, metatdata, and logging after your complete installing Storage Gateway. Any component you resize post-installation must be a storage block volume. See Resizing a Volume for more information.