[SFtrack] Updated: (XECS-1207) Backup fails on SuSE due to permissions
[
http://track.sipfoundry.org/browse/XECS-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Lawrence updated XECS-1207:
---------------------------------
Assignee: Carolyn Beeton
Component/s: portability
> Backup fails on SuSE due to permissions
> ---------------------------------------
>
> Key: XECS-1207
> URL: http://track.sipfoundry.org/browse/XECS-1207
> Project: sipXecs
> Issue Type: Bug
> Components: portability
> Environment: openSUSE 10.2 (X86-64) or SUSE Linux Enterprise Server
> 10 (x86_64)
> Reporter: Carolyn Beeton
> Assignee: Carolyn Beeton
> Fix For: 4.0
>
>
> On SuSE systems backup fails with an invisible message "PostgreSQL does not
> appear to be running. You must start it in order to backup".
> The problem is due to the following check in sipx-archive-common:
> if [ ! -f /var/run/postmaster*.pid -a \
> ! -f /var/lib/postgresql/data/postmaster*.pid -a \
> ! -f /var/lib/pgsql/data/postmaster*.pid -a \
> ! -f ~postgres/data/postmaster*.pid ]
> On SuSE, /var/run/postmaster*.pid does not exist.
> /var/lib/pgsql/data/postmaster.pid exists but has permission 600 (no read
> permission for non-root).
> Can the backup task be run as root? Also, would "pidof postmaster" be a
> better (more portable) way to see if postgres is running? (Note that pidof
> also requires root on some platforms). Or "ps -edaf|grep postmaster"...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://track.sipfoundry.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
