FAIL Opening stream xxxxxx failed - aborting initialization

[omega1]

Hello MistServer!

I'm streaming a number of streams (4 at the moment) from OBS to MistServer and I regularly get the above error message on one or more streams (it alternates).

All I get in the log is this:

Wed 24 Oct 2018, 09:29:31 FAIL Opening stream streamname failed - aborting initialization

Wed 24 Oct 2018, 09:29:29 FAIL Opening stream streamname failed - aborting initialization

Wed 24 Oct 2018, 09:29:28 FAIL Opening stream streamname failed - aborting initialization

Wed 24 Oct 2018, 09:29:26 FAIL Opening stream streamname failed - aborting initialization

Wed 24 Oct 2018, 09:29:24 FAIL Opening stream streamname failed - aborting initialization

Wed 24 Oct 2018, 09:29:23 FAIL Opening stream streamname failed - aborting initialization

Wed 24 Oct 2018, 09:29:21 FAIL Opening stream streamname failed - aborting initialization

Wed 24 Oct 2018, 09:29:19 FAIL Opening stream streamname failed - aborting initialization

Wed 24 Oct 2018, 09:29:18 FAIL Opening stream streamname failed - aborting initialization

Wed 24 Oct 2018, 09:29:16 FAIL Opening stream streamname failed - aborting initialization

Even when I disconnect the source, those messages still continue to come into the log file.

The only solution is to run service mistserver restart but then that restarts all the streams and isn't the best solution.

This happens to one of the streams at least every 24 hours.

What further info could I provide to help try and identify the problem?

Thank you in advance.

[Balder Vietor]

Hello,

It sounds like shared memory might be getting deleted. Are you perhaps running MistServer on Ubuntu or Debian and logging into the same user that is running MistServer (by default root)?

We do know that Ubuntu and Debian have a script that deletes shared memory when you log out of a user, which may include MistServers shared memory. Which is used for internal communication.

If this is the case there are several ways to work around this problem:

1. Make MistServer run as another user that you do not log in to (for example "mistserver").

2. Don't log into the same user that is running MistServer

3. Find and disable or modify the scripts that delete shared memory on log out.

With kind regards,

Balder Viëtor
Head of Testing

--
You received this message because you are subscribed to the Google Groups "Mistserver.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mistserver+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[omega1]

Hello Balder,

Thank you so much for your prompt reply!

Yes, you are correct on a number of those assumptions... I am running Debian on a VM and the console is left logged in as the same user (root).

I have created a new username to log in with.

I'll test with this to see what the results are.

Thanks again for your prompt response!

[Balder Vietor]

No problem, hope it helps!

With kind regards,

Balder Viëtor
Head of Testing

--

[omega1]

Hello Balder,

I have changed the user used for logging into the MistServer and there is no user currently logged in, but I've run into similar problems, although slightly different error messages.

One of the streams disconnected again overnight and the errors were as follows:

Thu 25 Oct 2018, 08:50:50 FAIL Could not register on page for /MstUSERstreamname
Thu 25 Oct 2018, 08:50:31 FAIL Could not register on page for /MstUSERstreamname
Thu 25 Oct 2018, 08:50:25 AUTH Failed login attempt mistadminuser from ::ffff:xxx.xxx.xxx.xxx

I stopped the OBS source and restarted it and got these error (along with more of the above ones)

Thu 25 Oct 2018, 08:55:31 FAIL Could not register on page for /MstUSERstreamname
Thu 25 Oct 2018, 08:55:28 FAIL Push rejected - stream streamname not configured or unavailable
Thu 25 Oct 2018, 08:55:26 AUTH Failed login attempt mistadminuser from ::ffff:xxx.xxx.xxx.xxx
Thu 25 Oct 2018, 08:55:25 AUTH Failed login attempt mistadminuser from ::ffff:xxx.xxx.xxx.xxx
Thu 25 Oct 2018, 08:55:24 AUTH Failed login attempt mistadminuser from ::ffff:xxx.xxx.xxx.xxx
Thu 25 Oct 2018, 08:55:21 FAIL Could not register as client for streamname
Thu 25 Oct 2018, 08:55:11 FAIL Could not register on page for /MstUSERstreamname
Thu 25 Oct 2018, 08:54:56 FAIL Push rejected - stream streamname not configured or unavailable
Thu 25 Oct 2018, 08:54:52 FAIL Could not register on page for /MstUSERstreamname
Thu 25 Oct 2018, 08:54:32 FAIL Could not register on page for /MstUSERstreamname

It looks like it could still be related to what you mentioned?

I did not reboot the server, only did a service mistserver restart May I need to restart the whole server?

Two questions...

1) If this happens, is there a way to 'release' that stream without issuing a service mistserver restart (as this interrupts all streams)?
2) Can you think of another solution that may resolve this?

Many thanks again for your assistance, much appreciated.

[Balder Vietor]

Hey Gavin,

Hmm, those errors are still consistent with a shared memory problem. 

From the logs what I'm guessing is that you've made a stream "streamname" which probably dissapears when you reset the MistController now as unless you've forced a configuration save it will only be stored in shared memory (in /dev/shm/MistCONF ). It looks like something still is deleting atleast that file and probably the other MistServer files, if you could do an " ls /dev/shm/*Mist* " you should get a list of all MistServer shared memory files, if MistCONF isn't there it definitely got deleted. If you could share that list with us as well we should be able to see whether it was deleted as well.

As for your questions:

1) Yes, there's a way to restart or release the streams without issuing a service restart. That's by killing the MistController, which will then restart and recover what it can. Running streams won't get interupted, stuck streams should get released and be made available again (provided the configurations it loads contains that stream, so you might want to force a configuration save once you've set everything up through the overview panel). You do this with:

killall -s USR1 MistController

2) The real solution would be checking if there's any other programs/applications running that use shared memory. Server management tools like CPanel tend to reset all shared memory once they update or restart something major, by making MistServer known to them they'll either restart MistServer as well or hopefully leave the MistServer files alone.

Something else you could try would probably making that new user for MistServer only and leave that login completely alone. Most things shouldn't be able to touch it if it's running on a seperate account, only the root account that would wipe the entire shared memory would still be a problem.

Another possible solution would be giving you one of our builds that works with files instead of shared memory. Which works basically the same, but instead of shared memory it'll use an actual location on your harddrive (in /tmp/ ). The only reason why I wouldn't recommend this is that I cannot imagine a program deleting shared memory and leaving the temporarily files folder alone.

With kind regards,

Balder Viëtor
Head of Testing

--

[omega1]

Hello Balder,

Thank you so much for your reply, much appreciated.

