Please enter search query. Search <product_name> all support & community content...
Last Published: 2019-12-05
Ratings: 1 0
Getting 'status 25: unable to update image database failure on media server' intermittently during backups. The backups are successful if retried.
Many similar status 25 errors messages, including:
- 'image cleanup failed' and 'cannot log message to error database
- error = cannot connect on socket'.
Reviewing bptm log file shows this similar behavior for all failing activities:
17:15:53.776  <2> nb_connect_to_vnetd_or_legacy: comm.c.2030: vnet_connect_to_vnetd_or_service failed: 6
17:15:53.776  <2> db_begin: nb_connect_to_vnetd_or_legacy(master1) failed retval 48 err 0
17:15:53.777  <2> db_begin: nb_getsockconnected() failed: Error 0 (0)
17:15:53.779  <2> db_ERROR: db_begin() failed: cannot connect on socket
The 'retval 48' indicates we are unable to perform name resolution for the hostname in question. In this case, the master server itself. The most likely explanation is a poorly performing DNS server and by using a hosts entry we are able to avoid using the DNS server.
By adding an entry for the master to /etc/hosts, the problem was resolved. The most likely explanation is a poorly performing DNS server and by using a hosts entry we are able to avoid using the DNS server.
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):