“there were SEVERE errors for some components during installation” message printed after Strategy 2021 Update 5.2 finished installed in Linux machine.
Setup is performing the specified operation.
[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||]100%
Finished
Press ENTER to Continue
Strategy Install Wizard complete
Setup has finished installing Strategy on your computer.
However, there were SEVERE errors for some components during installation. Check the log file
/var/log/MicroStrategy/install.log for full details. Contact Strategy Support for any questions
or concerns.
The intall.log shows ‘Unable to start Redis in time’ as below:
16 May 2022, 02:50:55 AM:INFO: Registered service: EMService
16 May 2022, 02:52:17 AM:SEVERE: Failed to start Strategy Platform Analytics In-Memory Cache.Starting Redis...
Unable to start Redis in time.
16 May 2022, 02:52:25 AM:INFO: Started Strategy Platform Analytics Consumer.
Redis could not be started due to Failed listening on port 6379 (TCP).
[root@xxxxxx bin]# cd /opt/MicroStrategy/Redis/
[root@xxxxxx Redis]# ./redis.sh status
Redis is stopped.
[root@xxxxxx Redis]# ./redis.sh start
Starting Redis...
Unable to start Redis in time.
Refer to Knowledge Base Article below to check and start Redis.
Troubleshooting: How to Check Platform Analytics Services
Below entries could be in redis.log:
124125:C 16 May 2022 03:16:44.528 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
124125:C 16 May 2022 03:16:44.528 # Redis version=6.2.6, bits=64, commit=2404a974, modified=0, pid=124125, just started
124125:C 16 May 2022 03:16:44.528 # Configuration loaded
124125:M 16 May 2022 03:16:44.529 * monotonic clock: POSIX clock_gettime
124125:M 16 May 2022 03:16:44.530 # Warning: Could not create server TCP listening socket 127.0.0.1:6379: bind: Address already in use
124125:M 16 May 2022 03:16:44.530 # Failed listening on port 6379 (TCP), aborting.
With ‘
ps aux | grep 6379’ command it turned out port 6379 is taken by an abnormal redis process as shown below:
NOTE: The abnormal redis process doesn’t listen to local machine and has Sl status while a good one has Ss status.
Kill the incorrect process by its PID and restart Redis.
[root@xxxxxx Redis]# kill -9 72377
[root@xxxxxx Redis]# ps aux | grep 6379
root 129889 0.0 0.0 112708 976 pts/3 S+ 03:31 0:00 grep --color=auto 6379
[root@xxxxxx Redis]# ./redis.sh start
Starting Redis...
Redis is started.
Now Redis shows properly listening socket 127.0.0.1:6379 as shown below:
Redis.log shows ready to accept connections.
129945:M 16 May 2022 03:31:51.945 # Server initialized
129945:M 16 May 2022 03:31:51.945 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysc
tl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
129945:M 16 May 2022 03:31:51.945 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this is
sue run the command 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be resta
rted after THP is disabled (set to 'madvise' or 'never').
129945:M 16 May 2022 03:31:51.946 * Ready to accept connections
Restart Platform Analytics Consumer
[root@xxxxxx Strategy]# /opt/MicroStrategy/PlatformAnalytics/bin/platform-analytics-consumer.sh start
Done! Please check log file: /opt/MicroStrategy/PlatformAnalytics/log/platform-analytics-consumer_2022-05-16.log for details.
[root@xxxxxx Strategy]# /opt/MicroStrategy/PlatformAnalytics/bin/platform-analytics-consumer.sh status
Platform Analytics Consumer is running with PID = 13793
