Add an XML export would be a nice step, then folks could downgrade if they want. I believe the real issue is how the code for polling and the code for exporting are somehow crossing their streams
I have a W2k3 server and when I do an export of my configuration using 4.0 beta 2 the larger the file the more likely it is going to disconnect and fail. We could not make these huge files with out being able to modify the raw keep time. The more interesting part is while it is creating the export some of the probes I have start failing as if the export function shares the thread with the polling process. This has me worried.
Also when I set a map to export at a timed interval I have more false positives. Once again polling process and disk process...
It seems that once the db hits about 300MB or 400MB there is just too much data for an export to work. (Some internal process times out? The client disconnects, have not tried it directly on the server. I no longer have a modified raw keep time because of this.
My server is a little old but still a very fast machine with 200 probes only using 17% of one core, quad core server. The dude service is running "real time priority" to reduce false positives.
!)--Your reply corroborates much of what I have been seeing, and adds a couple new concerns...I am going to try exporting to a server on the same network, in the same switch as the Dude server and see if gigabit network speed will let the export complete.
Im glad you agree with the XML output feature returning. That could help re-creation of a Dude instance.
You are fortunate to be able to determine the size of your .db file since you are on Win2K. In RouterOS you are essentially 'running blind' regarding any Dude core files. This is one of the few disadvantages I have ascertained running on the native RouterOS platform. Otherwise, over the last years, Dude has been very stable on ROS. I had run on Win2K for a long time, but experienced many more crashes and anomalies on Win2K. I wonder if some of what you are experiencing is OS related?
How about a 'Dude' menu item in 'Tools' in RouterOS? You could:
Kill, or just shutdown the process, without going through some dangerous methods.
Show file size of .db file
Show percentage of processor Dude process is eating up (Win2k can)
Backup/Export Dude instance to the Files menu for drag and drop to a location of your choice.
I could go on for quite a while, but would never send this reply....
Without a clean backup of my instance, I cant do anything (again, without getting dangerous)! Afterall, there is a 'Dude' tab in the device icon for a Dude server...
I wonder if I back off the raw data keep time if it will recreate a smaller file? I have noticed a marked sluggishness on many of my charts, especially the ones with a lot of history. Of course, this takes all the fun out of having all that realtime history that goes back as far as you dare...
Thanks for the reply Lebowski. Its giving me a whole bunch of new ideas, i.e. 'requests'......