NetWorker Recover: Segmentation Fault when using Exclude File Option

Recovery Process Failure

The recovery process fails when using a standard recover command with an exclude file.

This issue is reproducible with any client on versions 19.11 and 19.12.

Error Messages and Logs

The following error message is generated:

Segmentation fault (core dumped)

The core dump information shows:

Core was generated by `recover -e exclude.txt'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fa5a10697d6 in strtok_r () from /lib64/libc.so.6

Command Example

The issue can be reproduced using the following command:

[user@client]$ echo /asd > exclude.txt
[user@client]$ recover -D9 -e exclude.txt
179040:recover: Step (1 of 11) for PID-1077843: Recovery has been started on the client 'client.domain.local'.
179733:recover: Step (2 of 11) for PID-1077843: Checking if the set of exclusion files is given for the recovery of the selected files for the client 'client.domain.local'.
03/04/25 10:01:52.995857 recover-D4 exclude_file_open() opened exclusion file exclude.txt
Segmentation fault (core dumped)

Root Cause Analysis

The issue is caused by a segmentation fault that occurs when using the recover command with an exclude file.

This occurs due to a strtok_r function issue as shown in the core dump information.

As a workaround, do not use the -e flag for the time being.

A fix for this issue is planned for versions 19.11.0.5 and 19.12.0.2.