This article helps you to understand what
happens during metadata server start up and how to resolve Metadata
Server 1 is not up issue.
Configuration files read by Metadata server during start up
The first step to diagnose Metadata server start up problem is to check any changes are made to config files.
Metadata server start-up pattern
1. Meta data server first read the omaconfig.xml file. This file gives direction to the repository manager.
2. Repository manager will have the list of metadata repository.
3. Finally metadata server connects to the registered metadata repository.
Check for changes in omaconfig.xml file
If any modification were made to omaconfig.xml file there are very good chances Metadata server won't start.
Check sas.servers script
To bring up SAS Metadata Server we will use sas.servers script. If any changes are made to this script then it won't bring up the server. Below is the script that we run in our environment.#*****
# Commands passed to the server control scripts
#*****
STARTCMD=start
STOPCMD=stop
RESTARTCMD=restart
STATUSCMD=status
#*****
# Specify certain commands explicitly
#*****
WHOAMI="/usr/ucb/whoami"
TAIL="/usr/xpg4/bin/tail -n " # syntax different from deprecated /usr/bin/tail
# the trailing space is important
Logmsg=logmsg
#*****
# The following variable sets the number of, and delay between attempts
# to start each SAS server. Each number is the sleep seconds to delay
# before the next try. You probably don't need to change these.
#*****
RETRY_SERIES="2 2 2 5 5 5 5 5 5 5 5"
METADATA_SERVER_UP="Activated listen on IPv"
OLAP_SERVER_UP="Activated listen on IPv"
OBJECT_SPAWNER_UP="SAS Object Spawner Daemon III has completed initialization."
CONNECT_SPAWNER_UP="SAS Job Spawner for Open Systems"
TABLE_SERVER_UP="Activated listen on IPv"
REMOTE_SERVICES_UP="Services are deployed and running."
DEPTEST_SERVER_UP="Deployment Tester Server ready"
ANALYTICS_PLATFORM_UP="Analytics Platform - started"
is_server_up()
{
MATCH=
for st in $RETRY_SERIES
do
sleep $st
if [ -f $SERVER_PID_FILE ];
then
{
MATCH=yes
break;
}
fi
done
if [ -z "$MATCH" ];
then
{
return 0; # never found a PID file, so server isn't running
}
fi
SERVER_PID=`cat $SERVER_PID_FILE`
if [ "$SCONTEXT" != "NULL" ];
then
CHKLOG="`echo $SLOGNAME $SCRIPT_TIME $SERVER_PID $SCONTEXT | awk '{ printf "%s_%s_%s-%s-%s_%s.log", $4, $1, substr($2,
1,4),substr($2,5,2),substr($2,7,2), $3 }'`"
else
CHKLOG="`echo $SLOGNAME $SCRIPT_TIME $SERVER_PID | awk '{ printf "%s_%s-%s-%s_%s.log", $1, substr($2,1,4),substr($2,5,
2),substr($2,7,2), $3 }'`"
fi
This is not the whole script. It's just part of it.
Image Source: support.sas.com
Comments
Post a Comment