[A Lim]

So it is not possible to have the documentation separate from the cloverleaf server?

[A Lim]

David,

I have found 5.3 Operations Guide. I assume that’s what you are taking about in terms of “dealing with my question”?

I took a quick look at the pages of that document and I only see information on the different sections of the software, but nothing much on maintenance or preventive, unless we are talking about the troubleshooting section.

So maybe I am not looking at the right documentation… Would appreciate if you could help with more specific details? Thanks!

[A Lim]

Interesting that most are running AIX or something other than windows. Unfortunately, the sites I am task to find out about PM on the servers are all running QDX on windows. The sites have either 5.3 or 5.7 version.

David, no I have not read the documentation as I don’t think I have a copy of them. I am rather new to the task and being loaded with such a task to come up with PM at a short period of time, it was a shot in the dark to see if anyone has something which I could based on.

Thanks for the responses all. Will have to mull over the documentation, looking for the information and also take in what you have given. If anyone could add on more on this, that would be of great help.

[A Lim]

No one does anything to cloverleaf periodically to ensure it runs smoothly and with no issues?

[A Lim]

Well, according to the log, the save cycle was successful, but there is no regular msg files found. The next day msg files does not contain the previous day ones that went missing, so looks like the save cycle did happen, but something happened somewhere and causes the old.msg files to be missing.

The script was not written by me, I inherited the site, and this is the 1st time I am looking at the script! I do know that the script remove the “old.msg” ones, then do a save cycle, and then rename the .msg files to something else instead of “old.msg” like “date/time.msg”. I am not sure if it was the save cycle that causes it or something else – like someone did a manual save cycle before it triggers.

But there were no error messages in the auto save cycle logs, and the old messages was not retained from the thread in the next save cycle time frame.

[A Lim]

Russ,

Our daily filesize is not really that large, have not even reached 10MB yet, so I don’t think it’s a filesize limit issue.

I have check the SMAT filenames and they are definitely difference as they are using it to do some reconciliation matching (as a double checking system).

The only possibility that I could think of is that at the present moment when the save_cycle was run, there were things running in the thread, thus making it not possible for save_cycle to run. But I don’t exactly have any documentation or information on what could cause this to fail.

I always thought this would be part of a FAQ Q&A… But it does not look like anyone else has such issues before.

[Author]

Replies