On 6/11/20 3:07 PM, Christian Schoenebeck wrote:
Sounds like an old kernel issue to me:
Years ago, when LS was killed or crashed, then it used to happen that the
Linux kernel still listed its port (8888) as still being in use for a while,
even though the LS process (which actually used the port) was gone. However
since the kernel thought the port was still in use, it prevented the restarted
LS to bind to that port immediately. In that case you had to wait for around 1
or 2 minutes until the kernel finally freed that port and then LS eventually
was able to bind to the port in its wait loop that you pasted above.
However I have not seen this issue in years, so I thought it was fixed on
kernel side long ago. What's the kernel version that you are using, and is
there something special regarding your installation?
uname -a
Linux debian-T4 5.6.0-2-rt-amd64 #1 SMP PREEMPT_RT Debian 5.6.14-1
(2020-05-23) x86_64 GNU/Linux
But LS is still able to bind to the port automatically after some waiting time
there, right?
Last time (this morning) I had to reboot. But I'm not having this issue
always. But next time I will clock if I had enough patience ;)
CU
Christian
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
