How Can We Help You?

Yes, configuring a Mividas deployment with no direct internet access requires two separate Mividas Installer virtual machines:

1. Primary Mividas Installer (Main) VM: This VM provides the main Mividas Installer functions and is “air-gapped” from both the secondary VM and the internet.
2. Secondary Mividas Installer VM: This VM has internet access and is used solely for license activation and fetching updates.

Both VMs use the same image, with differences only in configuration and usage. Refer to Mividas Installer in Offline environment for more details.

If you encounter issues due to an expired local certificate, you can attempt to resolve it by reinitializing the Docker swarm cluster. This can be done using the following command:

sudo docker swarm init --force-new-cluster

This command forces Docker to create a new swarm cluster, which can help renew the local certificate and restore cluster functionality. Note that this should be done with caution and only if necessary, as it resets the swarm configuration.

To deactivate SAML SSO on the Mividas Installer, follow these steps:

1. Disable SAML SSO Temporarily: Run the following command to disable SAML SSO:

echo 'SAML_DISABLE=1' | sudo tee -a /opt/mividas/installer/.env; sudo /opt/mividas/installer/run_installer.sh

This command adds a line to the environment configuration file, disabling SAML, and then restarts the installer to apply the change.

2. Re-enable SAML SSO: When you’re ready to re-enable SAML, run the following command:

sudo sed -i 's/SAML_DISABLE=1//' /opt/mividas/installer/.env; sudo /opt/mividas/installer/run_installer.sh

This removes the disabling line and restarts the installer to activate SAML SSO again.

This approach lets you toggle SAML authentication on and off without permanently changing the configuration.

To clean up the /var/log directory when it’s full, you can follow these steps using SSH or the Mividas Installer console:

Check and Identify Large Files

Identify the largest folders in /var/log:

sudo du -xh /var/log | sort -h | tail -n40

List files by size within the /var/log and /var/log/docker/ directories to locate the largest log files:

ls -shSr /var/log/
ls -shSr /var/log/docker/

Delete Unnecessary Log Files

Delete specific old log files one at a time:

sudo rm /var/log/<file_name>

Bulk delete compressed log files:

sudo rm -f /var/log/*.log.[1-4].gz

Run Hard Drive Cleanup from the Mividas Installer Console

Access Hard drive cleanup options in the Mividas Installer console:

• Debug logs/raw call data: Remove old debug logs and raw call data.
• Old versions: Remove old versions of components or software.

Clean Up Docker Resources

Remove unused Docker images if they’re no longer needed:

sudo docker image prune -f

Remove all unused Docker resources (images, containers, networks):

sudo docker system prune -f

Clean up any Docker resources that are not currently in use:

sudo docker system prune -af

By following these steps, you can manage storage in /var/log effectively without compromising system stability.

To create a certificate bundle for your Mividas setup, follow these steps to ensure the correct sequence and format:

1. Open a Plain Text Editor: Use a simple text editor, such as Notepad or Gedit, to avoid adding hidden formatting.
2. Order the Certificates:
   • Nginx and similar servers require all certificates in a single file.
   • Start with the server certificate, followed by the intermediate certificate(s), and finally the root certificate.
3. Copy and Paste Certificates:
   • Begin by copying the entire text of the server certificate
     (including the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines)
     and paste it at the top of the document.
   • Next, add the intermediate certificate below the server certificate.
   • Finally, paste the root certificate at the end.
4. Save the Bundle: Save the file with an appropriate name (e.g., certificate_bundle.crt).
   Make sure it retains the .crt, .pem or .cer extension.
5. Verification: Before deploying, verify the concatenated order aligns with your server’s requirements. For example:
   • Nginx expects the server certificate at the beginning of the file, followed by intermediate and root certificates.

By following these steps, you create a valid certificate chain that Mividas and other servers can use to verify secure connections.

Certificate Bundle Example:

-----BEGIN CERTIFICATE----- 
MIIDdTCCAl2gAwIBAgILBAAAAAABFUtaw5QwDQYJKoZIhvcNAQEFBQAwVzELMAkG 
A1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExEDAOBgNVBAsTB1Jv 

...SERVER CERTIFICATE 

AbEVtQwdpf5pLGkkeB6zpxxxYu7KyJesF12KwvhHhm4qxFYxldBniYUr+WymXUad 
DKqC5JlR3XC321Y9YeRq4VzW9v493kHMB65jUr9TU/Qr6cf9tveCX4XSQRjbgbME 
HMUfpIBvFSDJ3gyICh3WZlXi/EjJKSZp4A== 
-----END CERTIFICATE----- 
-----BEGIN CERTIFICATE----- 
MIIEYDCCA0igAwIBAgILBAAAAAABL07hRQwwDQYJKoZIhvcNAQEFBQAwVzELMAkG 
A1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExEDAOBgNVBAsTB1Jv 

...INTERMEDIATE CERTIFICATE(S) 

pOBWYdw9P91nbHZF2krqrhqkYE/Ho9aqp9nNgSvBZnWygI/1h01fwlr1kMbawb30 
hag8IyrhFHvBN91i0ZJsumB9iOQct+R2UTjEqUdOqCsukNK1OFHrwZyKarXMsh3o 
wFZUTKiL8IkyhtyTMr5NGvo1dbU= 
-----END CERTIFICATE----- 
-----BEGIN CERTIFICATE----- 
MIIEYDCCA0igAwIBAgILBAAAAAABL07hRQwwDQYJKoZIhvcNAQEFBQAwVzELMAkG 
A1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExEDAOBgNVBAsTB1Jv 

...ROOT CERTIFICATE 

pOBWYdw9P91nbHZF2krqrhqkYE/Ho9aqp9nNgSvBZnWygI/1h01fwlr1kMbawb30 
hag8IyrhFHvBN91i0ZJsumB9iOQct+R2UTjEqUdOqCsukNK1OFHrwZyKarXMsh3o 
wFZUTKiL8IkyhtyTMr5NGvo1dbU= 
-----END CERTIFICATE-----

For external validation, use tools like SSL Labs or run openssl s_client -connect core.example.org:443 from the command line.

To extend the disk for Mividas, follow these steps:

1. Close the Mividas Installer – Stop any ongoing operations in the Mividas Installer.
2. Extend the Disk in VMware – Use the VMware interface to allocate additional storage space to the virtual machine where Mividas is installed.
3. Restart Mividas – Start the Mividas virtual machine after resizing the disk. The system will automatically detect and configure the new disk size, typically within 10-15 minutes.

These steps allow the Mividas environment to recognize and use the increased disk space without additional manual configurations.

The Mividas Installer sends the following data to license.mividas.com for licensing and version control purposes:

• IP Address – The IP address of the machine where Mividas Installer is running.
• Hostname – The hostname assigned to the Mividas Installer instance.
• Generated ID for the Docker Cluster – A unique identifier generated for the Docker cluster associated with this installation.
• Component Version Information – Information on the new and previous version numbers of each Mividas component being installed or upgraded.
• Installer/VM Version – Version details of the Mividas Installer and its associated VM.
• Signed EULA Identifier – Identifies if the End User License Agreement has been signed (currently not activated).
• Offline Installation Export Indicator – Specifies whether the request is for exporting an offline installation bundle.
• Installation/Download Status – For online installations, this indicates whether the installation or download operation was successful.

This data helps track licensing compliance, manage updates, and verify installation statuses.