1
angaran
xoops minimum requirements
  • 2005/9/17 21:21

  • angaran

  • Not too shy to talk

  • Posts: 103

  • Since: 2003/8/17


Hi,
I'm using XOOPS on a Linux Virtual server and I experiencing some problems.

The biggest is that Apache creates many children processes and those processes use a big amount of RAM resulting in frequent crashes.

My question is: what are the minimum requirement to run XOOPS on such a virtual server? My server has 64M of RAM.

Thx

P.S.: maybe there is a mpm module for apache that is most suitable for xoops. You know?

2
DonXoop
Re: xoops minimum requirements

64M is rather small to run a server. Are you running the MySQL server on the same box? Is a GUI running on the box too?

The other thing to do is to make sure you are running the PHP module and not as CGI. CGI will spark a lot of processes.

RAM is cheap and the most beneficial to a happy server. You don't need a GUI login on a server. You can also see better performance by compiling the Linux kernel, Apache, and PHP from source and only include relevant components. But that isn't for novices.
no max no bling. goes double for mik. triple for the insane aliases of said lunatics
===========================
Not around here anymore. Way too many idiots, so sad.

3
angaran
Re: xoops minimum requirements
  • 2005/9/18 9:40

  • angaran

  • Not too shy to talk

  • Posts: 103

  • Since: 2003/8/17


Yes I'm also running MySQL but no GUI. PHP is installed as a module.

Now I'm testing APACHE with the worker MPM. I'll let you know if this change something.

However I'm ready also to compile Apache

4
angaran
Re: xoops minimum requirements
  • 2005/9/18 10:42

  • angaran

  • Not too shy to talk

  • Posts: 103

  • Since: 2003/8/17


Mmm, worker don't work well with PHP. In fact you can't really use worker with PHP without special compilation options.

So I looker into the logs and found this:

[warn] child process xxxx still did not exit, sending a SIGTERM


I've plenty of this in the log where xxxx is the process id of the particular child.

Any idea?

EDIT: these are the modules embedded in the apache2 binaries:

core.c
mod_access.c
mod_auth.c
mod_log_config.c
mod_logio.c
mod_env.c
mod_setenvif.c
prefork.c
http_core.c
mod_mime.c
mod_status.c
mod_autoindex.c
mod_negotiation.c
mod_dir.c
mod_alias.c
mod_so.c

Are they all needed to run Xoops? Maybe I could remove some of them?? Please, let me know. I'm running Debian and it's easy to add and remove packages.

Login

Who's Online

114 user(s) are online (63 user(s) are browsing Support Forums)


Members: 0


Guests: 114


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits