Hi!

Version 6.39.2. RouterBOARD 750G r3.Trying:

/system reset-configuration keep-users=yes no-defaults=yes skip-backup=yes run-after-reset=flash/my_export_7.rsc

The configuration remains empty after this.

The file flash/my_export_7.rsc was produced by /export file=flash/my_export_7. When I use /import flash/my_export_7.rsc
configuration is restored normally.

Were is the problem?

BTW. After upgrading to 6.39.2 from factory 6.36.1 I've got the warning in config:
# Warning: memory not running at default frequency
set memory-frequency=1200DDR

/system routerboard settings set memory-frequency=? shows me "MemoryFrequency ::= 800DDR | 1066DDR | 1200DDR".
What is the default value from these ones?

Thank you in advance.

The reload of configuration is some unconfirmed bug, I encountered it as well and I have reported it but AFAIK nothing has been done about it yet.

Just ignore the frequency warning, it is a known bug as well. It appears to be very hard to compile a correct table of default frequencies for all models...
(so some models issue this incorrect warning)

pe1chl, thank you for the answer.

I've added ':delay 15s' at the top of rsc file and all works fine now.

Ah that is interesting, maybe it would solve the issue in my case as well. (was on a RB951G)
It is hard to debug these things because there is no logfile. When I reported the issue it was promised that they would
look into:
- writing a log of errors encountered during the import
- continuing the import as long as no disastrous errors occur
As it is now, whenever a minor problem occurs during the import the processing stops right there and you have an incomplete
config that may render the router inaccessible to see what happened. (especially on the low-end models without RS232 port)

@dfxer - Thanks for the tip on the delay in the config file! I have added this to my config file and it was able to import without a problem. You saved me a lot of time troubleshooting this issue, so thanks again for taking time to post how to work around it!

- Adam

+1 Thx

I think it is very unfortunate that:
1. the delay is still necessary. It would seem so trivial to include it in the first-boot procedure but it has not been done even after more than a year...
2. still nothing is done about the error recovery and logging. that would likely be more work.

Found this thread after same problem and guess what - the problem has not been fixed!
Years go by...

But now we have v7 beta so it certainly should be solved there! (all problems will be solved in v7)

Starting from ReuterOS 6.46.1, the run-after-reset script is not executed at all!
Can someone help?
Thanks

Starting from ReuterOS 6.46.1, the run-after-reset script is not executed at all!
Can someone help?
Thanks

Please read the above reply by dxfer to obtain your help.

run-after-reset seems to be working for me on 6.47b60. I am using "/delay delay-time=15s" at the top of my script. I found it helpful to issue the command "import file-name=[your file]" to test to functionality of the script prior to issuing the reboot command, there were some errors that were preventing the script from running properly (and with no logging at that stage you can't diagnose it).

run-after-reset seems to be working for me on 6.47b60. I am using "/delay delay-time=15s" at the top of my script. I found it helpful to issue the command "import file-name=[your file]" to test to functionality of the script prior to issuing the reboot command, there were some errors that were preventing the script from running properly (and with no logging at that stage you can't diagnose it).

Thank you very much "/delay delay-time=15s" is the key.

It is important to note that for certain devices, the configuration has to be placed inside the flash\ folder.

Warning: If the device has a folder named "flash", then the confscript.rsc file must be stored in that folder to work with "run-after-reset" command. Everything outside this folder is stored on the RAM drive which contents are deleted on reboot or power cycle.

But now we have v7 beta so it certainly should be solved there! (all problems will be solved in v7)

And there will be made new problems!

If someone else comes along and finds this topic as I did you may find it useful to reference my code repository which contains a baseline configuration that can be applied with `run-after-reset` to get a working router.