Latest test scenario was this.
It was streaming and recording with ndvr again for 2 days when my previous post was sent and I explain in that one how did I get the smil to work, with only two bitrates. And left the server to continue working without restarting it. Yesterday which is aprox. 4 days without restarting and continuous working, I checked the 3 bitrates smil and it did returned the chunklist and during the whole day it worked as it should. Seems to me some http resource on the streaming server is occupied which should return the 3 bitrate smil and after day or two becomes free again, resulting the 3 bitrate link to work again with nothing changed, it will be good to locate this with your assistance.
Inside the error log when 3 bitrate link is requested this is being logged, nothing else:
I'll send you the conf shortly.
HTTPStreamerAdapterCupertinoStreamer.service: Request timeout: 8000
Server uses 2 core CPU with 3GB memory it is a 32bit machine, which for the current setup had no other issues except the above one.
There was no network interruption logged on server side nor the FMLE side, both server and encoder are on a production high bandwidth network which is constantly monitored. I would exclude this a factor because all else was working, returning a playlist/chunklist for live streams with smils, returning a playlist/chunklist for all dvr streams and returning a playlist/chunklist for live streams with 2 bitrate smil.
Your advice for combined recording is already implemented, we are recording 6 hours of tv programs in mp4 files and the last hour is recorded with ndvr to allow pausing the currently played streams.
Meanwhile I'll reboot and leave it to work and start up another server in parallel with same setup to see what happens.