I have a CCM 5.1 cluster, I can pull logs via RTMT from the publisher
fine, but when I try from the subscriber, I get the following:

"An Error Occurred while Processing Request"

I am able to connect via RTMT and see performance stats (Virtual
Memory, CPU, registered phones, etc...) I just can't view log files.

Initially I couldn't even get into RTMT, so I restarted Cisco
Servicability and I was able to get in... Any ideas what could be
wrong here?



Jonathan

[ Post a follow-up to this message ]

RTMT bombs if it tries to touch a file and does not have permission.
This was initially caused by CSCsh36576.  Open a TAC case so we can get
in with remote account and correct file permissions.  RTMT limitation is
documented in CSCsi33810 and partial workaround supplied in CSCsi80661
whereby RTMT will continue collecting files even if error occurs on one
file.

/Wes

Jonathan Charles wrote:
> I have a CCM 5.1 cluster, I can pull logs via RTMT from the publisher
> fine, but when I try from the subscriber, I get the following:
>
> "An Error Occurred while Processing Request"
>
> I am able to connect via RTMT and see performance stats (Virtual
> Memory, CPU, registered phones, etc...) I just can't view log files.
>
> Initially I couldn't even get into RTMT, so I restarted Cisco
> Servicability and I was able to get in... Any ideas what could be
> wrong here?
>
>
>
> Jonathan
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]

Thanks, I will open a case later today


Jonathan

On 8/15/07, Wes Sisk <wsisk@cisco.com> wrote:
> RTMT bombs if it tries to touch a file and does not have permission.
> This was initially caused by CSCsh36576.  Open a TAC case so we can get
> in with remote account and correct file permissions.  RTMT limitation is
> documented in CSCsi33810 and partial workaround supplied in CSCsi80661
> whereby RTMT will continue collecting files even if error occurs on one
> file.
>
> /Wes
>
> Jonathan Charles wrote: 
>

[ Post a follow-up to this message ]