As The Dude is still in testing stage I suggest moving on to v6.36rc builds for those who experience issues with previous builds.

Known issues in v6.36rc39(reported for fixing):

All entries below are already confirmed and reported to DEV for fixing.

Higher priority problems:
* ...
Lower priority problems:
* Adapt dude link labels to be able to show 10G traffic and larger (snmp part left to fix);

Enhancement requests:
* Add option to use functions and oids in notification messages;
* Add AES encryption method to dude side snmp v3 profiles;
* Add option to configure user in a way to allow access only to certain panels;
* Add new notification method that allows to use ROS tool sms.

Changes in v6.36rc11 and prior v6.36rc builds:

*) arm - added Dude server support;
*) Fixed - Client crash on version upgrade, if client had previously already connected to some server;
*) Fixed - Various server crashes. Reported in following support tickets:
2016031666000464, 2016032366000987, 2016033066001025, 2016032266000283

Hi

Thank you for bringing The Dude back to active develpment, it is an awsome tool!

Now to my feature request. I have two RouterOS devices behind a CPE in the following setup:

CPE: 203.0.113.200 (and 192.168.88.1 on the LAN side)
hAPac01: 192.168.88.11
hAPac02: 192.168.88.12

Now I do a port-forward on the CPE so I get:
203.0.113.200:8292 -> 192.168.11:8291
203.0.113.200:8293 -> 192.168.12:8291

Now I want to add three devices in The Dude, monitored as RouterOS devices, but I am unable to add more than one device (the CPE) as there are no way of specifying what port The Dude should use to connect.

Could you please implement a feature so that we get the option to specify what port to connect to? I know this brings with it a lot of complications with regards to ping and so forth, but would another option be to specify a sub-device? Then you'll know that it is behind the other device, and only reachable on port xxxx or zzzz?

Good day,
i began to test new dude on ccr 1036, so far i see when i restart (dude or all ROS) snmpv3 passwords are gone (private, md5,des), i have manually write them again, mmm maybe a little slow when i login.... same behavior on 6,34,4 and 6,35,1

@kmk

This problem was originally intended to be avoided by using Dude agents in those remote networks. Somehow I don't think that such option will get implemented. I haven't seen many NMS that allow this kind of option.

@Percanta

Tried on one of my test server. In there snmp profile info didn't seem to go missing. Is that the only section where your dude server loses configuration?

Good day

i was doing some test and passwords arent losing but i have to push button "apply" on snmp profile window, i tried to wait if maybe some delay after reboot but 3 hours and nothing change, i have to push "apply". there are password but its not applied ....
i have 2 ccr 1036 and same result, the config came from 4beta3. another things work good.
regards

Feature request: syslogging to have severity levels

Got my mikros sending remote syslog to dude at info level. Gets very spammy looking at syslog in the dude when i can't filter on severity

@Percanta

How I tried it:
* Created new snmp profile on dude server.
* Rebooted server host.
* Reconnected with client.
* Tried to run snmpwalk on some device with v3 private snmp profile.

First try failed but on second try device seems to answer without issues.

@craigroser

Possibly we could add that filter, after some syslog section reworks that are planned.

Good news!
Btw, it will be so nice to can use hostnames for devices, not just IP addresses, because in that way we can add devices what are use DDNS (for example your IP-Cloud future), when IP Address is changes on the device...

Happy to hear news from you guys!

Search RB or other devices, does not work in SUBMAP
Search only works in SUBMAP

on version 3.6 works OK

Any ETA when " * Add new notification method that allows to use ROS tool sms." will be available in RC builds?

Changes in v6.36rc13 and prior v6.36rc builds:

*) Functions - Optimizations/Rework (work in progress) mostly background changes.


@abis

DNS name usage for SNMP servers has already been reported as feature request.

@autostoper76

Which exact filter/search option do you mean?

@padrecc

No ETA on that feature yet.

Any ETA when " * Add new notification method that allows to use ROS tool sms." will be available in RC builds?

@padrecc

No ETA on that feature yet.

Main reason we wait to use the new Dude. We're running the old Dude on a PC with UPS and UMTS-Stick so we get alarmed even when the whole Network/Power goes down. This cant be done with SMS Providers as there are a lot of components need to work to send the SMS.

Any word on adding SNMP Trap capability?

Please upgrade the embedded version of Winbox to 3.4 in the Dude.

