Cherokee Web Server on Linux ( Cross-platform Web server ) :

Cherokee is one of the fastest and most flexible web server's available. Cherokee is able to gracefully handle many concurrent connections while maintaining a low memory footprint. It supports a large variety of technologies, features, load balancing capabilities, platforms, and provides an administration interface to configure your server and sites.

Installation:

RPM:

[root@ranjith ~]# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm

YUM:

[root@ranjith ~]# yum install cherokee

start Cherokee and add it to the default runlevel (to start at boot time).

[root@ranjith ~]# /etc/init.d/cherokee start
[root@ranjith ~]# chkconfig cherokee on

Configuration

Unlike Apache, Cherokee itself provides an interface for administering the web server. To start the admin interface, run the following command in the shell.

[root@ranjith ~]# cherokee-admin -b

The output of this command will show the login pass, and URL. Similar to the following:

Login:
User: admin
One-time Password: password

Web Interface:
URL: http://localhost:9090/

Cherokee Web Server 1.0.6 (Aug 6 2010): Listening on port ALL:9090, TLS
disabled, IPv6 enabled, using epoll, 4096 fds system limit, max. 2041
connections, caching I/O, single thread

Cherokee's admin will now be listening on port 9090 of your server, web browser on http://your-servers-ip:9090.

Enjoy!!!

Comments

Post a Comment

Popular posts from this blog

Resolved: DOCKER: Error response from daemon: Could not attach to network / rpc error: code = 7 desc = network not manually attachable.

Image
I got this error: 'docker: Error response from daemon: Could not attach to network <nw-name>: rpc error: code = 7 desc = network <nw-name> not manually attachable.' when i try to create the container on the overlay network on swarm mode enabled, In docker 1.12 with swarm mode enabled, "Swarm" scoped networks (see the "SCOPE" column) cannot be used for docker run, only for services and now it has been rectified. I'm using updated version of docker, but still why i'm experiencing the error ? because the network just created but not manually attachable. To fix the issue we gonna use --attachable flag while creating network. [ --attachable             Enable manual container attachment ] (Need to create service on the overlay network, so that the overlay network will available / list on the worker node) docker inspect attnw (attnw is our test network)should show your own c
Read more

yum failed 6 times. Cannot continue!

Error while cPanel installation: (ERROR): - ssystem [EXIT_CODE] '/usr/bin/yum' exited with 1 (ignored) (DEBUG): - ssystem [END] (FATAL): yum failed 6 times. Cannot continue! fix: It looks like you have some name resolution issues on the server. Just run the following commands on your server and it will resolve the name resolution issues. #echo "nameserver 8.8.8.8" >> /etc/resolv.conf #echo "nameserver 8.8.4.4" >> /etc/resolv.conf if it is not working properly still facing same error, then here we go, # rpm -e --nodeps bind-chroot # rpm -e --nodeps bind # yum install bind
Read more

unexpectedly shrunk window (repaired) in dmesg log - TCP Peer

Don't Panic, This normally occurs when a client decides to reduce its TCP window size, without the server expecting it. This can be the case when fragmentation is an issue, or when the client is using an embedded device with very little NIC buffer memory. This is a completely normal behaviour, and you’re likely to see quite a few such packets in your log. The messages are informational only, and are used to debug networking issues. I’d be worried if you saw hundreds of thousands of these packets, since there are attacks that involve packet fragmentation and small window sizes, but otherwise it’s just the normal sort of noise you should expect to see on any internet-facing network. In fact, the “repaired” part of your message is showing that your network driver fixed the issue, which is usually done by concatenating the payloads of two fragmented packets together. Shouldn’t be an issue at all. … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … 
Read more