tp-socorro01-master02 init file not working properly

RESOLVED FIXED

Status

Data & BI Services Team
DB: MySQL
P2
normal
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: selenamarie, Assigned: sheeri)

Tracking

Details

(Whiteboard: [2013q3] September)

[root@tp-socorro01-master02.phx1 data]# /etc/init.d/postgresql-socorro-slave status
 is stopped
[root@tp-socorro01-master02.phx1 data]# /etc/init.d/postgresql-9.2 status
 dead but pid file exists

How do we fix this?
(Assignee)

Comment 1

5 years ago
Currently:

[root@tp-socorro01-master02.phx1 ~]# /etc/init.d/postgresql-socorro-slave status is stopped
[root@tp-socorro01-master02.phx1 ~]# /etc/init.d/postgresql-9.2 status
 (pid  14699) is running...
[root@tp-socorro01-master02.phx1 ~]# 

This is correct for tp-socorro01-master02.

[root@tp-socorro01-master01.phx1 ~]# /etc/init.d/postgresql-9.2 status
 (pid  15176) is running...
[root@tp-socorro01-master01.phx1 ~]#  /etc/init.d/postgresql-socorro-slave status
-bash: /etc/init.d/postgresql-socorro-slave: No such file or directory
[root@tp-socorro01-master01.phx1 ~]# 

Looking, I see a "replica" script:
[root@tp-socorro01-master01.phx1 ~]# /etc/init.d/postgresql-socorro-replica status
 is stopped
[root@tp-socorro01-master01.phx1 ~]# 

I'll note that the "slave" script on master02 has postgres 9.0 hardcoded into it as does the "replica" script on master01.

Where do these scripts come from, and how come they weren't upgraded when we upgraded to 9.2? Or is that the point of this bug, to fix the scripts so they work with 9.2?
(Assignee)

Updated

5 years ago
Assignee: server-ops-database → scabral
Whiteboard: [2013q3]
(Assignee)

Updated

5 years ago
Priority: -- → P2
(Assignee)

Updated

5 years ago
Whiteboard: [2013q3] → [2013q3] September
(Assignee)

Comment 2

5 years ago
postgres + master are showing OK on the master:

[root@tp-socorro01-master02.phx1 init.d]# ./postgresql-9.2 status (pid  6629) is running...
[root@tp-socorro01-master02.phx1 init.d]# ./postgresql-socorro-master status
 (pid  6629) is running...

And on the slave, the postgres status is fine:

[root@socorro3.db.phx1 init.d]# ./postgresql-9.2  status
 (pid  37283) is running...

I'm unsure there's a problem any more going by the problem in the description, so I'm going to resolve/invalid, unless there's more information on exactly what's broken - and then of course I'm happy to work on it again!
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Product: mozilla.org → Data & BI Services Team
You need to log in before you can comment on or make changes to this bug.