Media_index.c: Failed to stat

General Help
1

Running FreePBX 13.0.192.16 and Asterisk 13.17.0

Recently used the “warm spare” method to move to a new server (new VM on KVM/proxmox)

The server has about 120 remote extension, and had no real problems before.

However, a couple times now, we’ve had all or most of the extensions go offline. In one case, they all showed as OK, but couldn’t be reached (and endpoints showed unregistered from their perspective), and in another case, they went UNREACHABLE.

After some investigation, it looks like this issue happened right around the time this did:

[2017-08-20 10:33:07] WARNING[5413] media_index.c: Failed to stat /var/lib/asterisk/sounds/ru/intercom.sln16: No such file or directory
[2017-08-20 10:33:07] WARNING[5413] media_index.c: Failed to stat /var/lib/asterisk/sounds/ru/vmnotify-instructions2.sln: No such file or directory
[2017-08-20 10:33:07] WARNING[5413] media_index.c: Failed to stat /var/lib/asterisk/sounds/ru/vmnotify-instructions.sln16: No such file or directory
[2017-08-20 10:33:07] WARNING[5413] media_index.c: Failed to stat /var/lib/asterisk/sounds/ru/vmnotify-thankyou.sln16: No such file or directory
[2017-08-20 10:33:07] WARNING[5413] media_index.c: Failed to stat /var/lib/asterisk/sounds/ru/followme.sln: No such file or directory
[2017-08-20 10:33:07] WARNING[5413] media_index.c: Failed to stat /var/lib/asterisk/sounds/ru/vmnotify-instructions2.sln16: No such file or directory
[2017-08-20 10:33:07] WARNING[5413] media_index.c: Failed to stat /var/lib/asterisk/sounds/ru/vmnotify-followed-by-pound.sln16: No such file or directory
[2017-08-20 10:33:07] WARNING[5413] media_index.c: Failed to stat /var/lib/asterisk/sounds/ru/vmnotify-instructions.sln: No such file or directory

After that, about 550 more similar lines. And then 16 seconds later:

[2017-08-20 10:33:24] ERROR[29345] manager.c: Unable to process manager action 'login'. Asterisk is shutting down.
[2017-08-20 10:33:24] ERROR[29345] manager.c: Unable to process manager action 'Logoff'. Asterisk is shutting down.
[2017-08-20 10:33:36] VERBOSE[5370] asterisk.c: Remote UNIX connection
[2017-08-20 10:33:36] VERBOSE[29847] asterisk.c: Ignoring asterisk shutdown request, already in progress.
[2017-08-20 10:33:36] VERBOSE[29847] asterisk.c: Remote UNIX connection disconnected
[2017-08-20 10:33:36] VERBOSE[5337] asterisk.c: Ignoring asterisk shutdown request, already in progress.
[2017-08-20 10:33:36] VERBOSE[5337] asterisk.c: Ignoring asterisk shutdown request, already in progress.

And then this, which I think is Asterisk restarting:

[ 2017-08-20 10:34:06] Asterisk 13.17.0 built by mockbuild @ jenkins2.schmoozecom.net on a x86_64 running Linux on 2017-07-27 17:42:42 UTC

In one instance, I had force stop asterisk, and then fwconsole restart, to get endpoints to come back (fwconsole restart by itself hung, saying it couldn’t stop asterisk).

Do I just need to do what is stated in this article, rm the files listed:

?

Thanks in advance people.

2

Failed to stat errors don’t cause extensions to go offline nor does it cause Asterisk to crash. You can just do what I stated in the previous post if you want.

1 Like
3

Thanks Andrew, did do that. Will see of it helps.

Do you think 500 failed to stat errors could put enough stress on the server to cause the extensions to go unreachable until the end points re-register?

4

No. there’s no stress involved in a failed to stat.

5

Okay, thanks.

Here’s a different angle. We had maxexpirey set to 300 for some reason on that server. Do you think that could be the cause?

6

Maybe it really depends on what the phones are expecting.

7

Great, thanks