[Cherokee] cherokee-admin suddenly not working

[N. Brad Garrett]

After I ran a typical apt-get update/upgrade, cherokee-admin no longer works when I run "cherokee-admin -b" as root.

The libs that were updated were for openssl, so I assume it has to do with that, but as of now, my web browser will NOT bring up the cherokee admin.

This is obviously a major problem as I host several sites and can't currently add more.

Thanks for any assistance,

—brad g.

 
* * * * * * * * * * * * * * * *
Visit www.bradezone.com today and be the trailblazer of your peer group.

[pig...@gmail.com]

Have you checked option -t when starting admin ?


Does the browser asks you about login/password ?
-----Original Message-----
From: "N. Brad Garrett" <brad...@gmail.com>
Sender: cherokee...@lists.octality.com
Date: Mon, 25 Feb 2013 21:17:49
To: <cher...@lists.octality.com>
Subject: [Cherokee] cherokee-admin suddenly not working

_______________________________________________
Cherokee mailing list
Cher...@lists.octality.com
http://lists.octality.com/listinfo/cherokee


_______________________________________________
Cherokee mailing list
Cher...@lists.octality.com
http://lists.octality.com/listinfo/cherokee

[- -]

What packages have been upgraded?

---

Von: N. Brad Garrett <brad...@gmail.com>
An: cher...@lists.octality.com
Gesendet: 3:17 Dienstag, 26.Februar 2013
Betreff: [Cherokee] cherokee-admin suddenly not working

[Brad Garrett]

Yes, I tried -t and it was the same effect.
I do NOT get asked for user/pwd, because the browser just sits there spinning—it's as if I didn't even start cherokee-admin, but the process is definitely running on the server.

--brad g.

 
* * * * * * * * * * * * * * * *
Visit www.bradezone.com today and be the trailblazer of your peer group.

[Brad Garrett]

From the apt history log (4 packages total):

Upgrade: linux-libc-dev (2.6.32-45.103, 2.6.32-45.104), libssl-dev (0.9.8k-7ubuntu8.13, 0.9.8k-7ubuntu8.14), libssl0.9.8 (0.9.8k-7ubuntu8.13, 0.9.8k-7ubuntu8.14), openssl (0.9.8k-7ubuntu8.13, 0.9.8k-7ubuntu8.14)

--brad g.

 
* * * * * * * * * * * * * * * *
Visit www.bradezone.com today and be the trailblazer of your peer group.

[Stefan de Konink]

On Tue, 26 Feb 2013, Brad Garrett wrote:

> Yes, I tried -t and it was the same effect.
> I do NOT get asked for user/pwd, because the browser just sits there

> spinning?it's as if I didn't even start cherokee-admin, but the process is

> definitely running on the server.

What platform/architecture? Can you see if /etc/hosts containts IPv6
addresses for localhost?

Stefan

[Brad Garrett]

I host on Linode w/ these specs:

i686 GNU/Linux
Ubuntu 10.04.4 LTS

I do regular apt-get update/upgrade, so it's currently up to date.
This is the first time I've had a problem after the upgrade.

Here's my /etc/hosts file (w/ public server name and IP's changed):

127.0.0.1            localhost.localdomain    localhost
111.111.111.111            sub.domain.com    sub
28e6:28e6::28e6:28e6:28e6:28e6    sub.domain.com    sub

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

--brad g.

 
* * * * * * * * * * * * * * * *
Visit www.bradezone.com today and be the trailblazer of your peer group.

_______________________________________________
Cherokee mailing list
Cher...@lists.octality.com
http://lists.octality.com/listinfo/cherokee

!DSPAM:1,512ccbdb65951283132533!

[Stefan de Konink]

On Tue, 26 Feb 2013, Brad Garrett wrote:

> # The following lines are desirable for IPv6 capable hosts

> ::1ￜￜￜￜ ip6-localhost ip6-loopback

> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters

Try to escape everything IPv6 related...

[Brad Garrett]

Did that. Restarted cherokee. Same result.
I then went to /etc/modprobe.d/blacklist.conf and set "blacklist ipv6" and rebooted the whole server.

STILL the same result.

WTF has happened??

thanks,

--brad g.

 
* * * * * * * * * * * * * * * *
Visit www.bradezone.com today and be the trailblazer of your peer group.

On Tue, Feb 26, 2013 at 10:12 AM, Stefan de Konink <ste...@konink.de> wrote:

On Tue, 26 Feb 2013, Brad Garrett wrote:

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback

fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

[Stefan de Konink]

On Tue, 26 Feb 2013, Brad Garrett wrote:

> WTF has happened??

You already tried to do a clean compile of cherokee?

[Brad Garrett]

Noooo, I shouldn't have to do that IMO.
I originally installed via the Ubuntu package as described here:
http://www.cherokee-project.com/downloads.html

I just did a -V check and they are all the latest 1.2.101

