Topic: MySQL InnoDB Support

[Bud]

Hope you guys can help

Running on SME 8b6
I needed to get InnoDB " ENABLED " so I did the Following

Code Start:

db configuration setprop mysqld InnoDB enabled
expand-template /etc/my.cnf
sv t /service/mysqld
signal-event post-upgrade; signal-event reboot

Code End:

Now NONE of my web based systems are working including " server-manager "
I have tried

Code Start:

db configuration setprop mysqld InnoDB disable
expand-template /etc/my.cnf
sv t /service/mysqld
signal-event post-upgrade; signal-event reboot

Code End:

But I still cannot get access to the " server-manager "
Any ideas what i can do to rectify it. 

[Stefano]

first of all you should check your logs to find what's going wrong..

server-manager are not influenced by mysql in any way, so the problem seems to be with httpd

are you sure you did not modify anything else?

[cactus]

Code: [Select]

db configuration setprop mysqld InnoDB enabled
expand-template /etc/my.cnf
sv t /service/mysqld
signal-event post-upgrade; signal-event reboot


The last line was not required and might have changed more than you desired leading up to the webserver failure as you describe below:

Now NONE of my web based systems are working including " server-manager "

Code: [Select]

db configuration setprop mysqld InnoDB disable
expand-template /etc/my.cnf
sv t /service/mysqld
signal-event post-upgrade; signal-event reboot

That will not help as the configuration of MySQL is not related to the webserver (at least not for server-maanger as Stefano already said). Apart from that the keyword disable should be disabled IIRC.

Any ideas what i can do to rectify it. 

Not without your help as we need to find out why your webserver is not starting. Please show us the output off the following command:

Code: [Select]

httpd -t

[Bud]

thanks for your help guys much appreciated
my web service was not working
i did what cactus suggested

httpd -t

this command displayed the error being in the file " /etc/httpd/conf/httpd.conf "
my server was saying that there was " no directory end " on line 1308
i then added the code " </Directory> " at the line required and all is working now

thanks cactus much appreciated 

[gregswallow]

i then added the code " </Directory> " at the line required and all is working now

You shouldn't edit httpd.conf directly, it is templated, so your change will be lost when you reconfigure/reboot next.  You should figure out what contrib added a template without "</Directory>", edit that template file or copy it to templates-custom and edit it, and then test it is fixed by doing:

Code: [Select]

expand-template /etc/httpd/conf/httpd.conf
sv t /service/httpd-e-smith
httpd -tand report it on bugzilla if it was a contrib with a category there.

Some reading material:
http://wiki.contribs.org/Template_Tutorial

[cactus]

httpd -t

this command displayed the error being in the file " /etc/httpd/conf/httpd.conf "
my server was saying that there was " no directory end " on line 1308
i then added the code " </Directory> " at the line required and all is working now

Although that might fix it for now, you need to find out what is causing this incomplete directory block. The configuration file is generated from templates and most likely something is wrong there.
Since configuration changes and system updates cause the file to be regenerated the problem might re-appaer.

What directory block was not closed properly? Can you trace that back to a template fragment?