1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tomato beta10 ND K26 @ RT-N16 + cherokee web server

Discussion in 'Tomato Firmware' started by gobol, Apr 15, 2010.

  1. gobol

    gobol Networkin' Nut Member

    Hi,

    I have few questions and problems with cherokee web server 0.99.44 installed on my RT-N16 with Tomato beta10 ND K26.

    I'm installing it using optware/ipkg.
    Code:
    ipkg install cherokee
    ipkg install cherokee-admin
    went smooth, with all requested dependencies.

    Code:
    root@ASUS:/tmp/home/root# [B]python[/B]
    Python 2.5.5 (r255:77872, Feb 17 2010, 11:56:02)
    [GCC 4.1.1] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>>
    seems to be ok.

    Code:
    root@ASUS:/tmp/home/root# ps -w | grep cherokee
    23874 root      2540 S    /opt/sbin/cherokee -d
    23877 root      4764 S    /opt/sbin/cherokee-worker
    23880 root      4764 S    /opt/sbin/cherokee-worker
    23881 root      4764 S    /opt/sbin/cherokee-worker
    23882 root      4764 S    /opt/sbin/cherokee-worker
    23883 root      4764 S    /opt/sbin/cherokee-worker
    23884 root      4764 S    /opt/sbin/cherokee-worker
    24258 root      1540 R    grep cherokee
    root@ASUS:/tmp/home/root#
    
    cherokee seems to be working ok, lynx-ing localhost:8008 showing cherokee test page.


    #1 Problem is here :
    Code:
    root@ASUS:/tmp/home/root# cherokee-admin -b
    
    Login:
      User:              admin
      One-time Password: 6KnL4okcRCvwAOER
    
    Web Interface:
      URL:               http://localhost:9090/
    
    [B]Segmentation fault[/B]
    
    #2 Problem : cherokee binds only to localhost:8008, and is unavailable from LAN (as 192.168.1.1:8008), neither from WAN....
    It may be realted with the following :
    Code:
    root@ASUS:/opt/etc/init.d# ./S80cherokee start
    Starting web server: cherokee
    root@ASUS:/opt/etc/init.d# [15/04/2010 20:40:27.662] (error) [B]socket.c:421 - Could not create socket: Address family not supported by protocol
    [/B]Cherokee Web Server 0.99.44 (Mar 22 2010): Listening on port ALL:8008, TLS
    disabled, IPv6 enabled, using poll, 4096 fds system limit, max. 2041
    connections, caching I/O, 5 threads, 408 connections per thread, standard
    scheduling policy
    
     
  2. sasukepl

    sasukepl Addicted to LI Member

    I have problem to:

    Code:
    [root@unknown root]$ [17/04/2010 11:36:07.129] (error) socket.c:421 - Could not create socket: Address family not supported by protocol
    [17/04/2010 11:36:07.129] (critical) bind.c:284 - Could not bind() port=8008 (UID=0, GID=0)
    how i can disable IPv6?
     
  3. gobol

    gobol Networkin' Nut Member

    anybody tried to run Cherokee on tomato/dd-wrt ?

    i've found that one problem lies in path-to-admin python scripts, and path-to-config-file, but after specifing correct paths segfault remains in cherokee-admin.

    cherokee server is working properly, but without admin interface, any changes in configuration are very hard to proceed...
     
  4. gobol

    gobol Networkin' Nut Member

    giving up... :(

    visibility from WAN is to be achieved by setting proper port forwarding through firewall (port forwarding/basic/ ( external = 8008, TCP, On )).

    I believe that problems with cherokee arising from incompatible directory structure forced by optware and some problems with python. Had no time to dbg it, switching to lighttpd...

    If anyone has some experience with cherokee on this platform, I'd love to hear about.
     
  5. sasukepl

    sasukepl Addicted to LI Member

    as I remember Tomato does not support ipv6.Cherokee disable ipv6 then you can access the admin web.Lecz do not know how to disable it. I know a way to disable web admin General -> network.Nie know if there is a way to exclude from the console Putty
     
  6. gobol

    gobol Networkin' Nut Member

    I've disabled ipv6 in cherokee, but problem still remains - still SEGFAULT while running cherokee-admin
    I've switched router web admin to other port than 80, nothing better.
     

Share This Page