Any word on adding SNMP Trap capability?

+1 for snmp trap functionality

Thanks for continuing to develop DUDE

Question, I'm finding that DUDE on multicore routers runs only a single core at 100% - even with MultiCPU checked - tired on various models.

Anyone have a solution ?

Changes in v6.36rc16:

*) Refactored functions (background changes).
*) fixed - Various memory leaks.
*) fixed - 100% load on one cpu core by dude process on server startup in some cases.
*) The Dude admins now rely on ROS users. User requires dude policy to connect to server.
*) The Dude now uses ROS log. Requires dude topic to be added in log rules.
*) Removed data based commit interval change option in server settings.
*) Added comment option for servers in client loader window.

Notes:
* Old logs will not be transferred to new log.
* Log viewing option will at some point be returned in client.

@ScottReed @nimbo78

SNMP trap receiver just in feature requests stage.

@themenace

Sounds like one of the bugs that should be fixed in latest build.

Folks,

I do not know if I'm going blind, but I see any more mib, image, ... let alone upload any file. What is going on?

Regards,

Vagner Felipe Becker

OK Just to clarify

Update from rc13 (working but with 100% CPU issue) to rc16 using built in package upgrade, since upgrade to rc16 Dude Client now reports "Login failed: invalid username or password (6)"

AND CPU 100% on single core also

@VagnerBecker

On what platform do you have that problem. As far as I checked file and mib sections displayed content correctly. Uploading files also worked.

@themenace

1. Did you try to login with your ROS admin acc?
2. If you still have problem with cpu load by dude process please generate supout file on server host and send it to support@mikrotik.com

After updating rc13 to rc16 the new dude client just stucks at "Getting stuff" and never loads. The RX/TX in the left corner of the client is 0/0 . The client didnt offer an update, so I did it manually by downloading the RC16 exe installer.

Also tried deleting all users from the dude before update (except admin) and after update adding them to ROS - with right permissions. It logins, but gets stuck.

If i enable the new logging feature i can see that the dude server is working on background (getting up and down log lines for devices in Winbox), but impossible to connect trought the client.

@mondychan

Can you please generate supout file during period when you are trying to connect to server with client and send it to support@mikrotik.com?

@mondychan
Tips ...
1. Try running as administrator
2. If running on a Terminal Server, close all other Dude Sessions

@VagnerBecker

On what platform do you have that problem. As far as I checked file and mib sections displayed content correctly. Uploading files also worked.

CHR 6.36r16 vmware vmdk, follows the pictures for you to see. Can see that is missing files...

@mondychan
Tips ...
1. Try running as administrator
2. If running on a Terminal Server, close all other Dude Sessions

Hello, got answer from MKtik support. Your user has to have read/write policy enabled trought ROS groups.

Works OK now.

Changes in v6.36rc19:

*) Added back log panel in client.
*) Fix server crash that could happen on server disable event.
*) Various optimizations for server/client.
*) Various fixes and optimizations for db commit related issues. Now dude will warn user in form of log entry if there is to much commits queuing up. This will most likely point towards problem with storage drive write performance, asking user to move db to some faster storage medium.

Feature request: snmpset functionality for The Dude. Very usefull for updating software on some devices, for ex. cambium epmp 1000. Now we're using external snmpset software on Windows Server PC through tools menu for reboot, upgrade, port enable\disable on switchs and so on.

Changes in v6.36rc20:

*) Fixed various server crashes.
*) Various performance improvements on server side background tasks.
*) Removed some legacy setting that were no longer relevant as the dude users are now controlled by ROS AAA.

Changes in v6.36rc20:

*) Fixed various server crashes.
*) Various performance improvements on server side background tasks.
*) Removed some legacy setting that were no longer relevant as the dude users are now controlled by ROS AAA.

krisjanis, where the mib, fonts, images,... ?

krisjanis, where the mib, fonts, images,... ?

Checked on ESXi CHR and The Dude server does not seem to have that problem there. Have you tried deleting the dude dir and let server recreate it a new? Not that you should create dude backup before this experiment.

----

@abis

1. Run client as administrator when update is required. Otherwise it cannot overwrite certain files in program files.

2. We are aware that rc client is missing, it should be added back soon.

Yep, I didn't think to do that!

Thank's!

@abis

1. Run client as administrator when update is required. Otherwise it cannot overwrite certain files in program files.

