Hi, Liz:
If you open SAS Studio from the browser, after you run the .BAT file, you should automatically be connected to the correct server. However, if you use Enterprise Guide, you have to be sure you're logged onto the correct profile. Otherwise you're connecting to a local server instead of the remote server.
Let me explain. When you are using the Hadoop classes and you need to run code, you need to make a connection to the server. That's why the instructions for class tell you to start SAS Studio from the browser inside the Virtual Lab, and not the Start Menu. There is a particular userID and password that you specify to the browser logon for SAS Studio or for an Enterprise Guide logon that establishes the connection to the right server for your work.
So, if you want to use SAS Studio for code in the Hadoop classes, then access SAS Studio from inside a browser window (not from the Start menu of the Virtual Machine). And, when you log onto SAS Studio, you need to use student as the userID and Metadata0 as the password, so you are connected with the right profile. (If you use the sasdemo userID and the Student1 password, you’ll be logged onto the wrong server.) The instructions in the demo or exercise should list which credentials you need to use.
Or, if you were using Enterprise Guide, you may need to log onto your Profile to connect to the server using the above credentials (student as the userID and Metadata0 as the password). One of the messages you reported is typical of the type of message you might get from Enterprise Guide if you did NOT sign on with a profile to connect to the SASApp server before you submitted your code. There are 2 ways to submit the code for class:
1) Using SAS Studio by starting it from the browser toolbar inside the Virtual Lab. SAS Studio in the browser is automatically set up to connect to the correct server
or
2) Using SAS Enterprise Guide in server mode, not in "local" mode. To make sure you are logged onto an EG and connecting to a server server you will need to exit EG without saving a project if you are already logged on and then try again.
Reopen EG, open the connection profile to connect to SASApp. You should be prompted to login to the server when you first logon to EG. The username is: student with a password of Metadata0. If you accidentally cancel the logon window, you can always logon by manually opening the profile window. In the lower right hand corner of Enterprise Guide, you will see a "No profile selected" message at first if you are NOT logged on. The message should appear at the very bottom of your EG screen on the right side.
You click this link to connect to the SASApp server with the credentials I provided.
The recommendation from the instructors was to have you start from a fresh image (not a saved image) and before you do anything else, check Cloudera Manager to be sure the servers are up. If you save your image so you can come back to it, we expect that the servers will start up as soon as the image starts up, but there could be lag time and so, the first thing to do if your connection to the Hadoop cluster seems broken is to check the servers.
The consensus among the instructors who teach the class is that they see messages like this for 3 reasons:
1) did not start SAS Studio from a browser
2) did not log onto the right Profile in EG
3) the connection was refused because of an issue with the services not being started on the image or they were started, but then something caused them to go down.
I know that you are working in Module 2 of the Big Data package, but I'm not sure what class you're working on in Module 2. When you are setting up the data in the Introduction to SAS and Hadoop class, you first must run the cre8data.bat file and THEN run the cre8data.sas file. You need to use Windows Explorer, as instructed to run the .bat file. It does sound like you've already done this, so I am guessing that EG was not logged onto the correct Profile. So I would recommend doing that first before you restart the servers.
However, if you experience a lot of file creation errors, then the Troubleshooting document in Chapter 1 of the Introduction to SAS and Hadoop course is what you need to reference. The other document is specifically regarding how to restart the servers.
One thing you might do, when you first log onto the classroom image, since you have been experiencing problems is to try the setup steps again from a fresh image. Normally, we would expect the Hadoop servers to start quickly when your image is first ready. However, if you are experiencing any slowness or lag time, It would be a good idea to start a browser inside the image and click on the link for Cloudera Manager. Any browser in the Virtual Lab should have a Cloudera Manager link.
Some browsers may remember the user ID and password, when we tried Firefox, the userID and password were remembered, when we used IE, you needed to supply the user ID and password. The login for Cloudera Manager is admin for the user ID and Student1 for the password.
Once in Cloudera Manager, it is useful to just check that all the servers are started (green) on the left side of the screen, under the Cluster 1 header. It is OK for the Sqoop 1 Client icon to be gray. That is unused.
However, the other servers should be green. If you see that any of the other servers under Cluster 1 are gray, then you need to follow the instructions in the troubleshooting document https://support.sas.com/training/academy/hadoop.pdf to restart the servers. It can take up to an hour to start the servers, so you will need to be sure you have a long enough reservation to allow the servers to restart and then do your work.
According to the instructors, it is also possible that ending your reservation and starting over from a FRESH image will result in the servers starting as they should. When instructors encounter server issues in the classroom version of the class using the Virtual Lab, they are more likely to end the session and start over from a fresh session when working in the Virtual Lab -- it can take an hour for the servers to start in a session, but it only takes 35-45 minutes to start a reservation for a FRESH image. And with the new reservation, none of the startup time comes out of your allotment of hours.
Sorry for such a long posting, but I wanted to cover all the possibilities.
Cynthia
