Re: Unrecognized service

Hmm no, I wasn't able to find it. So I definitely didn't restart it in the
interim.

I'm thinking I must have used the command incorrectly since I didn't really
understand what it was doing. Maybe I invoked it from the wrong place? But
I was at the root, according to the prompt I pasted, so I don't really
understand it either.

root(at)server# ps ax | grep post

On Thu, Apr 17, 2014 at 10:31 PM, Adrian Klaver
<adrian(dot)klaver(at)aklaver(dot)com>wrote:

> On 04/17/2014 05:55 PM, Augori wrote:
>
>> Hi Adrian,
>>
>> I don't know the answer to #1. Was that a wildcard search?
>>
>
> It was a grep of the processes running. You replied with this:
>
>
> "Here's what the ps command gives:
>
> root(at)server# ps ax | grep post
>
> 9165 pts/1 S+ 0:00 grep post"
>
> If postgres was running it should have shown up above. Just seemed to be
> at odds with later post:
>
>
> "
> woohoo!
>
> service postgresql-9.2 status
>
> (pid 9924) is running...
> "
>
> All I can figure is at some point between the first and second post the
> service for Postgres was started again. There just was no mention of that
> so I was trying to figure out the sequence of events.
>
>
>
>> As for #2, I should have been more clear, that's not a check that it
>> does every night. I just ran that check when it seemed to be down. It
>> has been a long time to since I've worked with it, so I didn't correctly
>> recall that I needed to look for postgresql-9.2 and not just postgresql.
>> The problem came up because the nightly process (a Python script that
>> uses psycopg2) tried to, but couldn't connect to postgresql-9.2 server.
>>
>> Does that make more sense?
>>
>
> Sort of, if the Python script is the only thing hitting the database.
> Otherwise I would have expected other 'users' to notice the database was
> down. Furthermore, psycopg2 does not know service names, it connects to a
> port, host, database as a user. So unless those where changed I would
> expect it to keep on connecting, unless the service was stopped, which
> seems to follow what I mention above. At any rate everything worked out.
>
>
>>
>> On Tue, Apr 15, 2014 at 12:08 AM, Adrian Klaver
>> <adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>>
>> On 04/14/2014 08:25 PM, Augori wrote:
>>
>> Hi all,
>>
>> woohoo!
>>
>> service postgresql-9.2 status
>>
>> (pid 9924) is running...
>>
>>
>> It seems that I was looking for the service by the wrong
>> name, as
>> John guessed correcty. Also, Tom, it's good to know that the
>> data
>> won't necessarily go away if I need to reinstall at some point.
>>
>>
>> Well that still leaves two questions unanswered.
>>
>> 1) Why did the postgres process not show up in the ps ax output?
>>
>> 2) Why is the nightly process doing a status check on postgresql not
>> postgresql-9.2 ?
>>
>> >From the original post:
>>
>>
>> # service postgresql status
>> postgresql: unrecognized service
>>
>>
>>
>>
>> thank you so much for the messages from all three of you. Your
>> rapid
>> responses were very encouraging.
>>
>>
>>
>> --
>> Adrian Klaver
>> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>>
>>
>>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>