I tried to run bin/instance fg. It gave me the following
error:"/home/kattkung/webapps/zope3/parts/instance/bin/runzope" -X
"debug-mode=on"Traceback (most recent call last):  File
"/home/kattkung/webapps/zope3/parts/zope2/lib/python/Zope2/Startup/run.py",
line 56, in ?    run()  File
"/home/kattkung/webapps/zope3/parts/zope2/lib/python/Zope2/Startup/run.py",
line 21, in run    starter.prepare()  File
"/home/kattkung/webapps/zope3/parts/zope2/lib/python/Zope2/Startup/__init__.py",
line 96, in prepare    self.setupServers()  File
"/home/kattkung/webapps/zope3/parts/zope2/lib/python/Zope2/Startup/__init__.py",
line 229, in setupServers    raise
ZConfig.ConfigurationError(socket_errZConfig.ConfigurationError: There was a
problem starting a server of type "HTTPServer". This may mean that your user
does not have permission to bind to the port which the server is trying to use
or the port may already be in use by another application. (Address already in
use)I tried: "bin/instance stop" It says: "daemon manager not running" I only
have one application under this port number. How come it is occupied. I can't
get into ZMI either since it Proxy Error
The proxy server received an invalid
response from an upstream server.
The proxy server could not handle the request GET /.
Reason: Error reading from remote serverI am wondering if anybody can tell how
to stop the application in consoleThanks!Wendy Smith
Science Bridge Technology, LLC
Fairfax, VA 22030
Tel 703 352 5693
Cell 703 362 8098
http://www.scibridgetech.com

Hi Wendy,

After stopping your instance (even if it says it's not running, I'd stop 
it to be certain), look under the /var directory of it and confirm that 
you don't see any Z2.pid file.  If you do, then delete it as it should 
only exist while the process is running, typically.

If it was there when you have stopped your instance, then this may fix 
your problem.  If it wasn't there, then I'd suspect that your zope.conf 
and some other instance's zope.conf are both using the same https port 
to listen on.  If this is a hosted instance on a shared server, I'd 
recommend having the vendor check into that.  Otherwise - if you're 
hosting it yourself and have other instances on the server, then you can 
verify this yourself.

One other reason I've seen this come up is when one instance is copied 
to another and some tweaks have been made to existing runzope, zopectl, 
and zope.conf files, but not all of the necessary changes have been 
made, and so there is still some reference to the original instance (for 
instance, if the INSTANCE_HOME variable in runzope or the zope.conf is 
still set to the path of some other instance.)

I hope one of these tips helps - best of luck!

-Ken

wendy(at)scibridgetech.com wrote:[...]

Hey Ken! Thanks for the detailed reply :-)

On Fri, Feb 15, 2008 at 10:23:12PM -0600, Ken Wasetis wrote:[...]
[...]

Thank you very much for the input. Yes, I did rename an old src folder to a new
one. together rename an old develop-products folder to a new one. Amazingly, it
is not only use the old folder I renamed it. All stuff inside that folder are
gone some place. It includes all the products I installed. However, the
application still works. Well, so much to learn. Before I know your way of
killing it. I killed it by unix command: kill -9 process id. However, your
explanation makes great sense.Thank you very much.Wendy Smith
Science Bridge Technology, LLC
Fairfax, VA 22030
Tel 703 352 5693
Cell 703 362 8098
http://www.scibridgetech.com

-------- Original Message --------
Subject: Re: [ZPUGDC] how to shut down application from console?
From: Ken Wasetis <ken(at)wasetis.net>
Date: Fri, February 15, 2008 11:23 pm
To: zpugdc(at)lists.zpugdc.org

Hi Wendy,

After stopping your instance (even if it says it's not running, I'd stop 
it to be certain), look under the /var directory of it and confirm that 
you don't see any Z2.pid file.  If you do, then delete it as it should 
only exist while the process is running, typically.

If it was there when you have stopped your instance, then this may fix 
your problem.  If it wasn't there, then I'd suspect that your zope.conf 
and some other instance's zope.conf are both using the same https port 
to listen on.  If this is a hosted instance on a shared server, I'd 
recommend having the vendor check into that.  Otherwise - if you're 
hosting it yourself and have other instances on the server, then you can 
verify this yourself.

One other reason I've seen this come up is when one instance is copied 
to another and some tweaks have been made to existing runzope, zopectl, 
and zope.conf files, but not all of the necessary changes have been 
made, and so there is still some reference to the original instance (for 
instance, if the INSTANCE_HOME variable in runzope or the zope.conf is 
still set to the path of some other instance.)

I hope one of these tips helps - best of luck!

-Ken

wendy(at)scibridgetech.com wrote:[...]

[...]