On Tue, Aug 2, 2011 at 9:56 AM, jnolen <jnol...@mindspring.com> wrote: > I have the following error on a version 4.2.1-18890.6.1 system: > > Alarm: SPX00030 > Severity: CRIT > Alarm Text: Process 'CallResolver' failed its configuration test. > psql: FATAL: database is not accepting commands to avoid wraparound > data loss in database "postgres" > HINT: Stop the postmaster and use a standalone backend to vacuum > database "postgres". > ls: /etc/postgresql/*.*/main > : No such file or directory > Suggested Resolution: Check recent configuration changes. Do not > hand-edit configuration files. Check logs for more details. > > The suggested remedial procedure to vacuum the database, however, cannot > be carried out. The db is refusing connections. I cannot drop it, back > it up, or otherwise connect. > > I found several procedures to bypass this Catch-22 but am hesitant to do > this without a specific procedure for sipxecs. > > Can someone provide a specific procedure for sipxecs? > > Also, what would be the procedure to enable auto-vacuum for sipxecs?
There's postgres config I appended to http://track.sipfoundry.org/browse/XX-9688 but I'm not sure this will help you start postgres, but it might help to avoid the problem in the future. So my question is : what does the message means? "stop the postmaster and use a standalone backend to vacuum database "postgres"." _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
