perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Soichi,

My guess would be that whatever series of events led to your initial problem has resulted in an incorrect API key in your regular_testing.conf file. To fix that, run the following:

cd /opt/esmond

source /opt/rh/python27/enable

/opt/rh/python27/root/usr/bin/virtualenv --prompt="(esmond)" .

. bin/activate

python esmond/manage.py add_ps_metadata_post_user perfsonar

That will output a long API key. Copy that and paste it into /opt/perfsonar_ps/regular_testing/etc/regular_testing.conf in all three instances of the 'password' property located in the <measuremeny_archive> blocks. Then restart the regular_testing with "/sbin/service regular_testing restart".

Thanks,

Andy

On Nov 12, 2014, at 2:35 PM, Soichi Hayashi <> wrote:

OK .. still nothing else posted on /serviceTest.

Also, I started seeing the same error message again (or I always have?)

2014/11/12 14:28:57 (18410) DEBUG> EsmondBase.pm:257 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::send_post - Esmond repsonse:
2014/11/12 14:28:57 (18410) ERROR> EsmondBase.pm:53 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::__ANON__ - Error writing metadata (401) 401 UNAUTHORIZED
2014/11/12 14:28:57 (18410) ERROR> MeasurementArchiveChild.pm:209 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::handle_results - Problem storing results: Error writing metadata: 401 UNAUTHORIZED
2014/11/12 14:28:57 (18410) ERROR> MeasurementArchiveChild.pm:125 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::__ANON__ - Problem handling test results: Problem storing results: Error writing metadata: 401 UNAUTHORIZED at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Master/MeasurementArchiveChild.pm line 122.

I will rebuild the instance later this week, unless there is another way to fix this.

Soichi

On Wed, Nov 12, 2014 at 12:54 PM, Soichi Hayashi <> wrote:

Ah.. I should've checked. 

I found several processes owned by postgres, so I've killed them manually.

[root@perfsonar-bw ~]# ps -ef | grep post
postgres  2024     1  0 Oct21 ?        00:00:26 /usr/bin/postmaster -p 5432 -D /var/lib/pgsql/data

I've re-run the steps you suggested, and everything ran successfully except the last step.

[root@perfsonar-bw log]# /etc/init.d/regular_testing start
/opt/perfsonar_ps/regular_testing/bin/daemon --config=/opt/perfsonar_ps/regular_testing/etc/regular_testing.conf --pidfile=regular_testing.pid --piddir=/var/run --logger=/opt/perfsonar_ps/regular_testing/etc/regular_testing-logger.conf --user=perfsonar --group=perfsonar --daemonize
/opt/perfsonar_ps/regular_testing/bin/daemon already running: 28281
 at /opt/perfsonar_ps/regular_testing/bin/daemon line 227
        main::lockPIDFile('/var/run', 'regular_testing.pid') called at /opt/perfsonar_ps/regular_testing/bin/daemon line 46
/etc/init.d/regular_testing start: perfSONAR Regular Testing could not be started

Instead, I just rebooted my instance. Now, I am seeing some data posted to my esmond!

> http://perfsonar-bw.grid.iu.edu/esmond/perfsonar/archive/?format=json

But.. I am still seeing nothing here ...

> http://perfsonar-bw.grid.iu.edu/serviceTest/psGraph.cgi

I will check later again.

Thanks!

Soichi

On Wed, Nov 12, 2014 at 12:33 PM, Andrew Lake <> wrote:

Hi Soichi,

You probably don't need to do a complete re-install, just need to get postgres right. It looks like the init script is neither able to stop or start it properly, yet something is accepting connections from the client. Are there any old postgres processes lying around? or anything interesting in /var/lib/pgsql/pgstartup.log?

Thanks,
Andy

On Nov 12, 2014, at 12:20 PM, Soichi Hayashi <> wrote:

