[asterisk-bugs] [JIRA] (ASTERISK-28520) Failed to create temporary storage

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team closed ASTERISK-28520.
------------------------------------


> Failed to create temporary storage
> ----------------------------------
>
>                 Key: ASTERISK-28520
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28520
>             Project: Asterisk
>          Issue Type: Information Request
>      Security Level: None
>          Components: Resources/res_http_media_cache
>    Affects Versions: 16.5.0
>         Environment: Centos 6
>            Reporter: Volodymyr Dotsenko
>            Severity: Critical
>
> We intensively use Asterisk ARI  /bridges/{bridgeId}/play method for playing external files using http/https, sometimes we've experienced an issue that files stop playing with errors in log:
> [Sep  3 11:45:34] WARNING[45902][C-0000001a] res_http_media_cache.c: Failed to create temporary storage for 'http://berize-dev.com/common/utils/tmpfile/get/40cd90b0-c8d6-41f8-bb1c-cef5c18410b6-ee1dc704.wav'
> [Sep  3 11:45:34] WARNING[45902][C-0000001a] res_http_media_cache.c: Failed to create temporary storage for 'http://berize-dev.com/common/utils/tmpfile/get/40cd90b0-c8d6-41f8-bb1c-cef5c18410b6-ee1dc704.wav'
> [Sep  3 11:45:34] WARNING[45902][C-0000001a] file.c: File http://berize-dev.com/common/utils/tmpfile/get/40cd90b0-c8d6-41f8-bb1c-cef5c18410b6-ee1dc704.wav does not exist in any format
> [Sep  3 11:45:34] WARNING[45902][C-0000001a] file.c: Unable to open http://berize-dev.com/common/utils/tmpfile/get/40cd90b0-c8d6-41f8-bb1c-cef5c18410b6-ee1dc704.wav (format (slin)): No such file or directory
> [Sep  3 11:45:34] WARNING[45902][C-0000001a] res_stasis_playback.c: 1567500334.252: Playback failed for sound:http://berize-dev.com/common/utils/tmpfile/get/40cd90b0-c8d6-41f8-bb1c-cef5c18410b6-ee1dc704.wav 
> After reboot server and some time about 1 hours the error disappears and everything work as expected.



--
This message was sent by Atlassian JIRA
(v6.2#6252)