Hi Darren,
i'm following PATH B for alternative instead of using CM bin file to get CM
WEB UI
when i restarting CM DB it is giving that
*postgres -D /var/lib/cloudera-scm-server-db/data or*
* *
* pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start*
*
*
*Check below for reference:*
$sudo service cloudera-scm-server-db start
The files belonging to this database system will be owned by user
"cloudera-scm".
This user must also own the server process.
The database cluster will be initialized with locale en_US.UTF8.
The default text search configuration will be set to "english".
fixing permissions on existing directory
/var/lib/cloudera-scm-server-db/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 32MB
creating configuration files ... ok
creating template1 database in /var/lib/cloudera-scm-server-db/data/base/1
... ok
initializing pg_authid ... ok
setting password ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok
Success. You can now start the database server using:
postgres -D /var/lib/cloudera-scm-server-db/data
or
pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start
*$sudo pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start*
*
*
*pg_ctl: cannot be run as root*
*Please log in (using, e.g., "su") as the (unprivileged) user that will*
*own the server process.*
*
*
where do i need to run this command?
Thanks,
Dilip
On Wed, Oct 23, 2013 at 1:43 PM, Dilip Varma wrote:Hi Darren,
It is working fine with these 4 options(--i-agree-to-all-licenses,
--noprompt,--noreadme,--nooptions).
can i know what it is doing exactly?
and i want that bin file should run using my own repo file
for ex:
cat /etc/yum.repos.d/cloudera.manager.repo
[cloudera-manager]
name=Cloudera Manager
baseurl=http://<MY NODE PUBLIC DNS>/cm4/redhat/6/x86_64/cm/4/
gpgkey =
http://MY NODE PUBLIC
DNS/cm4/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera
gpgcheck=1
without this bin file is there any way to get CM WEB UI,i have seen that
PATH B will solve this..
i've followed PATH B but no use,while navigating to browser
http://<public dns>:7180
it is throwing CONNECTION TIMED ERROR.
how to oversome this issue using PATH B and what CM.BIN file is doing
while running?
Thanks & Regards,
Dilip
Thanks,
Dilip
On Wed, Oct 23, 2013 at 12:20 AM, Darren Lo wrote:Hi Dilip,
Sorry for misunderstanding. Did you run it as root? Was there a more
descriptive error message?
Thanks,
Darren
On Tue, Oct 22, 2013 at 8:08 AM, Dilip Varma wrote:Hi Darren,
Thanks for your quick response and inputs.
We want run *cloudera*-*manager*-*installer*.*bin* in non TUI mode. We
tried with below options but its not working.
--i-agree-to-all-licenses
--noprompt
--noreadme
--nooptions
We are getting "Fatal Error" installation failed message with above
options. Any pointers in this regards will help us in getting out of this
issue.
Thanks in advance.
Regards,
Dilip.
Thanks,
Dilip
On Fri, Oct 18, 2013 at 8:24 PM, Darren Lo wrote:Hi Dilip,
You can use the Cloudera Manager REST API to automate your setup
process once you have CM installed.
The most relevant API documentation is in Cloudera Manager, if you poke
around the menus in the upper right corner. You can also find API docs
online here:
http://cloudera.github.io/cm_api/. As you read through
them, you'll find an API endpoint "/cm/license" that will take care of the
license for you.
Note that when using the API to set up your cluster, you are
responsible for knowing which commands need to be run, such as formatting
the namenode, starting hdfs, creating /tmp, etc. Also the current API
doesn't help you install CM agents on your hosts, but that will be added in
an upcoming release.
Here's some useful links to help get you started:
CM Architecture blog
http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/API Examples and Tutorials
http://blog.cloudera.com/blog/2013/05/how-to-automate-your-hadoop-cluster-from-java/http://blog.cloudera.com/blog/2012/09/automating-your-cluster-with-cloudera-manager-api/Thanks,
Darren
On Fri, Oct 18, 2013 at 3:00 AM, Dilip Varma wrote:Hi Team,
How to run the cloudera binary file using shell or perl script.i mean
while it is running prompts to accept the license key and next etc..how to
select these prompts using scripts without entering manually..
On Sunday, June 9, 2013 1:19:15 PM UTC+5:30, Lenin Raj Rajasekaran
wrote:
Thanks Wong.
I will rebuild my system using 64 bit kernel and Ubuntu 12.04 LTS and
start from scratch.
Thanks,
Lenin
On Sunday, June 9, 2013 12:57:14 PM UTC+5:30, bc Wong wrote:On Sat, Jun 8, 2013 at 11:51 PM, Lenin Raj Rajasekaran
wrote:
Hi Wong,
Thanks for finding that out.
Earlier my server was a 32 bit system. Recently, I changed it to 64 bit
kernel (to install CDH) by changing the kernel via Linode Manager and
rebooting the server. After reboot, uname -a showed 64 bit system. So I
thought everything went fine. But looking at this libc6 problem, I think
there might be other related issues as well.
<snip>
Hi Lenin,
I'd highly recommend that you start from scratch, with a 64 bit
system. Who knows what other gotchas you'll find.
Cheers,
bc
To unsubscribe from this group and stop receiving emails from it,
send an email to scm-users+unsubscribe@cloudera.org.
--
Thanks,
Darren
To unsubscribe from this group and stop receiving emails from it, send
an email to scm-users+unsubscribe@cloudera.org.
--
Thanks,
Darren
To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.