EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB42865: When configuring Intelligence server on Linux, process starts but remain in waiting state, not ending normally.


Community Admin

• Strategy


After installing correctly base software and Microstrategy Intelligence Server on Linux (Red Hat 6.x),  Configuration wizard hangs either creating new Metadata or Upgrading earlier version of Metadata. This behaviour is for both GUI or Character based interface.  No Error is displayed in the screen or console.

 SYMPTOM:
After installing correctly base software and Strategy Intelligence Server on Linux (Red Hat 6.x),  Configuration wizard hangs either creating new Metadata or Upgrading earlier version of Metadata. This behaviour is for both GUI or Character based interface.  No Error is displayed in the screen or console . DSSError log shows following error:
 
Sample Code/Error
Error type: Database thread hung. Synchronous Calls Timeout expired.
2013-02-25 11:07:27.980+01:00 Failed to read from pipe.
System Error (0): --- Success
2013-02-25 11:07:28.025+01:00 Quiting child process because of error: Failed to read from pipe.
 
This error is shown when the Metadata database is located in a non-local server.
 
Kernel parameters have been verified as described in KB30320
Shell version  (ksh)  has been verified as described in KB41955
 
 
CAUSE:
TCP/IP Network configuration is preventing free two communication between I-server and Metadata DB server.
Symptoms are shown either network subnet is not the same for MD and I-Server,  Default gateway is wrong network, or there is a screening router (firewall) with some policy preventing feedback of some data.
 
ACTION:
Request Network Administrator to verify that all server are is the same network segment and/or communicating freely in bi-directional way. In case no NetAdmin is available and it is needed to rule out Strategy componenents, the following troubleshooting can be followed:
Incorrect Subnet Mask: If a network uses a subnet mask other than the default mask for its address class, and a client is still configured with the default subnet mask for the address class, communication will fail to some nearby networks but not to distant ones. As an example, if you create four subnets (such as in the subnetting example) but use the incorrect subnet mask of 255.255.255.0 in your TCP/IP configuration, hosts will not be able to determine that some computers are on different subnets than their own. When this happens, packets destined for hosts on different physical networks that are part of the same Class C address will not be sent to a default gateway for delivery. A common symptom of this is when a computer can communicate with hosts that are on its local network and can talk to all remote networks except those that are nearby and have the same class A, B, or C address. To fix this problem, just enter the correct subnet mask in the TCP/IP configuration for that host.
Incorrect IP Address: If you put computers with IP addresses that should be on separate subnets on a local network with each other, they will not be able to communicate. They will try to send packets to each other through a router that will not be able to forward them correctly. A symptom of this problem is a computer that can talk to hosts on remote networks, but cannot communicate with some or all computers on their local network. To correct this problem, make sure all computers on the same physical network have IP addresses on the same IP subnet. If you run out of IP addresses on a single network segment, there are solutions that go beyond the scope of this article.
Incorrect Default Gateway: A computer configured with an incorrect default gateway will be able to communicate with hosts on its own network segment, but will fail to communicate with hosts on some or all remote networks. If a single physical network has more than one router, and the wrong router is configured as a default gateway, a host will be able to communicate with some remote networks, but not others. This problem is common if an organization has a router to an internal TCP/IP network and another router connected to the Internet.
 
Workaround
-  Change the IP address / subnet  on I-Server to allow to communicate via ODBC on same network segment.
-  Install the Intelligence Server on same machine as Metadata Database Server.
 
Third Party Product Disclaimer
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
 


Comment

0 comments

Details

Knowledge Article

Published:

May 15, 2017

Last Updated:

May 15, 2017