Jan,   You can find previous releases here:   http://archive-primary.cloudera.com/cm5/   If you were using RedHat, for example, you could go to:   http://archive-primary.cloudera.com/cm5/redhat/6/x86_64/cm/5.1.2/   - Ben ... View more

Try checking the /var/log/cloudera-scm-server/cloudera-scm-server.log files for a WARN message that looks like this:   Host %s (derived version %s) not eligible for cluster %s   The %s will be replaced with the values generated from the validity check.   This should show us what verion was detected on the node and hopefully give us an idea of why the failure is occurring. ... View more

Without knowing what is growing or why, it is hard to say if this is normal or expected.  For an idle server with no notable problems and a few quiet nodes, I would not expect such growth.    I would suggest finding out exactly what disk directory is growing the most; if it is /var/lib/cloudera-scm-server-db/data/base/16387 as you mentioned earlier, I would find out to which database that oid maps to.  Knowing what database is growing will at least narrow the possible causes and provide some direction to the investigation.   With the aid of the following steps:   http://etutorials.org/SQL/Postgresql/Part+I+General+PostgreSQL+Use/Chapter+4.+Performance/How+PostgreSQL+Organizes+Data/   I was able to determine that in one of my test hosts, the "metrics" table in my "scm" database is taking the most space on disk, so I recommend taking a look at that to find out what database and table are growing.   ... View more

The point that mgrover was making in the previous post was that you should not delete anything.  Formatting will essentially destroy your hdfs data.   I think a good rule here is to not delete /var/lib data as you will likely corrupt or destroy key parts of your cluster.  In production, you would have an external database and monitor servers on other hosts, storing data in other directories.  There may be ways to free up space in your existing install, but none are trivial or without consequence.   Ben   ... View more

Maybe shut off iptables ( service iptables stop ) and then run the install.  If the network/yum can't get ironed out, then you may need to use Path B or C install rather than the "bin" install.   See http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Installation-Guide/cm5ig_install_cm_cdh.html ... View more

Those files are actually your embedded PostgreSQL database that contains your Cloudera Manager data, so deleting would be highly destructive.   The embedded PostgreSQL is only intended for demonstration, so the way to go for you may be to configure an external database as described in:   http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Installation-Guide/cm5ig_installing_configuring_dbs.html   If you want to dig in and find out what is actually being stored in the PostgreSQL directories, I found this page that walks you through navigating the various subdirectories:   http://etutorials.org/SQL/Postgresql/Part+I+General+PostgreSQL+Use/Chapter+4.+Performance/How+PostgreSQL+Organizes+Data/   -Ben   ... View more

Hello,   Cloudera Manager stores information there, so deleting it would not be advised.   Check what directory or directories grow with something like:   du -sh /var/lib/* |sort -n   If you can isolate what is growing, perhaps we can suggest a way to limit that growth.   Ben   ... View more

The error is from yum, so I suggest looking for answers there.  A web search turned up various hits for yum and IPv6.  This one seemed to have the most suggestions:   http://vaishnaav.com/2013/12/17/centos-yum-error-14-pcyurl-error-7-failed-to-connect-to-2a02249813d5054fffed3e9/   This backs up the suggestion that it may be a problem with the firewall:   https://www.centos.org/forums/viewtopic.php?t=6478   Once the yum/network issue is resolved, the installation should proceed.   Regards,   Ben ... View more

Hi there.   First, on each host, make sure this returns your FQDN and IP:   python -c "import socket; print socket.getfqdn(); print socket.gethostbyname(socket.getfqdn())"     If that does not return the fqdn and ip, then, in your hosts file, make sure you have the FQDN before host for each IP.   <IP>  <FQDN> <host>   That said, the errors you mention do not necessarily mean there is something wrong.   Your concern seems to be that "CDH Version" is none.  Where are you seeing that, exactly?  Can you manage the hosts via Cloudera Manager?   Ben ... View more