@Rak  You have a couple of errors in your sqoop syntax but you are almost there, please have a look at the below hints and retry after understanding and correcting them. 1. Sqoop import--connect This is wrong you need a space between the import and -- ie sqoop import --connect 2. 'jdbc:sqlserver'--username is also not correct you need a port number and databases name ie "jdbc:sqlserver://<Server_Host>:<Server_Port>;databaseName" 3. The quotes around the '2019-11-08'" is wrong too 3. All you -- should have a space before   sqoop import--connect 'jdbc:sqlserver'--username 'sa' -P--query "select * from dlyprice where $CONDITIONS AND `date`= '2019-11-08'"--split-by `date--target-dir /home/hduser2 -m 2   Try something like this ! sqoop import --connect --connect "jdbc:sqlserver://<Server_Host>:<Server_Port>;DB_Name>" \ --driver com.microsoft.sqlserver.jdbc.SQLServerDriver \ --username XXXX -P --query "select * from dlyprice  where $CONDITIONS AND `date`= '2019-11-08' \ --split-by `date`  --target-dir /home/hduser2 -m 2   The above isn't tested by I wanted to highlight some of your mistakes by making it work makes you a better hadooper !    Here is a link to Sqoop User Guide   Can you try out this syntax remember to replace the values with that  of your environment   sqoop import --connect "jdbc:sqlserver://hostname;username='sa';password='sa_password';database=yourDB" --driver com.microsoft.sqlserver.jdbc.SQLServerDriver --query "select * from dlyprice where \$CONDITIONS" --split-by date -m 2 --target-dir /home/hduser2   Please revert      ... View more

Hi,   Did you checked what process is running on this port and tried killing the process if required?  if the issue got solved?   Thanks AKR ... View more

@hassaniraj  Looks like the error reported in this thread could be due to the same reason mentioned on another thread of yours: https://community.cloudera.com/t5/Support-Questions/Hortonworks-sandbox-2-5-yum-update-not-working/m-p/278491 . It will be great to follow the same instructions mentioned on that thread to see if that fixes this issue. Specially  if you see some "dev2.hortonworks.com.s3.amazonaws.com" repos base URLs inside your "/etc/yum.repos.d" repos then please refer to the other thread and try to disable them and try again. You should set the "enabled=0" (this will disable the sandbox.repo) which has issue. As that is just development repo and might not be available always. https://community.cloudera.com/t5/Support-Questions/yum-install-error-please-help-me-out/m-p/203121 After removing the problematic repos try to perform a clean at yum level and then try again: # yum clean all # yum install python-pip . ... View more

Thanks.. Jsen.  ... View more

@hassaniraj  1. Please try restarting the VM once. 2. Inside the sandbox do SSH login and then try to see if you are able to make the following curl call .. this is just to verify the repo accessibility. If the following URL does not work then please share the HTTP Header section output of the following curl commands here so that we can verify if there are some special headers like Network proxy ..etc. # curl -iLvk <a href="http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6/repodata/repomd.xml" target="_blank">http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6/repodata/repomd.xml</a> AND   # curl -iLvk <a href="http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6/repodata/7fcacadb44b1a860fb704795c187f549103e855a0a93ed31293a0b270a9022b4-primary.sqlite.bz2" target="_blank">http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6/repodata/7fcacadb44b1a860fb704795c187f549103e855a0a93ed31293a0b270a9022b4-primary.sqlite.bz2</a>   3. If above works fine then we will have to look from the YUM side. Please try to perform the yum cache cleanup and then retry:   # yum clean all # yum update   4. It will be also good to verify if the "/etc/yum.repos.d/" directory has any problematic repo. Can you please list them?   # ls -lart /etc/yum.repos.d/   For temporarily you can move some of the repo files from "/etc/yum.repos.d/" file to outside and then retry... this will help in isolating if there are any corrupted repo issue. 5. Recently have you made any changes to the "/etc/yum.conf" file like enabling/disabling any proxy setting ..? # cat /etc/yum.conf   Also if you see some "dev2.hortonworks.com.s3.amazonaws.com" repos URLs inside your "/etc/yum.repos.d" repos then please refer to the other thread and try to disable them and try again: https://community.cloudera.com/t5/Support-Questions/yum-install-error-please-help-me-out/m-p/203121 Example:   # cat /etc/yum.repos.d/sandbox.repo [sandbox] baseurl=<a href="http://dev2.hortonworks.com.s3.amazonaws.com/repo/dev/master/utils/" target="_blank">http://dev2.hortonworks.com.s3.amazonaws.com/repo/dev/master/utils/</a> name=Sandbox repository (tutorials) gpgcheck=0 enabled=0       . . If your question is answered then, Please make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

I also faced the same issue.Found the issue was with mysql-connector-java.jar. I followed the below steps  1. Check whether you are able to connect remotely to mysql database. 2.If you are able to connect , then , its mysql-connector-java.jar in ambari 3. Download the correct version of mysql jar from https://dev.mysql.com/downloads/connector/j/ 4. Stop ambari server . 5.Remove the mysql connector jar from ambari 6. Set up again using ambari-server setup --jdbc-db=mysql --jdbc-driver=/usr/share/java/ mysql-connector-java-8.0.16 ... View more