Hey Cris,

the logs are in <INSTANCE_PATH>/var/log/

I would guess they didn't start due to permission issues. Did you start 
supervisord as root? When using the production buildout, the different 
processes will run under different user privileges according to site.cfg. Maybe 
some of those users (e.g. the zope user) don't exist in your system?


On Oct 5, 2011, at 1:39 PM, Chris McAnally wrote:

> 
> Another issue once it started  installing it didn't completely work yet.
> 
> When I run ./bin/supervisorctl status
> 
> I get:
> 
> Balancer      FATAL   Exited too quickly (process log may have details)
> Cache         RUNNING pid 22398, uptime 0:01:17
> instance1     FATAL   Exited too quickly (process log may have details)
> instance2     FATAL   Exited too quickly (process log may have details)
> main          RUNNING pid 22399, uptime 0:01:17
> ploneftp      RUNNING pid 22394, uptime 0:01:17
> Transcodedaemon       RUNNING pid 22393, uptime 0:01:17
> Zeo           FATAL   Exited too quickly (process log may have details)
> 
> 
> Where is the process log, and any idea what's missing?
> 
> ---
> I'm running an Ubuntu 11.04 server, and I'd run through the steps in the
> INSTALL.txt file...
> 
> 
> 
> ---
> Chris McAnally
> Director of Technology
> Shanghai Community International School
> http://www.scischina.org <http://www.scischina.org/>
> Phone:  8621-6261-4338
> Cell: 18621187481
> Extension:  7162
> 
> 
> 
> 
> 
> 
> On 10/1/11 8:00 PM, "[email protected]"
> <[email protected]> wrote:
> 
>> Send Discuss mailing list submissions to
>>      [email protected]
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>>      http://lists.plumi.org/listinfo/discuss
>> or, via email, send a message with subject or body 'help' to
>>      [email protected]
>> 
>> You can reach the person managing the list at
>>      [email protected]
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Discuss digest..."
>> 
>> 
>> Today's Topics:
>> 
>>  1. Re: Discuss Digest, Vol 52, Issue 17 (Chris McAnally)
>>  2. Plumi Installation problem - GFWOC (Chris McAnally)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Sat, 1 Oct 2011 04:31:10 +0000
>> From: Chris McAnally <[email protected]>
>> To: "[email protected]" <[email protected]>
>> Subject: Re: [plumi-discuss] Discuss Digest, Vol 52, Issue 17
>> Message-ID: <caacb854.2178f%[email protected]>
>> Content-Type: text/plain; charset="us-ascii"
>> 
>> No Dimitris , it's constant, both at home and at work...
>> 
>> 
>>> 
>>> Message: 1
>>> Date: Thu, 29 Sep 2011 15:25:04 +0300
>>> From: Dimitris Moraitis <[email protected]>
>>> To: Discussion about software development on Plumi
>>>     <[email protected]>
>>> Subject: Re: [plumi-discuss] Installation issues
>>> Message-ID: <[email protected]>
>>> Content-Type: text/plain; charset="us-ascii"
>>> 
>>> Hi Chris.
>>> 
>>> your problem looks like a temporary network issue. Did you try again? Do
>>> you get the same error each time you run buildout?
>>> 
>>> Cheers,
>>> Dimitris
>> 
>> 
>> 
>> ------------------------------
>> 
>> Message: 2
>> Date: Sat, 1 Oct 2011 06:01:41 +0000
>> From: Chris McAnally <[email protected]>
>> To: "[email protected]" <[email protected]>
>> Subject: [plumi-discuss] Plumi Installation problem - GFWOC
>> Message-ID: <caaccd01.2184a%[email protected]>
>> Content-Type: text/plain; charset="us-ascii"
>> 
>> 
>> Figured it out, it's the Great Firewall of China.  I'd thought like you
>> that it was some strange problem with our network, but it also didn't work
>> at home.... However if I connect to the USA via OpenVPN,it works!
>> 
>> Congratulations guys you've been blocked by the Chinese government!  Plumi
>> now takes it's place alongside Amnesty International and Youtube.
>> 
>> Sometimes I really hate living here...
>> 
>> Thanks for the help Dimitris.
>> 
>> ---
>> Chris McAnally
>> Director of Technology
>> Shanghai Community International School
>> http://www.scischina.org <http://www.scischina.org/>
>> Phone:  8621-6261-4338
>> Cell: 18621187481
>> Extension:  7162
>> 
>> 
>> 
>> 
>> 
>> 
>> On 9/30/11 8:00 PM, "[email protected]"
>> <[email protected]> wrote:
>> 
>>> Send Discuss mailing list submissions to
>>>     [email protected]
>>> 
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>     http://lists.plumi.org/listinfo/discuss
>>> or, via email, send a message with subject or body 'help' to
>>>     [email protected]
>>> 
>>> You can reach the person managing the list at
>>>     [email protected]
>>> 
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of Discuss digest..."
>>> 
>>> 
>>> Today's Topics:
>>> 
>>>  1. Re: Installation issues (Dimitris Moraitis)
>>> 
>>> 
>>> ----------------------------------------------------------------------
>>> 
>>> Message: 1
>>> Date: Thu, 29 Sep 2011 15:25:04 +0300
>>> From: Dimitris Moraitis <[email protected]>
>>> To: Discussion about software development on Plumi
>>>     <[email protected]>
>>> Subject: Re: [plumi-discuss] Installation issues
>>> Message-ID: <[email protected]>
>>> Content-Type: text/plain; charset="us-ascii"
>>> 
>>> Hi Chris.
>>> 
>>> your problem looks like a temporary network issue. Did you try again? Do
>>> you get the same error each time you run buildout?
>>> 
>>> Cheers,
>>> Dimitris
>>> 
>>> On Sep 29, 2011, at 12:44 PM, Chris McAnally wrote:
>>> 
>>>> 
>>>> Hello, 
>>>> 
>>>> I've tried finding a solution with google & on the Plumi site, but no
>>>> luck to date.  It's basically a connection reset when I run the
>>>> buildout.  What am I doing wrong?
>>>> 
>>>> My server:
>>>> Ubuntu 11.04 
>>>> 
>>>> I've run all the apt-get commands listed in the INSTALL.txt and edited
>>>> the site.cfg file placing my site name and the url of the encoder site,
>>>> and set a secret key.
>>>> 
>>>> As root I ran 
>>>> python2.6 bootstrap.py -c production.cfg -v 1.4.3
>>>> 
>>>> And got no errors, however when I ran:
>>>> ./bin/buildout -c production.cfg
>>>> 
>>>> I got:
>>>> ---
>>>> root@video:/iscsidrive/plumi.app-4.2.2# ./bin/buildout -c devel.cfg
>>>> While:
>>>>  Initializing.
>>>> 
>>>> An internal error occured due to a bug in either zc.buildout or in a
>>>> recipe being used:
>>>> Traceback (most recent call last):
>>>>  File 
>>>> "/iscsidrive/plumi.app-4.2.2/eggs/zc.buildout-1.4.3-py2.6.egg/zc/buildou
>>>> t
>>>> /buildout.py", line 1659, in main
>>>>    user_defaults, windows_restart, command)
>>>>  File 
>>>> "/iscsidrive/plumi.app-4.2.2/eggs/zc.buildout-1.4.3-py2.6.egg/zc/buildou
>>>> t
>>>> /buildout.py", line 182, in __init__
>>>>    data['buildout'].copy(), override))
>>>>  File 
>>>> "/iscsidrive/plumi.app-4.2.2/eggs/zc.buildout-1.4.3-py2.6.egg/zc/buildou
>>>> t
>>>> /buildout.py", line 1333, in _open
>>>>    eresult = _open(base, extends.pop(0), seen, dl_options, override)
>>>>  File 
>>>> "/iscsidrive/plumi.app-4.2.2/eggs/zc.buildout-1.4.3-py2.6.egg/zc/buildou
>>>> t
>>>> /buildout.py", line 1335, in _open
>>>>    _update(eresult, _open(base, fname, seen, dl_options, override))
>>>>  File 
>>>> "/iscsidrive/plumi.app-4.2.2/eggs/zc.buildout-1.4.3-py2.6.egg/zc/buildou
>>>> t
>>>> /buildout.py", line 1283, in _open
>>>>    path, is_temp = download(filename)
>>>>  File 
>>>> "/iscsidrive/plumi.app-4.2.2/eggs/zc.buildout-1.4.3-py2.6.egg/zc/buildou
>>>> t
>>>> /download.py", line 96, in __call__
>>>>    local_path, is_temp = self.download(url, md5sum, path)
>>>>  File 
>>>> "/iscsidrive/plumi.app-4.2.2/eggs/zc.buildout-1.4.3-py2.6.egg/zc/buildou
>>>> t
>>>> /download.py", line 173, in download
>>>>    tmp_path, headers = urllib.urlretrieve(url, tmp_path)
>>>>  File "/usr/lib/python2.6/urllib.py", line 93, in urlretrieve
>>>>    return _urlopener.retrieve(url, filename, reporthook, data)
>>>>  File "/usr/lib/python2.6/urllib.py", line 239, in retrieve
>>>>    fp = self.open(url, data)
>>>>  File "/usr/lib/python2.6/urllib.py", line 207, in open
>>>>    return getattr(self, name)(url)
>>>>  File "/usr/lib/python2.6/urllib.py", line 349, in open_http
>>>>    errcode, errmsg, headers = h.getreply()
>>>>  File "/usr/lib/python2.6/httplib.py", line 1064, in getreply
>>>>    response = self._conn.getresponse()
>>>>  File "/usr/lib/python2.6/httplib.py", line 990, in getresponse
>>>>    response.begin()
>>>>  File "/usr/lib/python2.6/httplib.py", line 391, in begin
>>>>    version, status, reason = self._read_status()
>>>>  File "/usr/lib/python2.6/httplib.py", line 349, in _read_status
>>>>    line = self.fp.readline()
>>>>  File "/usr/lib/python2.6/socket.py", line 427, in readline
>>>>    data = recv(1)
>>>> IOError: [Errno socket error] [Errno 104] Connection reset by peer
>>>> 
>>>> ---
>>>> 
>>>> Any help would be appreciated.
>>>> 
>>>> ---
>>>> Chris McAnally
>>>> Director of Technology
>>>> Shanghai Community International School
>>>> http://www.scischina.org
>>>> Phone:  8621-6261-4338
>>>> Cell: 18621187481
>>>> Extension:  7162
>>>> 
>>>> _______________________________________________
>>>> Discuss mailing list
>>>> [email protected]
>>>> http://lists.plumi.org/listinfo/discuss
>>> 
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL: 
>>> <http://lists.plumi.org/pipermail/discuss/attachments/20110929/0f6a3f83/a
>>> t
>>> tachment-0001.html>
>>> 
>>> ------------------------------
>>> 
>>> _______________________________________________
>>> Discuss mailing list
>>> [email protected]
>>> http://lists.plumi.org/listinfo/discuss
>>> 
>>> 
>>> End of Discuss Digest, Vol 52, Issue 17
>>> ***************************************
>> 
>> 
>> 
>> ------------------------------
>> 
>> _______________________________________________
>> Discuss mailing list
>> [email protected]
>> http://lists.plumi.org/listinfo/discuss
>> 
>> 
>> End of Discuss Digest, Vol 53, Issue 1
>> **************************************
> 
> _______________________________________________
> Discuss mailing list
> [email protected]
> http://lists.plumi.org/listinfo/discuss

_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss

Reply via email to