> Andy,
>
> I stopped the DB (was stopped already?) but I am still seeing the same problem.
>
> [root@perfsonar-bw ~]# rm -rf /var/lib/pgsql/data/*
> [root@perfsonar-bw ~]# /etc/init.d/postgresql stop
> Stopping postgresql service:                               [FAILED]
> [root@perfsonar-bw ~]# /opt/perfsonar_ps/toolkit/scripts/system_environment/configure_esmond
> Initializing database:                                     [  OK  ]
> Starting postgresql service:                               [FAILED]
> Waiting for postgresql to complete startup
> could not change directory to "/root"
> Password:
> psql: FATAL:  password authentication failed for user "postgres"
> could not change directory to "/root"
> Password:
>
> Maybe I should just re-install the whole toolkit?
>
> Soichi
>
> On Wed, Nov 12, 2014 at 10:10 AM, Andrew Lake <> wrote:
> Hi Soichi.
>
> After running 'rm -rf /var/lib/pgsql/data/*' try stopping postgresql with "/sbin/service postgresql stop" then proceeding with the rest of the commands. My guess would be the postgresql is already running and still has the old password loaded.
>
> Thanks,
> Andy
>
>
>
> On Nov 12, 2014, at 9:39 AM, Soichi Hayashi <> wrote:
>
>> Hello.
>>
>> I am having the same problem on perfsonar-bw.grid.iu.edu.
>>
>> When I run configure_esmond, it asks me for password,
>>
>> [root@perfsonar-bw ~]# rm -rf /var/lib/pgsql/data/*
>> [root@perfsonar-bw ~]# /opt/perfsonar_ps/toolkit/scripts/system_environment/configure_esmond
>> Initializing database:                                     [  OK  ]
>> Starting postgresql service:                               [FAILED]
>> Waiting for postgresql to complete startup
>> could not change directory to "/root"
>> Password:
>>
>>  I don't know what password it is asking.. what password should I enter here?
>>
>> Soichi
>>
>>
>>
>> On Tue, Oct 14, 2014 at 3:50 PM, Andrew Lake <> wrote:
>> Yes it will delete your data. On the flip side, if you have collected data then you shouldn't have this problem unless you are really just trying to mess with me  :)
>>
>> To anyone else reading this thread, in general, please do not run these commands. Under normal circumstances you shouldn't have to. If you have no data in the graphs as indicated in the subject there is a very high chance its something else entirely. Please contact the list with information about your specific case if you are unsure.
>>
>>
>> On Oct 14, 2014, at 3:45 PM, "John-Paul Robinson (Campus)" <> wrote:
>>
>> > Does this kill data collected so far?
>> >
>> > ~jpr
>> >
>> >> On Oct 14, 2014, at 8:59 AM, "Andrew Lake" <> wrote:
>> >>
>> >> Hi,
>> >>
>> >> Postgres user. Try running the following:
>> >>
>> >> rm -rf /var/lib/pgsql/data/*
>> >> /opt/perfsonar_ps/toolkit/scripts/system_environment/configure_esmond
>> >> /opt/perfsonar_ps/toolkit/scripts/system_environment/configure_regular_testing
>> >> /etc/init.d/httpd restart
>> >> /etc/init.d/regular_testing start
>> >>
>> >> Thanks,
>> >> Andy
>> >>
>> >>
>> >>> On Oct 14, 2014, at 9:54 AM, wrote:
>> >>>
>> >>> hi,
>> >>>
>> >>> Get the Error retrieving test data: undefined
>> >>>
>> >>> The django log shows this:
>> >>>
>> >>> File
>> >>> "/opt/esmond/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg
>> >>> 2/base.py", line 182, in _cursor
>> >>>  self.connection = Database.connect(**conn_params)
>> >>> File "/opt/esmond/lib/python2.7/site-packages/psycopg2/__init__.py", line
>> >>> 164, in connect
>> >>>  conn = _connect(dsn, connection_factory=connection_factory, async=async)
>> >>>
>> >>>
>> >>> OperationalError: FATAL:  Ident authentication failed for user "esmond"
>> >>>
>> >>>
>> >>> Is this supposed to be mysql user or postgres user?
>> >>>
>> >>> Mark
>> >>
>>
>>
>
>