Error while running customized default configuration script no such item
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 no such item
Thu Jul 02, 2020 9:17 am
Hopefully, someone will be kind enough to help me find the source of this error.
Router: RB2011UiAS-2Hnd
The following error is logged each time the router boots
Buffer: Memory
Topic: system, error, critical, 54288, 53832, 54288
Message: error while running customized default configuration script: no such item
The error started to appear suddenly 3 weeks ago.
No changes were made to the router configuration.
Would appreciate if anyone can point to what could be wrong and can suggest a solution.
Thank you in anticipation.
Re: RB2011UiAS-2Hnd Booting Log Error
Thu Jul 02, 2020 12:32 pm
.
Message: error while running customized default configuration script: no such item
The error started to appear suddenly 3 weeks ago.
No changes were made to the router configuration.
.
Re: RB2011UiAS-2Hnd Booting Log Error
Thu Jul 02, 2020 1:08 pm
Re: RB2011UiAS-2Hnd Booting Log Error
Thu Jul 02, 2020 1:16 pm
Re: RB2011UiAS-2Hnd Booting Log Error
Thu Jul 02, 2020 1:45 pm
It is not required to panic!
You can usually fix this by changing the name of the wlan interface.
By default it is named wlan1 but you can change that, e.g. I had added some virtual interfaces for different SSID (LAN, guest, etc) and I named all my wlan interfaces with a descriptive name like wlan-guest.
Due to an error in the scripts in 6.47 the scripts will fail when you do that. Instead of default-name the interfaces are searched by their actual name.
So to fix it, it is usually sufficient to rename the physical wlan interface back to wlan1 as it was.
Error while running customized default configuration script no such item
Fri Aug 10, 2018 4:31 pm
We found a bug in recent RouterOS versions (> 6.38) where sometimes disabled objects are not found by Winbox or Scripts.
As you can see in the attached print, sometimes when you try to enable a disabled tunnel you get a «object doesn’t exist» message. After two or three attemps it’s successfully enabled.
The same happens on scripts. But the message is slight different (no such item(4)). Again, we had to put a retry logic on theses steps in order to avoid these errors.
Re: Bug: No such item(4) or object doesn’t exist (4)
Tue Aug 14, 2018 6:20 pm
Hi, I’ve experienced the same issue after update to 6.42.6 from 6.40.4. It seems I’ve found a way to get rid of that bug.
What did I do:
— disabled and renamed ppp interace in question
— created the new one with exactly the same config and original name
— got a current config in text (export file=test)
— carefully searched for all references to renamed interface inside text config (by means of find) and replaced corresponding configuration items
to new interface with original name in winbox. That includes filter, nat, routing, led and traffic flow settings for me.
— enabled new interface and removed renamed one.
Not that much time passed since I do that, but for now I’ve never seen that problem again.
Re: Bug: No such item(4) or object doesn’t exist (4)
Mon Sep 17, 2018 3:06 pm
The same situation in 6.40.9 (bugfix)
[admin@MikroTik-Agg] /routing ospf interface> print
Flags: X — disabled, I — inactive, D — dynamic, P — passive
# INTERFACE COST PRIORITY NETWORK-TYPE AUTHENTICATION AUTHENTICATION-KEY
0 D 10 1 point-to-point none
1 DP Loopback-Backbone 10 1 broadcast none
2 D 10 1 point-to-point none
[admin@MikroTik-Agg] /routing ospf interface> set cost=100 0
no such item (4)
[admin@MikroTik-Agg] /routing ospf interface> set cost=100 1
no such item (4)
[admin@MikroTik-Agg] /routing ospf interface> set cost=100 2
no such item (4)
[admin@MikroTik-Agg] /routing ospf interface>
Re: Bug: No such item(4) or object doesn’t exist (4)
Mon Sep 17, 2018 4:28 pm
Re: Bug: No such item(4) or object doesn’t exist (4)
Mon Sep 24, 2018 1:08 pm
Re: Bug: No such item(4) or object doesn’t exist (4)
Mon Sep 24, 2018 1:28 pm
I’ve repeatedly seen cases where order of parameters did matter, so the ID had to follow the set immediately, although in most cases it is identified by context.
So try the following:
/routing ospf interface set 0 cost=100
/routing ospf interface set 1 cost=100
/routing ospf interface set 2 cost=100
Another point is that if the list changes in the meantime between print and issuing the command, the «user IDs» assigned to the internal references by the print lose validity (this is best visible with the /ip firewall connection elements)
Error while running customized default configuration script no such item
на форуме англоязычном у многих есть мелкие проблемы, днём читал на работе, там уже
было постов 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 no such item
Tue May 26, 2020 11:38 am
Version 6.47rc2 has been released.
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.47rc2 (2020-May-25 12:30):
Important note.
— The Dude server must be updated to monitor v6.46.4 and v6.47beta30+ RouterOS type devices.
— The Dude client must be manually upgraded after upgrading The Dude server.
— Make sure LTE APN Profile name does not match any of the DHCP server’s names if LTE passthrough is used.
— The Dude requires «winbox» policy instead of «dude» to monitor v6.46.4 and v6.47beta30+ RouterOS type devices.
MAJOR CHANGES IN v6.47:
———————-
!) dns — added client side support for DNS over HTTPS (DoH) (RFC8484);
!) socks — added support for SOCKS5 (RFC 1928);
!) user — enable «winbox» policy for groups with «dude» policy;
———————-
Changes since last beta release:
*) api — added ECDHE cipher support for «api-ssl» service;
*) bonding — fixed ALB and TLB bonding modes after interface disable/enable (introduced in v6.47beta19);
*) bonding — fixed packet receiving on bonding slave ports (introduced in v6.47beta19);
*) bridge — added warning message when a bridge port gets dynamically added to VLAN range;
*) chr — added support for hardware watchdog on ESXI;
*) crs3xx — fixed tagged VLAN packet receiving on Ethernet interfaces for CRS354 devices (introduced in v6.47beta49);
*) crs3xx — improved 10G interface initialization on CRS312 devices;
*) dhcpv4-server — disallow zero lease-time setting;
*) dhcpv6-server — do not require «server» parameter for bindings;
*) dns — added support for multiple type static entries;
*) dot1x — added «radius-mac-format» parameter;
*) dot1x — improved Dot1X service stability when receiving bogus packets;
*) dot1x — improved value validation for dynamically created switch rules;
*) email — added support for multiple «to» recipients;
*) ethernet — fixed interface stopping responding after blink command execution on CCR2004-1G-12S+2XS;
*) filesystem — fixed NAND memory going into read-only mode or becoming unstable over time;
*) health — improved stability for system health monitor on CCR2004-1G-12S+2XS;
*) ike2 — added support for RFC8598;
*) ike2 — allow initiator address change before authentication;
*) ike2 — fixed authentication handling when initiator disconnects before RADIUS response;
*) interface — improved system stability when receiving bogus packets;
*) ipsec — added «split-dns» parameter support for mode configuration;
*) ipsec — added «use-responder-dns» parameter support;
*) ipsec — allow specifying two peers for a single policy for failover;
*) ipsec — place dynamically created IPsec policies at the begining of the table;
*) l2tp — added «src-address» parameter for L2TP client;
*) l2tp — added «use-peer-dns» parameter for L2TP client;
*) l2tp — improved dynamically created IPsec configuration updating;
*) l2tp — use L2TP interface when adding dynamic IPsec peer;
*) lcd — improved general system stability when LCD is not present;
*) log — added logging entry when changing user’s password;
*) log — added tunnel endpoint address to establishment and disconnect logging entries;
*) log — fixed logging topic for MAC address learning on a different bridge port events;
*) log — made startup script failures log as critical errors;
*) lte — fixed «band» parameter persistence after disable/enable;
*) lte — fixed «ecno» and «rscp» value reporting on R11e-LTE6;
*) lte — fixed VLAN interface passthrough support;
*) lte — improved stability during firmware upgrade;
*) netwatch — improved Netwatch service stability when invalid configuration values are passed;
*) ovpn — added «use-peer-dns» parameter for OVPN client;
*) poe — fixed missing PoE out settings on CRS354-48P-4S+2Q (introduced in v6.47beta49);
*) port — removed serial console port on hEX S;
*) ppp — removed «comment», «set» and «edit» commands from «PPP->Active» menu;
*) pptp — added «use-peer-dns» parameter for PPTP client;
*) profile — added support for CCR2004-1G-12S+2XS;
*) qsfp — added support for FEC mode (fec74), with the FEC mode disabled by default
*) quickset — fixed invalid configuration applying when performing changes during LTE modem initialization process;
*) routerboard — added «hold-time» parameter to mode-button menu;
*) routerboard — added «reset-button» menu — custom command execution with reset button;
*) routing — improved routing service stability when receiving bogus packets;
*) sfp28 — added support for FEC modes (fec74 and fec91), with fec91 mode already enabled by default;
*) sfp28 — fixed interface linking after power cycle on CCR2004-1G-12S+2XS (introduced in v6.47beta49);
*) switch — correctly enable and disable CPU Flow Control on RB3011UiAS;
*) tr069-client — added LTE firmware update functionality support;
*) tr069-client — added additional LTE information parameters;
*) tr069-client — added additional wireless registration table parameters;
*) tr069-client — added interface type parameter support;
*) tr069-client — added multiple simultaneous session support for diagnostics test;
*) tr069-client — added total connection tracking entries parameter;
*) ups — added battery info for APC SmartUPS 2200;
*) webfig — fixed 5GHz wireless interface «frequency» parameter value list on Audience;
*) winbox — added «auth-info» parameter under «Dot1X->Active» menu;
*) winbox — added «auth-types», «comment», «mac-auth-mode» and «reject-vlan-id» parameters for Dot1X server;
*) winbox — added «bus» parameter for «USB Power Reset» command on NetMetal ac^2;
*) winbox — added «comment» parameter and «dynamic» flag support under «Switch->Rule» table;
*) winbox — added «comment» parameter for Dot1X client;
*) winbox — added «region» parameter for W60G interfaces;
*) winbox — added «skip-dfs-channels» parameter to wireless interface menu;
*) winbox — added enable and disable buttons for «MPLS->MPLS Interface» table;
*) winbox — do not allow to enter empty strings in «caps-man-names» and «common-name» parameters;
*) winbox — fixed WDS usage when connecting to RouterOS access point using QuickSet;
*) winbox — fixed dates and times in interface link up/down properties (WinBox v3.24 required);
*) winbox — fixed wireless sniffer parameter setting;
*) wireless — fixed Nstreme wireless protocol performance decrease;
*) wireless — updated «egypt» regulatory domain information;