I really don't want to get into the whole manual compiling business. The package should be robust enough.

--brad g.

 
* * * * * * * * * * * * * * * *
Visit www.bradezone.com today and be the trailblazer of your peer group.

[Stefan de Konink]

On Tue, 26 Feb 2013, Brad Garrett wrote:

> I really don't want to get into the whole manual compiling business. The
> package should be robust enough.

You updated ;) Not us.

What happens if you start cherokee-worker manually?

[Johannes Becker]

Am 26.02.2013 um 10:53 schrieb Stefan de Konink <ste...@konink.de>:

> On Tue, 26 Feb 2013, Brad Garrett wrote:
>
>> I really don't want to get into the whole manual compiling business. The
>> package should be robust enough.
>
> You updated ;) Not us.

Seriously?? Is this supposed to be an official statement?

[Brad Garrett]

Stopping/starting cherokee or cherokee-worker works fine (Thank God, my sites are still up).
The problem seems isolated to cherokee-admin.

So weird...

--brad g.

 
* * * * * * * * * * * * * * * *
Visit www.bradezone.com today and be the trailblazer of your peer group.

[- -]

> On Tue, 26 Feb 2013, Brad Garrett wrote:
>
>> I really don't want to get into the whole manual compiling business. The
>> package should be robust enough.

>> Am 26.02.2013 um 10:53 schrieb Stefan de Konink <ste...@konink.de>:
>>
>>> On Tue, 26 Feb 2013, Brad Garrett wrote:
>>
>>> I really don't want to get into the whole manual compiling business. The
>>> package should be robust enough.
>>
>> You updated ;) Not us.
>
> Seriously?? Is this supposed to be an official statement?

I am sure Stefan was just joking, don't take it too seriously.

But Cherokee on Github and Cherokee in the Ubuntu repositories are two totally different spheres of responsibility. The Ubuntu package is **OLD** and I am 99,9% sure that the compiled version is working. If someone would be able to maintain the Ubuntu packages, they would be up to date. It's not something that is ignored on purpose.

Once you are into compiling, there is no real difference in upgrading a package, or upgrading the compiled version. If you need help compiling, or have questions, ask here, or ask me directly.

Stadtpirat

[Brad Garrett]

I suppose I could do this, but it concerns me that cherokee would not keep its ubuntu packages up to date. All mainstream apps/utilities should do this IMO. Pretty sure apache never requires manual compilation, ya know?

Having said that, I definitely appreciate the work that's been done on Cherokee--I prefer it to the alternatives, but please, somebody get the packages up to date! (Although like I said, my version number is the same that is on the Cherokee home page.)

--brad g.

 
* * * * * * * * * * * * * * * *
Visit www.bradezone.com today and be the trailblazer of your peer group.

[pig...@gmail.com]

You're right, that apache doesn't require manual compilation (except when it crashes...). But cherokee dev process is way different, also man power is different. Keeping up to date distro packages IS hard work. That's one of the problems.

You should not be worried about manual compilation :) it's easy and when you will use --prefix=/opt/cherokee your setup will be separated from main distro things.

I strongly recommend this to you. That's obvoiusly caused by current cherokee state, where releasing versions would be not that smart, isn't it Stefan ?

Best regards,
Jedrzej Nowak

---

From: Brad Garrett <brad...@gmail.com>

Date: Tue, 26 Feb 2013 15:23:12 -0500

To: - -<stadtp...@ymail.com>

Cc: Johannes Becker<jo.b...@gmail.com>; Stefan de Konink<ste...@konink.de>; cher...@lists.octality.com<cher...@lists.octality.com>; Jędrzej Nowak<pig...@gmail.com>

Subject: Re: [Cherokee] cherokee-admin suddenly not working

[Stefan de Konink]

On 02/26/2013 11:07 PM, pig...@gmail.com wrote:
> I strongly recommend this to you. That's obvoiusly caused by current
> cherokee state, where releasing versions would be not that smart, isn't
> it Stefan ?

Unless one of the other fundamental things "the official website" is
solved. I agree. Never the less, I disagree that upstream should make
packages. And we have enough e-mails about that subject already.


Stefan

[Brade]

Oddly enough, things started working again when I upgraded from Ubuntu 10.04 to 12.04.
I was planning to install cherokee manually once the upgrade happened, but for some reason, it just started working again so I left it alone =D

[- -]

good to hear. you should try compiling it anyway ;)

---

Von: Brade <brad...@gmail.com>
An: cherok...@googlegroups.com
CC: cher...@lists.octality.com
Gesendet: 14:23 Dienstag, 19.März 2013
Betreff: Re: [Cherokee] cherokee-admin suddenly not working

Oddly enough, things started working again when I upgraded from Ubuntu 10.04 to 12.04.
I was planning to install cherokee manually once the upgrade happened, but for some reason, it just started working again so I left it alone =D