[Spacewalk-list] Schedule System Reboot not working

[Eric]

----- Original Message ----
From: Tom Brown <tom at ng23.net>
To: Eric <linux_4_u at yahoo.com>; spacewalk-list at redhat.com
Sent: Tue, July 27, 2010 3:23:32 AM
Subject: Re: [Spacewalk-list] Schedule System Reboot not working

> Bump.
>
> Still having issues with pxt pages. I have tried increasing debug = 5 in
> /etc/rhn/rhn.conf, but I still do not see anything revealing.
>
> It seems strange that I can do this through the API, but not through the Web
> GUI.
>

whats the default umask on the box? Does the apache error log tell you anything?

The default umask is 022.  
I see the following in httpd/error.log
[Tue Jul 27 08:23:03 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin
/suexec)
[Tue Jul 27 08:23:04 2010] [notice] Digest: generating secret for digest authent
ication ...
[Tue Jul 27 08:23:04 2010] [notice] Digest: done
[Tue Jul 27 08:23:04 2010] [notice] mod_python: Creating 4 session mutexes based
 on 256 max processes and 0 max threads.
[Tue Jul 27 08:23:04 2010] [notice] Apache configured -- resuming normal operati
ons
[Tue Jul 27 08:23:13 2010] [error] (111)Connection refused: proxy: AJP: attempt 
to connect to 127.0.0.1:8009 (*) failed
[Tue Jul 27 08:23:13 2010] [error] proxy: AJP: failed to make connection to back
end: localhost
[Tue Jul 27 08:23:17 2010] [error] (111)Connection refused: proxy: AJP: attempt 
to connect to 127.0.0.1:8009 (*) failed
[Tue Jul 27 08:23:17 2010] [error] proxy: AJP: failed to make connection to back
end: localhost

I did do a tcpdump on 127.0.0.1 8009 and I did see traffic going there. I think 
the errors are from the restart and tomcat taking a bit before
it is fully up and running.

Can I assume that errors related to pxt issues should show up in the apache 
error_log?

Thanks,

-Eric