Ok, so I've made some progress, but I'm still not achieving full functionality.
When I start the capture daemon, the /var/log/tiplogs/capture.log read: Oct 31 14:17:29 ops capture[995]: pc3 - starting Oct 31 14:17:29 ops capture[995]: pc3 - Handshake complete. Owner 0, Group 101 Oct 31 14:17:29 ops capture[995]: pc3 - Ready! Listening on TCP port 49971
Clicking "CreateSlivers" adds this line: Oct 31 14:24:44 ops capture[995]: pc3 - input select interrupted, continuing
And "BootSlivers": Oct 31 14:25:21 ops capture[995]: pc3 - revoked Oct 31 14:25:21 ops capture[995]: pc3 - new run started Oct 31 14:25:21 ops capture[995]: pc3 - Handshake complete. Owner 0, Group 6000 Oct 31 14:25:21 ops capture[995]: pc3 - input select interrupted, continuing
T Ficarra
--- On Fri, 10/30/09, Cheng Cui
<ccui1@tigers.lsu.edu> wrote:
From: Cheng Cui <ccui1@tigers.lsu.edu> Subject: RE: [Testbed-admins] Ops as Tipserv To: "'Timothy Ficarra'" <t.ficarra@yahoo.com> Cc: Testbed-admins@flux.utah.edu Date: Friday, October 30, 2009, 5:05 PM
Hi Timothy,
Try
/usr/local/etc/rc.d/capture.sh start. And I want to remind you about the
follows that I met before.
“I
found the problem with the capture daemon problem in my OPS. The $bindir in the
"Setting up the Emulab Console Server" section looks has a typo in
the capture.ssh that the location of "capture" should be
"/usr/testbed/sbin/capture", not "bindir=/usr/local/sbin"”
Best
Regards,
Cheng
Cui
•
Frey Computing Services Center • Baton Rouge, LA 70803
From: Timothy Ficarra
[mailto:t.ficarra@yahoo.com]
Sent: Friday, October 30, 2009 3:57 PM
To: Cheng Cui
Cc: Testbed-admins@flux.utah.edu
Subject: RE: [Testbed-admins] Ops as Tipserv
Cheng,
I don't believe I have started the capture daemon. How would I go about doing
so?
T Ficarra
--- On Fri, 10/30/09, Cheng Cui <ccui1@tigers.lsu.edu>
wrote:
From: Cheng Cui <ccui1@tigers.lsu.edu>
Subject: RE: [Testbed-admins] Ops as Tipserv
To: "'Timothy Ficarra'" <t.ficarra@yahoo.com>
Cc: Testbed-admins@flux.utah.edu
Date: Friday, October 30, 2009, 4:11 PM
Hi Timothy,
Have you started the
“capture” daemon yet?
Best Regards,
Cheng Cui
• Frey Computing
Services Center • Baton Rouge, LA 70803
From: Timothy Ficarra
[mailto:t.ficarra@yahoo.com]
Sent: Friday, October 30, 2009 1:24 PM
To: Cheng Cui
Cc: Testbed-admins@flux.utah.edu
Subject: RE: [Testbed-admins] Ops as Tipserv
Cheng,
Thanks for the tip, but unfortunately it didn't resolve the problem. I
didn't make the cable myself; we had the appropriate type kicking around in
the laboratory.
Regards,
T Ficarra
--- On Fri, 10/30/09, Cheng Cui <ccui1@tigers.lsu.edu>
wrote:
From: Cheng Cui <ccui1@tigers.lsu.edu>
Subject: RE: [Testbed-admins] Ops as Tipserv
To: "'Timothy Ficarra'" <t.ficarra@yahoo.com>
Cc: Testbed-admins@flux.utah.edu
Date: Friday, October 30, 2009, 2:05 PM
Hi
Timothy,
I got
the same problem before. But you do not need to use the root account. Try
another ordinary user account.
By the
way, do you make the console cable yourself? How do you make the pinout of
the console cable? Mine has some encoding display problem.
Best
Regards,
Cheng
Cui
• Frey
Computing Services Center • Baton Rouge, LA 70803
From:
testbed-admins-bounces@flux.utah.edu
[mailto:testbed-admins-bounces@flux.utah.edu] On Behalf Of Timothy
Ficarra
Sent: Friday, October 30, 2009 12:07 PM
To: Testbed-admins@flux.utah.edu
Subject: Re: [Testbed-admins] Ops as Tipserv
I followed the provided instructions. When I run the console
command, I receive errors:
ops# /usr/testbed/bin/console pc3
Traceback (most recent call last):
File "/usr/testbed/bin/script_wrapper.py", line 2784, in
<module>
exitval = instance.apply();
File "/usr/testbed/bin/script_wrapper.py", line 1850, in
apply
rval,response = do_method("node",
"console", params);
File "/usr/testbed/bin/script_wrapper.py", line 203, in
do_method
ctx.load_cert(CERTIFICATE, CERTIFICATE)
File
"/usr/local/lib/python2.5/site-packages/M2Crypto/SSL/Context.py",
line 75, in load_cert
m2.ssl_ctx_use_privkey(self.ctx, keyfile)
M2Crypto.SSL.SSLError: no start line
*** /usr/testbed/bin/console:
/usr/testbed/bin/script_wrapper.py failed
T Ficarra
--- On Thu, 10/29/09, Leigh Stoller <stoller@flux.utah.edu>
wrote:
From: Leigh Stoller <stoller@flux.utah.edu>
Subject: Re: [Testbed-admins] Ops as Tipserv
To: "Timothy Ficarra" <t.ficarra@yahoo.com>
Cc: "Mike Hibler" <mike@flux.utah.edu>,
Testbed-admins@flux.utah.edu
Date: Thursday, October 29, 2009, 12:20 PM
>
The first line of those instructions state that they are written for
> a tipserv separate from ops. Are they still relevant to running the
> tipserv on ops?
Yes, they are ...
|
|
|
|