Bug 1571863 - Issue with remote command execution
Summary: Issue with remote command execution
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-25 14:46 UTC by swsupp
Modified: 2019-09-16 12:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-09-16 12:16:59 UTC

Attachments (Terms of Use)

Description swsupp 2018-04-25 14:46:00 UTC
Description of problem:

I have setup a Spacewalk 2.7 Proof of Concept server but having issues with executing some remote commands. Please see brief details below:

Scenario 1/Client Test System 1 (CentOS 6)
Executing general test commands, like “date” or “df -h” complete immediately. However, when I run any “yum” commands they fail with the following error:

                Script killed, timeout of 600 seconds exceeded

Scenario2/Client Test System 2 (CentOS 6)
Any commands remain in a “Pending” state. However, I’ve found they are picked up fairly quickly if I re-start the Spacewalk app (spacewalk-service restart).

If anyone could offer any advice it would be appreciated.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Select relevant system
2. Click remote command
3. Add relevant command to script box
4. Click schedule

Actual results:

Scenario 1/Client Test System 1




 [IP Removed].us-west-2.compute.internal  4/25/18 9:36:21 AM GMT  Script killed, timeout of 600 seconds exceeded  

Expected results:
Command should return relevant output/action

Additional info:

Comment 1 Tomáš Kašpárek 2018-05-04 06:14:11 UTC

could you please try to schedule an action then pick it up on client with "rhn_check -vvv" and provide me the output?

Thank you

Comment 2 Michael Mráka 2019-09-16 12:16:59 UTC
This issue has been closed because it is missing requested data for a long time.
If you are still able to see it on your setup you are encouraged
to update the reproducer and reopen it.

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