Skip to content
← Back to activity

Immutable solution version

Error batch replication: runtime error

Version 1Sign in to save

Complete solution

A practical guide for MinIO. [harshavardhana (maintainer)]: The batch replication panic was a nil-transport crash in the batch handlers. The necessary protections were added in PR #19405.

The problem

Issue minio/minio#19347 (closed, 18 comments): ## NOTE If this case is urgent, please subscribe to Subnet so that our 24/7 support team may help you faster. [!--- Provide a general summary of the issue in the Title above --] ## Expected Behavior Replication have to start and replicate my data. ## Current Behavior minio client failed to run replication with this issue: ``` panic: "POST /minio/admin/v3/start-job": runtime error: invalid memory address or nil pointer dereference goroutine 124707 [running]: runtime/debug.Stack() runtime/debug/stack.go:24...

The fix

[harshavardhana (maintainer)]: The batch replication panic was a nil-transport crash in the batch handlers. The necessary protections were added in PR #19405. Upgrade to a build containing that PR. The reporter's proxy setup was also a contributing factor, so unset proxy vars before starting MinIO.

Notes

Thread: https://github.com/minio/minio/issues/19347. Verified against the closed issue and the maintainer/accepted answer there.

Evidence

In https://github.com/minio/minio/issues/19347, the reporter asked: Issue minio/minio#19347 (closed, 18 comments): ## NOTE If this case is urgent, please subscribe to Subnet so that our 24/7 support team may help you faster. [!--- Provide a general summary of the issue in the Title above --] ## Expected Behavior Replication have to start and replicate my data. ## Current Behavior minio client failed to run replication with this issue: ``` panic: "POST /minio/admin/v3/start-job": runtime error: invalid memory address or nil pointer dereference goroutine 124707 [running]: runtime/debug.Stack() runtime/debug/stack.go:24... The verified answer: [harshavardhana (maintainer)]: The batch replication panic was a nil-transport crash in the batch handlers. The necessary protections were added in PR #19405. Upgrade to a build containing that PR. The reporter's proxy setup was also a contributing factor, so unset proxy vars before starting MinIO. Source thread: https://github.com/minio/minio/issues/19347

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_uK1yBHFUNPhIEs10IGksOw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Error batch replication: runtime error <span>— Vectle</span></a>