v6.47.4 [stable] is released!

staticsafe · September 27, 2020, 3:02am

Anybody using this version with a SFP interface? Was the bug introduced with 6.47 with SFP interfaces not getting a link been fixed?

my primary router (a hAP ac) is getting internet via SFP and I’m still running 6.46.6, I’d prefer to run the latest stable but only if the SFP interface works.

Wangz · September 27, 2020, 10:13am

One of my CCR1009’s appears to have developed a memory leak. It had been running 6.47 and and uptime of 3.5 months and yesterday it crashed due to kernel fault, out of memory.
As there was a network interruption anyway I upgraded it, to 6.47.3 as that was the newest available yesterday, and now I see it is steadily using up memory again.
In 11 hours of uptime it went from 275MB used (typical for this router) to 535MB used, or about 23.5MB per hour.
(I am used to some memory usage increase that first increases more rapidly and than flats out but not to this level)

Can this be caused by the problem fixed in this release? (i.e. has it been released now due to reports like this from the field?)
I am not using SMB on this router and it has been firewalled. Can that bug still lead to this memory use?
If not, how can I debug this? I don’t think it is due to a configuration change, more likely due to some new (exploit?) traffic that causes this.
I took a supout.rif and uploaded it to the mikrotik.com site, but how can I find from that info where all this memory is being used?

Same with my Hap Ac2 actually. It was slowly developing a memory leak. From 80MB to 55 and it still going. After i restarted the mikrotik, things work fine then cycle repeats.

do you use doh (dns over https) ? it will reduce the amount of your memory

Nope just regular.

Ixander · September 28, 2020, 7:04am

No, I’ve updated the whole system (all packages are 6.47.4)

 system package print 
Flags: X - disabled 
 #   NAME                                                                                          VERSION                                                                                          SCHEDULED              
 0   routeros-mipsbe                                                                               6.47.4                                                                                                                  
 1   system                                                                                        6.47.4                                                                                                                  
 2 X ipv6                                                                                          6.47.4                                                                                                                  
 3   wireless                                                                                      6.47.4                                                                                                                  
 4   hotspot                                                                                       6.47.4                                                                                                                  
 5   mpls                                                                                          6.47.4                                                                                                                  
 6   routing                                                                                       6.47.4                                                                                                                  
 7   ppp                                                                                           6.47.4                                                                                                                  
 8   dhcp                                                                                          6.47.4                                                                                                                  
 9   security                                                                                      6.47.4                                                                                                                  
10   advanced-tools                                                                                6.47.4

andyhenckel · September 28, 2020, 2:08pm

Something has beed wrong with Dude beginning from some earlier 6.47.x version. Constant “connection reset by peer” and another errors of similar kind.

Now I accidentally happened to see, that after these errors SD card is not visible in System → Disks window and command /disk print shows only partial information (name and free space information missing), but this returns to normal immediately after Dude server is stopped. It looks like Dude server is screwing something up with storage when running. That might actually explain these connection errors and Dude sessions crashing etc.

It does not have to do with the current SD card itself as the card is checked with the computer and reformatted. Then I tried to use another “fresh out of the box” SD card and exactly same scenario occured again.

I’ve got the same problem. 6.47.4 the dude on RB1100AH dude edition with disk1 - 256GB SSD installed - DB now at 2 GB. I vaccumed and adjusted our polling and retention to minimal values. (I keep upgrading in the hopes the issue with go away) . Prior versions were working - though occasionally it would hang up for up to a minute before I could do anything. Basically, this dude instance is barely usable. Now it will go into connection reset by peer, while using it or editing a node record. Then it will re-connect, and is fine - as long as I don’t use it. I really don’t know what to do other than get a new device and start over, with fewer than 150 Nodes and little to no long term data collection on an instance. One thing I did start doing was having the dude scan a subnet every hour, to track new devices on a subnet - useful when a client antenna moves from sector to sector.

pito · September 28, 2020, 10:58pm

