BookmarkSubscribeRSS Feed
Lapis Lazuli | Level 10 woo
Lapis Lazuli | Level 10

Hello All, 

We have SAS 9.4 M7 installed on Linux 8.4. This is all-in-one machine. Installation and configuration completed successfully. however, when i try starting sas services its showing below message. 


./sas.servers start

starting sas servers 

starting sas web infrastructure data server 

SAS Metadata Server 1 is NOT up

the remaining SAS servers will not be started as a result


However, when i do status it shows both SAS WIP data server and metadata server are up. one thing i am not sure is why its starting sas WIP data server prior to metadata server 


Also, if i starts all services (metadata, wip data server, obj. spawner, dip runner, JMS broker. cache locator, web server, web app server, evm....) individually, everything starts fine...

Running start calls first, which starts the WIP Data Server. This is normal behavior.

When it reaches the point to start the Metadata Server it first checks for a PID file ( and if found checks to see if that process exists. If not, it runs the start command (i.e. start) and checks for the PID file again. If it confirms the process exists it will go on to check that the log file has indicated the Metadata Server has started successfully. In this case it seems that process is not successful. Does the <SASConfig>/Lev1/SASMeta/MetadataServer/ file exist, and is it owned by the SAS installation account user?
Greg Wootton | Principal Systems Technical Support Engineer
Lapis Lazuli | Level 10 woo
Lapis Lazuli | Level 10
yes, "" does exist with permission "-rw-rw-r--." and own by "sas" id
I agree with @Anand_V bash debugging might be helpful here to see what's happening. There are also several echo commands commented out that could be uncommented to provide more detail. Be sure to take a backup copy of the file before making any changes. For example:

cp sas.servers sas.servers.bak
sed -i 's/^#echo/echo/g' sas.servers
Greg Wootton | Principal Systems Technical Support Engineer
Meteorite | Level 14
I think you should check the metadata server log.
Ammonite | Level 13

May be you can try running in in debug mode? Enable set -x or run using bash -x start which will print out all the executed commands on the terminal giving more data on what's happening in background.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 5 replies
  • 4 in conversation