Upgrade/migration troubleshooting

Checks system machine appliance specs: cores, memory.

Make sure the machine meets the system requirements. See Upgrade/migration prerequisites.

For details, see Checking cores and memory on [machine IP] in the log.

Checks disk space on system machine.
See Disk space requirements .

Run auto-remove to free up disk or delete old run files.

To run auto-remove, in AFA Administration, go to the Options tab, Storage sub-tab, and click Clean-up now.

If the issue persists after running Clean-up now, contact AlgoSec support.

Checks source node disk speed.

We recommend disk write speed of at least 300MB/s. Minimum allowable is 80MB/s.

Contact your IT department to determine and adjust, if necessary, your node disk speed.

dd if=/dev/zero of=/data/test-big-file.bin bs=786432000 count=1 oflag=dsync 2>&1 ; rm -f /data/test-big-file.bin

786432000 bytes (786 MB) copied, 0.624098 s, 1.3 GB/s

Compares Time between system machine and distribution nodes (Remote Agent and LDUs).

The machines can be in different time zones but they have to be at the same time relative to UTC:

1. Compare time and date between CM and the distribution node by running this command on every node mentioned in the message :

   date +%s

   Acceptable results should be up to 180 difference (3 minutes). If a machine exceeds this limit:

   1. Configure NTP server. Use algosec_conf option 2 on the machine to be updated.

   2. Run this command as root user to force time sync:

      ntpdate -u $(awk '$1 =="server"  {print $2}' /etc/ntp.conf)

   3. Reboot the machine.

   4. To verify, rerun on the updated node:

      date +%s

Checks NAS status on Central Manager and LDUs.

Open algosec_conf menu on the node with the NAS issue. Run option option 11 - Configure NAS. Run option 3 - Re-enable NAS mount.

If issue persists on an LDU, in the algosec_conf menu, run option 15 - Distributed Architecture configuration.

If problem persists, contact AlgoSec support.

Open algosec_conf menu on the node with the NAS issue. Run option option 11 - Configure NAS. Run option 3 - Re-enable NAS mount.

If issue persists on an LDU, in the algosec_conf menu, run option 15 - Distributed Architecture configuration.

If problem persists, contact AlgoSec support.

Checks status of services.

First, try to restart the services. Run for each service:

for example, algosec_test_service -n postgresql -f

If services do not restart, contact AlgoSec support.

To fix the inconsistency, see procedure in the knowledge base article: www.algosec.com/r/a32.00/42845777.

• To enable FireFlow: Set the value of the FireFlow_configured parameter to 'yes' in /home/afa/.fa/config. Make sure that FireFlow and AFA run file build numbers match.

• To disable FireFlow: Delete the FireFlow installation .run file in the /root/AlgoSec_Upgrade directory,

Verifies that all installed products are in the same version + build on both source and migration target.

Update the source A32.00 build files that match build versions installed on the migration target.

For details, see raw version data and valuesfor comparison in the log.

Checks status of services on migration target.

First, try to restart the services. Run for each service:

for example, algosec_test_service -n postgresql -f

If services do not restart, contact AlgoSec support.

Checks if all remote nodes are reachable from migration target.

Open ports. See Required port connections.

For details, see Failed to check connectivity between migration IP {​​}​​ and dist node {​​} in the log.​​

Verifies that migration target machine is standalone.

The target machine must be a clean machine deployed directly from AlgoSec image installation.

Verifies license on migration target IP.

Install license on target machine. See Migration target license and ASMS licensing

Contact AlgoSec to add missing components to the target license. Insufficient license may cause problems.

For details, Localhost license modules: and Migration [migration IP] license modules: see in the log.

Verifies that traffic on ports 443 (https), 5432 (postgresql), and 9595 (HA/DR) is not filtered between source & migration target.

Check with your IT department that firewalls allow SSH traffic on these ports (bi-directional).

nmap -n -p <port> <ip target> 2>&1| grep -q filtered && echo "Traffic is blocked" || echo "Traffic is allowed"

nmap -n -p <port> <ip source> 2>&1| grep -q filtered && echo "Traffic is blocked" || echo "Traffic is allowed"

Checks for NATed traffic is between source and target.

Contact your IT department to disable any NAT configuration between source and target machines.

We recommend bandwidth of at least 1Gbit/s (125MB/s). Minimum allowable is 64Mbit/s (8MB/s).

Contact your IT department to determine and adjust, if necessary, your bandwidth between the source and the target machines.

Reassign owner of all files in the /var/lib/pgsql/data/ directory to user postgres. Run the following code:

algosec_test_service -n postgresql -k

chown -R postgres:postgres /var/lib/pgsql/data/

algosec_test_service -n postgresql -s

Check with your IT department that traffic is allowed from the target machine to the defined mail server in ASMS.

echo 'exit' | timeout --signal=9 5 telnet <IP> <PORT> 2>&1 | grep -q 'Connected' && echo "Traffic to mail server is allowed" || echo "Traffic to mail server is blocked"

Target node must have at least the same disk space as the source node.

Increase disk space as required.

For VMs, see Increase disk space of a new AlgoSec VM.

Checks target node disk speed.

We recommend disk write speed of at least 300MB/s. Minimum allowable is 80MB/s.

Contact your IT department to determine and adjust, if necessary, your node disk speed.

dd if=/dev/zero of=/data/test-big-file.bin bs=786432000 count=1 oflag=dsync 2>&1 ; rm -f /data/test-big-file.bin

786432000 bytes (786 MB) copied, 0.624098 s, 1.3 GB/s

Ask your IT department to analyze event logs of firewall(s) to determine which encountered an SSH Brute Force Attack.

Disable SSH rate limit on these firewall(s) during the migration procedure.

Restart postgresql service on source and try syncing reports again.

systemctl restart postgresql.service