The spoold process crashes during rebasing.

Article:TECH199067  |  Created: 2012-10-27  |  Updated: 2013-08-09  |  Article URL http://www.symantec.com/docs/TECH199067
Article Type
Technical Solution


Environment

Issue



Backup to MSDP storage fails with status 84.


Error



From the bptm log:

18:03:52.269 [8144.7584] <16> 10608:bptm:8144:nbumaster.company.name: [ERROR] PDSTS: tag_nbu_dsid: PdvfsRead() failed for (10061:No connection could be made because the target machine actively refused it. )
18:03:52.269 [8144.7584] <16> 10608:bptm:8144:nbumaster.company.name: [ERROR] PDSTS: pd_get_dsid_path: tag_nbu_dsid() failed (2060023:server is shut down)
18:03:52.269 [8144.7584] <16> 10608:bptm:8144:nbumaster.company.name: [ERROR] PDSTS: pd_mount: pd_get_dsid_path() failed (2060023:server is shut down)
18:03:52.269 [8144.7584] <16> 10608:bptm:8144:nbumaster.company.name: [ERROR] PDSTS: open_server: pd_mount() failed (2060023:server is shut down)
18:03:52.269 [8144.7584] <16> 10608:bptm:8144:nbumaster.company.name: [ERROR] PDSTS: impl_open_server: open_server(PureDisk:nbumaster.company.name) failed (2060023:server is shut down)
18:03:52.269 [8144.7584] <16> 10608:bptm:8144:nbumaster.company.name: [ERROR] PDSTS: pi_open_server_v7: impl_open_server(PureDisk:nbumaster.company.name) failed (2060023:server is shut down)


spoold reports database manager shut down:

October 27 18:03:59 INFO: Database Manager: initializing
October 27 18:03:59 INFO: Database Manager: initialization complete
October 27 18:03:59 INFO: Database Manager: closing storage database connection
October 27 18:03:59 INFO: Database Manager: shutdown


From the postgresql log:

2012-10-27 17:56:30 PDT LOG: database system is ready to accept connections
2012-10-27 17:56:30 PDT LOG: autovacuum launcher started
2012-10-27 18:03:47 PDT LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2012-10-27 18:03:47 PDT LOG: unexpected EOF on client connection

 

Event logs show spoold crash:

Event Name: APPCRASH
Response: Not available
Cab Id: 0
 

Problem signature:
P1: spoold.exe
P2: 7.3.12.915
P3: 505534d0
P4: ntdll.dll
P5: 6.1.7601.17725
P6: 4ec4aa8e
P7: c0000005
P8: 000000000000f279
P9:
P10:

 


Environment



This issue has been reported in Netbackup 7.5.0.4.

Note: This can occur on all supported MSDP platforms. The above example is from Windows, but the problem is not limited to Windows platform.


Cause



There is a possibility for spoold to segfault/APPCRASH during rebasing.


Solution



Symantec Corporation has acknowledged that the above-mentioned issue (Etrack 2962064) is present in the current version(s) of the product(s) mentioned in this article. Symantec Corporation is committed to product quality and satisfied customers.  This issue was scheduled to be addressed in the following release:

  • NetBackup 7.5 Maintenance Release 5 (7.5.0.5)

When NetBackup 7.5.0.5 is available, please visit the following link for download and README information:
 http://www.symantec.com/business/support/overview.jsp?pid=15143

Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Workaround:

  • Stop NetBackup processes
  • Start NetBackup and execute crcontrol --rebaseoff as soon as spoold will accept a connection.

Note:
- Shortly after the spoold process has loaded the fingerprint cache, rebasing will begin and, potentally, the spoold thread will fault.
- After each restart of spoold process, the 'crcontrol --rebaseoff' will need to be executed.
- Until either the EEB mentioned below is applied or (the perferred option) an upgrade to 7.5.0.5 (or later) is performed, rebasing should not be enabled.

An Emergency Engineering Binary (EEB) replacement for spoold is available containing a fix for this issue.  Please contact Symantec technical support, referencing this document and Etrack 2964167.


Supplemental Materials

SourceETrack
Value2962064
Description

spoold will crash during rebasing when the unique container number used after the rebase is larger than the unique container number before the rebase.



Article URL http://www.symantec.com/docs/TECH199067


Terms of use for this information are found in Legal Notices