[Spacewalk-list] Spacewalk 1.4 Monitoring issue

[Jan Pazdziora]

On Wed, Jul 20, 2011 at 09:02:40PM +0530, trm asn wrote:
> Hi List,
> 
> 
> Using nocpulse user I am creating the probe fron UI. Client end rhnmd is
> running and port 4545 is accessible from spacewalk server. I am able to
> login using that ssh-dss key.  Whatever the prove I am creating it's on
> "PENDING, Awaiting Update" state.
> 
> SatConfig-generator is already installed. Selinux is in disabled mode. 775
> permission is there for "/var/lib/nocpulse" .
> 
> Below is my "/var/log/nocpulse/execute_commands.log" files output.
> 
> 
> 
> 2011-07-20 20:46:03 154:        Finished with command 164
> 2011-07-20 20:46:03 157: Finished processing commands
> 2011-07-20 20:46:03 95: Freshening heartbeat file
> /var/lib/nocpulse/commands/heartbeat
> 2011-07-20 20:46:03 176: No commands executed, sleeping 60 seconds
> 2011-07-20 20:47:03 96: Starting queue run
> 2011-07-20 20:47:03 95: Freshening heartbeat file
> /var/lib/nocpulse/commands/heartbeat
> 2011-07-20 20:47:03 104:        Attempting to fetch commands (attempt 0)
> 2011-07-20 20:47:03 95:         Queue server URL:
> https://spacewalk.example.com/satconfig/cgi-mod-perl/fetch_commands.cgi?cluster_id=203a64827eb3&node_id=2&role=lead&version=1.0
> 2011-07-20 20:47:03 95:         Successfully got command list
> 2011-07-20 20:47:03 95:         CommandQueueParser parsing 411 bytes
> 2011-07-20 20:47:03 95:         Parser::parse returning
> NOCpulse::CommandQueue=HASH(0xa17c70c)
> 2011-07-20 20:47:03 95:         CQ::fetch_commands returning
> NOCpulse::CommandQueue=HASH(0xa17c70c)
> 2011-07-20 20:47:03 121:        Fetched 1 commands
> 2011-07-20 20:47:03 130:        Running command 164
> 2011-07-20 20:47:03 131:                Command line is:
> /usr/bin/scheduleEvents
> 2011-07-20 20:47:03 95:         Attempting to run command 164
> 2011-07-20 20:47:03 95:                 Last started: 164; Last completed:
> 164
> 2011-07-20 20:47:03 95:         164 is not executable (old, last started
> 164, last completed 164)
> 2011-07-20 20:47:03 150:        Not executing command 164: 164 is not
> executable (old, last started 164, last completed 164)

This means the command 164 is an old command, already completed.

You might want to dig deeper into the log file to find the first
occurence of the 164 thing.

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat