Mailing List Archive

Error with cherokee-admin
Hello All,

I have a weird error with cherokee-admin

When I execute it, and I go to the webpage I am prompted for user name and
password, I do that but the the management interface never loads.

On the terminal this is what I get:

root@linhost1:~# *sudo cherokee-admin -b -x*
Cherokee Web Server 1.2.103 (Feb 12 2013): Listening on port ALL:9090, TLS
disabled, IPv6 enabled, using epoll, 20000 fds system limit, max. 9993
connections, 4 threads, 2498 connections per thread, standard scheduling
policy

Login:
User: admin
One-time Password: IdBtAwWYC35wlgic

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

DEBUG: SIGUSR1 invokes the console..
SIGUSR2 prints a backtrace..
Server 1.2.103 running.. PID=21689 Port=4000
DEBUG: SIGUSR1 invokes the console..
SIGUSR2 prints a backtrace..
Server 1.2.103 running.. PID=21693 Port=4000
DEBUG: SIGUSR1 invokes the console..
SIGUSR2 prints a backtrace..
Server 1.2.103 running.. PID=21698 Port=4000
DEBUG: SIGUSR1 invokes the console..
SIGUSR2 prints a backtrace..
Server 1.2.103 running.. PID=22173 Port=4000
DEBUG: SIGUSR1 invokes the console..
SIGUSR2 prints a backtrace..
Server 1.2.103 running.. PID=22177 Port=4000


Any one has an idea of whats going on?

Details: Ubuntu 12.04
Cherokee: latest from source

Am I missing some python libraries? The system was working fine before
with ppa packages.


Regards,

Sergio
Re: Error with cherokee-admin [ In reply to ]
Hi, I don't know what's the problem, but this are some ideas:
Did you upgrade your config file? Did you ccheck your config file (Cherokee -t, I believe)? I dont believe you are missing libs. Cherokee should run with uninitiated out of the box. I will check it later and get back to you.


------------------------------
On Wed, Feb 13, 2013 3:11 AM CET Sergio Aguilar Guerrero wrote:

>Hello All,
>
>I have a weird error with cherokee-admin
>
>When I execute it, and I go to the webpage I am prompted for user name and
>password, I do that but the the management interface never loads.
>
>On the terminal this is what I get:
>
>root@linhost1:~# *sudo cherokee-admin -b -x*
>Cherokee Web Server 1.2.103 (Feb 12 2013): Listening on port ALL:9090, TLS
>disabled, IPv6 enabled, using epoll, 20000 fds system limit, max. 9993
>connections, 4 threads, 2498 connections per thread, standard scheduling
>policy
>
>Login:
> User: admin
> One-time Password: IdBtAwWYC35wlgic
>
>Web Interface:
> URL: http://localhost:9090/
>
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=21689 Port=4000
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=21693 Port=4000
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=21698 Port=4000
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=22173 Port=4000
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=22177 Port=4000
>
>
>Any one has an idea of whats going on?
>
>Details: Ubuntu 12.04
>Cherokee: latest from source
>
>Am I missing some python libraries? The system was working fine before
>with ppa packages.
>
>
>Regards,
>
>Sergio

_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee
Re: Error with cherokee-admin [ In reply to ]
Can you spawn cherokee admin process separately ?

I forgot exacly how it was. In fact such error means that cherokee admin process can't be spawned correctly. Its probably system missconfiguration, system error, missing dependency.

Cherokee admin command spawns cherokee server and then cherokee admin backend. You have to execute it by hand, then you will see whats wrong.

You can also try to run "cherokee-admin -t" command, it will spawn backend cherokee admin with unix sockets instead of local http/tcp.

-----Original Message-----
From: - - <stadtpirat11@ymail.com>
Sender: cherokee-bounces@lists.octality.com
Date: Tue, 12 Feb 2013 20:28:41
To: <chekolyn@gmail.com>; <cherokee@lists.octality.com>
Subject: Re: [Cherokee] Error with cherokee-admin


Hi, I don't know what's the problem, but this are some ideas:
Did you upgrade your config file? Did you ccheck your config file (Cherokee -t, I believe)? I dont believe you are missing libs. Cherokee should run with uninitiated out of the box. I will check it later and get back to you.


------------------------------
On Wed, Feb 13, 2013 3:11 AM CET Sergio Aguilar Guerrero wrote:

>Hello All,
>
>I have a weird error with cherokee-admin
>
>When I execute it, and I go to the webpage I am prompted for user name and
>password, I do that but the the management interface never loads.
>
>On the terminal this is what I get:
>
>root@linhost1:~# *sudo cherokee-admin -b -x*
>Cherokee Web Server 1.2.103 (Feb 12 2013): Listening on port ALL:9090, TLS
>disabled, IPv6 enabled, using epoll, 20000 fds system limit, max. 9993
>connections, 4 threads, 2498 connections per thread, standard scheduling
>policy
>
>Login:
> User: admin
> One-time Password: IdBtAwWYC35wlgic
>
>Web Interface:
> URL: http://localhost:9090/
>
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=21689 Port=4000
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=21693 Port=4000
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=21698 Port=4000
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=22173 Port=4000
>DEBUG: SIGUSR1 invokes the console..
> SIGUSR2 prints a backtrace..
>Server 1.2.103 running.. PID=22177 Port=4000
>
>
>Any one has an idea of whats going on?
>
>Details: Ubuntu 12.04
>Cherokee: latest from source
>
>Am I missing some python libraries? The system was working fine before
>with ppa packages.
>
>
>Regards,
>
>Sergio

_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee
Re: Error with cherokee-admin [ In reply to ]
On Wed, 13 Feb 2013, pigmej@gmail.com wrote:

> I forgot exacly how it was. In fact such error means that cherokee
> admin process can't be spawned correctly. Its probably system
> missconfiguration, system error, missing dependency.

Is this the IPv6 binding issue?

Stefan
_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee
Re: Error with cherokee-admin [ In reply to ]
Maybe, or that old ubuntu with something that I don't remember exactly
right now ;)

Pozdrawiam
Jędrzej Nowak


On Wed, Feb 13, 2013 at 9:47 AM, Stefan de Konink <stefan@konink.de> wrote:

> On Wed, 13 Feb 2013, pigmej@gmail.com wrote:
>
> I forgot exacly how it was. In fact such error means that cherokee admin
>> process can't be spawned correctly. Its probably system missconfiguration,
>> system error, missing dependency.
>>
>
> Is this the IPv6 binding issue?
>
> Stefan
>
Re: Error with cherokee-admin [ In reply to ]
Hello All,

Starting it with *cherokee-admin -t *works. Thanks for the
suggestion Jędrzej Nowak.

I'm not sure why cherokee-admin -b is not working; I've tested the compiled
Cherokee on my Laptop running the same version of Ubuntu and all was fine.

I appreciate every response on this thread.

Thank you,

Sergio






On Wed, Feb 13, 2013 at 1:37 AM, Jedrzej Nowak <pigmej@gmail.com> wrote:

> Maybe, or that old ubuntu with something that I don't remember exactly
> right now ;)
>
> Pozdrawiam
> Jędrzej Nowak
>
>
> On Wed, Feb 13, 2013 at 9:47 AM, Stefan de Konink <stefan@konink.de>wrote:
>
>> On Wed, 13 Feb 2013, pigmej@gmail.com wrote:
>>
>> I forgot exacly how it was. In fact such error means that cherokee admin
>>> process can't be spawned correctly. Its probably system missconfiguration,
>>> system error, missing dependency.
>>>
>>
>> Is this the IPv6 binding issue?
>>
>> Stefan
>>
>
>