Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfSonar installation trouble shooting

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfSonar installation trouble shooting


Chronological Thread 
  • From: "Yao,Rong" <>
  • To: Andrew Lake <>, Michael Johnson <>
  • Cc: "Adams,Andrew M" <>, "" <>
  • Subject: Re: [perfsonar-user] perfSonar installation trouble shooting
  • Date: Mon, 23 May 2016 17:34:16 +0000
  • Accept-language: en-US
  • Ironport-phdr: 9a23:UI07oBzaYIz5LuPXCy+O+j09IxM/srCxBDY+r6Qd 0OoUIJqq85mqBkHD//Il1AaPBtWKrakVwLOP6+jJYi8p39WoiDg6aptCVhsI24 09vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6kO74TNaIBjjLw09 fr2zQd6DyZ/mnLnro9X6WEZhunmUWftKNhK4rAHc5IE9oLBJDeIP8CbPuWZCYO 9MxGlldhq5lhf44dqsrtY4q3wD89pozcNLUL37cqIkVvQYSW1+ayFmrPHs4DDF QRGC+TM4W2Yb2k5BBQTUxBzhGJH8rn2+/s980ymTMMm+b7c0Xy+l6e8/TR240g 8ILTg++yfWl4p9gL8N8zy7oBkqib/dZ8WvM/xxNOuJR+ITQkJEUs9XWyFbGYS6 KYwVALxSbq5js4Dhqg5W/lOFDg62Cbaqk2cQiw==

Greetings, Andy,

Thanks for your reply.

"/etc/init.d/perfsonar-regulartesting restart” helps. It restarts without complain.

But "/etc/init.d/perfsonar-lsregistrationdaemon restart” not, 

[root@r1prpps01 ~]# /etc/init.d/perfsonar-lsregistrationdaemon restart

/etc/init.d/perfsonar-lsregistrationdaemon stop: LS Registration Daemon (pid ?) not running

waiting...

/usr/lib/perfsonar/bin/lsregistrationdaemon.pl --config=/etc/perfsonar/lsregistrationdaemon.conf --pidfile=/var/run/lsregistrationdaemon.pid --logger=/etc/perfsonar/lsregistrationdaemon-logger.conf --user=perfsonar --group=perfsonar

/etc/init.d/perfsonar-lsregistrationdaemon start: LS Registration Daemon could not be started


Regards,

Rong




From: Andrew Lake <>
Date: Monday, May 23, 2016 at 12:21 PM
To: Michael Johnson <>, Rong Yao <>
Cc: "Adams,Andrew M" <>, "" <>
Subject: Re: [perfsonar-user] perfSonar installation trouble shooting

Hi,

For the last two it looks like they are already running. You might want to try feeding them "/etc/init.d/perfsonar-regulartesting restart” and "/etc/init.d/perfsonar-lsregistrationdaemon restart” so it will stop any existing instances and then start them back-up. 

Thanks,
Andy


On May 23, 2016 at 12:11:09 PM, Yao,Rong () wrote:

Greetings, Michael,

Thank you very much for your explanation. I just found that the
documentation has updated to reflect this change.

I started the following services without a problem:

[root@r1prpps01 init.d]# /etc/init.d/bwctl-server start
/etc/init.d/bwctl-server start: bwctl-server (pid 3819) already running
[root@r1prpps01 init.d]# /etc/init.d/owamp-server start
/etc/init.d/owamp-server start: owamp-server (pid 13546) already running
[root@r1prpps01 init.d]# /etc/init.d/cassandra start
Starting Cassandra: OK


However, I can¹t start perfsonar-regulartesting and
perfsonar-lsregistrationdaemon
[root@r1prpps01 init.d]# /etc/init.d/perfsonar-regulartesting start
/usr/lib/perfsonar/bin/regulartesting.pl
--config=/etc/perfsonar/regulartesting.conf --pidfile=regulartesting.pid
--piddir=/var/run --logger=/etc/perfsonar/regulartesting-logger.conf
--user=perfsonar --group=perfsonar --daemonize
/usr/lib/perfsonar/bin/regulartesting.pl already running: 13579
at /usr/lib/perfsonar/bin/regulartesting.pl line 227
main::lockPIDFile('/var/run', 'regulartesting.pid') called at
/usr/lib/perfsonar/bin/regulartesting.pl line 46
/etc/init.d/perfsonar-regulartesting start: perfSONAR Regular Testing
could not be started

