FS#26396 - [cherokee] upgrade to 1.2.100 makes cherokee-admin stop responding

Attached to Project: Community Packages
Opened by Ari Caldeira (aricaldeira) - Tuesday, 11 October 2011, 13:12 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 13 May 2012, 16:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Yesterday I did a pacman -Syu and cherokee got updated, and linux (kernel) too.

So I restarted my machine, and then cherokee stoped working with some fcgi daemons it worked
well before (Django), and also cherokee-admin didn't work anymore.

I build it myself (v. 1.2.100) thru abs, installed, but it didn't work, so I downgraded it back to 1.2.99, and now it's
working again.

I tried run cherokee-admin -b -u -x, but haven't got anything usefull to find out what the problem was.

At first I thought it could be something related to python 2.7, since both the fcgi (Django projects) and
cherokee-admin are python-based, but, since the downgrading of just cherokee had it all working back again,
the problem is not related to python.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Sunday, 13 May 2012, 16:59 GMT
Reason for closing:  Upstream
Comment by Evangelos Foutras (foutrelis) - Wednesday, 12 October 2011, 05:32 GMT
I can't reproduce the issue. You'll need to either provide instructions to reproduce the issue on a clean installation, or try asking and/or filing a bug upstream.
Comment by Constantin Sclifos (Tehnari) - Friday, 14 October 2011, 05:11 GMT
May be mailing list of the cherokee project can help: http://www.gossamer-threads.com/lists/cherokee/dev/23185
Comment by Ari Caldeira (aricaldeira) - Friday, 14 October 2011, 13:14 GMT
Ok, yesterday I installed cherokee on my netbook (x86), and there too cherokee-admin didn't work.

It wasn't un upgrade, since it wasn't installed before.

But I found out that running "cherokee-admin -b -u -t" made it work on both architectures.

Before posting upstream, today I'll try a clean install on a VirtualBox machine, just in case.
Comment by Evangelos Foutras (foutrelis) - Friday, 14 October 2011, 14:05 GMT
I just pushed cherokee 1.2.100-2 which fixes  FS#26438  (cherokee-admin hanging). I'm thinking this is the same issue.

@Ari Caldeira: The changes in -2 are specific to cherokee-admin. Are you having further issues with your Django apps?
Comment by Ari Caldeira (aricaldeira) - Wednesday, 19 October 2011, 16:42 GMT
  • Field changed: Percent Complete (100% → 0%)
Evangelos,

I finally figured it out, what is wrong with cherokee-admin and my django sites: it all works back again if I comment out, on /etc/hosts, the following line:

#::1 localhost.localdomain localhost

If I do that, even with the upgrade of today, to version 1.2.101-1, everything works as it should.

I think it is not reason to reopen the bug, but it was the way I found to contact you about that issue.

Thank you, very much!
Comment by Evan (Evanlec) - Tuesday, 25 October 2011, 02:35 GMT
I can confirm this issue installing cherokee fresh (no upgrade) today - October 24th.
After commenting out the ::1 localhost.localdomain localhost line in /etc/hosts the cherokee-admin
now works properly.
Comment by ashley H (mrshlee) - Sunday, 22 January 2012, 10:58 GMT
Same issue as discussed, https://bbs.archlinux.org/viewtopic.php?id=129132

Fresh install of 1.2.101 is still having the issue with active IPv4 (unused IPv6 module enabled).

The issue was resolved by disabling the IPv6 module/functionality.

We'll likely need to raise this upstream.


Comment by Evangelos Foutras (foutrelis) - Sunday, 22 January 2012, 16:17 GMT
Upstream report is here: http://code.google.com/p/cherokee/issues/detail?id=1289

Loading...