Support Questions
Find answers, ask questions, and share your expertise

Why cloudera-manager-agent depends on package apache2 since 5.5.0

Why cloudera-manager-agent depends on package apache2 since 5.5.0

New Contributor

Hi

 

After upgrade CM from 5.3.2 to 5.5.1, I found out apache2 server is running and listening 80 port in my datanodes and namenodes. (debian wheezy)

 

Compare 5.4.9 to 5.5.0 deb repository

http://archive.cloudera.com/cm5/debian/wheezy/amd64/cm/dists/wheezy-cm5.4.9/contrib/binary-amd64/Pac...

 

Package: cloudera-manager-agent
Source: enterprise
Version: 5.4.9-1.cm549.p0.9~wheezy-cm5
Architecture: amd64
Maintainer: Cloudera Inc. <https://issues.cloudera.org>
Installed-Size: 29163
Depends: libc6 (>= 2.13), libcomerr2 (>= 1.01), libgcc1 (>= 1:4.1.1), libgssapi-krb5-2 (>= 1.10+dfsg~), libk5crypto3 (>= 1.6.dfsg.2), libkrb5-3 (>= 1.6.dfsg.2), libssl1.0.0 (>= 1.0.0), zlib1g (>= 1:1.2.0), lsb-base, psmisc, bash, libsasl2-modules, libsasl2-modules-gssapi-mit, libxslt1.1, libsqlite3-0, libfuse2, fuse-utils | fuse, rpcbind, cloudera-manager-daemons (= 5.4.9-1.cm549.p0.9~wheezy-cm5)

 

http://archive.cloudera.com/cm5/debian/wheezy/amd64/cm/dists/wheezy-cm5.5.0/contrib/binary-amd64/Pac...

 

Package: cloudera-manager-agent
Source: enterprise
Version: 5.5.0-1.cm550.p0.61~wheezy-cm5
Architecture: amd64
Maintainer: Cloudera Inc. <https://issues.cloudera.org>
Installed-Size: 29763
Depends: libc6 (>= 2.13), libcomerr2 (>= 1.01), libgcc1 (>= 1:4.1.1), libgssapi-krb5-2 (>= 1.10+dfsg~), libk5crypto3 (>= 1.6.dfsg.2), libkrb5-3 (>= 1.6.dfsg.2), libssl1.0.0 (>= 1.0.0), zlib1g (>= 1:1.2.0), lsb-base, psmisc, bash, libsasl2-modules, libsasl2-modules-gssapi-mit, libxslt1.1, libsqlite3-0, openssl, libssl-dev, libfuse2, fuse-utils | fuse, rpcbind, cloudera-manager-daemons (= 5.5.0-1.cm550.p0.61~wheezy-cm5), perl, python-psycopg2, python-mysqldb, apache2

 

It shows that dependency

perl, python-psycopg2, python-mysqldb, apache2

was added.

 

And in debian wheezy, with package apache2 installed, it will bring up apache2 http server service, which listening on port 80. Why cloudera-manager-agent depends apache2?  apache2 access log shows no incoming traffic to it.

 

If cloudera-manager-agent depends some libs in apache2 packages, could it depend on minimal lib package?

If not, could it stop apache2 service from running and autostart?

 

Thank you! 

2 REPLIES 2

Re: Why cloudera-manager-agent depends on package apache2 since 5.5.0

New Contributor

+1 for these requests. This was a surprise when upgrading from CM 5.4 to 5.6.0

 

As all the apache does is to serve "It works!" this does not seem like an intended feature?

 

Best regards,

Esben

Re: Why cloudera-manager-agent depends on package apache2 since 5.5.0

Apache2 is required for the Hue Load Balancer to work properly, which was introduced in CM 5.5 and launches a CM-managed apache2 server configured as Hue's load balancer. CM doesn't intend to start apache2 on port 80 - that's an issue with Debian.

Debian doesn't make it easy to install CM agent running + autostart while not doing the same for apache2. It's quite annoying =/

Installing just the libs didn't work out because then we don't have the executable, which we also need. Ideally init scripts would have been in a separate package.

Other than apache2 starting unexpectedly, was there another concern?