2. We are aware that rc client is missing, it should be added back soon.

Yep, I didn't think to do that!

Thank's!

@abis

1. Run client as administrator when update is required. Otherwise it cannot overwrite certain files in program files.

2. We are aware that rc client is missing, it should be added back soon.

This does not work on windows 10. I ended up having to find the temp folder remove the prefixes on all the files and manually copy them into the program folder.

krisjanis, where the mib, fonts, images,... ?

Checked on ESXi CHR and The Dude server does not seem to have that problem there. Have you tried deleting the dude dir and let server recreate it a new? Not that you should create dude backup before this experiment.

I found the problem, always used a second partition for the directory dude, indicate the directory as the root partition happens this problem.

Taking advantage of what the correct way to collect data from the wireless connection ccq, signal, signal to noise, ...
Below is an example of how to use, but the plot is unstable, what should I do?

ros_command(":put [interface wireless registration-table get number=0 rx-ccq]")

another situation, the following command does not work by dude why?

ros_command(":put [/interface find type~"wlan"]")

Yep, I didn't think to do that!

Thank's!

@abis

1. Run client as administrator when update is required. Otherwise it cannot overwrite certain files in program files.

2. We are aware that rc client is missing, it should be added back soon.

This does not work on windows 10. I ended up having to find the temp folder remove the prefixes on all the files and manually copy them into the program folder.

Only other reason I can think of why it would fail, even if the client is running with administrative rights would be some zombie processes of the dude still running in background.

Hello,

since upgrade with changed authorization, does not work radius auth in dude. Only in mikrotik host device.
When i try authorize in dude with radius credentials, in radius logs i become: rlm_pap: CRYPT password check failed. I think it is because dude sends password not crypted to freeradius.

when i log to mikrotik with Dude: freeradius[21455]: Login OK:

BR
krtko

And another one Feature Request: different Appearance for different types of devices. For ex. for Some-name-BSU device type MikroTik-AP I need to display frequency, bandwidth etc, for Some-name-CPE device type Mikrotik-CPE I need to display Signal strength, CCQ etc. It's not a prblem when you device list counts for ~50 devices, but when it grows for 2000 it can be more comfortable to assign like 'batch Appearance' for device types in one click

Changes in v6.36rc27:

* Server package is now made smaller. Client side content upgrade is now removed from it and is downloaded straight from our cloud. So workstations on which client is used will require access to wan. Alternatively upgrade must be done by reinstalling the client on each new release.
* Added - check-box in dude client loader settings to allow upgrade/downgrade without prompting user each time;
* Fixed - Some server crashes.
* Fixed - Server adds some latency to when monitored device is pinged from server;
* Fixed - Client - local pinger broken; (it still does require the client to used with admin permissions)
* Fixed - Dude loader preferences menu "auto connect at startup" check-box seems to be ignored;
* Fixed - Importing db from v4 removes assigned icons from devices/device-types;
* Fixed - Memory related default function no longer work;

PS - If older client crashes after update it's ok, just kill the process through task manager and relaunch the dude once again as administrator. Then the update process will be finished. This problem with loader crash on update should also be fixed starting with rc27.

Warning: Client might not be updatable till tomorrows morning from cloud.

Hello. Here we are used to use The Dude as we think its an awesome network monitoring tool.

One little thing is really annoying me, which is monitoring BGP Routers.
When we enable the RouterOS checkbox, all those routes (more then 1.2 million) would be read by The Dude.
If I enable SNMP, this also occur, which makes The Dude go crazy when a link become unavailable and all those routes need to disappear from the router.

So, would be possible to create a checkbox to not import routes from these types of routers?
This would be really effective as we could monitor all those services behind these routers but with only this exception.
I did read about many interfaces (used to appear in a PPPoE Server) also make this kind of behavior.

Maybe two checkbox, one about PPP interfaces and another about Routes.

Thanks!!!

Hello. Here we are used to use The Dude as we think its an awesome network monitoring tool.

One little thing is really annoying me, which is monitoring BGP Routers.
When we enable the RouterOS checkbox, all those routes (more then 1.2 million) would be read by The Dude.
If I enable SNMP, this also occur, which makes The Dude go crazy when a link become unavailable and all those routes need to disappear from the router.

So, would be possible to create a checkbox to not import routes from these types of routers?
This would be really effective as we could monitor all those services behind these routers but with only this exception.
I did read about many interfaces (used to appear in a PPPoE Server) also make this kind of behavior.

Maybe two checkbox, one about PPP interfaces and another about Routes.

Thanks!!!

may be some Custom Tables (or "Selected Tables" SNMP/RouterOS) would be better?

Warning: Client might not be updatable from cloud till tomorrows morning.

@krtko

I'll check the issue with freeradius. With user-manager as far as I can tell there were no such problem.

@ploquets @nimbo78

We'll check what we can do about these two scenarios.

Client update from cloud is now fixed.

I have noticed the "Getting stuff..." time has gone back to nearly a minute again. Any chance this can go back to what it was earlier in the beta process (previous full beta build) and in 3.6?

will dude server ever support the RB1100AHx2 or do i have to get aRB3011 ?

Changes in v6.36rc28:

* Fixed problem with sqlite storing it's tmp data on system disk even if dude store is located on another disk. Now vacuum tmp data is located in dude store and should no longer cause problems on server hosts with small system disk.
* When device is added it will now have the same ROS login credentials as for the user in currently logged in client by default.

Changes in v6.36rc28:

* Fixed problem with sqlite storing it's tmp data on system disk even if dude store is located on another disk. Now vacuum tmp data is located in dude store and should no longer cause problems on server hosts with small system disk.
* When device is added it will now have the same ROS login credentials as for the user in currently logged in client by default.

At last. Will test that.

Please, return web access feature. Only these stops to migrate dude from windows to CCR. Enything else what we need is worked in 6.35.2 on CCR1016.

Please, return web access feature. Only these stops to migrate dude from windows to CCR. Enything else what we need is worked in 6.35.2 on CCR1016.

+1

Please, return web access feature. Only these stops to migrate dude from windows to CCR. Enything else what we need is worked in 6.35.2 on CCR1016.

+1

We have some ideas for new web interface for The Dude. However at the moment there is no known date on when this new web interface might get implemented and in what form it will come. Note that it will not be re-implementation of old web interface.

We have some ideas for new web interface for The Dude. However at the moment there is no known date on when this new web interface might get implemented and in what form it will come. Note that it will not be re-implementation of old web interface.

Thanks for the feedback.

@krisjanis

Is there a way to move partial data from one instance of the Dude to another? We would like to stay with backhaul monitoring at our old windows based system and move the handling of the CPEs to a second dude/chr (to do updates). May be later we want to reintegrate this.

So we would like to export part of the device list and import it into a second dude.

If this could be done the same way as we could export ROS-Configuration and then paste it to a terminal it would be great. You started to integrate dude into ROS with user management. Go further 

@ste

At the moment that is not possible, but it might be in the future. We have some plans similar plans regarding The Dude to what you described in your request.

@ste

At the moment that is not possible, but it might be in the future. We have some plans similar plans regarding The Dude to what you described in your request.

Hi! Can you provide info about this 'some plans' to us?)

@nimbo78

The idea is to add cli support for the dude server side so that it can be managed not only from windows client side but also straight from ROS cli and possibly add it all to winbox/webfig later down the road. Just to note, there is no ETA for this change yet.

If management from Winbox is added that means it could be also managed from TikApp or at least view some info for devices - up/down status etc.
I'd like to see that a lot even if not soon. And for me at least if this is possible there is no real need for web access.

If management from Winbox is added that means it could be also managed from TikApp or at least view some info for devices - up/down status etc.
I'd like to see that a lot even if not soon. And for me at least if this is possible there is no real need for web access.

Admins would like to ssh into dude server and just say: /dude outages print, /dude device [id=xyz] print. Works with the slowest Smartphone connection.

Looks like automatic vacuuming was implemented...
... but had no impact on db file size. Also the vacuum-db command run for few seconds without any impact.

another one FR: I need DNS names for SMTP (and other) Servers, not only IPs... for ex for smtp.gmail.com

Changes in v6.36rc30:

* Optimizations for larger setups where most monitored devices use secure mode. 
* Fixed - Agent re-connection problems.


@jarda

Any size difference when vacuuming is done on windows for that dude db backup?

@nimno78

Adding option to allow use of dns name for smtp servers in the dude is already in our feature request todo list.

I have never done vacuum on the windows as old dude doesn't have such feature. Therefore I expected some effect.

Is the rc30 secure mode optimisation relevant to snmp v3?

