performance manager ttp error

its from yesterday. was rolled up automatically @ midnight this morning.

the gzip wasn't curropted and it started a new collection file for today; so the ttp end process should have been done.

did you stop STP daemon before you copied the file over ?

oh yeah, i can open any other TTP the daemon has made and the file itself seems to be fine.. I spooled through it with php and dumped the last few hundred lines... the last timestamp of data looks complete and ends with an tag.

It's a big file (2.8GB) but  the one from 2 days ago was 2.9 and it opened fine so that can't really be the trouble.

tried it on seperate hosts as well to no avail so it seems to be something in the file that performance manager doesn't like.

Wish it was a bit more verbose with it's error message though... like is 68121 some cryptic error code? or a line #? or a timestamp?

are all these files corrupted, can you run "stordaemon action storstpd -cmd archive" and try to open that file ?

If you could provide us with the ttp we can take a look and get back to you.

You could probably save it a shared location and provide us with the link.

Or you could open a CQ defect.

Thanks

Veena

Hi, I have got exactly the same issue. I would appreciate if the reason or, even better, the fix is figured out by somebody...

Thanks.

feel free to have a look.

I dumped the file @ /incoming/T1_20100902_000208_000190105289.ttp.gz

I didn't open the file in an editor... I have a program I wrote in php that stitches ttp files together so we don't have to deal with multiple interval files if we archive the stp collection during the day.

You could however find the timestamps easy enough on a *nix box by doing cat ttpfile.ttp | grep "TIMESTAMP"

That is a completely false statement.

here is just a small sample of the timestamp markups found in just the first 500 meg of the ttp file I uploaded.

Hi Timothy.

I have encountered something similar before.  The issue that I had was the the ttp file was copied from its original location to a directory that had restricted permissions.  The copied file then inherited those when it was copied over.

Check the permissions on your file, make sure it is read/write and not read-only.

Downloading your file to see if I can either convert or open.

Thanks,

Ted