Topic: boot mysql.init ERROR

[aecc]

I've upgraded from sme 6 to 7 and everything seems to work: databases, webmail, ... but booting I got an ERROR message at the end of the booting process related to mysql.init.

I would like to know if I have to worry about it or not. Is it a bug? I've have access to mysql and my php-mysql programs work. But i'm not sure if it will fail in the future. Excuses for my english

Thanks in advance.

[cactus]

Please search the bugtracker and if not there report it as a bug to the bugtracker.

[daley]

Can you capture log messages for look?

[aecc]

I've solved it renaming templates before upgrading to version 7. I think... At least, doing this the error disappear, but I'm not completely sure that this had been the reason.

[mrjhb3]

I've solved it renaming templates before upgrading to version 7. I think... At least, doing this the error disappear, but I'm not completely sure that this had been the reason.

Any mysql.init errors should show up in /var/log/messages after a post-upgrade and reboot, or after every reboot if the offending file isn't removed from /etc/e-smith/sql/init.

John

[pfloor]

I've solved it renaming templates before upgrading to version 7. I think... At least, doing this the error disappear, but I'm not completely sure that this had been the reason.

What errors did you see?
What templates did you rename?

You are not doing anybody any good here by being cryptic.  Please find and post those errors and tell us exactly what you did.

[aecc]

The templates renamed are related to crontab, php.ini and httpd.conf.

The first time I didn't renamed them beacause I thought they were not important. After several upgrading proofs and fails, at last, when I renamed them, the errors disappeared. I've not done more upgrades since then.
I renamed them because I read in the forums that that was the way to proceed when you upgrade to v.7 from v.6


These are the error messages:

......
File: boot.log          Col 0              20095 bytes                       92%

Mar 25 16:10:28 alboran1 mysql.init:
Mar 25 16:10:28 alboran1 mysql.init: Loading 77horde_mysql_update_privs into mys
ql
Mar 25 16:10:28 alboran1 77horde_mysql_update_privs: ERROR
Mar 25 16:10:28 alboran1 77horde_mysql_update_privs:  1045 (28000): Access denie
d for user 'root'@'localhost' (using password: YES)
Mar 25 16:10:28 alboran1 mysql.init: ERROR 1045 (28000): Access denied for user
'root'@'localhost' (using password: YES)
Mar 25 16:10:28 alboran1 mysql.init: Loading 77horde_mysql_update_privs into mys
ql failed
Mar 25 16:10:28 alboran1 mysql.init: .[60G
Mar 25 16:10:28 alboran1 mysql.init:
Mar 25 16:10:28 alboran1 mysql.init: Loading 77mysql_update_privs into mysql
Mar 25 16:10:28 alboran1 77mysql_update_privs: ERROR
Mar 25 16:10:28 alboran1 77mysql_update_privs:  1045 (28000): Access denied for
user 'root'@'localhost' (using password: YES)
Mar 25 16:10:28 alboran1 mysql.init: ERROR 1045 (28000): Access denied for user
'root'@'localhost' (using password: YES)
Mar 25 16:10:28 alboran1 mysql.init: Loading 77mysql_update_privs into mysql fai
led
Mar 25 16:10:28 alboran1 mysql.init: .[60G
Mar 25 16:10:28 alboran1 mysql.init:

..............


I hope this will help.
Any comment will be welcome.
Thank you for your patience and interest.

[mrjhb3]

Curious that you report that webmail works.  That script updates the horde user's priviledges so that horde will run correctly under SME 7.
If you do a config show horde and compare the DbPassword entry with what's in /home/httpd/html/horde/config/conf.php, do they match?  The above error would lead me to believe no.  Which also leads to another question to are you sure you don't have any other mysql.init errors after a post-upgrade and reboot?

John

[aecc]

Since last installation+upgrade I have had no errors. Soon, I'll have to do another one in the main server. All this happened to me in the test server. I'll report future errors or difficulties which might arise.

[aecc]

The errors have appeared again. ¿¿¿¿¿????? I don't understand anything
Well, how can I proceed to determine the origin of this error?
Should I detail all the process I have followed to install v.6, transfer the data from the old server and upgrade to v.7? Maybe there some wrong things on that process.