On Sep 13, 2006, at 1:57 PM, Ken Ara wrote:
I have a new problem but it's related, so I'll keep
this thread alive.
To recap: possibly due to some network problems at my
hosting provider, my Zope would periodically stop
responding and I was unable to stop, restart or kill
it, or even restart th
I have a new problem but it's related, so I'll keep
this thread alive.
To recap: possibly due to some network problems at my
hosting provider, my Zope would periodically stop
responding and I was unable to stop, restart or kill
it, or even restart the machine remotely. I am
operating within a Free
Chris Withers wrote at 2006-9-6 10:59 +0100:
>Andreas Jung wrote:
>>
>> This remark was just stupid. There is nothing with BSD except
>> there are some known issues you need to consider when compiling Python
>> (at least there were some issues in the past).
>
>Sorry, I disagree.
>
>Look back over
Andreas Jung wrote:
This remark was just stupid. There is nothing with BSD except
there are some known issues you need to consider when compiling Python
(at least there were some issues in the past).
Sorry, I disagree.
Look back over the list archives, it seems common for people to have
prob
Thank you, Dieter, for your valuable insights and
information. I am forwarding this to my ISP.
--- Dieter Maurer <[EMAIL PROTECTED]> wrote:
> Ken Ara wrote at 2006-9-5 07:47 -0700:
> >...
> >Of immediate concern to me is whether I can do
> >anything to prevent this happening again. From time
> to
Ken Ara wrote at 2006-9-5 07:47 -0700:
>...
>Of immediate concern to me is whether I can do
>anything to prevent this happening again. From time to
>time, my Zope hangs, usually because of an attack by a
>bad robot requesting lots of complex pages and sending
>no-cache headers. Then I am able to re
Ken Ara wrote at 2006-9-5 01:14 -0700:
> ...
>and I can't even restart the machine with the
>shutdown command.
If you cannot shutdown your system, then something seriously
is wrong with it. It will have nothing to do with Zope.
You may try the "reboot" command. It is similar to "shutdown"
but sta
--On 5. September 2006 07:47:05 -0700 Ken Ara <[EMAIL PROTECTED]> wrote:
OK, once again, after many hours of costly down time,
we have restarted our Zope machine.
Chris, could state your reasons for recommending
against FreeBSD? I have had no trouble in over five
years that I can directly att
OK, once again, after many hours of costly down time,
we have restarted our Zope machine.
Chris, could state your reasons for recommending
against FreeBSD? I have had no trouble in over five
years that I can directly attribute to FreeBSD, but I
am open-minded. That said, I don't mean to reopen the
On Tuesday 05 September 2006 3:58 am, Chris Withers wrote:
> Move hosters. FreeBSD for all its robustness is not something I'd
> recommend running Zope on...
Seriously? Why so? I've been running Zope exclusively on FreeBSD since
2001 without any known problems.
--
Kirk Strauser
The Day Compan
Ken Ara wrote:
One and a half days later, I am again unable to stop,
restart or kill Zope. My ISP host is making changes on
their network and I believe the problem is with them.
I am in a FreeBSD jail, sharing the machine with a DNS
server. It's 3am over there, and I wish I could do
something whi
One and a half days later, I am again unable to stop,
restart or kill Zope. My ISP host is making changes on
their network and I believe the problem is with them.
I am in a FreeBSD jail, sharing the machine with a DNS
server. It's 3am over there, and I wish I could do
something while waiting for th
You are right, Dieter. The ISP network admin had to
restart the machine. There seems to be no way to power
down and then power up the machine remotely.
Fortunately everything worked out. Thanks.
--- Dieter Maurer <[EMAIL PROTECTED]> wrote:
> Ken Ara wrote at 2006-9-2 23:43 -0700:
> > ...
> >I ca
Ken Ara wrote at 2006-9-2 23:43 -0700:
> ...
>I can't restart or stop Zope -
>'/usr/local/www/Zope/zope01/bin/zopectl stop' just
>produces '' for a long time - should I wait? I
>was unable to kill one of the python2.3 processes, and
>can't even reboot the machine, using 'shutdown -r
>now',
--On 3. September 2006 01:56:44 -0700 Ken Ara <[EMAIL PROTECTED]> wrote:
Actually, I need to read up on the netstat command.
Have a look:
geneva# netstat -anp
netstat: option requires an argument -- p
Please read the man page for netstat (man netstat). Nobody has
all options for all program
Actually, I need to read up on the netstat command.
Have a look:
geneva# netstat -anp
netstat: option requires an argument -- p
usage: netstat [-AaLnSW] [-f protocol_family | -p
protocol]
[-M core] [-N system]
netstat -i | -I interface [-abdnt] [-f
address_family]
--On 3. September 2006 01:18:55 -0700 Ken Ara <[EMAIL PROTECTED]> wrote:
Thanks Andreas,
I am logged in as root user.
Here is the result of 'top':
"top" is *not* the right tool to check for processes. Use "ps"!!!
I was able to kill one of the Zope processes but not
pid 945. Maybe it was
Thanks Andreas,
I am logged in as root user.
Here is the result of 'top':
last pid: 77998; load averages: 0.01, 0.06, 0.06
up
0+15:03:27 04:06:22
18 processes: 1 running, 11 sleeping, 5 stop
--On 2. September 2006 23:43:50 -0700 Ken Ara <[EMAIL PROTECTED]> wrote:
Hi all,
My Zope is stuck like never before. With my server on
another continent, 8 hours time difference, and on a
Sunday, I am pulling out my few remaining hairs...
Our box runs FreeBSD 5, Zope 2.78 (if I remember
corr
Hi all,
My Zope is stuck like never before. With my server on
another continent, 8 hours time difference, and on a
Sunday, I am pulling out my few remaining hairs...
Our box runs FreeBSD 5, Zope 2.78 (if I remember
correctly) and Squid.
The ISP has been preparing for a move and shifted some
mac
20 matches
Mail list logo