Re: MiniVend dies & Hammerlock issues

[Patrick Schoonveld <pschoonveld@venux.net>]

Inside of the minivend.cfg, there is a way to increase the possible
number of request and I believe, processes. I would check that out.

I looked in my cfg, things for people to checkout:
HammerLock
PIDcheck
MaxServers

HammerLock has to do with making sure searches and the like don't take
too long.
PIDcheck sees if any of the processes have hung.
MaxServers allows for a number of servers to be running in the backend
to serve multiple customers (set this high, like 25 for lots of people).
Interestingly, Apache uses the same sort of thing on webservers.
Definately a plus for minivend.



Bill wrote:
> 
> ******    message to minivend-users from "Bill" <bill@webteam.net>     ******
> 
> I've been having a problem with minivend crashing when it receives several
> concurrent requests.  The error can also be reproduced by reloading any page
> in my catalog several times very quickly.  From mail posts, it sounds like
> many people have done load testing without experiencing this problem, but I
> don't have the slightest idea where to start looking for a solution to this.
> 
> There's nothing in the error logs.  Checking processes, I see a number of
> catalog requests waiting to be served, and one that appears to be defunct.
> However, minivend appears to be hung and never recovers.  I've seen defunct
> processes before, but they are usually terminated and minivend continues on
> its way.  I have found that running debug (-D4096) in the foreground
> prevents Minivend from crashing.
> 
> Any ideas on what to?  I'm running MV3.12 on Digital Unix 550MHz, 512 RAM.
> 
> Bill Rothbauer
> 
> -
> To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
> email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
> Archive of past messages: http://www.minivend.com/minivend/minivend-list