I used webmin to do the update. It blew away my config file because of
the force yes option it uses so it overwrote mine with the default
config from the package. When it was done all my settings were gone
(obviously) and there wasn't a default server. The first vserver I made
was changed/converted into the default server and I went from there
redoing all my settings.
Not sure if this applies to anyone else with config problems after
upgrading but that was my issue and I wont be using webmin to upgrade
cherokee again..
On 1/24/2011 4:22 PM, Gunnar Wolf wrote:
Michiel van Es dijo [Sat, Jan 22, 2011 at 02:12:46PM +0100]:
On Sat, Jan 22, 2011 at 01:44:51PM +0100, Anders Omar Bocanegra Mendoza wrote:
I have the same problem. I solve this reinstall cherokee. My mistake install
cherokee in other path.
But you installed from source right? I installed by using the
Debian/Ubuntu package repository, perhaps something is wrong with the
package?
I really doubt this is in any way related to the packaging - We do not
touch the configuration at all. At some point (between 0.5 and 0.99,
IIRC), installing a new version passed the configuration through a
parser updating it, but since the configuration format stabilized, all
that code is no longer run - but is part of cherokee-admin's startup.
I cannot but believe this is a parsing problem in cherokee-admin.
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
