[sorry if this double posts]

yep, i can help

here are the two things you should always do as a first line of
defense (i have moved sites all over the place :) )

first, make sure that after you copy, the permissions for the
directory and folder are correct

something like....   sudo chown -R plone *    (where * = be in the
Default directory in /Applications/Plone2)
.. and if nescessary,  sudo chgrp -R admin *    (if that's the group
that your plone uses - should be by default on OSX)

and if that doesn't work.. then go to your instance home, in the 'bin'
directory and run

./zopectl

at the prompt, type 'debug'

and see what it says. Always a winner. The deal is that although
starting the server will return a process ID, if the startup throws an
exception, you'll never know it unless you use the debug.

When you get a clean start, stop the server and restart it normally.
I'd also advise going into zope.conf and setting the effective-user
entry to

effective-user plone

and using sudo to start the server, that is 'sudo ./zopectl start'

let me know if any of this solves it.

best, 
.j.


On Feb 16, 2005, at 6:46 PM, David Diskin wrote:

Does anyone have any experience moving data.fs from a Server (Zettai
in my case) to your Mac and getting it to work?  I stopped the Plone
site on my Mac, moved the data.fs and data.fs.index files into the
/var directory and restarted the Plone site.  I can't get to the ZMI. 
Says "connection refused".  Below is from the event log:

------
2005-02-16T17:48:38 INFO(0) Zope Ready to handle requests
------
2005-02-16T18:18:23 INFO(0) Z2 Caught signal SIGTERM
------
2005-02-16T18:18:23 INFO(0) Z2 Shutting down fast
------
2005-02-16T18:18:23 INFO(0) ZServer closing HTTP to new connections
------
2005-02-16T18:18:23 INFO(0) ZServer closing HTTP to new connections
------
2005-02-16T18:18:23 INFO(0) Zope Shutting down with exit code 0

Thanks.

David
==============================
David Diskin, david.diskin(at)verizon.net

[...]

jamesr wrote:
[...]

A follow-on to James' informative post:  It's bitten me a few times in the past
where I've had two machines both with users named "kjcole"... however one has
a user ID of 501, and the other has a user ID of 502...  Oops. ;-)  James'
solution would take care of that (among other things), but I'd be curious to
know if that was the source of trouble in your case.
[...]

james -

Thanks so much for this great email reply.  I'm a bit of a newbie on 
Unix, so please bear with me.

When you say to do:  sudo chown -R plone *
I'm not sure what this does exactly - changes ownership to everything 
in Plone directory recursively - so now i'm owner of all?
And does * =  "/Applications/Plone2" (which is where Plone2 is 
installed)

And in the sudo chgrp command below does * again = 
"/Applications/Plone2".

Thanks,

David

On Feb 16, 2005, at 7:20 PM, jamesr wrote:
[...]
==============================
David Diskin, david.diskin(at)verizon.net

Sorry - one more point of confusion for me is that doesn't the chown  
command require a user name (as the new owner)?  Thanks.

David

On Feb 16, 2005, at 7:54 PM, David Diskin wrote:
[...][...][...]
==============================
David Diskin, david.diskin(at)verizon.net

David Diskin wrote:[...][...]

A bit of a  breakdown of the command:

'sudo'     = grant god-like powers to do things mere mortals cannot
'chown -R' = change ownership recursively
'plone'    = to the user with the username 'plone'
'*'        = all files  in the CURRENT directory (a.k.a. folder)

So, first you want to 'cd /Applications/Plone2' or alternatively
'chown -R plone /Applications/Plone2/*' so that you don't change
the ownership of EVERY file everywhere on your computer to user plone.
This would be a "bad" thing: The universe as you know it would cease
to exist. ;-)

Really, you'll want to be sure that the 'plone' part (the username)
of the above command matches an actual username on your system, and
that the effective-user in the zope.conf file which James mentioned
is the same user.

You're telling Plone to run as if it was being started by a user
named 'plone' and that you want this user to have ownership of
all the files that are relevant to that application.
[...]
>>> Default directory in /Applications/Plone2)
>>> .. and if nescessary,  sudo chgrp -R admin *    (if that's the
group
>>> that your plone uses - should be by default on OSX)[...]

Kevin,

Thanks very much for the explanation.  The username below - should it 
be 'plone' since that is startup,conf has the entry runasuser=plone 
which matches what's in the zope.conf for effective user?  Or, should 
it really be a user on my Mac system and then I would need to change 
both startup.conf and zope.conf??

For my other Plone site on the Mac, I did not change any of these 
settings.  But, also I did an export/import of plone.zexp to get 
started.

Thanks,

David
On Feb 17, 2005, at 8:08 AM, Kevin Cole wrote:
[...][...]
>>>
>>> Thanks so much for this great email reply.  I'm a bit of a newbie
on 
>>>  Unix, so please bear with me.
>>>
>>> When you say to do:  sudo chown -R plone *
>>> I'm not sure what this does exactly - changes ownership to 
>>> everything  in Plone directory recursively - so now i'm owner of 
>>> all?
>>> And does * =  "/Applications/Plone2" (which is where Plone2 is  
>>> installed)[...]
>>> "/Applications/Plone2".
>>>
>>> Thanks,
>>>
>>> David
>>>
>>> On Feb 16, 2005, at 7:20 PM, jamesr wrote:
>>>
>>>> something like....   sudo chown -R plone *    (where * = be in
the
>>>> Default directory in /Applications/Plone2)
>>>> .. and if nescessary,  sudo chgrp -R admin *    (if that's the
group
>>>> that your plone uses - should be by default on OSX)[...]
==============================
David Diskin, david.diskin(at)verizon.net

We're just all full 'o help today :)

It should be mentioned that using 'sudo' (granting superuser
priveledges on a command-by-command basis) has one advantage
(otherwise, why not just start it as plone?)

When you use sudo, zope can aquire the sockets/ports/networking as
root - to give you access to port 80, for instance - and THEN drop
into the plone user to stop bad things happening if Stuff Goes Wrong
(TM). Without it, zope could possibly be told to zark off by the OS
when getting 'priviledged' (under 1024) ports.

and maybe other things, hm? 


On Thu, 17 Feb 2005 11:45:39 -0500, David Diskin
<david.diskin(at)verizon.net> wrote:[...]

On Thursday 17 February 2005 12:49 pm, jamesr wrote:[...]

This is unrelated entirely to sudo.

"sudo" merely means "run this command as user xxx". It doesn't imply 
anything about the command releasing privileges before completion.

Separate from this, though, Zope already has an "effective-user" 
mechanism: in zope.conf, you specify what user Zope should run as, so 
that, while you may have to start up as root (to get access to port 
80), you can drop down to user "zope" or "nobody" or whatever to have 
a safer experience running Zope/Plone after that.

In any event, though, it's not a good idea to run Zope/Plone as port 
80, except on your development box. Zope/Plone should always be 
fronted by a proxy server (like Apache) running on 80, and proxying 
to 8080. You don't want to expose a naked zope to the world.

- j.
[...]

well, root is implied in the escalation, correct? But yes, the program
has to be nice enough to give up the new found powers, which zope
does. Try that with a poltician...

remember: everytime you run zope on port 80, god kills a kitten. 

i kid, i kid..

.j.


On Thu, 17 Feb 2005 12:55:39 -0500, Joel Burton <joel(at)joelburton.com>
wrote:[...]

Joel Burton wrote:
[...]

Yeah. The FCC fines you big time for that. ;-)
[...]