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.

Any idea?

Thanks for help!

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:

Rebooting...
Stopping services...
failed to stop ppp: std failure: timeout (13)
Restarting system.

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.

Upgraded to v4.11 and problem still remains. Randomly when rebooting, I get the above error. Randomly after reboot PPP settings show up or not.

I've contacted support with this issue. I will post response when I hear back.

is MNDP enabled ?
try to disable >ip neighbor discovery on all interfaces and report back .

is MNDP enabled ?
try to disable >ip neighbor discovery on all interfaces and report back .

MNDP is only enabled on a one bridge interface. The PPP (l2tp and pptp) interfaces are not part of this bridge though. The only interfaces that are in this bridge are EoIP.

What's weird is that it seems random. I checked for invalid settings all around the OS, and I couldn't find any. When I try to add an interface (/interface l2tp-server add OR /interface pptp-server add) it hangs, and no settings are applied. Also, in /ppp *, everything is empty (no defaults, no entries at all).

A few things to note: When I took a supout.rif and uploaded it to my Mikrotik account (supout.rif viewer), it showed two failures:
/export -> "falure:"
/ppp -> "failure:"
Everything else looked ok though.

It's almost like the underlying config for ppp is corrupt (but why it comes up ok randomly is really odd).

I'll try to disable MNDP for every interface and run with that for awhile and see what happens.

This is really odd. After disabling MNDP on all interfaces it stopped happening for awhile. I then did a bunch of reboots and it was working great for about 5 reboots. Then after the 6 time it came up, PPP was completely gone. I've got it up for now (and I'm scared to reboot!)

The files are there, the config is apparently ok, but it randomly can't bring up all the configuration. This really sounds like a very deep internal problem with the reading of the raw data files.

you should try to disable each mndp in one reboot . after disabling all mndp you and mikrotik devs should give me many karmas
i have found this bug long time ago and report it to support but after some emails from me and them, they ignored it like many others

The thing is, I only had one interface using MNDP. I disabled that single interface and rebooted. It worked ok for about 5 reboots, but returned to randomly failing after that. I don't know if it's a problem with MNDP alone, I think there may be many potential causes to this problem.

I'm still waiting for a response from support.

Are you using PCQ on that router ?

Nope, no PCQ, no simple queues, no queue trees.