KS-Soft

After installing RMA version 1.25 on aprox. 80 machines ( by hand to try to avoid RMA 301: Text file busy - all TextLog tests that are working through symbolic links now returns "301 - File does not exist"...

Not sure I understand the problem. "Text file busy" error could be displayed on some systems by old RMA (1.22) when you used Shell Script test method, right? This problem was fixed in version 1.23. Shell Script test works fine in RMA 1.25, right?
So, what exactly is the problem? TextLog test method does not work with symbolic links? That's because now it supports wildcards in filename. I think its not a problem to use real name of the file instead symbolic link?

Regards
Alex

Well, as Logfiles often are names "stupid", server.log.somepostfix.somedate and stuff like that, a symbolic link comes in handy sometimes, and often applications maintains the link to the supidnamedlogfile themselves.

But I will rework my tests some way.

A at glance, "the 301 File does not exist" seems to be gone, yes - if not - I will report back.

Hm, the "301 Script execution error: Text file busy" is not gone with 1.25 - I get a lot fewer, but still some now and then.

mos-eisley wrote:Hm, the "301 Script execution error: Text file busy" is not gone with 1.25 - I get a lot fewer, but still some now and then.

Could you provide more information, please?
- What exact Linux systems do you use?
- Do you see "Text file busy" error on each system?
- What folder have you specified as "TmpDir" into "rma.ini" file?
- What exact tests do show such error? Shell Script?
- How many tests do show such error simultaneously on one particular system?

Regards,
Max