Error while running customized default configuration script std failure timeout 13

Error while running customized default configuration script std failure timeout 13

Thu Dec 02, 2021 8:20 pm

Re: Unable to export configuration on hAP mini 7.1

Thu Dec 02, 2021 8:28 pm

one of many v7 bugs, probably

Re: Unable to export configuration on hAP mini 7.1

Fri Dec 03, 2021 9:22 am

Export RouterOS 7.1 on:
SXT 5HPnD r2 (600Mhz) slow
SXT 5HPnD (400Mhz) weeeeery slow.
Some time when logging in on the 400MHz I do get «Console has crashed; please log in again.»

Edit:
When trying to export the config from SXT 5HPnD (400Mhz), it does loos its client and Winbox may be disconnected (connected using cable)

Use Splunk> to log/monitor your MikroTik Router(s). See link below.

Re: Unable to export configuration on hAP mini 7.1

Sat Dec 04, 2021 11:31 am

Export RouterOS 7.1 on:
SXT 5HPnD r2 (600Mhz) slow
SXT 5HPnD (400Mhz) weeeeery slow.
Some time when logging in on the 400MHz I do get «Console has crashed; please log in again.»

Edit:
When trying to export the config from SXT 5HPnD (400Mhz), it does loos its client and Winbox may be disconnected (connected using cable)

Re: Unable to export configuration on hAP mini 7.1

Mon Dec 06, 2021 3:45 pm

I’ve got exactly the same issue with the hAP-mini. But mysteriously, it is not happening with mAP lite, which I think it shares CPU (but different architecture)
Anyone knows if that’s the correct place for reporting this kind of issues, or any other we find out in 7.1 ?

Re: Unable to export configuration on hAP mini 7.1

Mon Dec 06, 2021 3:51 pm

Re: Unable to export configuration on hAP mini 7.1

Wed Dec 08, 2021 2:02 am

Same issue on a hAP lite with a fairly minimal configuration.

Upgraded from 6.48.6 to 7.1 by selecting upgrade channel in System > Packages. Export stalls after emitting the /ip dhcp-server section, the next would be /interface bridge port under v6.

Edit: If left in this state for some time the following messages appear in the terminal window followed by more of the export:
#error exporting /mpls/traffic-eng/path
#error exporting /routing/bgp/template
#error exporting /routing/pimsm/instance

Stalls again after /interface ovpn-server server, next would be /ip address. Continues after the following message:
#error exporting /interface/vpls/bgp-vpls

And again after /ipv6 nd, next would be /system clock. Continues after the following messages:
#error exporting /mpls/interface
#error exporting /mpls/ldp
#error exporting /mpls/ldp/accept-filter
#error exporting /mpls/ldp/advertise-filter
#error exporting /mpls/ldp/interface
#error exporting /mpls/ldp/local-mapping
#error exporting /mpls/ldp/neighbor
#error exporting /mpls/ldp/remote-mapping
#error exporting /mpls/traffic-eng/interface
#error exporting /mpls/traffic-eng/tunnel
#error exporting /routing/bgp/connection
#error exporting /routing/bgp/vpn
#error exporting /routing/pimsm/bsr/candidate
#error exporting /routing/pimsm/bsr/rp-candidate
#error exporting /routing/pimsm/interface-template
#error exporting /routing/pimsm/static-rp

Eventually finished well over 2 hours later!

Источник

Error while running customized default configuration script std failure timeout 13

Wed Dec 08, 2021 11:46 am

Hello,
I tried to upgrade one router in our network to 7.1, but unfortunately, it ended up badly.

After reboot, there was high packet loss (90+%) to the router and to a few people behind it. Winbox hung up on «logging in». I was able to login via SSH a few times for a short amount of time, so I could get to these last messages:

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Thu Dec 16, 2021 10:34 pm

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Tue Dec 28, 2021 7:52 pm

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Mon Jan 03, 2022 10:28 am

Thank you for reply.

I still wait for reaction or at least some new major version with more bugfixes which could mean «we got this».

It might be bad luck, but it was second RouterBoard I upgraded back then and that happened. I do not have confidence to continue with similarly configured devices.

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Tue Jan 11, 2022 3:11 am

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Fri Jan 14, 2022 11:14 am

Thank you for sharing this info.

I can netinstall that board for sure, but still — I wish to know that what caused this issue was fixed, so probably I do not encounter that on any other board upgrades.

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Fri Jan 14, 2022 5:37 pm

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Sat Feb 19, 2022 10:47 am

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Sat Feb 19, 2022 12:15 pm

It is probably better not to try to upgrade such old and small devices, especially when you are not using any of the newer features.
(and also not when you were using features that are not yet stable in v7)

It really is not an upgrade to just do for the fun of it. And certainly not on a remote router.

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Sun Feb 20, 2022 12:25 pm

It is probably better not to try to upgrade such old and small devices, especially when you are not using any of the newer features.
(and also not when you were using features that are not yet stable in v7)

