Original author: sci.f...@gmail.com (November 01, 2011 10:21:23)
What steps will reproduce the problem?
Virtual Server, Unknown key 'subdomains'
Most probably you are using an old configuration file that contains a deprecated key. Loading and then saving it through Cherokee-Admin should update the old entries for you automatically.
Looks like when disabling HSTS the "Include Subdomains" option is still there.
In /etc/cherokee/cherokee.conf it's like this:
vserver!XX!subdomains = 1
I need to delete above line manually to make it work again.
Original issue: http://code.google.com/p/cherokee/issues/detail?id=1297
From ste...@konink.de on November 14, 2011 08:50:53
1301 contains the fix.
From alobbs on November 22, 2011 18:45:23
Fixed on 'dev'. It will be released on Cherokee 1.2.102.
Stefan, good catch! :)
From gend...@gmail.com on December 12, 2012 00:02:29
ed still reporting the same error with the same fix in the current release buildt from source.
From ste...@opengeo.nl on December 12, 2012 00:08:27
Did you try github?
@sinkie I do believe him. It does not look like the dev branch has been merged into master at any time.
I am extremely sure this one is fixed.
No, I have the same error now,
Cherokee Web Server 1.2.101
I'm using the PPA, isn't that the latest version?
No. There is no guarantee every PPA will always be up-to-date.
Ok, but now I got that error:
Could not find a Cherokee resource: /usr/sbin/cherokee-worker
although I copied /usr/local/sbin/cherokee-worker to /usr/sbin/cherokee-worker
I purged the previous before
EDIT: I recompiled and installed Cherokee again and it creates no files in /usr/sbin/
That's right, compiled software usually goes into /usr/local/, so you find it in /usr/local/sbin/. But why do you need that anyway? Just type cherokee
So I purged and reinstalled Cherokee a third one and it works now but why would the PPA not updated ?
The easy answer is: that's not our job nor our resonsibility. There is no one who offered to do the packaging and publishing to the PPA.
Glad you got it working. And I hate to have off-topic talk in this issue, so please confirm that the bug has been fixed :)
Yes the bug has been fixed :)