Hello,

Big crash on rc30 with RB3011 everytime I double click on Snmp > Interface > Ethernet... on a simple HP switch

6.35.1 BREAKPOINT at: 9a3a8de6

eip=9a3a8de6 eflags=206
edi=9a3a89ae esi=7ee2dbb0 ebp=a5e738 esp=a5e730
eax=1 ebx=7ee2d970 ecx=0 edx=0

log:
cw:1411 backtrace:[416733, 4168a3, 500cbc, 74008c, 5007c4, 502dc6, 6f8b7a, 4010b9, 40129c, 7b87414c, 7b878202, 7bca6c8c, 7bcaa33b, 7bca6c52, 7bc61f94, 4000a54d]

unreliable backtrace:

modules:

stack: 0 4292512000

6.36rc30 ACCESS VIOLATION at: 68c8a5

eip=68c8a5 eflags=10202
edi=477fca esi=9f4338 ebp=99f008 esp=99efd8
eax=6f0d80 ebx=19bead0 ecx=0 edx=19beb5c

log:
 419d13, 47c3a7, 47e194, 47e2c7, 41112b, 44b812fa, 44b833a0, 44b8364b, 44b20e51, 40e9be, 4f8c2f, 4fa079, 647172, 4010b9, 40129c, 7b87414c, 7b878202, 7bca6c8c, 7bcaa33b, 7bca6c52, 7bc61f94, 4000a54d]

unreliable backtrace:

modules:

stack: 0 4292493400

6.36rc30 ACCESS VIOLATION at: 68c8a5

eip=68c8a5 eflags=10202
edi=477fca esi=1b8df70 ebp=99f008 esp=99efd8
eax=6f0d80 ebx=1b9b550 ecx=0 edx=1b9b5dc

log:
cw:1411 backtrace:[4, 41639b, 41650b, 4f7c0b, 68b5dc, 4f8a78, 4fa079, 647172, 4010b9, 40129c, 7b87414c, 7b878202, 7bca6c8c, 7bcaa33b, 7bca6c52, 7bc61f94, 4000a54d]

unreliable backtrace:

modules:

stack: 0 4292493400

6.36rc30 ACCESS VIOLATION at: 68c8a5

eip=68c8a5 eflags=10202
edi=477fca esi=1b82b60 ebp=99f008 esp=99efd8
eax=6f0d80 ebx=1b40058 ecx=0 edx=1b400e4

log:
race:[4, 419d13, 42d53f, 42dedf, 41112b, 442b72fa, 442b93a0, 442b964b, 44256e51, 40e9be, 4f8c2f, 4fa079, 647172, 4010b9, 40129c, 7b87414c, 7b878202, 7bca6c8c, 7bcaa33b, 7bca6c52, 7bc61f94, 4000a54d]

unreliable backtrace:

modules:

stack: 0 4292493400

It's very inconvenient to install additional client version each time the dude is updated. Please, make the client more universal like winbox is to allow the connection to multiple server versions.

This is My Dream for SNMP monitoring:

IF-MIB::ifRxccq.1
IF-MIB::ifTxccq.1

Or or something like this because by API is very hard, please implement this new option..

i updated to version 6.36rc30 and email notifications doesn't work anymore.Emails are not sent.

