WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: How to use the cherokee-admin interface  (Read 3091 times)

Offline Lee

  • Hero Member
  • *****
  • Posts: 645
    • My Core wiki user page
How to use the cherokee-admin interface
« on: November 20, 2012, 10:51:06 PM »
I've been using cherokee web server for some very simple web page serving and I've decided I want to expand the capabilities a little and use some CGI.  Until now I had not used the cherokee-admin tool, just edited the cherokee.conf file by hand for the tiny changes I was making.  I've been unable to get CGI working that way so I tried to run the admin tool... and it doesn't start.

I found this thread:  http://forum.tinycorelinux.net/index.php/topic,8683.msg46950.html#msg46950 with posts by vinnie and combo3 but the steps there didn't get it working for me.

Here is what I get when I try to run it:
Code: [Select]
tc@timpc:~$ which cherokee-admin
/usr/local/sbin/cherokee-admin

tc@timpc:~$ sudo /usr/local/sbin/cherokee-admin
env: can't execute 'python': No such file or directory
ERROR: Couldn't find python.

tc@timpc:~$ tce-load -i python
/usr/bin/tce-load: line 294: desktop.sh: not found
bzip2-lib.tcz: OK
/usr/bin/tce-load: line 294: desktop.sh: not found
sqlite3.tcz: OK
/usr/bin/tce-load: line 294: desktop.sh: not found
python.tcz: OK

tc@timpc:~$ sudo /usr/local/sbin/cherokee-admin
[20/11/2012 22:35:58.203] (error) source_interpreter.c:479 - Could not find
    interpreter '/usr/local/share/cherokee/admin/server.py 4000
    /usr/local/etc/cherokee/cherokee.conf' | The server configuration refers to
    an interpreter that is not installed in this system.

main_admin.c:425 - Could not initialize the server
tc@timpc:~$

This is on a reasonably fresh install of Core 4.7.

Any ideas?

32 bit core4.7.7, Xprogs, Xorg-7.6, wbar, jwm  |  - Testing -
PPR, data persistence through filetool.sh          |  32 bit core 8.0 alpha 1
USB Flash drive, one partition, ext2, grub4dos  | Otherwise similar

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11704
Re: How to use the cherokee-admin interface
« Reply #1 on: November 20, 2012, 11:07:49 PM »

Offline althalus

  • Sr. Member
  • ****
  • Posts: 351
Re: How to use the cherokee-admin interface
« Reply #2 on: November 20, 2012, 11:18:45 PM »
Quote
I found this thread:  http://forum.tinycorelinux.net/index.php/topic,8683.msg46950.html#msg46950 with posts by vinnie and combo3 but the steps there didn't get it working for me.

According to the change log, there have been two updates to cherokee since that thread. Presumably there were some files left out necessary for the admin interface to run. The thread Rich linked to seems to have reached the same conclusion, though no one fixed it...

Offline Lee

  • Hero Member
  • *****
  • Posts: 645
    • My Core wiki user page
Re: How to use the cherokee-admin interface
« Reply #3 on: November 21, 2012, 01:29:57 AM »
Thanks Rich.  I had not seen that other thread.

And thank you, Althalus - it looks like you are right about omitted files.  I'll probably play with it a bit over the long weekend and see if I can pull in the missing files - maybe figure out what needs to be added to the extension.

Its particularly frustrating because what I really want is to just edit the config file!  But there's no documentation beyond "oh, just run cherokee-admin - you should never edit the config file".
32 bit core4.7.7, Xprogs, Xorg-7.6, wbar, jwm  |  - Testing -
PPR, data persistence through filetool.sh          |  32 bit core 8.0 alpha 1
USB Flash drive, one partition, ext2, grub4dos  | Otherwise similar

Offline althalus

  • Sr. Member
  • ****
  • Posts: 351
Re: How to use the cherokee-admin interface
« Reply #4 on: November 21, 2012, 05:38:10 AM »
Its particularly frustrating because what I really want is to just edit the config file!  But there's no documentation beyond "oh, just run cherokee-admin - you should never edit the config file".
Yeah, I stopped using cherokee and switched to nginx at about the point where cherokee started generating a config file that was all but impossible to edit by hand. It was just too much of a hassle to keep persisting with it.