It really is not an upgrade to just do for the fun of it. And certainly not on a remote router.

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Tue Mar 01, 2022 2:19 pm

I get it and common sense says the same. But they said in the newsletter that even an historical devices can benefit better performance with RoS 7, you get the idea that it’s not a problem. After they released v7 even for those devices, I expect to get it working if not with initial stable release, then after some time for sure.

I have no problem with having devices like RB750 deprecated for RoS 7. Well, RB750 isn’t that bad, if you consider other like RB433

Wish luck to developers with getting the most types of their routerboards compatible, bug free and working without problem. They already did a tons of great work.

Источник

Error while running customized default configuration script std failure timeout 13

Sun Dec 13, 2009 8:54 pm

Hi there!
I have a serius problem with MT.
We used for 2 years, and no problem occured. Until this month.
We bought a new PC, because the old one crashed (capacitor problem)
The new hardware is:
-FPS 400 PN power.
-Intel E5300 CPU
-Intel dg41ty motherboard
-Kingstone HyperX X500 1GB.
-MT in DOM module v5. licesne
-Samsung HD161 Sata HDD for proxy.
-MT 4 port LAN card
-SMC PCI LAN card.

This MT sometimes crash, and after that, we can’t manage remotely.
When I go to the server room, the console is active, and working fine.
I try to restart, the service stopping screen is go, and after that nothing happens.
After some trying and wait a couple of minutes, this error message active:
«Failed to stop route: std failure: timeout (13)» or
«Failed to stop ppp: std failure: timeout (13)»
I turn it off the PC, because nothing happens.
After the boot, the route and the ppp and sometimes the proxy not working, and only local console and MAC Winbox avaible.
I tried many times the restore, but it won’t work. The restore works partially many times.
After few shutdown and restore attempt, the system going to be work finally with old-new configuration mixed, but if I want reboot, all situation going from the beginning.

-I downgraded the MT to 4.2.
-Some packages disabled, for example: xen, routerboard, ipv6
-The CPU usage around 4-5 %
-2 ISP and 1 test ISP, 1 bridge, 1 proxy, 1 routed network

I changed few days ago to another type e5300, but the problem still.

Thanks for help!

Re: Mikrotik crashing randomly, reboot, restore failure

Thu Sep 30, 2010 8:56 am

I just had this exact problem.

I upgraded from v4.8 to v4.9.
1) Copy all package files to router
2) Reboot
3) Upgrade to v4.9 successful, but /interface l2tp-server and /interface pptp-server completely empty.
4) When I try to reboot, it hangs for a bit and says:

The solution:
For me, the solution was to disable all logging to disk. This fixed the problem, and all PPP entries showed up again.

If anyone else has this issue and knows a specific cause, please post, I still haven’t found the root cause yet.

Источник

Error while running customized default configuration script std failure timeout 13

на форуме англоязычном у многих есть мелкие проблемы, днём читал на работе, там уже
было постов 90. Частично разработчики что-то ответили, одних просили прислать логи,
и дебаг-файл, другим сказали, что что-то поправят снова в будущих версиях.
Но когда делают большие обновления и есть минимум 10-20 у которых что-то уже
не то, уже повод обождать.
Также обратите внимание на параметры в окне Ресурсы: а именно на кол-во
записанных секторов и на кол-во всего записанных секторов.
Данные значения у людей на прошивке 6.47 растут достаточно быстро.

Пару визуальных проверок сделали, и если грубо, то параметр «Total Sector Writes»
на старой прошивке за 30 дней примерно показал параметр в 417 тысяч, на новой
прошивке этот показатель равен 1,5 миллиону за 52 минуты аптайма.
Я не говорю что это плохо, но память, в микротике, NAND, и что с ней там делают.

2300 перезаписаных секторов, при этом есть устройство которое не обновил, другой модели (750g3), но тоже как свич и даже чуть больше, там конфиг изредка меняется, там за 14 дней аптайма 36000, явно что-то не так.
З.Ы. Глянул на старичка RB751U-2HnD которого тоже обновил, там за 3 часа 1200 и на hAP за то же время 1100.

У меня на двух 951Ui-2nD за двое суток всего 5700

Источник

Error while running customized default configuration script std failure timeout 13

Fri Feb 05, 2021 10:51 am

RouterOS version 6.48.1 has been released in public «stable» channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

What’s new in 6.48.1 (2021-Feb-03 10:54):

