Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to JSON parse a line from worker stream #15122

Open
5 of 11 tasks
zou-can opened this issue Apr 22, 2024 · 2 comments
Open
5 of 11 tasks

Failed to JSON parse a line from worker stream #15122

zou-can opened this issue Apr 22, 2024 · 2 comments

Comments

@zou-can
Copy link

zou-can commented Apr 22, 2024

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that AWX is open source software provided for free and that I might not receive a timely response.
  • I am NOT reporting a (potential) security vulnerability. (These should be emailed to [email protected] instead.)

Bug Summary

After I upgrade AWX to 24.2.0, i met some JSON parse error:

Failed to JSON parse a line from worker stream. Error: Expecting ',' delimiter
Failed to JSON parse a line from worker stream. Error: Invalid \escape

I upgraded AWX due to issue - #14693, and i follows the comment - #14693 (comment), but Failed to JSON parse a still happens, and happens more often.

Note that my AWX jobs are performed to collect configs for network devices, and job outputs are large.

AWX version

24.2.0

Select the relevant components

  • UI
  • UI (tech preview)
  • API
  • Docs
  • Collection
  • CLI
  • Other

Installation method

kubernetes

Modifications

yes

Ansible version

2.15.10

Operating system

CentOS 7

Web browser

Chrome

Steps to reproduce

Lauch a job which will produce a large output, and output contains special characters(e.g. , \ []...)

Expected results

Job result is success.

Actual results

Job result is error: Failed to JSON parse a line from worker stream. ...

Additional information

I use a custom image for default instance group, however, the image is built from quay.io/ansible/awx-ee:24.2.0

The Dockerfile looks like:

FROM quay.io/ansible/awx-ee:24.2.0

USER root

# Install Python libs
ADD python_environment.txt ./
RUN pip install --no-cache-dir -r python_environment.txt

# Install expect
RUN dnf install -y expect

# Ensures cryptographic components compatibility with legacy systems
# https://access.redhat.com/articles/3642912
# https://access.redhat.com/documentation/zh-cn/red_hat_enterprise_linux/9/html/9.1_release_notes/enhancement_security
RUN echo 'min_rsa_size@openssh = 1024' > /etc/crypto-policies/policies/modules/RSA-OPENSSH-1024.pmod
RUN update-crypto-policies --set LEGACY:RSA-OPENSSH-1024

USER 1000

# Add ssh config files
ADD --chown=1000 --chmod=600 id_rsa /runner/.ssh/
ADD --chown=1000 --chmod=644 id_rsa.pub config /runner/.ssh/
@bhaskar-alagala
Copy link

Same version, we are also facing same issue. our Kubernetes on AKS
Failed to JSON parse a line from worker stream. Error. Expecting value: line 1 column 1 ( char0) line with invalid JSON data: b

@bhaskar-alagala
Copy link

kubectl logs awx-webxxxxxx -n xxxx

I am getting Imagepullbackoff and in awx jobs, I am getting below error.

Failed to JSON parse a line from worker stream. Error. Expecting value: line 1 column 1 ( char0) line with invalid JSON data: b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants