Hi, in the trace I see the output "......config out removed" instead of the candidate configuration (in the xml element <commit-script-input>). Did you edit the file? If not, if you read the trace from the CLI, typing "show log <log file name>" do you see the same output?
Here it is what it should look like:
[...]
Jun 7 22:13:46 post: paging: faults 0, reclaims 189, swaps 0
Jun 7 22:13:46 post: other: inb 0, outb 2, snd 1, rcv 1, sig 0, csw 2, icsw 8
Jun 7 22:13:46 commit script input
Jun 7 22:13:46 begin dump
<?xml version="1.0"?>
<commit-script-input xmlns:junos="http://xml.juniper.net/junos/*/junos">
<configuration junos:changed-seconds="1339107013" junos:changed-localtime="2012-06-07 22:10:13 UTC">
<version>10.4R1.9</version>
<system>
[...]
I also compared your output with mine: the configuration-output variable is empty in your log, while it's showing the added configuration in mine:
<rpc-reply xmlns:junos="http://xml.juniper.net/junos/10.4R1/junos" xmlns="">
<configuration-information>
<configuration-output>
[edit interfaces ge-1/0/0 unit 0 family inet]
+ policer {
+ output rate_limiter_400m;
+ }
</configuration-output>
</configuration-information>
So it's like the script is not detecting the configuration change, thus it's not matching the added policer...In order to confirm that, I would like to see the <commit-script-input>!
i would also suggest you to copy the content of same of the script variables to the result-tree, using the copy-of statement, like this:
var $changed-config = jcs:invoke($get-config-rpc);
copy-of $changed-config;
var $changed-lines = jcs:break-lines($changed-config/configuration-output);
copy-of $changed-lines;
This should generate the following output in the trace file:
<configuration-output>+ output rate_limiter_400m;</configuration-output>
<configuration-output>+ }</configuration-output>