rsc script stops on error

When you run the import file-name = file.rsc script stops on error.
Can I say the import command ignore errors and continue?

Thanks
Dmitry

try to open the rsc in a text editor. paste it and see where the error is coming.

Probobly, you have a script form another ros version. MT change syntax all the time.

Hi,

This happens for sure on RB750 units. Both shall be for e.g. at v5.20 and the latest firmware. One is set at factory default with no config, that is a fresh unit. If you export from the used unit and try to import to the new unit, you still get this error. This happens in a full export/import. It also happens if you export the data using the ‘compact’ option and then import and you also get certain changed items in the new unit missing, even if you just rename the interfaces e.g. ‘ether1’ got renamed to ‘ether1 - Data’. This change and other changes to the config shall not be reflected on the new unit when the data is imported.

It’s my opinion, although I’ve not checked this out, that it’s the order that the commands are imported back in that screw this up.

Rgds,
Mark.

do like i told. One line by line, and you’ll see where the error appere.

Thanks for your answer, but as you can see I did not ask how to find the error. I asked how to ignore the error.
A common problem - the creation of something that already exists. Yes it is possible to check for the existence before every creation. But it’s much easier to ignore the error and continue to configure.

Try add, default=no to the line where the error come.

there is no way to ignore. Just to remove the line, or to rewrite script. And to do this. you need to know where the error is, figure out. why, and remove, or rewrite the syntax.

it is not possible to ignore errors, if one is encountered script will stop regardless you are running script from file or form /system script or simply written in cli.

On older ROS versions script just ignored the line with error and continued to execute, that was changed due to problems with debugging and inconsistencies that appeared when running scripts. Now this ensured that you get same result always. And you notice problem sooner.

usually it is good idea to create script with source from your RSC and then open it in CLI, automatic highlighting will work till it encounters error. If everything is ok with highlighting till the end of the script, you will need to execute this line by line.

Is there any hope to get a feature for ignoring errors? I’m trying to fetch-upload files to list of servers but if first one of them gives error then all of them fail.