Issue 1:
Checklist

I have verified that the issue exists against the master branch of Celery.

This has already been asked to the discussions forum first.

I have read the relevant section in the

contribution guide

on reporting bugs.

I have checked the issues list

for similar or identical bug reports.

I have checked the pull requests list

for existing proposed fixes.

I have checked the commit log

to find out if the bug was already fixed in the master branch.

I have included all related issues and possible duplicate issues

in this issue (If there are none, check this box anyway).

Mandatory Debugging Information

I have included the output of celery -A proj report in the issue.

(if you are not able to do this, then at least specify the Celery

version affected).

I have verified that the issue exists against the master branch of Celery.

I have included the contents of pip freeze in the issue.

I have included all the versions of all the external dependencies required

to reproduce this bug.

Optional Debugging Information

I have tried reproducing the issue on more than one Python version

and/or implementation.

I have tried reproducing the issue on more than one message broker and/or

result backend.

I have tried reproducing the issue on more than one version of the message

broker and/or result backend.

I have tried reproducing the issue on more than one operating system.

I have tried reproducing the issue on more than one workers pool.

I have tried reproducing the issue with autoscaling, retries,

ETA/Countdown & rate limits disabled.

I have tried reproducing the issue after downgrading

and/or upgrading Celery and its dependencies.

Related Issues and Possible Duplicates

Related Issues

None

Possible Duplicates

None

Environment & Settings

Celery version:

celery report Output:

Steps to Reproduce

Required Dependencies

Minimal Python Version: N/A or Unknown

Minimal Celery Version: N/A or Unknown

Minimal Kombu Version: N/A or Unknown

Minimal Broker Version: N/A or Unknown

Minimal Result Backend Version: N/A or Unknown

Minimal OS and/or Kernel Version: N/A or Unknown

Minimal Broker Client Version: N/A or Unknown

Minimal Result Backend Client Version: N/A or Unknown

Python Packages

pip freeze Output:

Other Dependencies

N/A

Minimally Reproducible Test Case

Expected Behavior

Actual Behavior

tcp 0 0 10.1.4.214:50088 10.105.93.168:3212 ESTABLISHED 0 3990648 1/python off (0.00/0/0)
tcp 0 0 10.1.4.214:50044 10.105.93.168:3212 ESTABLISHED 0 3990583 1/python off (0.00/0/0)
tcp 0 0 10.1.4.214:51230 10.105.93.168:3212 ESTABLISHED 0 3990447 29/python off (0.00/0/0)
tcp 0 0 10.1.4.214:50090 10.105.93.168:3212 ESTABLISHED 0 3990650 1/python off (0.00/0/0)
tcp 0 0 10.1.4.214:50092 10.105.93.168:3212 ESTABLISHED 0 3990652 1/python off (0.00/0/0)
tcp 0 0 10.1.4.214:51174 10.105.93.168:3212 ESTABLISHED 0 3997105 28/python off (0.00/0/0)
tcp 0 0 10.1.4.214:50046 10.105.93.168:3212 ESTABLISHED 0 3990587 1/python off (0.00/0/0)
tcp 0 0 10.1.4.214:50050 10.105.93.168:3212 ESTABLISHED 0 3990591 1/python off (0.00/0/0)
tcp 0 0 10.1.4.214:50048 10.105.93.168:3212 ESTABLISHED 0 3990589 1/python off (0.00/0/0)
tcp 0 0 10.1.4.214:50052 10.105.93.168:3212 ESTABLISHED 0 3990593 1/python off (0.00/0/0)
tcp 0 0 10.1.4.214:51228 10.105.93.168:3212 ESTABLISHED 0 3990445 29/python off (0.00/0/0)
tcp 0 0 10.1.4.214:51176 10.105.93.168:3212 ESTABLISHED 0 3997107 28/python off (0.00/0/0)
tcp 0 0 10.1.4.214:50086 10.105.93.168:3212 ESTABLISHED 0 3990646 1/python off (0.00/0/0)
tcp 0 0 10.1.4.214:50084 10.105.93.168:3212 ESTABLISHED 0 3990644 1/python off (0.00/0/0)

I set the port of the broker to be 3212 and the backed to be 3213 so I can distinguish them.

We found the issue since our GKE is behind a NAT, which doesn't like idle connections, so we get a lot of "Connection reset by peer"

We also set broker_pool_limit to 3 but as you can see there are much more.

Issue 2:
Checklist

I have verified that the issue exists against the master branch of Celery.

This has already been asked to the discussion group first.

I have read the relevant section in the

contribution guide

on reporting bugs.

I have checked the issues list

for similar or identical bug reports.

I have checked the pull requests list

for existing proposed fixes.

I have checked the commit log

to find out if the bug was already fixed in the master branch.

I have included all related issues and possible duplicate issues

in this issue (If there are none, check this box anyway).

Mandatory Debugging Information

I have included the output of celery -A proj report in the issue.

(if you are not able to do this, then at least specify the Celery

version affected).

I have verified that the issue exists against the master branch of Celery.

I have included the contents of pip freeze in the issue.

I have included all the versions of all the external dependencies required

to reproduce this bug.

Optional Debugging Information

I have tried reproducing the issue on more than one Python version

and/or implementation.

I have tried reproducing the issue on more than one message broker and/or

result backend.

I have tried reproducing the issue on more than one version of the message

broker and/or result backend.

I have tried reproducing the issue on more than one operating system.

I have tried reproducing the issue on more than one workers pool.

I have tried reproducing the issue with autoscaling, retries,

ETA/Countdown & rate limits disabled.

I have tried reproducing the issue after downgrading

and/or upgrading Celery and its dependencies.

Related Issues and Possible Duplicates

Related Issues

None

Possible Duplicates

None

Environment & Settings

Celery version:

celery report Output:

Steps to Reproduce

Required Dependencies

Minimal Python Version: N/A or Unknown

Minimal Celery Version: N/A or Unknown

Minimal Kombu Version: N/A or Unknown

Minimal Broker Version: N/A or Unknown

Minimal Result Backend Version: N/A or Unknown

Minimal OS and/or Kernel Version: N/A or Unknown

Minimal Broker Client Version: N/A or Unknown

Minimal Result Backend Client Version: N/A or Unknown

Python Packages

pip freeze Output:

Other Dependencies

N/A

Minimally Reproducible Test Case

Expected Behavior

I would like to include the output of a python script or other relevant data in the result backend. For example if I have a celery worker processing a request that has multiple steps I would like to see the output included whether the result is a success or failure. As the code stands it sends "NULL" as a result to the backend if the job is successful. Failure only sends the traceback information. I would like to include in both anything that is logged to the console during the running of the script. I don't see anyway to make this happen in the documentation.

Is there an option to include the the console output to the result field?

Actual Behavior

As the code stands it sends "NULL" as a result to the backend if the job is successful. Failure only sends the traceback information.