After working around my previous problem here, I found out that the File Browser on Cloudera Manager is not up to date, all the files & folders are old, which makes reports to not show anything useful. On the top right corner on HDFS -> File Browser -> Directory Usage page it says "The file system image was last indexed on January 26, 2017 1:55 PM".    This is preventing me from generating disk usage reports and also analyzing statistics on Cloudera Navigator.   I' ve found this very informing article, but couldn't really helped me.   If I'm not wrong there is something wrong with namenodes are not checkpointing or not using the image they extract. Can anyone give more information about this?   As it shows in the outputs I posted below, it does checkpoint every 1 hour as in the config but how can I make Cloudera Manager, Navigator, File Browser etc. to see it?       I have 1 active 1 stand-by namenodes.   Checkpoint directory setting:            Though, I have no "/ds1/dfs/snn" folder on stand-by namenode machine.   When I search for fsimage* on active namenode:   2015-08-19+17:54: 7878 ./ds1/dfs/snn/current/fsimage_0000000000000000279 2015-08-19+17:54 62 ./ds1/dfs/snn/current/fsimage_0000000000000000279.md5 2015-08-19+17:54 10272 ./ds1/dfs/snn/current/fsimage_0000000000000000510 2015-08-19+17:54 62 ./ds1/dfs/snn/current/fsimage_0000000000000000510.md5 2017-03-29+13:57 281926964 ./ds1/dfs/nn/current/fsimage_0000000000287939457 (today) 2017-03-29+13:57 281926964 ./ds2/dfs/nn/current/fsimage_0000000000287939457 2017-03-29+13:58 62 ./ds1/dfs/nn/current/fsimage_0000000000287939457.md5 2017-03-29+13:58 62 ./ds2/dfs/nn/current/fsimage_0000000000287939457.md5 2017-03-29+14:58 282426827 ./ds1/dfs/nn/current/fsimage_0000000000287980225 2017-03-29+14:58 282426827 ./ds2/dfs/nn/current/fsimage_0000000000287980225 2017-03-29+14:58 62 ./ds1/dfs/nn/current/fsimage_0000000000287980225.md5 2017-03-29+14:58 62 ./ds2/dfs/nn/current/fsimage_0000000000287980225.md5   on stand-by namenode:   2017-03-29+13:57 281926964 ./ds1/dfs/nn/current/fsimage_0000000000287939457 2017-03-29+13:57 62 ./ds1/dfs/nn/current/fsimage_0000000000287939457.md5 2017-03-29+13:57 281926964 ./ds2/dfs/nn/current/fsimage_0000000000287939457 2017-03-29+13:57 62 ./ds2/dfs/nn/current/fsimage_0000000000287939457.md5 2017-03-29+14:58 282426827 ./ds1/dfs/nn/current/fsimage_0000000000287980225 2017-03-29+14:58 282426827 ./ds2/dfs/nn/current/fsimage_0000000000287980225 2017-03-29+14:58 62 ./ds1/dfs/nn/current/fsimage_0000000000287980225.md5 2017-03-29+14:58 62 ./ds2/dfs/nn/current/fsimage_0000000000287980225.md5             ... View more

  I've done an upgrade to Cloudera Manager from 5.5.3 to 5.10.0 then upgraded CDH from 5.5.1 to 5.8.4. After these operations, I saw the disk usages of all DataNodes on Hosts->All Hosts page increased. On HDFS file browser and with CLI commands I see almost every directory has double the size before, but I noticed no difference among the file counts, types, names etc.. Same thing when I also check disk usage on Linux terminal. I am a little bit confused and need help to figure out what happened. ... View more

I'm guessing I somehow managed to do the same typo twice while changing the password. Tried the combinations but no luck.   CDH version is 5.5.1 There is no /var/lib/cloudera-scm-server-db folder. Here's my /etc/cloudera-scm-server/db.properties file:     com.cloudera.cmf.db.type=mysql com.cloudera.cmf.db.host=hds01:3306 com.cloudera.cmf.db.name=scmdb com.cloudera.cmf.db.user=scm com.cloudera.cmf.db.password=scm_passwd   The host I'm on is hdsm. I browsed for a solution and tried these:   $ psql -U scm -d scmdb Password for user scm: scm_passwd psql: FATAL: password authentication failed for user "scm" $ psql -h hds01 -U scm -d scmdb psql: could not connec to server: Connection Refused Is the server running on host "hds01" and accepting TCP/IP connections on port 5432? There's mysqld up on hds01.    On hds01;   $ mysql -u scm -p scm_passwd -h localhost ERROR 1045 (28000): Access denied for user 'scm'@'localhost' (using password: YES)   Every other username/password combination fails and I can't seem to connect to the DB whatsoever. I'm not able to reach anyone who knows the credentials, in fact I doubt there is anyone. What's the consequences if I stop mysql, start with skip-grant, edit user passwords, flush privileges then restart?   Appreciate any help     EDIT (SOLVED): I'm now connected to database (found out scm user is only accepted from hdsm, so installed mysql client on there)  and thanks to rufusayeni's comment at this post, I solved my issue. Though, I would wanna know what if I couldn't. ... View more