From: Hancock, D. (DHANCOCK) <DHA...@ar...> - 2003-01-25 14:30:30
|
I hope someone chimes in with a better idea, because my ideas involve some work... If you have sufficient rights to have cron jobs, consider writing a little monitor that runs via cron. It just needs to look for the appserver process, or retrieve a page using wget or lynx -dump, and if it can't get the page, run a script to restart webkit. If you can't have cron jobs, but can have 'at' jobs, write the same monitor as for cron, but extend it slightly to resubmit itself via the 'at' mechanism when it completes. If you can't have 'at' jobs, I don't know what to try. Of two proposed above, cron is the better. It will survive a reboot nicely, wait its waiting period, and start your webkit. With 'at', I don't know the behavior across a reboot that takes the machine out of commission past the start time of the job. Cheers! -- David Hancock | dha...@ar... | 410-266-4384 -----Original Message----- From: Ben Logan [mailto:be...@wb...] Sent: Saturday, January 25, 2003 6:12 AM To: web...@li... Subject: [Webware-discuss] Keeping Webware running. Hi, everyone. I am running Webware on a shared Linux web server (I don't have root priveleges), and am wondering what I can do to make certain that it stays running. I've been starting the appserver by logging in via ssh, and running 'nohup Appserver &', and that works, but sometimes it dies for no apparent reason. I also need a way to make sure that it gets restarted if they reboot the server. I am hoping for a solution that doesn't involve the server admins installing Webware system wide. Has anyone else solved this problem? Thanks, Ben -- Ben Logan Google Answers Researcher answers.google.com When you're searching for information, Google Answers. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Webware-discuss mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Hancock, D. (DHANCOCK) <DHA...@ar...> - 2003-01-26 01:52:25
|
8192KB of stack is a lot, and that seems to be the default on Linux. We haven't had any stack-limit problems running very large apps in Webware on Linux. Cheers! -- David Hancock | dha...@ar... | 410-266-4384 -----Original Message----- From: Ian Bicking [mailto:ia...@co...] Sent: Saturday, January 25, 2003 8:13 PM To: Webware discuss Subject: Re: [Webware-discuss] Keeping Webware running. They might have a daemon that kills long-running processes too. Might want to check with them on that. On Sat, 2003-01-25 at 18:29, Ben Logan wrote: > Thanks to everyone for your responses. I do have cron access on the > server, so I'll give that method a shot. I hadn't considered that > appserver might be dying because they've limited my cpu time, so I ran > 'ulimit -a' on the server, and my cpu time is unlimited. However, the > stack size is limited to 8192Kb. I wouldn't have thought that I would > be using that much stack with my application, but maybe that's the > problem. > > Thanks again, > Ben -- Ian Bicking <ia...@co...> ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Webware-discuss mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Ian B. <ia...@co...> - 2003-01-25 19:21:12
|
On Sat, 2003-01-25 at 08:30, Hancock, David (DHANCOCK) wrote: > I hope someone chimes in with a better idea, because my ideas involve some > work... Sadly there's not a much better solution included with Webware or that I've used, though someone else may have a solution. > If you have sufficient rights to have cron jobs, consider writing a little > monitor that runs via cron. It just needs to look for the appserver > process, or retrieve a page using wget or lynx -dump, and if it can't get > the page, run a script to restart webkit. > > If you can't have cron jobs, but can have 'at' jobs, write the same monitor > as for cron, but extend it slightly to resubmit itself via the 'at' > mechanism when it completes. If you aren't sure if you have cron access, just try "crontab -e", and read "man 5 crontab" to learn about it. If you find the AppServer isn't running, you should be sure to kill it (-9) before restarting it, in case it's not dead but not responding. Hmm... might go something like: # crontab: */10 * * * * $HOME/bin/checkwebware >> $HOME/bin/checkwebware.log 2>&1 # checkwebware: wget http://localhost/WK -O - > /dev/null 2>&1 if [ "$?" != "0" ] ; then # wget failed killall -9 AppServer ~/Webware/WebKit/webkit start fi It'll take some testing to get this properly tweaked. -- Ian Bicking Colorstudy Web Development ia...@co... http://www.colorstudy.com PGP: gpg --keyserver pgp.mit.edu --recv-keys 0x9B9E28B7 4869 N Talman Ave, Chicago, IL 60625 / (773) 275-7241 |