cloudera manager installation fails

cloudera manager installation fails

	J
	Mar 11, 2013 at 8:42 am

Hi, guys.

I have a problem when installing cloudera manager. Log file looks like
below;

# cat /var/log/cloudera-manager-installer/5.start-embedded-db.log
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.

fixing permissions on existing directory
/var/lib/cloudera-scm-server-db/data ... ok
creating directory /var/lib/cloudera-scm-server-db/data/global ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_xlog ... ok
creating directory
/var/lib/cloudera-scm-server-db/data/pg_xlog/archive_status ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_clog ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_subtrans ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_twophase ... ok
creating directory
/var/lib/cloudera-scm-server-db/data/pg_multixact/members ... ok
creating directory
/var/lib/cloudera-scm-server-db/data/pg_multixact/offsets ... ok
creating directory /var/lib/cloudera-scm-server-db/data/base ... ok
creating directory /var/lib/cloudera-scm-server-db/data/base/1 ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_tblspc ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
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
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-db/data
or
pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start

Creating SCM configuration file: /etc/cloudera-scm-server/db.properties
waiting for postmaster to
start...............................................................could
not start postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both root
and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile
start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera manager.

Thanks.

Search Discussions

9 responses
Oldest
Nested

bc Wong

at Mar 11, 2013 at 8:46 am

⇧

