After using gor --input-file, the program hangs indefinitely rather than closing.

[bluestorm-faker]

My environment is Windows 10. When using the latest version 1.3.3, I execute the command gor --input-file requests0.log --output-http "http://192.168.2.44:446" --verbose 9. However, after requests0.log has been fully forwarded, the program remains running and does not terminate. If I only intend to run it once, shouldn't it conclude normally? Is this a bug or is it intentionally designed to keep waiting?
#999

[github-actions]

GoReplay File Input Behavior Analysis

After analyzing the GoReplay codebase, I can confirm that the behavior you're experiencing is by design, not a bug. GoReplay doesn't automatically terminate after processing an input file.

Why GoReplay Doesn't Exit Automatically

Looking at the main function in cmd/gor/gor.go, the program only exits under these conditions:

1. When receiving an interrupt signal (Ctrl+C)
2. When the --exit-after duration expires (if specified)
3. When receiving a SIGTERM signal

There's no mechanism to detect when all inputs have finished processing and automatically terminate the program.

The FileInput Implementation

The FileInput plugin in input_file.go does properly detect when it reaches the end of the file:

// When file is fully processed
Debug(2, fmt.Sprintf("[INPUT-FILE] FileInput: end of file '%s'\n", i.path))

However, it doesn't signal to the main program that it's done. The emitter continues running, waiting for more input that will never come.

Solution: Use the --exit-after Flag

To make GoReplay exit automatically after processing your file, use the --exit-after flag with an appropriate duration:

gor --input-file requests0.log --output-http "http://192.168.2.44:446" --verbose 9 --exit-after=5s

This will make GoReplay exit after 5 seconds (adjust the duration as needed). You can set it to a value slightly longer than the expected processing time of your file.

This behavior is intentional as GoReplay is designed for continuous traffic capture and replay, where inputs like network interfaces would run indefinitely.

---

Tip: Mention me again using /probe <request>.
Powered by Probe AI