Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: hottweelz on January 09, 2013, 09:09:46 pm

Title: Centova Installation Complex Password Bug
Post by: hottweelz on January 09, 2013, 09:09:46 pm
I just installed v3 on a clean CentOS5 server.  No third party control panels

During the stage 2 web based installation it asks for the DB Info.

the password format used was "abcdefg$2013"

Centova then writes the tables to the database

BUT

updates /usr/local/centova/etc/centovacast.conf

DB_PASS=abcdefg13  (stripping the $20) resulting in a cannot connect error on the web at the final step.
Title: Re: Centova Installation Complex Password Bug
Post by: hottweelz on January 09, 2013, 09:12:32 pm
after a few feeble attempts at overriding multiple ways, the only answer was to change the DB Password inside the server to meet the needs of centovacast.conf  (I even tried overwriting centovacast.conf)
Title: Re: Centova Installation Complex Password Bug
Post by: hottweelz on January 20, 2013, 11:18:51 am
Was this not an issue?
Title: Re: Centova Installation Complex Password Bug
Post by: gutoeterno on January 20, 2013, 01:11:40 pm
Hello

I think you're doing the wrong process.
Although I understand correctly your problem.

When you install v3, after installation you have to run this command via ssh on your server:

/usr/local/centovacast/bin/mysqlauthfix root

This password must be the same password for your root and mysql.
Always worked for me this way.

If I have misunderstood your problem forgive me.
Title: Re: Centova Installation Complex Password Bug
Post by: Centova - Steve B. on January 20, 2013, 09:21:58 pm
Was this not an issue?
Yes, it is a bug and will be fixed in a future build.

I think you're doing the wrong process.
No, he's doing everything correctly.
Title: Re: Centova Installation Complex Password Bug
Post by: gutoeterno on January 21, 2013, 02:38:48 am
Exactly why Steve I said (if I understood correctly)

Thank you!
Title: Re: Centova Installation Complex Password Bug
Post by: Centova - Steve B. on January 22, 2013, 04:16:45 pm
This has now been fixed for the next build, thanks for the bug report.