yes, email doesn`t working for me too(

@jarda

1. No these optimizations are not related to snmp v3. 
2. Regarding multiple dude versions. At the moment it will stay as it is with client. Making it to work similarly as winbox would take fair amount of work and at least for now we do not plan to change that.

@vosgessystemes

Crash confirmed and reported for fixing.

@kolorasta @smile__2006

Problem with email notification confirmed and reported for fixing.

Hi,

In version 6.35.4, "the dude" seems to create multiple "builtin" panels each line with "admin <ip address>" which cannot be removed.  If you try, it would just say "cannot change builtin".
Is there anyway to remove these multiple "builtin" panels?  Right now, I have over 50 of them than cannot be removed and the list keeps growing.  Normally there is only one builtin.

Also, is there anyway to automate adding devices or any procedures in the dude?  If you are a company that needs to add over 1000 devices, it would speed things up a lot with some sort of scripting or api support.

Quinn

It's very inconvenient to install additional client version each time the dude is updated. Please, make the client more universal like winbox is to allow the connection to multiple server versions.

+1 I agree very much with this.  Alternative is to use a web interface.
Quinn

@qiet72

1. I suggest to upgrade to upgrade to latest v6.36rc build and check what is going on with panels there. I haven't observed such issue, yet.
2. At the moment only option would be to use Auto-discovery and hope that it will cover most of those devices that you want to add. CLI/API support is something that come in the future. 
3. Old web interface has been removed from The Dude and new one will be implemented in time.

Changes in v6.36rc33:

*) Fixed - Mac to Ip lookup.
*) Fixed - Auto-discovery feature for devices behind remote Agents.
*) Fixed - Access of ROS tab for devices behind remote Agents.
*) Fixed - Email notifications. (broken in one of previous rc builds)
*) Fixed - Client crash which occurred when in device management window in snmp tab
under interface section any of interfaces where double clicked for detailed view.

Changes in v6.36rc33:

*) Fixed - Mac to Ip lookup.
*) Fixed - Auto-discovery feature for devices behind remote Agents.
*) Fixed - Access of ROS tab for devices behind remote Agents.
*) Fixed - Email notifications. (broken in one of previous rc builds)
*) Fixed - Client crash which occurred when in device management window in snmp tab
under interface section any of interfaces where double clicked for detailed view.

Email notifications now works!!!

I upgraded from RC 21 to 33 this morning.  Upgraded the client to the same version and now when I try to login I get "Operation Failed: 10053:An established connection was aborted by the software in your host machine"

Suggestions on how to troubleshoot this.

I used TCPing on port 2211 and it is responding so I believe the service is up.

I upgraded from RC 21 to 33 this morning.  Upgraded the client to the same version and now when I try to login I get "Operation Failed: 10053:An established connection was aborted by the software in your host machine"

Suggestions on how to troubleshoot this.

I used TCPing on port 2211 and it is responding so I believe the service is up.

I have the same problem.
Version 6.36rc33 contains a bug.
I had to downgrade back to the version 6.36rc28.

@dnelson @jcmelik

Download latest client from our download page and reinstall it manually. I think that was the version where we started work on moving client update side to cloud. And this first build didn't contain all of the needed changes, so it cannot update it self to most recent builds.

after install 6.36Rc33, its not accept login user name and password......

Username and password now integrated with user management in ros, you need to use username and password using log into router.

Username and password now integrated with user management in ros, you need to use username and password using log into router.

dont understand what you mean... Im trying to login dude server via dude client and its says me wrong username and password.

Username and password now integrated with user management in ros, you need to use username and password using log into router.

dont understand what you mean... Im trying to login dude server via dude client and its says me wrong username and password.

You dude server is on Mikrotik is it service on RouterOS use username and password that you use to log on that router. Before some RC version there is not any more user management in Dude.

My English is not so good but just put username and password in dude client that you use in winbox, telnet... when login in Mikrotik where dude server is installed. You will see now in Dude client not have any more options to define username and password they are integrated with username and password in RouterOS.

I create new user group and select dude there... now is ok.. thank you verymuch

Changes in v6.36rc35:

*) Fixed - Auto-discovery tool has problems with typical homeAP/CPE setups that 
has snmp enabled. (only one of many devices gets discovered. Due to identical LAN networks.);
*) Fixed - Outages cannot be removed by "remove resolved" button;
*) Fixed - Link label does not show correct link speed when ROS mastering type is used, in place of 1G it shows 10M.

Changes in v6.36rc35:

*) Fixed - Auto-discovery tool has problems with typical homeAP/CPE setups that 
has snmp enabled. (only one of many devices gets discovered. Due to identical LAN networks.);
*) Fixed - Outages cannot be removed by "remove resolved" button;
*) Fixed - Link label does not show correct link speed when ROS mastering type is used, in place of 1G it shows 10M.

Great! our oldest resolved outage is from 2010 .

How to report bugs to the dude and ask for new features? Could I use just this thread on forum?

Use this thread or write to support.

upgraded from rc10 to rc36 looks like dude is crashing now or maybe its just busy doing something like vacuuming? 

 /dude> print

action timed out - try again, if error continues contact MikroTik support and send a supout file (13)

EDIT: I rebooted it works now.

EDIT2: or not I'll send a supout
 >/dude print
         enabled: yes
  data-directory: dude
          status: 
> /dude print
         enabled: yes
  data-directory: dude
          status: applying settings: enabling: reading db object #1441
> /dude print
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)

Same problem here the dude crash after 10 to 60 min.

Downgrade to 36rc30 solves the problem.

I have just downloaded the latest (rc36) .vhdx file on 3 different systems and when it boots, it sees "Missing Operating System" and bugger all else.  :)  Yup, Gen 1 Hyper-V VM (as you don't yet support Gen 2 - how far off is this?) and all else is fine.  I even drop a working CHR.vhdx file in place and it boots, so the VM is fine, but it looks like the .vhdx on the download site is broken.

Same here. VMDK on ESXI also says missing operating system. Previous version worked fine.

@craigroser @kivimart

Yes, if possible send supout files from problematic dude hosts to support@mikrotik.com, We will take a look at what is causing problems there.

@HiltonT @ethernet

We are aware of problem that starting with some of latest rc CHR image has been broken. It should be fixed soon. 
If fresh CHR VM is needed I would just take bug-fcix or current chain CHR image and use it. After upgrade to latest rc it will work fine.

As for Gen2 for HyperV as far as I know currently there would be no benefit for it for ROS VMs which is why there is no support for it.

"As for Gen2 for HyperV as far as I know currently there would be no benefit for it for ROS VMs which is why there is no support for it."

So, you don't count looking towards the future as important?  Gen 1 VMs are the old pre-UEFI format VM container with heaps of hardware emulation that's been optimized in a Gen 2 VM.  A number of Linux distros now support Gen 2 so it isn't just Windows 8 (Server 2012) and later Microsoft Operating Systems that support the new format.  I don't know for how much longer Microsoft will support the old Generation 1 VMs (I'm betting for quite some time), but all of the development will be going into Gen 2 and later.

Were I developing something now, I'd be supporting Gen 2 not Gen 1.  But that's me.

Oh, and thankyou, Thankyou, THANKYOU for fixing the remote agents - this is a MASSIVE part of how I wish to use The Dude!

It means I can now not only monitor our own network and our client Internet connectivity, but I can also monitor, live, their internal network performance - and that's awesome!

Now, I'm wondering about hosting my Dude Server in Azure which means that even when our office Internet drops out (which, being in Australia, is par for the course) I will have The Dude monitoring all or our clients all of the time.  I just wonder how "chatty" this would be, therefore what the cost of running The Dude in Azure would be...

#YouMadeMeAHappyManAgain

v6.36rc36

Unable to "Add static" to the map. - shows "No netmap"
Also unable to copy static item, If I try to copy it just disappears from the map and it is unable to make undo.

@LATNET

Problem reported for fixing.

@dnelson @jcmelik

Download latest client from our download page and reinstall it manually. I think that was the version where we started work on moving client update side to cloud. And this first build didn't contain all of the needed changes, so it cannot update it self to most recent builds.

Unfortunately, the above procedure doesn't work.
I updated Dude server from rc28 to rc36 and manually reinstalled Dude client from rc28 to rc36, but I still can't connect to the Dude server (get "Operation Failed: 10053:An established connection was aborted by the software in your host machine").
Build rc28 working well.

@jchmelik

You get this error on multiple workstations with latest rc client? Is server status on ROS host "running"?

@jchmelik

You get this error on multiple workstations with latest rc client? Is server status on ROS host "running"?

Yes I get this error on multiple workstations and the Dude server status is running.
Dude server operates normally, because I getting a notice about outages. I cannot connect using dude client only.

@jchmelik

Can you please try the latest build once more and generate supout file right after connection attempt. Then send that supout to support@mikrotik.com I'll check if something useful is saved in debug logs.

in rc37 snmpwalk dosnt work, no profile, nothing happens.

@kivimart

That should be fixed in next build.

Changes in v6.36rc39:

*) Fixed - diff64 function broken.
*) Fixed - snmpwalk tool broken, status message simply shows "no profile" when starting. (broken in one of previous rc builds)
*) Fixed - Cannot add static element to map shows "no netmap" in status field.
*) Fixed - Server syslog port cannot be changed back to default if it has been changed one to something else.
*) Fixed - Server cannot upgrade device is it is running old ROS version: 5.26, 6.7. Error: "router packages unknown"
*) Fixed - Various problems with snmp probes.

Settings - > click OK :

6.36rc28 ACCESS VIOLATION at: 45d000

eip=45d000 eflags=210202
edi=2c esi=99e298 ebp=99e26c esp=99e23c
eax=29 ebx=0 ecx=5dcaa74 edx=29

log:
4, 776e5de3, 776e5dae]

sm:backtrace:[4, 419c6f, 4dbe36, 4dc20d, 4dc3a7, 411087, 775684f3, 77546c40, 77546541, 77546300, 40e91a, 4fa287, 4fb6d1, 6487c2, 4010b9, 40129c, 760338f4, 776e5de3, 776e5dae]

unreliable backtrace:

modules:

Looking good so far,  Thanks for bringing it back.  

Two feature request:

Upgrade device firmware via Dude 
Be able to upload .dpk files to devices via Dude

Change font size/type in static element - crash.

Changes in v6.36rc40:

*) Fixed - "..." button function in link configuration menu.

NOTE:  There is a server crash in rc40 which occurs on server disable, that also breaks db export process. We will fix it in next build.

@LATNET

Both issues reproduced in rc40 and reported for fixing.

@bclewl1ns

You mean option to upload the branding package? 

Having multiple Dude versions installed in different virtual / physical devices for testing purposes (mainly RC builds). For each version I have separate client software installed on my pc (in its own folder). When I move forward with some versions, I do not need the relevant client anymore. So I go to the "add and remove programs" in Windows7 and I see that there is only one "dude" record to be unistalled while 8 different versions are installed now. Why I cannot remove selectively in the standard way the versions of the dude client that I do not need anymore?

Please, make the windows installer to work correctly with versions! Each version should have its record in "add and remove programs" to be managed separately if installed separately.

Please, put the logging to syslog files back.

Please, make again backup/restore function to be working like in old 3.6 or 4.0b3 version.

Please, make the dude commands usable from CLI to be available from Winbox (and webfig) too. Think about to make these functions manageable from the dude client too, if possible.

Those additional parameters for dude vacuum-db are not described in the manual: Are they relevant?

Tried vacuum again with rc40.
Running vaccuum-db in "running" state it failed with message: So I have stopped dude and run vacuum-db again. Now the state is "vacuum in progress" but cpu is iddling, doing nothing. How it can vacuum the database when doing nothing?

Thank you.

Edit: I removed the unnecessry clients by running uninstall.exe in their folder. But never mind the records in control panel - add and remove programs should be correct anyway.

@Jarda.

Having multiple Dude versions installed in different virtual / physical devices for testing purposes (mainly RC builds). For each version I have separate client software installed on my pc (in its own folder). When I move forward with some versions, I do not need the relevant client anymore. So I go to the "add and remove programs" in Windows7 and I see that there is only one "dude" record to be unistalled while 8 different versions are installed now. Why I cannot remove selectively in the standard way the versions of the dude client that I do not need anymore?

Please, make the windows installer to work correctly with versions! Each version should have its record in "add and remove programs" to be managed separately if installed separately.

 Same as for many other programs The Dude installed treats it similarly as program upgrade which is why there is only one entry in windows installed program list. I could check if we can make a portable archive version this. I guess it would fit this case better than installer?

Please, put the logging to syslog files back.

That will be done at some point. I understand the issue of syslog not being a whole with The Dude server as it was originally.

Please, make again backup/restore function to be working like in old 3.6 or 4.0b3 version.

It's doubtful that Import/Export button will make reappearance in client side. 

Please, make the dude commands usable from CLI to be available from Winbox (and webfig) too. Think about to make these functions manageable from the dude client too, if possible.

Before we do this, we will dig around and bit more in CLI side. After that we could possibly start adding support for The Dude in Winbox/Webfig side.

Those additional parameters for dude vacuum-db are not described in the manual:
Code: Select all

Code: Select all

[jarda@CHR virt1] /dude> vacuum-db 
append  as-value  do  file  interval  once  without-paging

Are they relevant?

Vacuum command has no arguments, so they are not relevant.

Tried vacuum again with rc40.
Running vaccuum-db in "running" state it failed with message:
Code: Select all

Code: Select all

action timed out - try again, if error continues contact MikroTik support and send a supout file (13)

In v6.36 final build there wont be that problem, rc39/rc40 had some crashes that occurred on server disable this prevented: disable, export, vacuum.

Thanks for the answers and looking forward to 6.36.

Topic locked. Continuing discussion in http://forum.mikrotik.com/viewtopic.php?f=8&t=110424