Ya sorry again about that. I usually always make sure to read the
documentation but I became "that guy". RTFM!
Cherokee runs from inside a jail without System V IPC I'm just hoping
Alvaro can shed some light on the performance implications to Cherokee.
Regarding #527 I was able to come up with this. When you first boot a
server with cherokee_enable="YES" in /etc/rc.conf the admin interface
will cleanly stop and start the server (refresh the admin frontpage and
the button updates when you stop it). You can then hit the "start
server" button. You will get a gateway timeout but if you go back to the
admin's frontpage it will show that the server is running and if you
check you can see the cherokee processes have cleanly started. After
that though the stop server button doesn't work. If however you reboot
the server (or restart the jail, which for testing purposes was much
faster) you can again cleanly stop and start the server once. It seems
like there is a difference in how cherokee is being started when you
first boot where it works cleanly with cherokee-admin. But once cherokee
is started from cherokee-admin it can no longer be controlled from
there. I was able to repeat this over and over from both inside and
outside a jail. Hopefully this helps in tracking down the bug.
Cherokee started from boot (cherokee_enable="YES")
root 2401 0.0 0.5 4768 1668 ?? IsJ 8:05PM 0:00.00
/usr/local/sbin/cherokee -C /usr/local/etc/cherokee/cherokee.conf -d
www 2406 0.0 0.8 6044 2980 ?? SJ 8:05PM 0:00.03
/usr/local/sbin/cherokee-worker -C /usr/local/etc/cherokee/cherokee.conf
Cherokee started from cherokee-admin "Start Server"
root 2032 0.0 0.5 4768 1668 ?? IsJ 7:55PM 0:00.01
/usr/local/sbin/cherokee --admin_child -C
/usr/local/etc/cherokee/cherokee.conf
www 2034 0.0 0.8 6044 2984 ?? SJ 7:55PM 0:00.06
/usr/local/sbin/cherokee-worker --admin_child -C
/usr/local/etc/cherokee/cherokee.conf
On 7/25/2010 8:11 AM, Diego Schulz wrote:
On Sat, Jul 24, 2010 at 10:06 PM, Rocky Borg<[email protected]> wrote:
Well apparently restarting my SSH session "magically" fixed the permission
issue. This issue is now resolved although I do have one more question about
running cherokee inside a FreeBSD jail. What are the performance
implications of Cherokee without System V IPC.
(error) spawner.c:87 - Could not initialize SHM '/cherokee-spawner-2250':
Function not implemented
This can be fixed by:
sysctl security.jail.sysvipc_allowed=1
But per the FreeBSD handbook
(http://www.freebsd.org/doc/en/books/arch-handbook/jail-restrictions.html)
it defeats the purpose of having a jail because privileged users from the
jail would be able to affect processes outside the jailed environment with
this enabled. If I keep this turned off for security reasons what are the
implications in relation to cherokee.
On 7/24/2010 5:07 PM, Rocky Borg wrote:
I've had Cherokee running on a linux system but I'm currently having
problems getting it running with freebsd8-release (32bit generic kernel) for
the first time. I installed cherokee from ports (1.0.5). I can run
cherokee-admin but when I go to start server I get.
Could not open '/var/log/cherokee.error' for appending
When I try to start it from the shell I get:
(error) logger_writer.c:296 - Could not open '/var/log/cherokee.error' for
appending
Now at first I thought this was a permission problem. So I did:
touch /var/log/cherokee.error
chown www /var/log/cherokee.error
-rw-r--r-- 1 www wheel 0 Jul 24 19:56 cherokee.access
-rw-r--r-- 1 www wheel 0 Jul 24 19:47 cherokee.error
But I still get the exact same error.
Any help would be greatly appreciated as I've kind of hit a brick wall on
what to do.
Hi,
The permissions issue is explained in the pkg-message file, which is
displayed at the end of the port installation. For now it is the
expected behavior if you configure the port to run as www:www user
(make config). Also, it's expected that the port user actually reads
those messages :)
Clearly the port has some rough edges, I think it's a good idea for
improvement to let it adjust the permissions properly, as it is
default to run as www user. I'll take a look ASAP.
I never tried to run Cherokee in a jail, so I can't be of any help on
that for now, sorry.
Please be aware of issue #527 [1], it's still reproducible in 1.0.5,
but YMMV. Please report back any news you could find on this issue, it
will be much appreciated.
regards,
diego
[1] http://code.google.com/p/cherokee/issues/detail?id=527
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