Can you attach `/var/log/cloudera-scm-server/db.log'? (Btw, you're not
supposed to run pg_ctl yourself, since that's controlled by the
cloudera-scm-server-db initscript. But your original failure seems to be
something else anyway.)

Cheers,
bc

On Mon, Mar 11, 2013 at 1:41 AM, j wrote:

Hi, guys.

I have a problem when installing cloudera manager. Log file looks like
below;

# cat /var/log/cloudera-manager-installer/5.start-embedded-db.log
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.

fixing permissions on existing directory
/var/lib/cloudera-scm-server-db/data ... ok
creating directory /var/lib/cloudera-scm-server-db/data/global ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_xlog ... ok
creating directory
/var/lib/cloudera-scm-server-db/data/pg_xlog/archive_status ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_clog ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_subtrans ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_twophase ... ok
creating directory
/var/lib/cloudera-scm-server-db/data/pg_multixact/members ... ok
creating directory
/var/lib/cloudera-scm-server-db/data/pg_multixact/offsets ... ok
creating directory /var/lib/cloudera-scm-server-db/data/base ... ok
creating directory /var/lib/cloudera-scm-server-db/data/base/1 ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_tblspc ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
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
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-db/data
or
pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start

Creating SCM configuration file: /etc/cloudera-scm-server/db.properties
waiting for postmaster to
start...............................................................could
not start postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both root
and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile
start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera manager.

Thanks.

reply | permalink

at Mar 11, 2013 at 8:50 am

⇧

It's like below;

$ cat /var/log/cloudera-scm-server/db.log
postmaster: the number of buffers (-B) must be at least twice the number of
allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number of
allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number of
allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number of
allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number of
allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number of
allowed connections (-N) and at least 16

Thanks,
Jun

2013년 3월 11일 월요일 오후 5시 46분 34초 UTC+9, bc Wong 님의 말:

Hi, guys.

I have a problem when installing cloudera manager. Log file looks like
below;

# cat /var/log/cloudera-manager-installer/5.start-embedded-db.log
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.

fixing permissions on existing directory
/var/lib/cloudera-scm-server-db/data ... ok
creating directory /var/lib/cloudera-scm-server-db/data/global ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_xlog ... ok
creating directory
/var/lib/cloudera-scm-server-db/data/pg_xlog/archive_status ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_clog ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_subtrans ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_twophase ... ok
creating directory
/var/lib/cloudera-scm-server-db/data/pg_multixact/members ... ok
creating directory
/var/lib/cloudera-scm-server-db/data/pg_multixact/offsets ... ok
creating directory /var/lib/cloudera-scm-server-db/data/base ... ok
creating directory /var/lib/cloudera-scm-server-db/data/base/1 ... ok
creating directory /var/lib/cloudera-scm-server-db/data/pg_tblspc ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
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
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-db/data
or
pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile start

Creating SCM configuration file: /etc/cloudera-scm-server/db.properties
waiting for postmaster to
start...............................................................could
not start postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both root
and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-db/data -l logfile
start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera
manager.

Thanks.

reply | permalink

Vikas Singh Can you paste the output of 'cat /proc/sys/kernel/shmmax' on your host. Which distribution of Linux are you using? Vikas

Vikas Singh at Mar 11, 2013 at 5:10 pm ⇧

Can you paste the output of 'cat /proc/sys/kernel/shmmax' on your host.
Which distribution of Linux are you using?

Vikas

On Mon, Mar 11, 2013 at 1:50 AM, j wrote:

It's like below;

$ cat /var/log/cloudera-scm-server/db.log
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16

Thanks,
Jun

2013년 3월 11일 월요일 오후 5시 46분 34초 UTC+9, bc Wong 님의 말:
Can you attach `/var/log/cloudera-scm-server/**db.log'? (Btw, you're not
supposed to run pg_ctl yourself, since that's controlled by the
cloudera-scm-server-db initscript. But your original failure seems to be
something else anyway.)

Cheers,
bc

On Mon, Mar 11, 2013 at 1:41 AM, j wrote:

Hi, guys.

I have a problem when installing cloudera manager. Log file looks like
below;

# cat /var/log/cloudera-manager-**installer/5.start-embedded-db.**log
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.

fixing permissions on existing directory /var/lib/cloudera-scm-server-**db/data
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/global ... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_xlog ... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_xlog/archive_status
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_clog ... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_subtrans
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_twophase
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_multixact/members
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_multixact/offsets
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/base ... ok
creating directory /var/lib/cloudera-scm-server-**db/data/base/1 ... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_tblspc ...
ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
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
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-**db/data
or
pg_ctl -D /var/lib/cloudera-scm-server-**db/data -l logfile start

Creating SCM configuration file: /etc/cloudera-scm-server/db.**
properties
waiting for postmaster to start.........................**
..............................**........could not start postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both root
and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-**db/data -l logfile
start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera
manager.

Thanks.

reply | permalink

at Mar 11, 2013 at 10:50 pm

⇧

Vikas,

# cat /proc/sys/kernel/shmmax
33554432

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.8 (Tikanga)

Thanks,
Jun

2013년 3월 12일 화요일 오전 2시 10분 52초 UTC+9, Vikas Singh 님의 말:

Can you paste the output of 'cat /proc/sys/kernel/shmmax' on your host.
Which distribution of Linux are you using?

Vikas

On Mon, Mar 11, 2013 at 1:50 AM, j <hyunju...@gmail.com <javascript:>>wrote:

It's like below;

$ cat /var/log/cloudera-scm-server/db.log
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16

Thanks,
Jun

2013년 3월 11일 월요일 오후 5시 46분 34초 UTC+9, bc Wong 님의 말:

Can you attach `/var/log/cloudera-scm-server/**db.log'? (Btw, you're
not supposed to run pg_ctl yourself, since that's controlled by the
cloudera-scm-server-db initscript. But your original failure seems to be
something else anyway.)

Cheers,
bc

On Mon, Mar 11, 2013 at 1:41 AM, j wrote:

Hi, guys.

I have a problem when installing cloudera manager. Log file looks like
below;

# cat /var/log/cloudera-manager-**installer/5.start-embedded-db.**log
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.

fixing permissions on existing directory /var/lib/cloudera-scm-server-*
*db/data ... ok
creating directory /var/lib/cloudera-scm-server-**db/data/global ... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_xlog ...
ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_xlog/archive_status
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_clog ...
ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_subtrans
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_twophase
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_multixact/members
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_multixact/offsets
... ok
creating directory /var/lib/cloudera-scm-server-**db/data/base ... ok
creating directory /var/lib/cloudera-scm-server-**db/data/base/1 ... ok
creating directory /var/lib/cloudera-scm-server-**db/data/pg_tblspc
... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
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
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-**db/data
or
pg_ctl -D /var/lib/cloudera-scm-server-**db/data -l logfile start

Creating SCM configuration file: /etc/cloudera-scm-server/db.**
properties
waiting for postmaster to start.........................**
..............................**........could not start postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both
root and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-**db/data -l
logfile start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera
manager.

Thanks.

reply | permalink

Vikas Singh

at Mar 11, 2013 at 11:27 pm

⇧

Hi Jeong,

The value seems reasonable. When this happens, can you copy the content of
/var/lib/cloudera-scm-server-db/data/postgresql.conf. We are interested in
value of shared_buffers in the file. You may have to do this while postgres
is trying to restart (otherwise installer will rollback the installation
and the file will be gone)

Vikas

On Mon, Mar 11, 2013 at 3:50 PM, j wrote:

Vikas,

# cat /proc/sys/kernel/shmmax
33554432

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.8 (Tikanga)

Thanks,
Jun

2013년 3월 12일 화요일 오전 2시 10분 52초 UTC+9, Vikas Singh 님의 말:

Can you paste the output of 'cat /proc/sys/kernel/shmmax' on your host.
Which distribution of Linux are you using?

Vikas

On Mon, Mar 11, 2013 at 1:50 AM, j wrote:

It's like below;

$ cat /var/log/cloudera-scm-server/**db.log
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the number
of allowed connections (-N) and at least 16

Thanks,
Jun

2013년 3월 11일 월요일 오후 5시 46분 34초 UTC+9, bc Wong 님의 말:

Can you attach `/var/log/cloudera-scm-server/****db.log'? (Btw, you're
not supposed to run pg_ctl yourself, since that's controlled by the
cloudera-scm-server-db initscript. But your original failure seems to be
something else anyway.)

Cheers,
bc

On Mon, Mar 11, 2013 at 1:41 AM, j wrote:

Hi, guys.

I have a problem when installing cloudera manager. Log file looks like
below;

# cat /var/log/cloudera-manager-**inst**aller/5.start-embedded-db.**log

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.

fixing permissions on existing directory /var/lib/cloudera-scm-server-
**d**b/data ... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/global
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_xlog
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_xlog/archive_status
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_clog
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_subtrans
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_twophase
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_multixact/members
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_multixact/offsets
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/base ...
ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/base/1
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_tblspc
... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
creating configuration files ... ok
creating template1 database in /var/lib/cloudera-scm-server-**d**b/data/base/1
... ok
initializing pg_authid ... ok
setting password ... ok
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-**d**b/data
or
pg_ctl -D /var/lib/cloudera-scm-server-**d**b/data -l logfile
start

Creating SCM configuration file: /etc/cloudera-scm-server/db.**pr**
operties
waiting for postmaster to start.........................****
..............................****........could not start postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both
root and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-**d**b/data -l
logfile start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera
manager.

Thanks.

reply | permalink

at Mar 11, 2013 at 11:41 pm

⇧

redirect_stderr = on # Enable capturing of stderr into
log
log_directory = 'pg_log' # Directory where log files are
written
log_filename = 'postgresql-%a.log' # Log file name pattern.
log_truncate_on_rotation = on # If on, any existing log file of the same
log_rotation_age = 1440 # Automatic rotation of logfiles
will
log_rotation_size = 0 # Automatic rotation of logfiles
will
lc_messages = 'en_US.UTF8' # locale for system error
lc_monetary = 'en_US.UTF8' # locale for monetary
formatting
lc_numeric = 'en_US.UTF8' # locale for number
formatting
lc_time = 'en_US.UTF8' # locale for time formatting

I removed all the lines starting with '#'.

Thanks,
Jun

2013년 3월 12일 화요일 오전 8시 27분 29초 UTC+9, Vikas Singh 님의 말:

Hi Jeong,

The value seems reasonable. When this happens, can you copy the content of
/var/lib/cloudera-scm-server-db/data/postgresql.conf. We are interested
in value of shared_buffers in the file. You may have to do this while
postgres is trying to restart (otherwise installer will rollback the
installation and the file will be gone)

Vikas

On Mon, Mar 11, 2013 at 3:50 PM, j <hyunju...@gmail.com <javascript:>>wrote:

Can you paste the output of 'cat /proc/sys/kernel/shmmax' on your host.
Which distribution of Linux are you using?

Vikas

On Mon, Mar 11, 2013 at 1:50 AM, j wrote:

It's like below;

$ cat /var/log/cloudera-scm-server/**db.log
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16

Thanks,
Jun

2013년 3월 11일 월요일 오후 5시 46분 34초 UTC+9, bc Wong 님의 말:

Can you attach `/var/log/cloudera-scm-server/****db.log'? (Btw,
you're not supposed to run pg_ctl yourself, since that's controlled by the
cloudera-scm-server-db initscript. But your original failure seems to be
something else anyway.)

Cheers,
bc

On Mon, Mar 11, 2013 at 1:41 AM, j wrote:

Hi, guys.

I have a problem when installing cloudera manager. Log file looks
like below;

# cat /var/log/cloudera-manager-**inst**aller/5.start-embedded-db.**log

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.

fixing permissions on existing directory /var/lib/cloudera-scm-server-
**d**b/data ... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/global
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_xlog
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_xlog/archive_status
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_clog
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_subtrans
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_twophase
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_multixact/members
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_multixact/offsets
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/base ...
ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/base/1
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_tblspc
... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
creating configuration files ... ok
creating template1 database in /var/lib/cloudera-scm-server-**d**b/data/base/1
... ok
initializing pg_authid ... ok
setting password ... ok
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-**d**b/data
or
pg_ctl -D /var/lib/cloudera-scm-server-**d**b/data -l logfile
start

Creating SCM configuration file: /etc/cloudera-scm-server/db.**pr**
operties
waiting for postmaster to start.........................****
..............................****........could not start postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both
root and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-**d**b/data -l
logfile start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera
manager.

Thanks.

reply | permalink

J There was no shared_buffers value set. 2013년 3월 12일 화요일 오전 8시 27분 29초 UTC+9, Vikas Singh 님의 말:

J at Mar 11, 2013 at 11:43 pm ⇧

There was no shared_buffers value set.

2013년 3월 12일 화요일 오전 8시 27분 29초 UTC+9, Vikas Singh 님의 말:
Hi Jeong,

The value seems reasonable. When this happens, can you copy the content of
/var/lib/cloudera-scm-server-db/data/postgresql.conf. We are interested
in value of shared_buffers in the file. You may have to do this while
postgres is trying to restart (otherwise installer will rollback the
installation and the file will be gone)

Vikas

On Mon, Mar 11, 2013 at 3:50 PM, j <hyunju...@gmail.com <javascript:>>wrote:
Vikas,

# cat /proc/sys/kernel/shmmax
33554432

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.8 (Tikanga)

Thanks,
Jun

2013년 3월 12일 화요일 오전 2시 10분 52초 UTC+9, Vikas Singh 님의 말:
Can you paste the output of 'cat /proc/sys/kernel/shmmax' on your host.
Which distribution of Linux are you using?

Vikas

On Mon, Mar 11, 2013 at 1:50 AM, j wrote:

It's like below;

$ cat /var/log/cloudera-scm-server/**db.log
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16

Thanks,
Jun

2013년 3월 11일 월요일 오후 5시 46분 34초 UTC+9, bc Wong 님의 말:
Can you attach `/var/log/cloudera-scm-server/****db.log'? (Btw,
you're not supposed to run pg_ctl yourself, since that's controlled by the
cloudera-scm-server-db initscript. But your original failure seems to be
something else anyway.)

Cheers,
bc

On Mon, Mar 11, 2013 at 1:41 AM, j wrote:

Hi, guys.

I have a problem when installing cloudera manager. Log file looks
like below;

# cat /var/log/cloudera-manager-**inst**aller/5.start-embedded-db.**log

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.

fixing permissions on existing directory /var/lib/cloudera-scm-server-
**d**b/data ... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/global
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_xlog
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_xlog/archive_status
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_clog
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_subtrans
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_twophase
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_multixact/members
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_multixact/offsets
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/base ...
ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/base/1
... ok
creating directory /var/lib/cloudera-scm-server-**d**b/data/pg_tblspc
... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
creating configuration files ... ok
creating template1 database in /var/lib/cloudera-scm-server-**d**b/data/base/1
... ok
initializing pg_authid ... ok
setting password ... ok
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-**d**b/data
or
pg_ctl -D /var/lib/cloudera-scm-server-**d**b/data -l logfile
start

Creating SCM configuration file: /etc/cloudera-scm-server/db.**pr**
operties
waiting for postmaster to start.........................****
..............................****........could not start postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both
root and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-**d**b/data -l
logfile start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera
manager.

Thanks.

reply | permalink
Vikas Singh Should have asked this before, which version of CM are you using? And what's the version of postgresql? Vikas

Vikas Singh at Mar 11, 2013 at 11:47 pm ⇧

Should have asked this before, which version of CM are you using? And
what's the version of postgresql?

Vikas

On Mon, Mar 11, 2013 at 4:43 PM, j wrote:

There was no shared_buffers value set.

2013년 3월 12일 화요일 오전 8시 27분 29초 UTC+9, Vikas Singh 님의 말:
Hi Jeong,

The value seems reasonable. When this happens, can you copy the content
of /var/lib/cloudera-scm-**server-db/data/postgresql.**conf. We are
interested in value of shared_buffers in the file. You may have to do this
while postgres is trying to restart (otherwise installer will rollback the
installation and the file will be gone)

Vikas

On Mon, Mar 11, 2013 at 3:50 PM, j wrote:

Vikas,

# cat /proc/sys/kernel/shmmax
33554432

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.8 (Tikanga)

Thanks,
Jun

2013년 3월 12일 화요일 오전 2시 10분 52초 UTC+9, Vikas Singh 님의 말:
Can you paste the output of 'cat /proc/sys/kernel/shmmax' on your host.
Which distribution of Linux are you using?

Vikas

On Mon, Mar 11, 2013 at 1:50 AM, j wrote:

It's like below;

$ cat /var/log/cloudera-scm-server/**d**b.log
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16

Thanks,
Jun

2013년 3월 11일 월요일 오후 5시 46분 34초 UTC+9, bc Wong 님의 말:
Can you attach `/var/log/cloudera-scm-server/******db.log'? (Btw,
you're not supposed to run pg_ctl yourself, since that's controlled by the
cloudera-scm-server-db initscript. But your original failure seems to be
something else anyway.)

Cheers,
bc

On Mon, Mar 11, 2013 at 1:41 AM, j wrote:

Hi, guys.

I have a problem when installing cloudera manager. Log file looks
like below;

# cat /var/log/cloudera-manager-**inst****aller/5.start-embedded-db.
**log
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.

fixing permissions on existing directory
/var/lib/cloudera-scm-server-**d****b/data ... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/global
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_xlog
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_xlog/archive_status
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_clog
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_subtrans
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_twophase
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_multixact/members
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_multixact/offsets
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/base
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/base/1
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_tblspc
... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
creating configuration files ... ok
creating template1 database in /var/lib/cloudera-scm-server-**d****b/data/base/1
... ok
initializing pg_authid ... ok
setting password ... ok
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-**d****b/data
or
pg_ctl -D /var/lib/cloudera-scm-server-**d****b/data -l logfile
start

Creating SCM configuration file: /etc/cloudera-scm-server/db.**pr***
*operties
waiting for postmaster to start.........................******
..............................******........could not start
postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both
root and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-**d****b/data -l
logfile start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera
manager.

Thanks.

reply | permalink

at Mar 11, 2013 at 11:49 pm

⇧

I downloaded 4.5 free edition and didn't install postgre by myself. Postgre
8.1.23-1.el5_7.3 was installed, so I've used this.

Thanks,
Jun

2013년 3월 12일 화요일 오전 8시 47분 11초 UTC+9, Vikas Singh 님의 말:

Should have asked this before, which version of CM are you using? And
what's the version of postgresql?

Vikas

On Mon, Mar 11, 2013 at 4:43 PM, j <hyunju...@gmail.com <javascript:>>wrote:

There was no shared_buffers value set.

2013년 3월 12일 화요일 오전 8시 27분 29초 UTC+9, Vikas Singh 님의 말:

Hi Jeong,

The value seems reasonable. When this happens, can you copy the content
of /var/lib/cloudera-scm-**server-db/data/postgresql.**conf. We are
interested in value of shared_buffers in the file. You may have to do this
while postgres is trying to restart (otherwise installer will rollback the
installation and the file will be gone)

Vikas

Can you paste the output of 'cat /proc/sys/kernel/shmmax' on your
host. Which distribution of Linux are you using?

Vikas

On Mon, Mar 11, 2013 at 1:50 AM, j wrote:

It's like below;

$ cat /var/log/cloudera-scm-server/**d**b.log
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16
postmaster: the number of buffers (-B) must be at least twice the
number of allowed connections (-N) and at least 16

Thanks,
Jun

2013년 3월 11일 월요일 오후 5시 46분 34초 UTC+9, bc Wong 님의 말:

Can you attach `/var/log/cloudera-scm-server/******db.log'? (Btw,
you're not supposed to run pg_ctl yourself, since that's controlled by the
cloudera-scm-server-db initscript. But your original failure seems to be
something else anyway.)

Cheers,
bc

On Mon, Mar 11, 2013 at 1:41 AM, j wrote:

Hi, guys.

I have a problem when installing cloudera manager. Log file looks
like below;

# cat /var/log/cloudera-manager-**inst****
aller/5.start-embedded-db.**log
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.

fixing permissions on existing directory
/var/lib/cloudera-scm-server-**d****b/data ... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/global
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_xlog
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_xlog/archive_status
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_clog
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_subtrans
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_twophase
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_multixact/members
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_multixact/offsets
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/base
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/base/1
... ok
creating directory /var/lib/cloudera-scm-server-**d****b/data/pg_tblspc
... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
creating configuration files ... ok
creating template1 database in /var/lib/cloudera-scm-server-**d****b/data/base/1
... ok
initializing pg_authid ... ok
setting password ... ok
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... 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:

postmaster -D /var/lib/cloudera-scm-server-**d****b/data
or
pg_ctl -D /var/lib/cloudera-scm-server-**d****b/data -l
logfile start

Creating SCM configuration file: /etc/cloudera-scm-server/db.**pr**
**operties
waiting for postmaster to start.........................******
..............................******........could not start
postmaster
Could not start database server, giving up

Could you let me know what the problem is? I failed when using both
root and another account which has sudo privilege.

I executed 'pg_ctl -D /var/lib/cloudera-scm-server-**d****b/data
-l logfile start' and
root cannot execute pg_ctl...
another account can execute, but anyway failed to install cloudera
manager.

Thanks.

reply | permalink

Related Discussions

Discussion Navigation

view	thread \| post

Discussion Overview

group	scm-users @
categories	hadoop
posted	Mar 11, '13 at 8:42a
active	Mar 11, '13 at 11:49p
posts	10
users	3
website	cloudera.com
irc	#hadoop

responses	expanded	Hotkey: s
font	variable	Hotkey: f
user style	avatars	Hotkey: a

cloudera manager installation fails

Search Discussions

Related Discussions

3 users in discussion