[Date Prev][Date Next][Thread Prev][Thread Next][Minivend by date
][Minivend by thread
]
Re: Hanging and crashing in BSD-type OSes (Was: Re: [mv] Setting MV session ID from outside of Minivend.)
****** message to minivend-users from "kyle@invisio.com" <kyle@invisio.com> ******
My $.02
I have been running MV3.11 on FreeBSD3.1 continuously for nearly
6 months now. The site is very busy 8,000+ page views per day and
MV has never "crashed" or "stopped" on it!
I did try to originally set up this new box with 3.12 (or maybe it was 3.13)
but that MV kept "dying" with no info in the logs and I could not figure it
out so I downgraded to 3.11 and for some reason it works just fine.
I also have 3.11 running for nearly a year on another FreeBSD(2.2.7) box
and it has never had a problem and serves 20+ catalogs and nearly
20,000+ MV pages per day. The only problem I've encountered on that
box is that it has only 128M memory and occasionally it gets all used
up and slows down the response while using swap space.
I will probably try to install the newest MV version in the next few months
on the newer box and see what it does. I'll let the list know the results then.
Kyle Cook (KC)
At 01:28 PM 4/7/00 -0400, you wrote:
>****** message to minivend-users from Mike Heins <mikeh@minivend.com>
>******
>
>Quoting March Roseland (march@uia.net):
>> So is this (the kernel interrupting socket reads) responsible for the
>> trouble? Has anyone any ideas or solutions to the problem?
Incidentally, it
>> doesn't seem to hang and then exit; it seems to be running fine and then
>> quit. Many thanks!
>
>I don't know what to do. I think great strides have been made in porting
>Perl to BSD recently, and the BSD people even include Perl 5 in standard
>builds (they put in Perl 4 as /usr/bin/perl as late as December 1998!),
>but they still have problems as far as I can see. Every other release of
>BSD seems to break Perl sockets in some way, and I have no answer. I am
>not involved with Perl on that level, and since I don't run BSD I haven't
>had the exposure to try and debug or workaround. I just avoid BSD. A
>shame, because by all accounts it is a very stable and fast-performing
>system.
>
>This has been going on for three years or more. At one time I worked
>on an Iserver settup running BSDI, and this problem bedeviled us all
>along, even when we switched to a dedicated server running BSDI. I am
>sure that the client thought I was lying when I said that MV ran for
>months on end on Linux or Solaris. Of course, MV wasn't quite as well
>known back in 1996, so I don't blame them. 8-) I think there has been
>enough collective experience now to validate my claim.
>
>Answers? I have none. I can't get involved in the BSD kernel or the
>Perl guts, for I have no time. It is frustrating, because I am sure
>that there are many other transitory Perl problems on BSD that are
>not addressed simply because they are so infrequent and do nothing
>but cause a transitory 500 server error. Minivend gets hit because
>when it segfaults, the server dies.
>
>--
>Internet Robotics, 131 Willow Lane, Floor 2, Oxford, OH 45056
>phone +1.513.523.7621 fax 7501 <mikeh@minivend.com>
>
>Light travels faster than sound. This is why some people appear bright
>until you hear them speak. -- unknown
>-
>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
-
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