[Seaside] Monit on Ubuntu / Debian to monitor Seaside images

Sebastian Sastre ssastre at seaswork.com
Sun Feb 10 18:49:40 UTC 2008


You intuitively tried to find process by names as we humans name things to
identify them but those *nix boxes are not smart things to interact with.
I'm glad you find the way. Cheers !

Sebastian Sastre


________________________________

	De: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] En nombre de Rajeev
Lochan
	Enviado el: Domingo, 10 de Febrero de 2008 15:52
	Para: Seaside - general discussion
	Asunto: Re: [Seaside] Monit on Ubuntu / Debian to monitor Seaside
images
	
	
	Hi Sebastian,
	I had got confused with the process name in "check process
'someProcessName' ..... to be the same as that shown when we use ps -A or
top (which shows squeakvm for all the squeak images). 
	
	In other examples (such as for Apache/ sshd etc), they have a single
process running and they are assigned apache2 and sshd as process name in
monitrc file.
	
	I tried with the following in monitrc
	check process caartz01 with pidfile /var/run/caartz01.pid
	...............
	...............
	
	check process caartz02 with pidfile /var/run/caartz02.pid
	...............
	...............
	
	check process caartz03 with pidfile /var/run/caartz03.pid
	...............
	...............
	
	
	and I restarted Monit. All the squeak-seaside images started on
their own. files qith pid is saved as explained by one of my previous mails
in this thread. I am happy that there is no real need to change the process
name of squeak in general :) . Sorry for the trouble given due to my
misconception.
	
	So, I am nearing towards deployment of my Seaside App :)
	
	Thanks again,
	Rajeev
	

	On Feb 10, 2008 10:58 PM, Sebastian Sastre <ssastre at seaswork.com>
wrote:
	

		As far as I know for *nix systems process only have PID
number as formal reference so I don't get why do you need a name and
identify them by it. 
		 
		I exposed I make squeak images to create a PID file in
/var/run/services with it's unique *service name* which match the name of
the script which starts/stops the process of that service, just to make them
human manageable. So the OJ7WRE is just the name of the script which
starts/stops that image and the name of the PID file that image
creates/deletes when it starts/shutsdown. 
		 
		I've made all that just to be able to invoke with a name the
process of that image so monit can watch on its pid file to know if it's
alive or other details of the process.
		 
		I plan to create scripts-paths-images automagically but they
are manually created by now.
		 
		    cheers,
		 
		Sebastian Sastre

				 


________________________________

						De:
seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] En nombre de Rajeev
Lochan
			
			Enviado el: Domingo, 10 de Febrero de 2008 00:41 

			Para: Seaside - general discussion
			Asunto: Re: [Seaside] Monit on Ubuntu / Debian to
monitor Seaside images
			
			
			
			Sebastian,
			In your first mail of this thread, you have given
out the code that needs to be appended into monitrc. How could you create
process named OJ7WRE ?
			
			
			Right now, I have got start and stop script working
as explained my previous mail. My concern now are :
			
			1] Is it possile to name or rename the
process/Command in Linux (By default it is set 'squeakvm' ) ? Can this be
done on Linux or is it possible to change something in SqueakVM so that the
process name it assigns to the process is somewhat unique (Is it easy to
tweak SqueakVM by an amateur like me ?)
			
			2] As of now, I would like to give preference to
Monit as I have got about 75% working. Remaining depends on point 1.
			
			3] If [1] is not possible, I shall try to follow
Ramon's instruction of creating event.d and then installing Daemontools.
			
			Thanks & Regards,
			Rajeev
			
			
			
			On Feb 9, 2008 11:18 PM, Sebastian Sastre
<ssastre at seaswork.com> wrote:
			

				>
				> I didn't say monit wasn't still useful,
just that services
				> are easier to create and automate with
daemontools than with init.d.
				>
				
				Just asking to compare. I'm glad they moved
to a more powerful model.
				...
				
				> Sort of, I haven't blogged about it, but
we hashed out the
				> necessary steps a while back
				>
http://lists.squeakfoundation.org/pipermail/seaside/2007-Novem
				ber/015071.htm
<http://lists.squeakfoundation.org/pipermail/seaside/2007-November/015071.ht
m> 
				> l
				>
				> Ramon Leon
				> http://onsmalltalk.com
				>
				
				Reference very appreciated,
				
				       cheers!
				
				Sebastian
				

	
_______________________________________________
				seaside mailing list
				seaside at lists.squeakfoundation.org
	
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
				




			-- 
			Rajeev Lochan
			
			Co-founder, AR-CAD.com
			
			http://www.ar-cad.com
			+91 9243468076 (Bangalore)
			080 65355873 


		_______________________________________________
		seaside mailing list
		seaside at lists.squeakfoundation.org
	
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
		
		




	-- 
	Rajeev Lochan
	
	Co-founder, AR-CAD.com
	
	http://www.ar-cad.com
	+91 9243468076 (Bangalore)
	080 65355873 




More information about the seaside mailing list