[root@r1prpps01 init.d]# /etc/init.d/perfsonar-lsregistrationdaemon start
/usr/lib/perfsonar/bin/lsregistrationdaemon.pl
--config=/etc/perfsonar/lsregistrationdaemon.conf
--pidfile=/var/run/lsregistrationdaemon.pid
--logger=/etc/perfsonar/lsregistrationdaemon-logger.conf --user=perfsonar
--group=perfsonar
/etc/init.d/perfsonar-lsregistrationdaemon start: LS Registration Daemon
could not be started

Please advise if you know if I missed anything?

Are those the five service total that I need to start?

Thanks again,
Rong





On 5/12/16, 8:10 PM, "Michael Johnson" <> wrote:

>Hi Rong,
>
>The owampd and bwctld services were renamed in the latest perfSONAR
>version to owamp-server and bwctl-server respectively. Also,
>ls_registration_daemon is now perfsonar-lsregistrationdaemon. You will
>also want to start perfsonar-regulartesting and cassandra (this is
>esmond, the measurement archive). That should be all the services you
>need to start.
>
>You don't need the central management bundle to do basic testing, only if
>you wish to run a mesh.
>
>Let us know if you have further questions.
>
>Thanks,
>Michael
>
>On Thu, May 12, 2016 at 03:25:51PM +0000, Yao,Rong wrote:
>>Dear perfsonar user support,
>>
>>I installed perfsonar-toolkit on a RHEL 6.7 box following the
>>installation documentation:
>> http://docs.perfsonar.net/install_centos.html
>>
>>I haven¹t installed perfSONAR Central Management yet. (Is this required
>>for the time being?)
>>
>>There are several things puzzled me:
>>
>>
>> 1. I don't find /etc/bwctld, instead, I have /etc/bwctl-server
>> 2. In section "start your services²,
>>
>> I don¹t find /etc/init.d/bwctld, instead, I have
>>/etc/init.d/bwctl-server
>> I don¹t find /etc/init.d/owampd, instead, I have
>>/etc/init.d/owamp-server
>> I don¹t find /etc/init.d/ls_registration_daemon
>>
>>After I access the web interface, it looks like the following image.
>>Please kindly advise me if there is anything I missed Š
>>
>>Thanks!
>>Rong
>>
>>------------------------
>>
>>Rong Yao
>>
>>Applications Systems Analyst
>>
>>Research IS & Technology Services
>>
>>Email: | Tel: (713) 563-2687
>>
>>[cid:76863B69-0220-4D0E-8DA4-74746D02B7E5]
>>The information contained in this e-mail message may be privileged,
>>confidential, and/or protected from disclosure. This e-mail message may
>>contain protected health information (PHI); dissemination of PHI should
>>comply with applicable federal and state laws. If you are not the
>>intended recipient, or an authorized representative of the intended
>>recipient, any further review, disclosure, use, dissemination,
>>distribution, or copying of this message or any attachment (or the
>>information contained therein) is strictly prohibited. If you think that
>>you have received this e-mail message in error, please notify the sender
>>by return e-mail and delete all references to it and its contents from
>>your systems.
>
>

The information contained in this e-mail message may be privileged, confidential, and/or protected from disclosure. This e-mail message may contain protected health information (PHI); dissemination of PHI should comply with applicable federal and state laws. If you are not the intended recipient, or an authorized representative of the intended recipient, any further review, disclosure, use, dissemination, distribution, or copying of this message or any attachment (or the information contained therein) is strictly prohibited. If you think that you have received this e-mail message in error, please notify the sender by return e-mail and delete all references to it and its contents from your systems.

The information contained in this e-mail message may be privileged, confidential, and/or protected from disclosure. This e-mail message may contain protected health information (PHI); dissemination of PHI should comply with applicable federal and state laws. If you are not the intended recipient, or an authorized representative of the intended recipient, any further review, disclosure, use, dissemination, distribution, or copying of this message or any attachment (or the information contained therein) is strictly prohibited. If you think that you have received this e-mail message in error, please notify the sender by return e-mail and delete all references to it and its contents from your systems.




Archive powered by MHonArc 2.6.16.

Top of Page