question Re: Not Able to start hive metastore in Archives of Support Questions (Read Only)

Not Able to start hive metastore

chennuri_gouris — Thu, 14 Jul 2016 14:37:17 GMT

Resource_management.core.exceptions.Fail: Execution of 'export HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ; /usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType postgres -userName hive -passWord [PROTECTED]' returned 254. /etc/profile: fork: retry: Resource temporarily unavailable
/etc/profile: fork: retry: Resource temporarily unavailable
/etc/profile: fork: retry: Resource temporarily unavailable
/etc/profile: fork: retry: Resource temporarily unavailable
/etc/profile: fork: Resource temporarily unavailable
/etc/profile: fork: retry: Resource temporarily unavailable

/etc/profile: fork: retry: Resource temporarily unavailable

Re: Not Able to start hive metastore

ledel — Thu, 14 Jul 2016 14:46:07 GMT

you're apparently running out of file descriptors, try to adjust your ulimit accordingly

Re: Not Able to start hive metastore

chennuri_gouris — Thu, 14 Jul 2016 14:53:16 GMT

su hive su: cannot set user id: Resource temporarily unavailable

Re: Not Able to start hive metastore

dchiguruvad — Thu, 14 Jul 2016 15:53:24 GMT

@chennuri gouri shankar

Main issue could be :

The system was not able to create new process(es), because of the limits set for nproc in /etc/security/limits.conf file.

Increase the value of "nproc" parameter for user or all user's in /etc/security/limits.d/90-nproc.conf example of /etc/security/limits.d/90-nproc.conf file.

<code><user>       -          nproc     2048      <<<----[ Only for "<user>" user ]

Please use this link to debug for redhat linux flavours:

https://access.redhat.com/solutions/543503

Other thing you can check is the user limit in creating processes.

Check with : ulimit -a. (TO check Limits in your shell)

Esp check for 'ulimit -u' max user processes,

Re: Not Able to start hive metastore

chennuri_gouris — Thu, 14 Jul 2016 18:04:05 GMT

Thanks Everyone,

I resolved the issue by increasing the /etc/security/limits.d/hive.conf . Everything went fine.