I cant install current frmwre to hAP lite “smips”.
no space! =(

santyx32 · September 29, 2020, 12:15am

Export your config and netinstall

mszru · September 29, 2020, 6:53am

You may try to install current “long-term” version first and then upgrade to this “stable”.

6.46.7 - 7464 KB (current long-term)
6.47.3 - 7580 KB (previous stable)
6.47.4 - 7628 KB (current stable)

6.46.7 is one of the smallest builds of RouterOS for smips, that should allow you to install larger build.

Jotne · September 29, 2020, 12:00pm

Install an older/smaller version of the software like 6.44.x then upgrade

nmt1900 · September 29, 2020, 6:19pm

Well… 1100Dx4 and Dude on big network - it’s been tried and abandoned after two attempts. First time - Dude worked for about 4 days until it went 100% CPU and only reboot cured it. Second time rendered whole router inaccessible, but luckily all networking still worked fine. Had to cold reboot by cutting power.

Finally ended up with 1100x4 with 60 GB disk for logs etc. Dude can be used on small networks without problems, but probably less so on the router itself in big networks. Separate Dude server might be a better idea in these cases…

AntoineS · September 30, 2020, 8:46pm

Hi, I confirm the same problem on my RB3011. I have raised a ticket and the bug has been solved in a beta firmware I have tested. I believe (hope) the fix will be shipped in the next release.

staticsafe · October 1, 2020, 1:05pm

Thanks Antoine! I’ll wait for the fix to be shipped then.

CoMMyz · October 3, 2020, 2:33pm

I confirm this no longer works. run-after-reset is now broken. Also flashfig is now broken and will not execute scripts on boot after flashfigged. 6.46.7 also is broken.

After upgrade from 6.47.3 my device stopped working. I was not able to connect over ethernet or WiFi. Even after restore config. I had to do netinstall. Then router booted again. But it is shame, that standard tools like restore backup or restore from RSC does not work. I have tried with releases and backups from 6.47.2 to .4 but I was not able to restore config from backup or RSC. Even reset configuration with option run ater reset does not work. It is even not possible to copy/paste whole export config, I had to copy paste config manually by 20-30 lines.
       routerboard: yes
        board-name: hAP ac^2
             model: RBD52G-5HacD2HnD
     serial-number: 9EF709C73784
     firmware-type: ipq4000L
  factory-firmware: 6.42.3
  current-firmware: 6.44.3
  upgrade-firmware: 6.47.4

biomesh · October 3, 2020, 5:05pm

It worked for me a week or so ago when I deployed a new cap ac. You need to make sure the config is stored in the /flash directory to make sure it is available after the reset. I used 6.47.4.

SiB · October 3, 2020, 10:34pm

export.rsc must be modify, you must put a new first line “delay 20s ;” and that new file upload to RB
export4mod.rsc must be at /flash if that folder exist

CoMMyz · October 4, 2020, 11:07pm

Yes, the file is in flash/file.rsc and we call the reset with that parameter. Same way as it was in previous versions and it was working. After upgrade this has stopped.
There is a delay in the script also at start 15 seconds again as in previous versions.

These tips you are mentioning are also required for past versions so unless “nothing” changed as per Mikrotik then this new version is broken.

Ferda · October 5, 2020, 6:34am

After updating to 6.47.4, my IPTV stopped working. Does anyone know how to fix it? Thank you in advance for your help.

MDE · October 5, 2020, 7:23am

Downgrade

Sent from my VTR-L29 using Tapatalk

Chupaka · October 5, 2020, 10:08am

Yep, downgrade and check if it’s fixed for you.

IPTV is very wide term, so it’s not easy to help without additional info.

rchovan · October 6, 2020, 7:58am

Thanks, I’m aware of delay, tried 15 and 30 seconds. Didn’t help.

SiB · October 6, 2020, 10:19am

rchovan

you can reset configuration (without default)
login winbox via MAC layer
/import original-script.rsc
watch error

after fixing error you must repat reset to clear setting and again import… until you found a proper syntax in script or bug what you can report to support@mikrotik.com .
But, all this should be obvious I think.
My scripts who generate a new branch via that way have in some parts the /system identity set name=“dhcp done”; and I from winbox see the detected RB with part he stuck with error.