<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: CDH 5.3 KeyTrustee DB Service in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-5-3-KeyTrustee-DB-Service/m-p/30334#M6429</link>
    <description>&lt;P&gt;I am happy to see that you figured out the problem. Thank you for sharing the solution as it may help others as well.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 31 Jul 2015 12:20:27 GMT</pubDate>
    <dc:creator>cjervis</dc:creator>
    <dc:date>2015-07-31T12:20:27Z</dc:date>
    <item>
      <title>CDH 5.3 KeyTrustee DB Service</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-5-3-KeyTrustee-DB-Service/m-p/29088#M6427</link>
      <description>&lt;P&gt;I have managed to initialize and setup Navigator Encrypt plus KeyTrustee solution, with several data drives encrypted and mounted. The data nodes can be rebooted, the keys fetched on boot, and mounted. This is great. But - when the KeyTrustee server was rebooted, postgresql-9.3 failed to start. I cannot start this database service and I don't understand why. Because of this, now all data volumes are now not able to be mounted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a TEST/CONCEPT setup and so far as no actual data on it. If we need to start over and re-initialize the database, and re-encrypt data volumes, then fine. But, we need to know if this is recoverable and/or how to prevent this from occuring in production cluster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm also new to postgresql. I can only imagine I need to try to "su -" as "cloudera-scm" account, but I don't remember the password used. I also imagine we can fix it by adding user privileges within postgresql database, but not sure how to go about properly doing this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any insight here would be really helpful. Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;sudo /sbin/service postgresql-9.3 status&lt;/P&gt;&lt;P&gt;postgresql-9.3 is stopped&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;sudo /sbin/service postgresql-9.3 start&lt;BR /&gt;Starting postgresql-9.3 service:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [FAILED]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;/usr/pgsql-9.3/bin/pg_ctl -D /var/lib/pgsql/9.3/keytrustee start&lt;BR /&gt;pg_ctl: could not open PID file "/var/lib/pgsql/9.3/keytrustee/postmaster.pid": Permission denied&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;sudo /usr/pgsql-9.3/bin/pg_ctl -D /var/lib/pgsql/9.3/keytrustee start&lt;BR /&gt;pg_ctl: cannot be run as root&lt;BR /&gt;Please log in (using, e.g., "su") as the (unprivileged) user that will&lt;BR /&gt;own the server process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;sudo ls -l /var/lib/pgsql/9.3/&lt;BR /&gt;total 24&lt;BR /&gt;drwx------&amp;nbsp; 2 postgres postgres 4096 May 20 03:50 backups&lt;BR /&gt;drwx------ 16 postgres postgres 4096 Jun 15 09:39 data&lt;BR /&gt;drwx------ 16 postgres postgres 4096 Jun 15 09:43 keytrustee&lt;BR /&gt;-rw-------&amp;nbsp; 1 postgres postgres 9424 Jun 15 09:43 pgstartup.log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;sudo ls -l /var/lib/pgsql/9.3/keytrustee&lt;BR /&gt;total 120&lt;BR /&gt;drwx------ 6 postgres postgres&amp;nbsp; 4096 May 18 13:39 base&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 May 28 15:42 global&lt;BR /&gt;-rw-r--r-- 1 root&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; root&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0 May 18 13:30 MASTER&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 May 18 13:30 pg_clog&lt;BR /&gt;-rw------- 1 postgres postgres&amp;nbsp; 4564 Jun 15 08:38 pg_hba.conf&lt;BR /&gt;-rw------- 1 postgres postgres&amp;nbsp; 1636 May 18 13:30 pg_ident.conf&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 May 24 00:00 pg_log&lt;BR /&gt;drwx------ 4 postgres postgres&amp;nbsp; 4096 May 18 13:30 pg_multixact&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 Jun 15 09:43 pg_notify&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 May 18 13:30 pg_serial&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 May 18 13:30 pg_snapshots&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 May 28 15:41 pg_stat&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 Jun&amp;nbsp; 6 08:25 pg_stat_tmp&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 May 18 13:30 pg_subtrans&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 May 18 13:30 pg_tblspc&lt;BR /&gt;drwx------ 2 postgres postgres&amp;nbsp; 4096 May 18 13:30 pg_twophase&lt;BR /&gt;-rw------- 1 postgres postgres&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4 May 18 13:30 PG_VERSION&lt;BR /&gt;drwx------ 3 postgres postgres&amp;nbsp; 4096 May 18 13:30 pg_xlog&lt;BR /&gt;-rw-r--r-- 1 postgres postgres&amp;nbsp;&amp;nbsp; 874 May 18 15:22 postgres.conf.include&lt;BR /&gt;-rw------- 1 postgres postgres 20855 May 18 15:22 postgresql.conf&lt;BR /&gt;-rw------- 1 postgres postgres&amp;nbsp;&amp;nbsp;&amp;nbsp; 77 Jun 15 09:43 postmaster.opts&lt;BR /&gt;-rw------- 1 postgres postgres&amp;nbsp; 1245 May 18 13:30 root.crt&lt;BR /&gt;-rw------- 1 postgres root&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1704 May 18 13:30 root.key&lt;BR /&gt;-rw------- 1 postgres postgres&amp;nbsp; 1127 May 18 13:30 server.crt&lt;BR /&gt;-rw------- 1 postgres postgres&amp;nbsp; 1704 May 18 13:30 server.key&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 09:32:50 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-5-3-KeyTrustee-DB-Service/m-p/29088#M6427</guid>
      <dc:creator>jadmin</dc:creator>
      <dc:date>2022-09-16T09:32:50Z</dc:date>
    </item>
    <item>
      <title>Re: CDH 5.3 KeyTrustee DB Service</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-5-3-KeyTrustee-DB-Service/m-p/30330#M6428</link>
      <description>Update: Interestingly, when I had another user try to run the service, it gave a different error in the logs, which ended up being much more helpful error message. Essentially it all was related to permissions to the files for keytrustee.</description>
      <pubDate>Fri, 31 Jul 2015 10:53:31 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-5-3-KeyTrustee-DB-Service/m-p/30330#M6428</guid>
      <dc:creator>jadmin</dc:creator>
      <dc:date>2015-07-31T10:53:31Z</dc:date>
    </item>
    <item>
      <title>Re: CDH 5.3 KeyTrustee DB Service</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-5-3-KeyTrustee-DB-Service/m-p/30334#M6429</link>
      <description>&lt;P&gt;I am happy to see that you figured out the problem. Thank you for sharing the solution as it may help others as well.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jul 2015 12:20:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-5-3-KeyTrustee-DB-Service/m-p/30334#M6429</guid>
      <dc:creator>cjervis</dc:creator>
      <dc:date>2015-07-31T12:20:27Z</dc:date>
    </item>
  </channel>
</rss>

