Skip to content

SIGSEGV when I try to view the stream content #1483

@db-ks

Description

@db-ks

Observed behavior

I am connected through a k8s-hosted NATS server (2.10.29-alpine) to a leaf-node server (2.11.1) and trying to view data from a JetStream on that leaf-node using NATS CLI (0.2.3).

I get the following:

./nats --timeout 5m -s localhost:4223 --creds production.creds --js-api-prefix='$JS.Realm.RemoteEndpoint.API' stream view StreamName
Subject:  Reply: 

  Status: 503
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x11875cd]

goroutine 1 [running]:
github.com/nats-io/jsm%2ego.(*MsgInfo).Stream(...)
	/home/runner/go/pkg/mod/github.com/nats-io/[email protected]/msginfo.go:40
github.com/nats-io/natscli/cli.(*streamCmd).viewAction(0xc000036408, 0x40e3df?)
	/home/runner/work/natscli/natscli/cli/stream_command.go:1165 +0x88d
github.com/choria-io/fisk.(*actionMixin).applyActions(...)
	/home/runner/go/pkg/mod/github.com/choria-io/[email protected]/actions.go:28
github.com/choria-io/fisk.(*Application).applyActions(0xc000415a40?, 0xc000402120)
	/home/runner/go/pkg/mod/github.com/choria-io/[email protected]/app.go:827 +0xd0
github.com/choria-io/fisk.(*Application).execute(0xc000415a40, 0xc000402120, {0xc0002d85c0, 0x2, 0x2})
	/home/runner/go/pkg/mod/github.com/choria-io/[email protected]/app.go:613 +0x65
github.com/choria-io/fisk.(*Application).Parse(0xc000415a40, {0xc000150010?, 0x2c?, 0xc0004a2870?})
	/home/runner/go/pkg/mod/github.com/choria-io/[email protected]/app.go:276 +0x17f
github.com/choria-io/fisk.(*Application).MustParseWithUsage(0xc000415a40, {0xc000150010, 0xa, 0xa})
	/home/runner/go/pkg/mod/github.com/choria-io/[email protected]/app.go:893 +0x45
main.main()
	/home/runner/work/natscli/natscli/nats/main.go:84 +0x2e08

Expected behavior

No crash

Server and client version

  • NATS server - 2.10.29-alpine
  • NATS leaf-node server - 2.11.1
  • NATS CLI - 0.2.3

Host environment

  • k8s v1.31.10
  • Ubuntu 24.04.3 LTS

Steps to reproduce

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    defectSuspected defect such as a bug or regression

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions