Found it. It seems this change didn't make it in the 0.4.0 release :(
I'll update my documentation. 

On 2017-07-12 08:48, Ryan Merriman wrote:

> The fix was part of METRON-990.  The exact fix was a one line change in 
> /metron-interface/metron-rest/src/main/scripts/metron-rest: 
> 
> line 148:  "$0 start" was changed to "$0 start $2" 
> 
> Ryan  
> 
> On Wed, Jul 12, 2017 at 10:06 AM, Kyle Richardson <[email protected]> 
> wrote:
> 
> I'm encountering the Ambari restart bug on the 0.4.0 release branch. Ryan, 
> can you let me know which PR/JIRA has the fix for it; I'd like to test it 
> out. 
> 
> Thanks! 
> 
> -Kyle 
> 
> On Wed, Jul 12, 2017 at 9:48 AM, Ryan Merriman <[email protected]> wrote:
> 
> Does this error happen on start or restart?  The bug I fixed only happened on 
> restart.   
> 
> On Tue, Jul 11, 2017 at 5:13 PM, Nick Allen <[email protected]> wrote:
> 
> Yes, I have seen this. It is a bug. I believe Ryan submitted a fix in one of 
> his open PRs.  He can chime in with the exact one. 
> 
> On Jul 11, 2017 6:08 PM, "Laurens Vets" <[email protected]> wrote:
> Before I open a JIRA ticket, does anyone know why starting Metron REST fails, 
> but manually starting it with "service metron-rest start <password>" works?
> 
> In /var/log/metron/metron-rest.log, I see the following:
> 
> .   ____          _            __ _ _
> /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
> ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
> \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
> '  |____| .__|_| |_|_| |_\__, | / / / /
> =========|_|==============|___/=/_/_/_/
> :: Spring Boot ::        (v1.4.1.RELEASE)
> 
> Jul 11, 2017 9:43:09 PM org.apache.tomcat.jdbc.pool.Co [1]nnectionPool init
> SEVERE: Unable to create initial connections of pool.
> java.sql.SQLException: Access denied for user 'metron'@'metron' (using 
> password: YES)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:964)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3973)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3909)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:873)
> at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:4420)
> at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1278)
> ...
> 
> But the username & password are correct (tested manually via CLI) and 
> manually starting the service works as well... Is Ambari somehow forgetting 
> to supply the password? How can I test this?
> 
> Thanks in advance!

 

Links:
------
[1] http://org.apache.tomcat.jdbc.pool.Co

Reply via email to