perfsonar-user - Re: [perfsonar-user] no graphs since upgrade to 3.4
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Andrew Lake <>
- To: Soichi Hayashi <>
- Cc: "John-Paul Robinson (Campus)" <>, "" <>, "" <>
- Subject: Re: [perfsonar-user] no graphs since upgrade to 3.4
- Date: Wed, 12 Nov 2014 12:33:38 -0500
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
>> >>
>>
>>
>
>
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Soichi Hayashi, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Andrew Lake, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Soichi Hayashi, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Andrew Lake, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Soichi Hayashi, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Soichi Hayashi, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Andrew Lake, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Soichi Hayashi, 11/14/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Andrew Lake, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Soichi Hayashi, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Soichi Hayashi, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Andrew Lake, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Soichi Hayashi, 11/12/2014
- Re: [perfsonar-user] no graphs since upgrade to 3.4, Andrew Lake, 11/12/2014
Archive powered by MHonArc 2.6.16.