Critical mail:Error backing up database:... not permitted

All documents from the original Software Support Library (SSL)

Moderators: Leon van Heerden, Luanda_Junzi, Belinda Frick, Lee Hendricks

Critical mail:Error backing up database:... not permitted

Postby Belinda Frick » Tue Dec 06, 2011 3:22 pm

--------------------- CRITICAL ERRORS START HERE ---------------------
[2011-12-04 21:00:11] Version [1.6.3.18]Error backing up database: Operation not permitted
---------------------- CRITICAL ERRORS END HERE ----------------------


Please check admin log for more details. Archiving starts at 21h00 each night.

How do I log into AMETHYST webadmin and supervisor?

AMETHYST Webadmin Home page, select 'View Logs'

Select date as per critical e-mail.
Check the log entries from 21h00 onwards.

Possible issues:

  • The first steps of the archiving is to make a backup of the database on the system drive. If not enough space to backup the database, then you could get this critical e-mail.

    Please check the size of your database - How do I check the size of my database?
    Please check your available diskspace - How do I check disk space available on AMETHYST server?

    You need double your database size space free in the database drive section to do the backup and restore.

    For more information regarding how space is maintained - How is spaced maintained on the AMETHYST server

  • Check in the Webadmin log for additonal information, for example:

    • This error is still under investigation:

      Code: Select all
      [2012-07-09 09:11:37]  Version [1.6.4.2]******** ARCHIVE EXECUTION STARTS HERE *************
      [2012-07-09 09:11:37]  Version [1.6.3.15]Archiving started (PID 3795)
      gbak: ERROR:bad parameters on attach or create database
      gbak:Exiting before completion due to errors
      [2012-07-09 09:11:47]  Version [1.6.3.15]Error backing up database: Operation not permitted
      [2012-07-09 09:11:57]  Version [1.6.3.15]Done archiving (PID 3795)
  • If not additional detail in the admin.log, this could relate to the database engine. Please check the supervisor and sweeper logs.

    If the sweeper is not running, then your recordings will be stored in the database drive until 1G space free. The ftp will then be stopped. Once the sweeper runs again, the calls can load to the Exclusive drive and free space on the database drive.

    Examples of amtsweeper entries that will cause database drive space issues for archiving:


UNDER INVESTIGATION!
Belinda Frick
 
Posts: 3808
Joined: Fri Nov 12, 2010 4:25 pm

Return to Support Archive's (Amethyst)

Who is online

Users browsing this forum: No registered users and 1 guest

cron