I found the command was  ls /dev/shm/*Mst* (rather than  ls /dev/shm/*Mist*)  which gave me the list at the bottom of this post, rather long. I can see that there is a MstConf file there.

When you say "unless you've forced a configuration save" I'm not sure I have understood that, I am creating the streams in the Management Interface, "Create a new stream", and then I save it. Is this not the correct procedure? Maybe I am missing the 'Configuration Save" part and, as you say, the streams are only being held in shared memory. What is the correct process to force a Configuration Save other than creating each stream and clicking the 'save' button? If I restart/reboot, the streams are always there. There isn't an issue of them disappearing, just disconnecting and then getting 'stuck'.

I was able to issue the command killall -s USR1 MistController but it did not 'unlock' the stream streamname, I got these errors:

Thu 25 Oct 2018, 11:38:06 FAIL Could not register on page for /MstUSERstreamname
Thu 25 Oct 2018, 11:37:54 FAIL Push rejected - stream streamname not configured or unavailable
Thu 25 Oct 2018, 11:37:47 FAIL Could not register on page for /MstUSERstreamname
Thu 25 Oct 2018, 11:37:31 FAIL Creating copy of semaphore /MstSTAT failed: No such file or directory
Thu 25 Oct 2018, 11:37:30 CONF Controller started

That command did not interrupt the other streams as you confirmed, so this is good!

I'll make an entirely separate user for MistServer and run it under that user and see how that works.

Thanks again for your replies.

Response of ls /dev/shm/*Mst*:

/dev/shm/MstCnns                     /dev/shm/MstDATAstreamname2@2_1069  /dev/shm/MstDATAstreamname3@2_1213
/dev/shm/MstConf                     /dev/shm/MstDATAstreamname2@2_1081  /dev/shm/MstDATAstreamname3@2_1225
/dev/shm/MstDATAstreamname4@1_559   /dev/shm/MstDATAstreamname2@2_109   /dev/shm/MstDATAstreamname3@2_1237
/dev/shm/MstDATAstreamname4@1_562   /dev/shm/MstDATAstreamname2@2_1093  /dev/shm/MstDATAstreamname3@2_1249
/dev/shm/MstDATAstreamname4@1_565   /dev/shm/MstDATAstreamname2@2_1105  /dev/shm/MstDATAstreamname3@2_1261
/dev/shm/MstDATAstreamname4@1_568   /dev/shm/MstDATAstreamname2@2_1117  /dev/shm/MstDATAstreamname3@2_1273
/dev/shm/MstDATAstreamname4@1_571   /dev/shm/MstDATAstreamname2@2_1129  /dev/shm/MstDATAstreamname3@2_1285
/dev/shm/MstDATAstreamname4@2_1     /dev/shm/MstDATAstreamname2@2_1141  /dev/shm/MstDATAstreamname3@2_1297
/dev/shm/MstDATAstreamname4@2_1009  /dev/shm/MstDATAstreamname2@2_1153  /dev/shm/MstDATAstreamname3@2_13
/dev/shm/MstDATAstreamname4@2_1021  /dev/shm/MstDATAstreamname2@2_1165  /dev/shm/MstDATAstreamname3@2_1309
/dev/shm/MstDATAstreamname4@2_1033  /dev/shm/MstDATAstreamname2@2_1177  /dev/shm/MstDATAstreamname3@2_1321
/dev/shm/MstDATAstreamname4@2_1045  /dev/shm/MstDATAstreamname2@2_1189  /dev/shm/MstDATAstreamname3@2_133
/dev/shm/MstDATAstreamname4@2_1057  /dev/shm/MstDATAstreamname2@2_1201  /dev/shm/MstDATAstreamname3@2_1333
/dev/shm/MstDATAstreamname4@2_1069  /dev/shm/MstDATAstreamname2@2_121   /dev/shm/MstDATAstreamname3@2_1345
/dev/shm/MstDATAstreamname4@2_1081  /dev/shm/MstDATAstreamname2@2_1213  /dev/shm/MstDATAstreamname3@2_1357
/dev/shm/MstDATAstreamname4@2_109   /dev/shm/MstDATAstreamname2@2_1225  /dev/shm/MstDATAstreamname3@2_1369
/dev/shm/MstDATAstreamname4@2_1093  /dev/shm/MstDATAstreamname2@2_1237  /dev/shm/MstDATAstreamname3@2_1381
/dev/shm/MstDATAstreamname4@2_1105  /dev/shm/MstDATAstreamname2@2_1249  /dev/shm/MstDATAstreamname3@2_1393
/dev/shm/MstDATAstreamname4@2_1117  /dev/shm/MstDATAstreamname2@2_1261  /dev/shm/MstDATAstreamname3@2_1405
/dev/shm/MstDATAstreamname4@2_1129  /dev/shm/MstDATAstreamname2@2_1273  /dev/shm/MstDATAstreamname3@2_1417
/dev/shm/MstDATAstreamname4@2_1141  /dev/shm/MstDATAstreamname2@2_1285  /dev/shm/MstDATAstreamname3@2_1429
/dev/shm/MstDATAstreamname4@2_1153  /dev/shm/MstDATAstreamname2@2_1297  /dev/shm/MstDATAstreamname3@2_1441
/dev/shm/MstDATAstreamname4@2_1165  /dev/shm/MstDATAstreamname2@2_13    /dev/shm/MstDATAstreamname3@2_145
/dev/shm/MstDATAstreamname4@2_1177  /dev/shm/MstDATAstreamname2@2_1309  /dev/shm/MstDATAstreamname3@2_1453
/dev/shm/MstDATAstreamname4@2_1189  /dev/shm/MstDATAstreamname2@2_1321  /dev/shm/MstDATAstreamname3@2_1465
/dev/shm/MstDATAstreamname4@2_1201  /dev/shm/MstDATAstreamname2@2_133   /dev/shm/MstDATAstreamname3@2_1477
/dev/shm/MstDATAstreamname4@2_121   /dev/shm/MstDATAstreamname2@2_1333  /dev/shm/MstDATAstreamname3@2_1489
/dev/shm/MstDATAstreamname4@2_1213  /dev/shm/MstDATAstreamname2@2_1345  /dev/shm/MstDATAstreamname3@2_1501
/dev/shm/MstDATAstreamname4@2_1225  /dev/shm/MstDATAstreamname2@2_1357  /dev/shm/MstDATAstreamname3@2_1513
/dev/shm/MstDATAstreamname4@2_1237  /dev/shm/MstDATAstreamname2@2_1369  /dev/shm/MstDATAstreamname3@2_1525
/dev/shm/MstDATAstreamname4@2_1249  /dev/shm/MstDATAstreamname2@2_1381  /dev/shm/MstDATAstreamname3@2_1537
/dev/shm/MstDATAstreamname4@2_1261  /dev/shm/MstDATAstreamname2@2_1393  /dev/shm/MstDATAstreamname3@2_1549
/dev/shm/MstDATAstreamname4@2_1273  /dev/shm/MstDATAstreamname2@2_1405  /dev/shm/MstDATAstreamname3@2_1561
/dev/shm/MstDATAstreamname4@2_1285  /dev/shm/MstDATAstreamname2@2_1417  /dev/shm/MstDATAstreamname3@2_157
/dev/shm/MstDATAstreamname4@2_1297  /dev/shm/MstDATAstreamname2@2_1429  /dev/shm/MstDATAstreamname3@2_1573
/dev/shm/MstDATAstreamname4@2_13    /dev/shm/MstDATAstreamname2@2_1441  /dev/shm/MstDATAstreamname3@2_1585
/dev/shm/MstDATAstreamname4@2_1309  /dev/shm/MstDATAstreamname2@2_145   /dev/shm/MstDATAstreamname3@2_1597
/dev/shm/MstDATAstreamname4@2_1321  /dev/shm/MstDATAstreamname2@2_1453  /dev/shm/MstDATAstreamname3@2_1609
/dev/shm/MstDATAstreamname4@2_133   /dev/shm/MstDATAstreamname2@2_1465  /dev/shm/MstDATAstreamname3@2_1621
/dev/shm/MstDATAstreamname4@2_1333  /dev/shm/MstDATAstreamname2@2_1477  /dev/shm/MstDATAstreamname3@2_1633
/dev/shm/MstDATAstreamname4@2_1345  /dev/shm/MstDATAstreamname2@2_1489  /dev/shm/MstDATAstreamname3@2_1645
/dev/shm/MstDATAstreamname4@2_1357  /dev/shm/MstDATAstreamname2@2_1501  /dev/shm/MstDATAstreamname3@2_1657
/dev/shm/MstDATAstreamname4@2_1369  /dev/shm/MstDATAstreamname2@2_1513  /dev/shm/MstDATAstreamname3@2_1669
/dev/shm/MstDATAstreamname4@2_1381  /dev/shm/MstDATAstreamname2@2_1525  /dev/shm/MstDATAstreamname3@2_1681
/dev/shm/MstDATAstreamname4@2_1393  /dev/shm/MstDATAstreamname2@2_1537  /dev/shm/MstDATAstreamname3@2_169
/dev/shm/MstDATAstreamname4@2_1405  /dev/shm/MstDATAstreamname2@2_1549  /dev/shm/MstDATAstreamname3@2_1693
/dev/shm/MstDATAstreamname4@2_1417  /dev/shm/MstDATAstreamname2@2_1561  /dev/shm/MstDATAstreamname3@2_1705
/dev/shm/MstDATAstreamname4@2_1429  /dev/shm/MstDATAstreamname2@2_157   /dev/shm/MstDATAstreamname3@2_1717
/dev/shm/MstDATAstreamname4@2_1441  /dev/shm/MstDATAstreamname2@2_1573  /dev/shm/MstDATAstreamname3@2_1729
/dev/shm/MstDATAstreamname4@2_145   /dev/shm/MstDATAstreamname2@2_1585  /dev/shm/MstDATAstreamname3@2_1741
/dev/shm/MstDATAstreamname4@2_1453  /dev/shm/MstDATAstreamname2@2_1597  /dev/shm/MstDATAstreamname3@2_1753
/dev/shm/MstDATAstreamname4@2_1465  /dev/shm/MstDATAstreamname2@2_1609  /dev/shm/MstDATAstreamname3@2_1765
/dev/shm/MstDATAstreamname4@2_1477  /dev/shm/MstDATAstreamname2@2_1621  /dev/shm/MstDATAstreamname3@2_1777
/dev/shm/MstDATAstreamname4@2_1489  /dev/shm/MstDATAstreamname2@2_1633  /dev/shm/MstDATAstreamname3@2_1789
/dev/shm/MstDATAstreamname4@2_1501  /dev/shm/MstDATAstreamname2@2_1645  /dev/shm/MstDATAstreamname3@2_1801
/dev/shm/MstDATAstreamname4@2_1513  /dev/shm/MstDATAstreamname2@2_1657  /dev/shm/MstDATAstreamname3@2_181
/dev/shm/MstDATAstreamname4@2_1525  /dev/shm/MstDATAstreamname2@2_1669  /dev/shm/MstDATAstreamname3@2_1813
/dev/shm/MstDATAstreamname4@2_1537  /dev/shm/MstDATAstreamname2@2_1681  /dev/shm/MstDATAstreamname3@2_1825
/dev/shm/MstDATAstreamname4@2_1549  /dev/shm/MstDATAstreamname2@2_169   /dev/shm/MstDATAstreamname3@2_1837
/dev/shm/MstDATAstreamname4@2_1561  /dev/shm/MstDATAstreamname2@2_1693  /dev/shm/MstDATAstreamname3@2_1849
/dev/shm/MstDATAstreamname4@2_157   /dev/shm/MstDATAstreamname2@2_1705  /dev/shm/MstDATAstreamname3@2_1861
/dev/shm/MstDATAstreamname4@2_1573  /dev/shm/MstDATAstreamname2@2_1717  /dev/shm/MstDATAstreamname3@2_1873
/dev/shm/MstDATAstreamname4@2_1585  /dev/shm/MstDATAstreamname2@2_1729  /dev/shm/MstDATAstreamname3@2_1885
/dev/shm/MstDATAstreamname4@2_1597  /dev/shm/MstDATAstreamname2@2_1741  /dev/shm/MstDATAstreamname3@2_1897
/dev/shm/MstDATAstreamname4@2_1609  /dev/shm/MstDATAstreamname2@2_1753  /dev/shm/MstDATAstreamname3@2_1909
/dev/shm/MstDATAstreamname4@2_1621  /dev/shm/MstDATAstreamname2@2_1765  /dev/shm/MstDATAstreamname3@2_1921
/dev/shm/MstDATAstreamname4@2_1633  /dev/shm/MstDATAstreamname2@2_1777  /dev/shm/MstDATAstreamname3@2_193
/dev/shm/MstDATAstreamname4@2_1645  /dev/shm/MstDATAstreamname2@2_1789  /dev/shm/MstDATAstreamname3@2_1933
/dev/shm/MstDATAstreamname4@2_1657  /dev/shm/MstDATAstreamname2@2_1801  /dev/shm/MstDATAstreamname3@2_1945
/dev/shm/MstDATAstreamname4@2_1669  /dev/shm/MstDATAstreamname2@2_181   /dev/shm/MstDATAstreamname3@2_1957
/dev/shm/MstDATAstreamname4@2_1681  /dev/shm/MstDATAstreamname2@2_1813  /dev/shm/MstDATAstreamname3@2_1969
/dev/shm/MstDATAstreamname4@2_169   /dev/shm/MstDATAstreamname2@2_1825  /dev/shm/MstDATAstreamname3@2_1981
/dev/shm/MstDATAstreamname4@2_1693  /dev/shm/MstDATAstreamname2@2_1837  /dev/shm/MstDATAstreamname3@2_1993
/dev/shm/MstDATAstreamname4@2_1705  /dev/shm/MstDATAstreamname2@2_1849  /dev/shm/MstDATAstreamname3@2_2005
/dev/shm/MstDATAstreamname4@2_1717  /dev/shm/MstDATAstreamname2@2_1861  /dev/shm/MstDATAstreamname3@2_2017
/dev/shm/MstDATAstreamname4@2_1729  /dev/shm/MstDATAstreamname2@2_1873  /dev/shm/MstDATAstreamname3@2_2029
/dev/shm/MstDATAstreamname4@2_1741  /dev/shm/MstDATAstreamname2@2_1885  /dev/shm/MstDATAstreamname3@2_2041
/dev/shm/MstDATAstreamname4@2_1753  /dev/shm/MstDATAstreamname2@2_1897  /dev/shm/MstDATAstreamname3@2_205
/dev/shm/MstDATAstreamname4@2_1765  /dev/shm/MstDATAstreamname2@2_1909  /dev/shm/MstDATAstreamname3@2_2053
/dev/shm/MstDATAstreamname4@2_1777  /dev/shm/MstDATAstreamname2@2_1921  /dev/shm/MstDATAstreamname3@2_2065
/dev/shm/MstDATAstreamname4@2_1789  /dev/shm/MstDATAstreamname2@2_193   /dev/shm/MstDATAstreamname3@2_2077
/dev/shm/MstDATAstreamname4@2_1801  /dev/shm/MstDATAstreamname2@2_1933  /dev/shm/MstDATAstreamname3@2_2089
/dev/shm/MstDATAstreamname4@2_181   /dev/shm/MstDATAstreamname2@2_1945  /dev/shm/MstDATAstreamname3@2_2101
/dev/shm/MstDATAstreamname4@2_1813  /dev/shm/MstDATAstreamname2@2_1957  /dev/shm/MstDATAstreamname3@2_2113
/dev/shm/MstDATAstreamname4@2_1825  /dev/shm/MstDATAstreamname2@2_1969  /dev/shm/MstDATAstreamname3@2_2125
/dev/shm/MstDATAstreamname4@2_1837  /dev/shm/MstDATAstreamname2@2_1981  /dev/shm/MstDATAstreamname3@2_2137
/dev/shm/MstDATAstreamname4@2_1849  /dev/shm/MstDATAstreamname2@2_1993  /dev/shm/MstDATAstreamname3@2_2149
/dev/shm/MstDATAstreamname4@2_1861  /dev/shm/MstDATAstreamname2@2_2005  /dev/shm/MstDATAstreamname3@2_2161
/dev/shm/MstDATAstreamname4@2_1873  /dev/shm/MstDATAstreamname2@2_2017  /dev/shm/MstDATAstreamname3@2_217
/dev/shm/MstDATAstreamname4@2_1885  /dev/shm/MstDATAstreamname2@2_2029  /dev/shm/MstDATAstreamname3@2_2173
/dev/shm/MstDATAstreamname4@2_1897  /dev/shm/MstDATAstreamname2@2_2041  /dev/shm/MstDATAstreamname3@2_2185
/dev/shm/MstDATAstreamname4@2_1909  /dev/shm/MstDATAstreamname2@2_205   /dev/shm/MstDATAstreamname3@2_2197
/dev/shm/MstDATAstreamname4@2_1921  /dev/shm/MstDATAstreamname2@2_2053  /dev/shm/MstDATAstreamname3@2_2209
/dev/shm/MstDATAstreamname4@2_193   /dev/shm/MstDATAstreamname2@2_2065  /dev/shm/MstDATAstreamname3@2_2221
/dev/shm/MstDATAstreamname4@2_1933  /dev/shm/MstDATAstreamname2@2_2077  /dev/shm/MstDATAstreamname3@2_2233
/dev/shm/MstDATAstreamname4@2_1945  /dev/shm/MstDATAstreamname2@2_2089  /dev/shm/MstDATAstreamname3@2_2245
/dev/shm/MstDATAstreamname4@2_1957  /dev/shm/MstDATAstreamname2@2_2101  /dev/shm/MstDATAstreamname3@2_2257
/dev/shm/MstDATAstreamname4@2_1969  /dev/shm/MstDATAstreamname2@2_2113  /dev/shm/MstDATAstreamname3@2_2269
/dev/shm/MstDATAstreamname4@2_1981  /dev/shm/MstDATAstreamname2@2_2125  /dev/shm/MstDATAstreamname3@2_2281
/dev/shm/MstDATAstreamname4@2_1993  /dev/shm/MstDATAstreamname2@2_2137  /dev/shm/MstDATAstreamname3@2_229
/dev/shm/MstDATAstreamname4@2_2005  /dev/shm/MstDATAstreamname2@2_2149  /dev/shm/MstDATAstreamname3@2_2293
/dev/shm/MstDATAstreamname4@2_2017  /dev/shm/MstDATAstreamname2@2_2161  /dev/shm/MstDATAstreamname3@2_2305
/dev/shm/MstDATAstreamname4@2_2029  /dev/shm/MstDATAstreamname2@2_217   /dev/shm/MstDATAstreamname3@2_2317
/dev/shm/MstDATAstreamname4@2_2041  /dev/shm/MstDATAstreamname2@2_2173  /dev/shm/MstDATAstreamname3@2_2329
/dev/shm/MstDATAstreamname4@2_205   /dev/shm/MstDATAstreamname2@2_2185  /dev/shm/MstDATAstreamname3@2_2341
/dev/shm/MstDATAstreamname4@2_2053  /dev/shm/MstDATAstreamname2@2_2197  /dev/shm/MstDATAstreamname3@2_2353
/dev/shm/MstDATAstreamname4@2_2065  /dev/shm/MstDATAstreamname2@2_2209  /dev/shm/MstDATAstreamname3@2_2365
/dev/shm/MstDATAstreamname4@2_2077  /dev/shm/MstDATAstreamname2@2_2221  /dev/shm/MstDATAstreamname3@2_2377
/dev/shm/MstDATAstreamname4@2_2089  /dev/shm/MstDATAstreamname2@2_2233  /dev/shm/MstDATAstreamname3@2_2389
/dev/shm/MstDATAstreamname4@2_2101  /dev/shm/MstDATAstreamname2@2_2245  /dev/shm/MstDATAstreamname3@2_2401
/dev/shm/MstDATAstreamname4@2_2113  /dev/shm/MstDATAstreamname2@2_2257  /dev/shm/MstDATAstreamname3@2_241
/dev/shm/MstDATAstreamname4@2_2125  /dev/shm/MstDATAstreamname2@2_2269  /dev/shm/MstDATAstreamname3@2_2413
/dev/shm/MstDATAstreamname4@2_2137  /dev/shm/MstDATAstreamname2@2_2281  /dev/shm/MstDATAstreamname3@2_2425
/dev/shm/MstDATAstreamname4@2_2149  /dev/shm/MstDATAstreamname2@2_229   /dev/shm/MstDATAstreamname3@2_2437
/dev/shm/MstDATAstreamname4@2_2161  /dev/shm/MstDATAstreamname2@2_2293  /dev/shm/MstDATAstreamname3@2_2449
/dev/shm/MstDATAstreamname4@2_217   /dev/shm/MstDATAstreamname2@2_2305  /dev/shm/MstDATAstreamname3@2_2461
/dev/shm/MstDATAstreamname4@2_2173  /dev/shm/MstDATAstreamname2@2_2317  /dev/shm/MstDATAstreamname3@2_2473
/dev/shm/MstDATAstreamname4@2_2185  /dev/shm/MstDATAstreamname2@2_2329  /dev/shm/MstDATAstreamname3@2_2485
/dev/shm/MstDATAstreamname4@2_2197  /dev/shm/MstDATAstreamname2@2_2341  /dev/shm/MstDATAstreamname3@2_2497
/dev/shm/MstDATAstreamname4@2_2209  /dev/shm/MstDATAstreamname2@2_2353  /dev/shm/MstDATAstreamname3@2_25
/dev/shm/MstDATAstreamname4@2_2221  /dev/shm/MstDATAstreamname2@2_2365  /dev/shm/MstDATAstreamname3@2_2509
/dev/shm/MstDATAstreamname4@2_2233  /dev/shm/MstDATAstreamname2@2_2377  /dev/shm/MstDATAstreamname3@2_2521
/dev/shm/MstDATAstreamname4@2_2245  /dev/shm/MstDATAstreamname2@2_2389  /dev/shm/MstDATAstreamname3@2_253
/dev/shm/MstDATAstreamname4@2_2257  /dev/shm/MstDATAstreamname2@2_2401  /dev/shm/MstDATAstreamname3@2_2533
/dev/shm/MstDATAstreamname4@2_2269  /dev/shm/MstDATAstreamname2@2_241   /dev/shm/MstDATAstreamname3@2_2545
/dev/shm/MstDATAstreamname4@2_2281  /dev/shm/MstDATAstreamname2@2_2413  /dev/shm/MstDATAstreamname3@2_2557
/dev/shm/MstDATAstreamname4@2_229   /dev/shm/MstDATAstreamname2@2_2425  /dev/shm/MstDATAstreamname3@2_2569
/dev/shm/MstDATAstreamname4@2_2293  /dev/shm/MstDATAstreamname2@2_2437  /dev/shm/MstDATAstreamname3@2_2581
/dev/shm/MstDATAstreamname4@2_2305  /dev/shm/MstDATAstreamname2@2_2449  /dev/shm/MstDATAstreamname3@2_2593
/dev/shm/MstDATAstreamname4@2_2317  /dev/shm/MstDATAstreamname2@2_2461  /dev/shm/MstDATAstreamname3@2_2605
/dev/shm/MstDATAstreamname4@2_2329  /dev/shm/MstDATAstreamname2@2_2473  /dev/shm/MstDATAstreamname3@2_2617
/dev/shm/MstDATAstreamname4@2_2341  /dev/shm/MstDATAstreamname2@2_2485  /dev/shm/MstDATAstreamname3@2_2629
/dev/shm/MstDATAstreamname4@2_2353  /dev/shm/MstDATAstreamname2@2_2497  /dev/shm/MstDATAstreamname3@2_2641
/dev/shm/MstDATAstreamname4@2_2365  /dev/shm/MstDATAstreamname2@2_25    /dev/shm/MstDATAstreamname3@2_265
/dev/shm/MstDATAstreamname4@2_2377  /dev/shm/MstDATAstreamname2@2_2509  /dev/shm/MstDATAstreamname3@2_2653
/dev/shm/MstDATAstreamname4@2_2389  /dev/shm/MstDATAstreamname2@2_2521  /dev/shm/MstDATAstreamname3@2_2665
/dev/shm/MstDATAstreamname4@2_2401  /dev/shm/MstDATAstreamname2@2_253   /dev/shm/MstDATAstreamname3@2_2677
/dev/shm/MstDATAstreamname4@2_241   /dev/shm/MstDATAstreamname2@2_2533  /dev/shm/MstDATAstreamname3@2_2689
/dev/shm/MstDATAstreamname4@2_2413  /dev/shm/MstDATAstreamname2@2_2545  /dev/shm/MstDATAstreamname3@2_2701
/dev/shm/MstDATAstreamname4@2_2425  /dev/shm/MstDATAstreamname2@2_2557  /dev/shm/MstDATAstreamname3@2_2713
/dev/shm/MstDATAstreamname4@2_2437  /dev/shm/MstDATAstreamname2@2_2569  /dev/shm/MstDATAstreamname3@2_2725
/dev/shm/MstDATAstreamname4@2_2449  /dev/shm/MstDATAstreamname2@2_2581  /dev/shm/MstDATAstreamname3@2_2737
/dev/shm/MstDATAstreamname4@2_2461  /dev/shm/MstDATAstreamname2@2_2593  /dev/shm/MstDATAstreamname3@2_2749
/dev/shm/MstDATAstreamname4@2_2473  /dev/shm/MstDATAstreamname2@2_2605  /dev/shm/MstDATAstreamname3@2_2761
/dev/shm/MstDATAstreamname4@2_2485  /dev/shm/MstDATAstreamname2@2_2617  /dev/shm/MstDATAstreamname3@2_277
/dev/shm/MstDATAstreamname4@2_2497  /dev/shm/MstDATAstreamname2@2_2629  /dev/shm/MstDATAstreamname3@2_2773
/dev/shm/MstDATAstreamname4@2_25    /dev/shm/MstDATAstreamname2@2_2641  /dev/shm/MstDATAstreamname3@2_2785
/dev/shm/MstDATAstreamname4@2_2509  /dev/shm/MstDATAstreamname2@2_265   /dev/shm/MstDATAstreamname3@2_2797
/dev/shm/MstDATAstreamname4@2_2521  /dev/shm/MstDATAstreamname2@2_2653  /dev/shm/MstDATAstreamname3@2_2809
/dev/shm/MstDATAstreamname4@2_253   /dev/shm/MstDATAstreamname2@2_2665  /dev/shm/MstDATAstreamname3@2_2821
/dev/shm/MstDATAstreamname4@2_2533  /dev/shm/MstDATAstreamname2@2_2677  /dev/shm/MstDATAstreamname3@2_2833
/dev/shm/MstDATAstreamname4@2_2545  /dev/shm/MstDATAstreamname2@2_2689  /dev/shm/MstDATAstreamname3@2_289
/dev/shm/MstDATAstreamname4@2_2557  /dev/shm/MstDATAstreamname2@2_2701  /dev/shm/MstDATAstreamname3@2_301
/dev/shm/MstDATAstreamname4@2_2569  /dev/shm/MstDATAstreamname2@2_2713  /dev/shm/MstDATAstreamname3@2_313
/dev/shm/MstDATAstreamname4@2_2581  /dev/shm/MstDATAstreamname2@2_2725  /dev/shm/MstDATAstreamname3@2_325
/dev/shm/MstDATAstreamname4@2_2593  /dev/shm/MstDATAstreamname2@2_2737  /dev/shm/MstDATAstreamname3@2_337
/dev/shm/MstDATAstreamname4@2_2605  /dev/shm/MstDATAstreamname2@2_2749  /dev/shm/MstDATAstreamname3@2_349
/dev/shm/MstDATAstreamname4@2_2617  /dev/shm/MstDATAstreamname2@2_2761  /dev/shm/MstDATAstreamname3@2_361
/dev/shm/MstDATAstreamname4@2_2629  /dev/shm/MstDATAstreamname2@2_277   /dev/shm/MstDATAstreamname3@2_37
/dev/shm/MstDATAstreamname4@2_2641  /dev/shm/MstDATAstreamname2@2_2773  /dev/shm/MstDATAstreamname3@2_373
/dev/shm/MstDATAstreamname4@2_265   /dev/shm/MstDATAstreamname2@2_2785  /dev/shm/MstDATAstreamname3@2_385
/dev/shm/MstDATAstreamname4@2_2653  /dev/shm/MstDATAstreamname2@2_2797  /dev/shm/MstDATAstreamname3@2_397
/dev/shm/MstDATAstreamname4@2_2665  /dev/shm/MstDATAstreamname2@2_2809  /dev/shm/MstDATAstreamname3@2_409
/dev/shm/MstDATAstreamname4@2_2677  /dev/shm/MstDATAstreamname2@2_2821  /dev/shm/MstDATAstreamname3@2_421
/dev/shm/MstDATAstreamname4@2_2689  /dev/shm/MstDATAstreamname2@2_2833  /dev/shm/MstDATAstreamname3@2_433
/dev/shm/MstDATAstreamname4@2_2701  /dev/shm/MstDATAstreamname2@2_289   /dev/shm/MstDATAstreamname3@2_445
/dev/shm/MstDATAstreamname4@2_2713  /dev/shm/MstDATAstreamname2@2_301   /dev/shm/MstDATAstreamname3@2_457
/dev/shm/MstDATAstreamname4@2_2725  /dev/shm/MstDATAstreamname2@2_313   /dev/shm/MstDATAstreamname3@2_469
/dev/shm/MstDATAstreamname4@2_2737  /dev/shm/MstDATAstreamname2@2_325   /dev/shm/MstDATAstreamname3@2_481
/dev/shm/MstDATAstreamname4@2_2749  /dev/shm/MstDATAstreamname2@2_337   /dev/shm/MstDATAstreamname3@2_49
/dev/shm/MstDATAstreamname4@2_2761  /dev/shm/MstDATAstreamname2@2_349   /dev/shm/MstDATAstreamname3@2_493
/dev/shm/MstDATAstreamname4@2_277   /dev/shm/MstDATAstreamname2@2_361   /dev/shm/MstDATAstreamname3@2_505
/dev/shm/MstDATAstreamname4@2_2773  /dev/shm/MstDATAstreamname2@2_37    /dev/shm/MstDATAstreamname3@2_517
/dev/shm/MstDATAstreamname4@2_2785  /dev/shm/MstDATAstreamname2@2_373   /dev/shm/MstDATAstreamname3@2_529
/dev/shm/MstDATAstreamname4@2_2797  /dev/shm/MstDATAstreamname2@2_385   /dev/shm/MstDATAstreamname3@2_541
/dev/shm/MstDATAstreamname4@2_2809  /dev/shm/MstDATAstreamname2@2_397   /dev/shm/MstDATAstreamname3@2_553
/dev/shm/MstDATAstreamname4@2_2821  /dev/shm/MstDATAstreamname2@2_409   /dev/shm/MstDATAstreamname3@2_565
/dev/shm/MstDATAstreamname4@2_2833  /dev/shm/MstDATAstreamname2@2_421   /dev/shm/MstDATAstreamname3@2_577
/dev/shm/MstDATAstreamname4@2_2845  /dev/shm/MstDATAstreamname2@2_433   /dev/shm/MstDATAstreamname3@2_589
/dev/shm/MstDATAstreamname4@2_289   /dev/shm/MstDATAstreamname2@2_445   /dev/shm/MstDATAstreamname3@2_601
/dev/shm/MstDATAstreamname4@2_301   /dev/shm/MstDATAstreamname2@2_457   /dev/shm/MstDATAstreamname3@2_61
/dev/shm/MstDATAstreamname4@2_313   /dev/shm/MstDATAstreamname2@2_469   /dev/shm/MstDATAstreamname3@2_613
/dev/shm/MstDATAstreamname4@2_325   /dev/shm/MstDATAstreamname2@2_481   /dev/shm/MstDATAstreamname3@2_625
/dev/shm/MstDATAstreamname4@2_337   /dev/shm/MstDATAstreamname2@2_49    /dev/shm/MstDATAstreamname3@2_637
/dev/shm/MstDATAstreamname4@2_349   /dev/shm/MstDATAstreamname2@2_493   /dev/shm/MstDATAstreamname3@2_649
/dev/shm/MstDATAstreamname4@2_361   /dev/shm/MstDATAstreamname2@2_505   /dev/shm/MstDATAstreamname3@2_661
/dev/shm/MstDATAstreamname4@2_37    /dev/shm/MstDATAstreamname2@2_517   /dev/shm/MstDATAstreamname3@2_673
/dev/shm/MstDATAstreamname4@2_373   /dev/shm/MstDATAstreamname2@2_529   /dev/shm/MstDATAstreamname3@2_685
/dev/shm/MstDATAstreamname4@2_385   /dev/shm/MstDATAstreamname2@2_541   /dev/shm/MstDATAstreamname3@2_697
/dev/shm/MstDATAstreamname4@2_397   /dev/shm/MstDATAstreamname2@2_553   /dev/shm/MstDATAstreamname3@2_709
/dev/shm/MstDATAstreamname4@2_409   /dev/shm/MstDATAstreamname2@2_565   /dev/shm/MstDATAstreamname3@2_721
/dev/shm/MstDATAstreamname4@2_421   /dev/shm/MstDATAstreamname2@2_577   /dev/shm/MstDATAstreamname3@2_73
/dev/shm/MstDATAstreamname4@2_433   /dev/shm/MstDATAstreamname2@2_589   /dev/shm/MstDATAstreamname3@2_733
/dev/shm/MstDATAstreamname4@2_445   /dev/shm/MstDATAstreamname2@2_601   /dev/shm/MstDATAstreamname3@2_745
/dev/shm/MstDATAstreamname4@2_457   /dev/shm/MstDATAstreamname2@2_61    /dev/shm/MstDATAstreamname3@2_757
/dev/shm/MstDATAstreamname4@2_469   /dev/shm/MstDATAstreamname2@2_613   /dev/shm/MstDATAstreamname3@2_769
/dev/shm/MstDATAstreamname4@2_481   /dev/shm/MstDATAstreamname2@2_625   /dev/shm/MstDATAstreamname3@2_781
/dev/shm/MstDATAstreamname4@2_49    /dev/shm/MstDATAstreamname2@2_637   /dev/shm/MstDATAstreamname3@2_793
/dev/shm/MstDATAstreamname4@2_493   /dev/shm/MstDATAstreamname2@2_649   /dev/shm/MstDATAstreamname3@2_805
/dev/shm/MstDATAstreamname4@2_505   /dev/shm/MstDATAstreamname2@2_661   /dev/shm/MstDATAstreamname3@2_817
/dev/shm/MstDATAstreamname4@2_517   /dev/shm/MstDATAstreamname2@2_673   /dev/shm/MstDATAstreamname3@2_829
/dev/shm/MstDATAstreamname4@2_529   /dev/shm/MstDATAstreamname2@2_685   /dev/shm/MstDATAstreamname3@2_841
/dev/shm/MstDATAstreamname4@2_541   /dev/shm/MstDATAstreamname2@2_697   /dev/shm/MstDATAstreamname3@2_85
/dev/shm/MstDATAstreamname4@2_553   /dev/shm/MstDATAstreamname2@2_709   /dev/shm/MstDATAstreamname3@2_853
/dev/shm/MstDATAstreamname4@2_565   /dev/shm/MstDATAstreamname2@2_721   /dev/shm/MstDATAstreamname3@2_865
/dev/shm/MstDATAstreamname4@2_577   /dev/shm/MstDATAstreamname2@2_73    /dev/shm/MstDATAstreamname3@2_877
/dev/shm/MstDATAstreamname4@2_589   /dev/shm/MstDATAstreamname2@2_733   /dev/shm/MstDATAstreamname3@2_889
/dev/shm/MstDATAstreamname4@2_601   /dev/shm/MstDATAstreamname2@2_745   /dev/shm/MstDATAstreamname3@2_901
/dev/shm/MstDATAstreamname4@2_61    /dev/shm/MstDATAstreamname2@2_757   /dev/shm/MstDATAstreamname3@2_913
/dev/shm/MstDATAstreamname4@2_613   /dev/shm/MstDATAstreamname2@2_769   /dev/shm/MstDATAstreamname3@2_925
/dev/shm/MstDATAstreamname4@2_625   /dev/shm/MstDATAstreamname2@2_781   /dev/shm/MstDATAstreamname3@2_937
/dev/shm/MstDATAstreamname4@2_637   /dev/shm/MstDATAstreamname2@2_793   /dev/shm/MstDATAstreamname3@2_949
/dev/shm/MstDATAstreamname4@2_649   /dev/shm/MstDATAstreamname2@2_805   /dev/shm/MstDATAstreamname3@2_961
/dev/shm/MstDATAstreamname4@2_661   /dev/shm/MstDATAstreamname2@2_817   /dev/shm/MstDATAstreamname3@2_97
/dev/shm/MstDATAstreamname4@2_673   /dev/shm/MstDATAstreamname2@2_829   /dev/shm/MstDATAstreamname3@2_973
/dev/shm/MstDATAstreamname4@2_685   /dev/shm/MstDATAstreamname2@2_841   /dev/shm/MstDATAstreamname3@2_985
/dev/shm/MstDATAstreamname4@2_697   /dev/shm/MstDATAstreamname2@2_85    /dev/shm/MstDATAstreamname3@2_997
/dev/shm/MstDATAstreamname4@2_709   /dev/shm/MstDATAstreamname2@2_853   /dev/shm/MstSTATA
/dev/shm/MstDATAstreamname4@2_721   /dev/shm/MstDATAstreamname2@2_865   /dev/shm/MstSTATB
/dev/shm/MstDATAstreamname4@2_73    /dev/shm/MstDATAstreamname2@2_877   /dev/shm/MstStateAccs
/dev/shm/MstDATAstreamname4@2_733   /dev/shm/MstDATAstreamname2@2_889   /dev/shm/MstSTATEstreamname4
/dev/shm/MstDATAstreamname4@2_745   /dev/shm/MstDATAstreamname2@2_901   /dev/shm/MstSTATEstreamname
/dev/shm/MstDATAstreamname4@2_757   /dev/shm/MstDATAstreamname2@2_913   /dev/shm/MstSTATEstreamname2
/dev/shm/MstDATAstreamname4@2_769   /dev/shm/MstDATAstreamname2@2_925   /dev/shm/MstSTATEstreamname3
/dev/shm/MstDATAstreamname4@2_781   /dev/shm/MstDATAstreamname2@2_937   /dev/shm/MstStateLogs
/dev/shm/MstDATAstreamname4@2_793   /dev/shm/MstDATAstreamname2@2_949   /dev/shm/MstStateStreams
/dev/shm/MstDATAstreamname4@2_805   /dev/shm/MstDATAstreamname2@2_961   /dev/shm/MstSTRMstreamname4
/dev/shm/MstDATAstreamname4@2_817   /dev/shm/MstDATAstreamname2@2_97    /dev/shm/MstSTRMstreamname2
/dev/shm/MstDATAstreamname4@2_829   /dev/shm/MstDATAstreamname2@2_973   /dev/shm/MstSTRMstreamname3
/dev/shm/MstDATAstreamname4@2_841   /dev/shm/MstDATAstreamname2@2_985   /dev/shm/MstTRIDstreamname4@1
/dev/shm/MstDATAstreamname4@2_85    /dev/shm/MstDATAstreamname2@2_997   /dev/shm/MstTRIDstreamname4@2
/dev/shm/MstDATAstreamname4@2_853   /dev/shm/MstDATAstreamname3@1_559   /dev/shm/MstTRIDstreamname2@1
/dev/shm/MstDATAstreamname4@2_865   /dev/shm/MstDATAstreamname3@1_562   /dev/shm/MstTRIDstreamname2@2
/dev/shm/MstDATAstreamname4@2_877   /dev/shm/MstDATAstreamname3@1_565   /dev/shm/MstTRIDstreamname3@1
/dev/shm/MstDATAstreamname4@2_889   /dev/shm/MstDATAstreamname3@1_568   /dev/shm/MstTRIDstreamname3@2
/dev/shm/MstDATAstreamname4@2_901   /dev/shm/MstDATAstreamname3@1_571   /dev/shm/MstUSERstreamname4A
/dev/shm/MstDATAstreamname4@2_913   /dev/shm/MstDATAstreamname3@2_1     /dev/shm/MstUSERstreamname4B
/dev/shm/MstDATAstreamname4@2_925   /dev/shm/MstDATAstreamname3@2_1009  /dev/shm/MstUSERstreamnameA
/dev/shm/MstDATAstreamname4@2_937   /dev/shm/MstDATAstreamname3@2_1021  /dev/shm/MstUSERstreamname2A
/dev/shm/MstDATAstreamname4@2_949   /dev/shm/MstDATAstreamname3@2_1033  /dev/shm/MstUSERstreamname2B
/dev/shm/MstDATAstreamname4@2_961   /dev/shm/MstDATAstreamname3@2_1045  /dev/shm/MstUSERstreamname3A
/dev/shm/MstDATAstreamname4@2_97    /dev/shm/MstDATAstreamname3@2_1057  /dev/shm/MstUSERstreamname3B
/dev/shm/MstDATAstreamname4@2_973   /dev/shm/MstDATAstreamname3@2_1069  /dev/shm/sem.MstConfLock
/dev/shm/MstDATAstreamname4@2_985   /dev/shm/MstDATAstreamname3@2_1081  /dev/shm/sem.MstInptstreamname4
/dev/shm/MstDATAstreamname4@2_997   /dev/shm/MstDATAstreamname3@2_109   /dev/shm/sem.MstInptstreamname
/dev/shm/MstDATAstreamname2@1_559    /dev/shm/MstDATAstreamname3@2_1093  /dev/shm/sem.MstInptstreamname2
/dev/shm/MstDATAstreamname2@1_562    /dev/shm/MstDATAstreamname3@2_1105  /dev/shm/sem.MstInptstreamname3
/dev/shm/MstDATAstreamname2@1_565    /dev/shm/MstDATAstreamname3@2_1117  /dev/shm/sem.MstLIVEstreamname4
/dev/shm/MstDATAstreamname2@1_568    /dev/shm/MstDATAstreamname3@2_1129  /dev/shm/sem.MstLIVEstreamname
/dev/shm/MstDATAstreamname2@1_571    /dev/shm/MstDATAstreamname3@2_1141  /dev/shm/sem.MstLIVEstreamname2
/dev/shm/MstDATAstreamname2@2_1      /dev/shm/MstDATAstreamname3@2_1153  /dev/shm/sem.MstLIVEstreamname3
/dev/shm/MstDATAstreamname2@2_1009   /dev/shm/MstDATAstreamname3@2_1165  /dev/shm/sem.MstSTAT
/dev/shm/MstDATAstreamname2@2_1021   /dev/shm/MstDATAstreamname3@2_1177  /dev/shm/sem.MstUSERstreamname4
/dev/shm/MstDATAstreamname2@2_1033   /dev/shm/MstDATAstreamname3@2_1189  /dev/shm/sem.MstUSERstreamname
/dev/shm/MstDATAstreamname2@2_1045   /dev/shm/MstDATAstreamname3@2_1201  /dev/shm/sem.MstUSERstreamname2
/dev/shm/MstDATAstreamname2@2_1057   /dev/shm/MstDATAstreamname3@2_121   /dev/shm/sem.MstUSERstreamname3

[Balder Vietor]

Hey There,

You're correct about the ls command, sorry about that I had a typo in there.

I'll explain the force configuration a bit more:

When you create streams/protocols in MistServer it stores these new settings in shared memory and writes it to the mistserver.conf file the moment MistServer succesfully shuts down. The reason why we've made it work this way is that if you set something up that causes an instant crash/problem it will not cause this the moment MistServer restarts so you can actually prevent that same setting from happening again. There is however a way to store the configurations without shutting down MistServer and that's ticking the "force configuration json" box and pressing save button in the overview panel of MistServer.

The following error:

Thu 25 Oct 2018, 11:37:54 FAIL Push rejected - stream streamname not configured or unavailable  

Should mean that the stream "streamname" has dissapeared from your settings, so it was most likely not saved. You might have to ctrl+shift+r the configurations window if you've got it active for a longer period of time, but the stream shouldn't show up in your stream configurations.

The logs

You've got a huge list in your shared memory, did you raise the buffer of your live streams by a lot? Depending on the size of those files your problem might simply be that you've ran out of shared memory and that parts have started to overwrite itself. If you have the RAM to handle this it'll be fine, but you might want to double check if your RAM is near full.

With kind regards,

Balder Viëtor
Head of Testing

On Thu, Oct 25, 2018 at 1:00 PM omega1 <ga...@easywebcommunications.com> wrote:

Try again with the list:

--

[omega1]

Hello Balder,

Thank you for your ongoing support.

I've just had a stream disconnect again and it will not reconnect as it appears to be in this 'stuck' status. I have tried hard refreshing the streams page and logging out and back in again as you suggested and the stream is still present in the 'streams' page, it appears as in 'standby' status but the encoder cannot connect to it.

The logs are continuously saying this:

Fri 26 Oct 2018, 19:41:56 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:41:46 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:41:23 FAIL Could not connect to data for streamname

I've used the 'Force save configuration' in the overview page, this does not seem to have made a difference.

Regarding the items you mention about the logs, I did not alter any buffer settings at all, it is a fresh Debian (x64) install with just MistServer installed. In terms of RAM, no issues, it has 4G with reported 400M used, so I do not think this is the problem.

The command killall -s USR1 MistController doesn't seem to work as expected, when I issue that command, I get the following:

Fri 26 Oct 2018, 19:46:10 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:45:54 FAIL Push rejected - stream streamname not configured or unavailable

Fri 26 Oct 2018, 19:45:47 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:45:37 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:45:27 AUTH Failed login attempt mistadmin from ::ffff:xxx.xxx.xxx.xxx

Fri 26 Oct 2018, 19:45:26 AUTH Failed login attempt mistadmin from ::ffff:xxx.xxx.xxx.xxx

Fri 26 Oct 2018, 19:45:25 AUTH Failed login attempt mistadmin from ::ffff:xxx.xxx.xxx.xxx

Fri 26 Oct 2018, 19:45:18 CONF Controller started

Which seems to indicate that the stream is still 'stuck' and the only possibility is now to issue a service mistserver restart which will disconnect all the streams.

Even if I delete the stream entirely, I continue to get the same message:

Fri 26 Oct 2018, 19:51:54 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:51:31 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:51:08 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:50:59 WARN Configuration semaphore was stuck. Force-unlocking it and re-writing config.

Fri 26 Oct 2018, 19:50:58 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:50:35 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:50:27 AUTH Failed login attempt mistadmin from ::ffff:xxx.xxx.xxx.xxx

Fri 26 Oct 2018, 19:50:26 AUTH Failed login attempt mistadmin from ::ffff:xxx.xxx.xxx.xxx

Fri 26 Oct 2018, 19:50:25 AUTH Failed login attempt mistadmin from ::ffff:xxx.xxx.xxx.xxx

Fri 26 Oct 2018, 19:50:25 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:50:06 STRM Deleted stream streamname

Fri 26 Oct 2018, 19:50:06 STRM Deleted stream streamname

If I re-add the stream, I get this:

Fri 26 Oct 2018, 19:53:39 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:53:35 FAIL Push rejected - stream streamname not configured or unavailable

Fri 26 Oct 2018, 19:53:16 FAIL Could not connect to data for streamname

Fri 26 Oct 2018, 19:53:15 STRM New stream streamname

So it looks like whatever I do other than the service mistserver restart  the stream is somehow 'stuck' with no way of releasing it.

The only thing I haven't been able to do yet is run MistServer under it's own username.

[omega1]

Hello Balder,

In your first response, you mentioned an option 3 ( Find and disable or modify the scripts that delete shared memory on log out.) would this be the correct way to do this...

Edit /etc/systemd/logind.conf, uncomment the line RemoveIPC=yes, change it to RemoveIPC=no, save, and reboot the system

I have gone ahead with the above steps and rebooted, if you had time to answer the above items, that would be great!

Thanks again.

[Balder Vietor]

Hello again Gavin,

Sorry for taking a while to answer.

From what you send in the edit that does indeed look like the correct way, IPC would include shared memory so that should be it. 

It looks like you might've been hit by another issue we've recently found (at least if the RemoveIPC didn't help). We'll release another bugfix release soon that should solve some issues we've found in shared memory. 

With kind regards,

Balder Viëtor
Head of Testing

--

[omega1]

Hi Balder,

Thanks again for your response.

Yes, it still continues to drop streams which then get into this 'stuck' status even after applying that change (Edit /etc/systemd/logind.conf, uncomment the line RemoveIPC=yes, change it to RemoveIPC=no, save, and reboot the system)

Where would I find out when the release has been pushed out? Via your website?

Thank you.

[Balder Vietor]

Hey there,

Okay good to know, it'll most likely stop after the next patch then.

You'd be able to see the MistServer update at our website main page, the changelog or at the MistServer overview (it should tell you an update is available). Though I'll probably let you know here as well ;)

With kind regards,

Balder Viëtor
Head of Testing

--