Bug 849628 - osad make the remote command function error.
Summary: osad make the remote command function error.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Spacewalk
Classification: Community
Component: Clients
Version: 1.6
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Pazdziora
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space18
TreeView+ depends on / blocked
 
Reported: 2012-08-20 11:46 UTC by dylan
Modified: 2012-11-01 16:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-25 18:24:06 UTC
Embargoed:


Attachments (Terms of Use)

Description dylan 2012-08-20 11:46:09 UTC
Description of problem:
i use the osad to manage may system. These days i found a very odd problem when i am using remote-command feature.

my script is very simple and only have two lines:
#!/bin/sh
ps -elf

but the result is not appeared as i expect, since the result has been cut off in each line. 
For example:
1 S root      3715     1  0  80   0 - 20524 wait   19:05 ?        00:00:00 /usr/bin/python /usr/
1 S gdm       3742     1  0  80   0 -  5513 -      19:05 ?        00:00:00 /usr/bin/dbus-launch
1 S gdm       3743     1  0  80   0 -  3293 -      19:05 ?        00:00:00 /bin/dbus-daemon --fo
4 S gdm       3744  3558  0  80   0 - 39480 -      19:05 ?        00:00:00 /usr/bin/gnome-sessio

Actually, the entire message should looks like this:
1 S root      3715     1  0  80   0 - 20524 -      19:05 ?        00:00:00 /usr/bin/python /usr/sbin/osad --pid-file=/var/run/osad.pid
1 S gdm       3742     1  0  80   0 -  5513 -      19:05 ?        00:00:00 /usr/bin/dbus-launch --exit-with-session
1 S gdm       3743     1  0  80   0 -  3293 -      19:05 ?        00:00:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

See? The end of the message in each line is missing.

Version-Release number of selected component (if applicable):
The client is suse 11 sp1.

How reproducible:
After hours trying, I find the problem may have some relation with osad agent.
the osad is configured to start at the runlevel of 3,5

When i reboot the system and the osad is online, the problem occurs. Then if i restart the osad using "service osad restart" the problem seems to be fixed.

And this seems not to be a service start sequence problem, since i already set the osad to be the last service to start in the client system.

Any idea? Really need help from you guys....

Great thanks



Steps to Reproduce:
1. set the osad to start at runlevel 3,5
2. reboot the system
3. schedule a remote-command action.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jan Pazdziora 2012-08-25 18:24:06 UTC
I believe it's the value of the COLUMNS environment variable which affects the ps command's output. On my Fedora 17, the ps man page mentions that the --columns parameter to ps can also be used to override the perceived width of the output.

I suggest you just add that argument to your remote script.

Please reopen if it does not help.

Comment 2 dylan 2012-08-27 06:59:05 UTC
got it. Really thx. And user the -w option in ps command can also help to solve the problem.

(In reply to comment #1)
> I believe it's the value of the COLUMNS environment variable which affects
> the ps command's output. On my Fedora 17, the ps man page mentions that the
> --columns parameter to ps can also be used to override the perceived width
> of the output.

I suggest you just add that argument to your remote script.
> Please reopen if it does not help.


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