*) crs312 — fixed missing SwOS firmware on revision 2 devices;
*) crs3xx — fixed packet duplication when multiple bonding interfaces are created for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx — fixed port-isolation on ether37-ether48 ports for CRS354 device;
*) crs3xx — improved load balancing on bonding interfaces for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx — improved system stability when bonding and IGMP snooping is used (introduced in v6.48);
*) hotspot — fixed «idle-timeout» usage with RADIUS authentication;
*) hotspot — fixed special character parsing in «target» variable (CVE-2021-3014);
*) ike2 — fixed phase 2 rekeying with enabled PFS (introduced in v6.48);
*) ike2 — improved stability when invalid certificate is configured (introduced in v6.48);
*) ike2 — properly register packet time after expensive CPU operations;
*) interface — fixed pwr-line interface linking (introduced in v6.48);
*) ipsec — improved stability when processing IPv6 packets larger than interface MTU;
*) led — fixed default LED configuration for RB911-5HnD;
*) package — do not include multiple The Dude packages in HDD installer;
*) snmp — fixed «send-trap» functionality (introduced in v6.48);
*) switch — fixed interface toggling for devices with multiple QCA8337, Atheros8327 or RTL8367 switch chips (introduced in v6.48);
*) winbox — fixed enable/disable button presence for «Bridge/Hosts» menu;
*) wireless — renamed «macedonia» regulatory domain information to «north macedonia»;

To upgrade, click «Check for updates» at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

Please keep this forum topic strictly related to this particular RouterOS release.

Источник

I’ve started getting the same recently, I ran it with RUST_LOG=debug and got:

$ RUST_LOG=debug RUST_BACKTRACE=1 cargo build --bin runner
...
[2019-04-10T20:17:35Z DEBUG globset] built glob set; 0 literals, 2 basenames, 0 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 1 regexes
[2019-04-10T20:17:35Z INFO  cargo::util::rustc] updated rustc info cache
[2019-04-10T20:17:35Z DEBUG cargo] exit_with_error; err=CliError { error: Some(Os { code: 13, kind: PermissionDenied, message: "Permission denied" }

stack backtrace:
   0: failure::backtrace::internal::InternalBacktrace::new::h8d6d9abeadb47698 (0x560037bbe9f3)
   1: failure::backtrace::Backtrace::new::hc66590c50d3d5a2a (0x560037bbe69f)
   2: cargo::sources::path::PathSource::walk::h156df4e3b728b6cd (0x5600376ea601)
   3: cargo::sources::path::PathSource::walk::h156df4e3b728b6cd (0x5600376ea955)
   4: cargo::sources::path::PathSource::list_files::h7bdb580f82226180 (0x5600376e761e)
   5: cargo::sources::path::PathSource::last_modified_file::h327eac454607eb9c (0x5600376eabcd)
   6: <cargo::sources::path::PathSource<'cfg> as cargo::core::source::Source>::fingerprint::he55956dc9cd9bc4c (0x5600376eb815)
   7: cargo::core::compiler::fingerprint::pkg_fingerprint::hc05670626ba10a80 (0x56003775cc9c)
   8: cargo::core::compiler::fingerprint::prepare_build_cmd::hb5f29c2698ba1b07 (0x560037759366)
   9: cargo::core::compiler::custom_build::prepare::h28cf21ba620f65f9 (0x560037511e7b)
  10: cargo::core::compiler::compile::h87829c6f40288c15 (0x56003775ef06)
  11: cargo::core::compiler::compile::h87829c6f40288c15 (0x56003775f4ab)
  12: cargo::core::compiler::compile::h87829c6f40288c15 (0x56003775f4ab)
  13: cargo::core::compiler::context::Context::compile::hc59394fe8834cb3d (0x5600376d2ce4)
  14: cargo::ops::cargo_compile::compile_ws::hcd03deb2dd8e37c3 (0x5600374a5af0)
  15: cargo::ops::cargo_compile::compile::h57d9550ec550a472 (0x5600374a1db8)
  16: cargo::commands::build::exec::hc595c6a2b98b3047 (0x56003742b17d)
  17: cargo::cli::main::hbbce86d40638f2f0 (0x5600373f0c55)
  18: cargo::main::ha6397e0193ae2834 (0x56003740ee1f)
  19: std::rt::lang_start::{{closure}}::h783b28c4e06ed518 (0x560037404ca2)
  20: {{closure}} (0x560037be5812)
             at src/libstd/rt.rs:49
      do_call<closure,i32>
             at src/libstd/panicking.rs:297
  21: __rust_maybe_catch_panic (0x560037bf18f9)
             at src/libpanic_unwind/lib.rs:87
  22: try<i32,closure> (0x560037be63dc)
             at src/libstd/panicking.rs:276
      catch_unwind<closure,i32>
             at src/libstd/panic.rs:388
      lang_start_internal
             at src/libstd/rt.rs:48
  23: main (0x560037411441)
  24: __libc_start_main (0x7f6db17d8222)
  25: <unknown> (0x5600373e6028)), unknown: false, exit_code: 101 }
error: Permission denied (os error 13)

I’ve added anything that’s chowned by root or any other user to the exclude package field in my Cargo.toml.

My ~/.cargo is all recursively chowned by me.

Not sure how to fix this now. The backtrace is a bit obscur.

This is using the rust 1.34 pre-release, but also on 1.33.

Edit: If I remove a folder chowned by root, this works fine. Even though the folder is in my exclude list.