running eZ Publish daemons in virtual host environment

Wednesday 05 January 2011 7:08:18 am - 3 replies

Introduction

The recommended way of using the ezfind and ezodf extensions on a server with multiple eZP installations is to have only one instance of Solr server and one instance of OO conversion server for all the eZP installations.

Running single instances of this servers for multiple eZP installations is not a problem if you have full access to your server, but if you happen to have many eZP installation in a limited virtual hosting environment, setting this two servers can be a little bit tricky. So here is how you'll do it...

» Read full blog post

3 replies

Author	Message
Nicolas Pastorino	Wednesday 05 January 2011 8:13:03 am Brilliant Marko ! Well structured, properly documented, hot topic. All good, keep-up ! This could even turn into a tutorial, given the furnished content. Your call ;) Cheers, -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye
Paul Borgermans	Monday 10 January 2011 9:57:20 am A small comment on changing the port for Solr: its better to use a specific command line option "jetty.port" when using the jetty (bundled) servlet container. Of course you can also add this as a variable in your init script. java -jar -Djetty.port=55555 start.jar hth Paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Marko Žmak	Monday 17 January 2011 6:43:04 am Paul, the purpose of this blogpost is to describe how to setup ezodf and solr daemons in a shared virtual host environment where you don't have root access. And setting the solr port via the command line parameter requires you to change the startup script, and therefore whenever you want to change the port you have to ask the system admin to reinstall the modified script. And this is contrary to the "spirit" of this post: to setup and maintain the daemons with a minimum of system admin intervention. -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth

Author

Message

Nicolas Pastorino

Wednesday 05 January 2011 8:13:03 am

Brilliant Marko !

Well structured, properly documented, hot topic. All good, keep-up !
This could even turn into a tutorial, given the furnished content. Your call ;)

Cheers,

--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter: http://twitter.com/ezcommunity

t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye

Paul Borgermans

Monday 10 January 2011 9:57:20 am

A small comment on changing the port for Solr: its better to use a specific command line option "jetty.port" when using the jetty (bundled) servlet container. Of course you can also add this as a variable in your init script.

java -jar -Djetty.port=55555 start.jar

hth

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Marko Žmak

Monday 17 January 2011 6:43:04 am

Paul, the purpose of this blogpost is to describe how to setup ezodf and solr daemons in a shared virtual host environment where you don't have root access.

And setting the solr port via the command line parameter requires you to change the startup script, and therefore whenever you want to change the port you have to ask the system admin to reinstall the modified script.

And this is contrary to the "spirit" of this post: to setup and maintain the daemons with a minimum of system admin intervention.

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

You must be logged in to post messages in this topic!

eZ debug

Timing:	Jan 17 2025 23:38:08
Script start
Timing:	Jan 17 2025 23:38:08
Module start 'layout'
Timing:	Jan 17 2025 23:38:08
Module start 'content'
Timing:	Jan 17 2025 23:38:08
Module end 'content'
Timing:	Jan 17 2025 23:38:08
Script end

Main resources:

Total runtime	0.0135 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0047	589.2891	152.6563
Module start 'layout'	0.0047	0.0024	741.9453	39.5156
Module start 'content'	0.0071	0.0046	781.4609	98.0469
Module end 'content'	0.0117	0.0018	879.5078	34.2891
Script end	0.0135		913.7969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	16.8319	14	0.0002
Check MTime	0.0010	7.2003	14	0.0001
Mysql Total
Database connection	0.0005	3.9505	1	0.0005
Mysqli_queries	0.0021	15.2703	3	0.0007
Looping result	0.0000	0.0968	1	0.0000
Template Total	0.0015	11.1	1	0.0015
Template load	0.0008	5.7532	1	0.0008
Template processing	0.0007	5.3025	1	0.0007
Override
Cache load	0.0005	3.8097	1	0.0005
General
dbfile	0.0008	5.7250	8	0.0001
String conversion	0.0000	0.0599	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs