litmus: LitmusPortal subscriber fails to start

What happened:

When connecting the LitmusPortal agent, the following occurs in the log of the subscriber pod:

The fatal error is │ time="2021-07-13T01:54:30Z" level=fatal msg="invalid character 'p' after top-level value"

This happens every time.

The agent does not connect and every time, my subscriber fails on a CrashBackLoop. Could anyone advise?

│ time="2021-07-13T02:05:14Z" level=info msg="Go OS/Arch: linux/amd64"                                                                                                                              │
│ time="2021-07-13T02:05:14Z" level=info msg="all deployments up"                                                                                                                                   │
│ time="2021-07-13T02:05:14Z" level=info msg="all components live...starting up subscriber"                                                                                                         │
│ time="2021-07-13T02:05:14Z" level=fatal msg="invalid character 'p' after top-level value"                                                                                          

What you expected to happen:

The subscriber should start normally.

How to reproduce it (as minimally and precisely as possible):

Connect the litmusctl agent with the portal.

Anything else we need to know?:

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 17 (6 by maintainers)

Most upvoted comments

@rajdas98 can you help @itustanic with the ingress issue. I think this issue is due to the ingress/k8s version