1419510 – Garbled ps -ef output

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1419510 - Garbled ps -ef output

Summary: Garbled ps -ef output

Keywords:
Status:	CLOSED INSUFFICIENT_DATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	procps-ng
Sub Component:
Version:	7.3
Hardware:	Unspecified
OS:	Unspecified
Priority:	low
Severity:	low
Target Milestone:	rc
Target Release:	---
Assignee:	Jan Rybar
QA Contact:	BaseOS QE - Apps
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2017-02-06 11:38 UTC by Marko Myllynen
Modified:	2018-01-19 11:55 UTC (History)
CC List:	1 user (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2018-01-19 11:55:38 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Marko Myllynen 2017-02-06 11:38:35 UTC

Description of problem:
[root@infra02 ~]# cat /proc/21401/cmdline 
/usr/bin/dockerd-current--add-runtimedocker-runc=/usr/libexec/docker/docker-runc-current--default-runtime=docker-runc--authorization-plugin=rhel-push-plugin--exec-optnative.cgroupdriver=systemd--userland-proxy-path=/usr/libexec/docker/docker-proxy-current--selinux-enabled--log-driver=json-file--log-optmax-size=50m--storage-driverdevicemapper--storage-optdm.fs=xfs--storage-optdm.thinpooldev=/dev/mapper/docker--vg-docker--pool--storage-optdm.use_deferred_removal=true--add-registryregistry.example.com:5000--block-registryall--insecure-registryregistry.example.com:5000[root@infra02 ~]# 
[root@infra02 ~]# ps auxwww | grep 5000
root     21401  0.1  0.3 474504 28412 ?        Ssl  11:40   0:00 /usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --authorization-plugin=rhel-push-plugin --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --selinux-enabled --log-driver=json-file --log-opt max-size=50m --storage-driver devicemapper --storage-opt dm.fs=xfs --storage-opt dm.thinpooldev=/dev/mapper/docker--vg-docker--pool --storage-opt dm.use_deferred_removal=true --add-registry registry.example.com:5000 --block-registry all --insecure-registry registry.example.com:5000
root     21524  0.0  0.0  11084   720 pts/1    S+   11:42   0:00 grep --color=auto 5000
[root@infra02 ~]# ps -ef | grep 5000
root     21401     1  0 11:40 ?        00:00:00 /usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --authorization-plugin=rhel-push-plugin --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --selinux-enabled --log-driver=json-file --log-opt max-size=50m --storage-driver devicemapper --storage-opt dm.fs=xfs --storage-opt dm.thinpooldev=/dev/mapper/docker--vg-docker--pool --storage-opt dm.use_deferred_removal=true --add-registry registry.example.com:5000 --block-registry all --insecure-registry registry.example.com5000

Note the missing colon at the end. I haven't been able to reproduce this so I'm not sure what was going on but I saw this a couple of times so not necessarily due to hallucinations.

Version-Release number of selected component (if applicable):
procps-ng-3.3.10-10.el7.x86_64

Comment 2 Jan Rybar 2017-02-06 12:51:13 UTC

Hello Marko,
can you please specify the actual issue?

Thanks and have a nice day.

Comment 3 Marko Myllynen 2017-02-06 13:22:58 UTC

(In reply to Jan Rybar from comment #2)
> Hello Marko,
> can you please specify the actual issue?

The last colon is missing;

> --insecure-registry registry.example.com:5000

vs

> -insecure-registry registry.example.com5000

As said, I'm not able to reproduce (OTOH, haven't see the process in the same state afterwards the output in that sense has been slightly different) so I'm afraid I can't provide more details than this.

Thanks.

Comment 5 Jan Rybar 2018-01-19 11:55:38 UTC

Since there is no reproducer and we have insufficient data to investigate the problem, I'll close this bug for now.

Note You need to log in before you can comment on or make changes to this bug.