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
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/1S+ 0:00 grep post"
If postgres w
Hi Adrian,
I don't know the answer to #1. Was that a wildcard search?
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
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 reins
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.
thank you so much for
On 04/14/2014 07:52 PM, John R Pierce wrote:
On 4/14/2014 7:34 PM, Tom Lane wrote:
Augori writes:
>Here's what the ps command gives:
>root@server# ps ax | grep post
> 9165 pts/1S+ 0:00 grep post
>Does this mean it's not running?
Sure looks that way.
>It's certainly possible that so
On 04/14/2014 07:17 PM, Augori wrote:
Here's what the ps command gives:
root@server# ps ax | grep post
9165 pts/1S+ 0:00 grep post
Does this mean it's not running?
Yes, it is not running.
It's certainly possible that software updates have occurred. There are
a lot of people work
On 4/14/2014 7:34 PM, Tom Lane wrote:
Augori writes:
>Here's what the ps command gives:
>root@server# ps ax | grep post
> 9165 pts/1S+ 0:00 grep post
>Does this mean it's not running?
Sure looks that way.
>It's certainly possible that software updates have occurred. There are a
>lo
On 4/14/2014 7:17 PM, Augori wrote:
Here's what the ps command gives:
root@server# ps ax | grep post
9165 pts/1S+ 0:00 grep post
Does this mean it's not running?
It's certainly possible that software updates have occurred. There
are a lot of people working on this machine, so I'm no
On 4/14/2014 5:33 PM, Augori wrote:
# service postgresql status
postgresql: unrecognized service
Does this mean it's gone? Does anyone have any suggestions?
the 'service' command on rhel/centos/etc runs /etc/rc.d/init.d/$1 $2
so, ls -l /etc/rc.d/init.d/postgres*and see what the service n
Augori writes:
> Here's what the ps command gives:
> root@server# ps ax | grep post
> 9165 pts/1S+ 0:00 grep post
> Does this mean it's not running?
Sure looks that way.
> It's certainly possible that software updates have occurred. There are a
> lot of people working on this machine,
Here's what the ps command gives:
root@server# ps ax | grep post
9165 pts/1S+ 0:00 grep post
Does this mean it's not running?
It's certainly possible that software updates have occurred. There are a
lot of people working on this machine, so I'm not aware of which changes
have been made
On 04/14/2014 05:33 PM, Augori wrote:
Hi Folks,
I set up postgresql on a CentOS 5 Linux months ago. I had a process that
ran every night and connected to the database. Everything was working
fine until a few days ago when my process tried to connect and failed.
Now I'm getting:
# service post
Hi Folks,
I set up postgresql on a CentOS 5 Linux months ago. I had a process that
ran every night and connected to the database. Everything was working fine
until a few days ago when my process tried to connect and failed. Now I'm
getting:
# service postgresql status
postgresql: unrecognized
14 matches
Mail list logo
