Solved Backup Failure

[[email protected]]

Version 15 - Windows Server 2012 R2 - 8GB memory

Have had no problems with backups before. For the last few days have had a backup failure with the following message.

3CX Phone System tried to backup but failed due to the following reason(s):

System.Exception: Error creating backup ---> System.AggregateException: One or more errors occurred. ---> Npgsql.NpgsqlException: The connection pool has been exhausted, either raise MaxPoolSize (currently 100) or Timeout (currently 600 seconds)

at Npgsql.ConnectorPool.<WaitForTaskAsync>d__24.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

The back up file is not very large, there is 500GB of disk space available. Have cleared temp files, and rebooted.

 

[GiannosC_3CX]

Dear phil,

Please disable your schedule backup, next enable verbose mode on activity log settings, after restart your services and then enable the schedule backup again and let the system to run the schedule. Please let us know if this error still received.

 

[[email protected]]

Still no go. Rebooted Server, ran windows updates, normal temp file cleanup. Manual backup works as expected.

System.Exception: Error creating backup ---> System.AggregateException: One or more errors occurred. ---> Npgsql.NpgsqlException: The connection pool has been exhausted, either raise MaxPoolSize (currently 100) or Timeout (currently 600 seconds)

 

[orion]

We also have a 3CX v15 server with all current updates which started showing the exact same error on Friday nights scheduled backup.

Server 2012 R2 with 8Gb RAM running on VMWare 5.5.

Backup works fine manually.

Backup size is 1Gb.

Regards

Rob

Version 15 - Windows Server 2012 R2 - 8GB memory

Have had no problems with backups before. For the last few days have had a backup failure with the following message.

3CX Phone System tried to backup but failed due to the following reason(s):

System.Exception: Error creating backup ---> System.AggregateException: One or more errors occurred. ---> Npgsql.NpgsqlException: The connection pool has been exhausted, either raise MaxPoolSize (currently 100) or Timeout (currently 600 seconds)

at Npgsql.ConnectorPool.<WaitForTaskAsync>d__24.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

The back up file is not very large, there is 500GB of disk space available. Have cleared temp files, and rebooted.[/QUOTE

 

[IT Admin]

Same here and issue first occurred on Friday night.

Running v15.0.59950.0 on Server 2012 R2 with 8Gb RAM, Manual backup works fine.

Backup size is 136 MB

 

[GiannosC_3CX]

Hi there,

What scheduled backup do you use? (weekly or daily)

 

[IT Admin]

Hi there,

What scheduled backup do you use? (weekly or daily)

Daily

 

[7networks1]

Hello there,
same problem here on version 15.0.59381.0 on Win 2012 R2.

Manual Backup works just fine, scheduled (daily) one stopped working January 26. Backup size is just 111MB.

 

[YiannisH_3CX]

As a first step upgrade to the latest service pack and try scheduling the backup again. Let us know if that works

 

[GiannosC_3CX]

Hi there,

Also, please try with weekly schedule and let us know if the problem persists.

 

[Brett Garfitt]

Running v15.0.59950.0 and having a similar issue with daily backups about once a month or so.

 

[GiannosC_3CX]

Hi Brett,

Please upgrade to the latest service pack ( 15.0.60903.0 )and try scheduling the backup again. Let us know if that works

 

[orion]

Already running the latest version here and still receiving the backup error.

 

[GiannosC_3CX]

Hi Orion,

Are you on version 15.0.60903.0 ?
Also please try to change from weekly to daily and vise versa.
Please let us know if still receiving the backup error on both cases. (weekly or daily)

 

[GoPiTM]

We have the same problem
I switched from a daily to a weekly but this did not work.
Daily error:

3CX Phone System tried to backup but failed due to the following reason(s):
System.Exception: Error creating backup ---> System.AggregateException: One or more errors occurred. ---> Npgsql.NpgsqlException: The connection pool has been exhausted, either raise MaxPoolSize (currently 100) or Timeout (currently 600 seconds)
at Npgsql.ConnectorPool.<WaitForTaskAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Npgsql.ConnectorPool.<AllocateAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Npgsql.NpgsqlConnection.<OpenInternalAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at _3cxNetInterfaces.Implementation.Npgsql.NpgsqlDbOperation.<CreateConnectionAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at _3cxNetInterfaces.Implementation.Npgsql.NpgsqlDbOperation.<BeginTransactionAsync>d__36.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at _3cxNetInterfaces.Implementation.Npgsql.NpgsqlDbOperation.<BeginTransactionAsync>d__35.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at _3cxNetBackupAndRestore.BackupTasks.BaseDBTask.<RunAll>d__12.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at _3cxNetBackupAndRestore.BackupTasks.MyPhoneTask.<.ctor>b__0_0(BaseTask x)
at _3cxNetManagement.BaseTask.Run()
--- End of inner exception stack trace ---
at _3cxNetBackupAndRestore._3cxBackup.WaitForFinish()
at _3cxBackupRestoreImpl.BackupRestoreUtils.Backup(String instanceId, String cfgPath, String dbConnectionString, BackupConfig options, String fullpathFilename, NetworkCredential credentials, Boolean sendEmail)
at BackupRestoreSchedule.BackupJob.Execute(IJobExecutionContext context)

Weekly error:

3CX Phone System tried to backup but failed due to the following reason(s):
System.Exception: Error creating backup ---> System.AggregateException: One or more errors occurred. ---> Npgsql.NpgsqlException: The connection pool has been exhausted, either raise MaxPoolSize (currently 100) or Timeout (currently 600 seconds)
at Npgsql.ConnectorPool.<WaitForTaskAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Npgsql.ConnectorPool.<AllocateAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Npgsql.NpgsqlConnection.<OpenInternalAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at _3cxNetInterfaces.Implementation.Npgsql.NpgsqlDbOperation.<CreateConnectionAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at _3cxNetInterfaces.Implementation.Npgsql.NpgsqlDbOperation.<BackupTableAsync>d__27.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at _3cxNetBackupAndRestore.BackupTasks.BaseDBTask.<>c__DisplayClass13_0.<BackupTable>b__0(Stream x)
at _3cxNetBackupAndRestore._3cxBackup.ZipDbTable(String table, Action`1 writeContent)
at _3cxNetBackupAndRestore.BackupTasks.BaseDBTask.<RunAll>d__12.MoveNext()
--- End of inner exception stack trace ---
at _3cxNetBackupAndRestore._3cxBackup.WaitForFinish()
at _3cxBackupRestoreImpl.BackupRestoreUtils.Backup(String instanceId, String cfgPath, String dbConnectionString, BackupConfig options, String fullpathFilename, NetworkCredential credentials, Boolean sendEmail)
at BackupRestoreSchedule.BackupJob.Execute(IJobExecutionContext context)

 

[GiannosC_3CX]

Hi There,

Please could you (If those are on SP4 ) do the following steps?

1) Put the system in Verbose mode
2) Disable the scheduled backup
3) Restart All 3CX Services including the Database
4) Enable your scheduled backup
5) Monitor and let us know if this happens again.

 

[GoPiTM]

Where is the Verbose mode in 15?

 

[GiannosC_3CX]

Hi @GoPiTM
To enable the verbose option, you can go to Dashboard => Activity Log => Settings => and choose the Verbose option.

 

[GoPiTM]

The backup worked.

 

[GiannosC_3CX]

Hi GoPiTM,

Please keep an eye on it and let us know if it happens again.