MistServer v3 for Windows Feedback

[Jimmy Knudsen]

Hi,

I got the dev version (3.3-25-g3422b1dbc Free_cyg64) you linked to me, and I set it up, exactly as the old v2.8 server.

It produces ONE error at startup:

[2024-06-27 14:45:32] MistController (1736) FAIL: Could not store connector data!

I guess this is why I can't stream to the server.

Using OBS I get the error message that either the channel or stream key is incorrect, or there is a connection problem.

If I try WITHOUT my stream key, then the server refuses the connection immediately.
I have tried both as rtmp and srt streams. same errors. I MORE than triple-checked the key on both the server and in OBS,

WITHOUT a key, the server logs this:

[2024-06-27 14:57:31] MistOutRTMP (1788) WARN: Could not get stream '' config!
[2024-06-27 14:57:31] MistOutRTMP (1788) WARN: Could not get stream '' config!
[2024-06-27 14:57:31] MistOutRTMP (1788) FAIL: onFail '': Stream open failed
[2024-06-27 14:57:31] MistOutRTMP (1788) FAIL: onFail '': Could not connect to stream data
[2024-06-27 14:57:31] MistOutRTMP (1788) FAIL: Push rejected - stream  not configured or unavailable

WITH a key, it logs nothing.

[Jimmy Knudsen]

I forgot to mention this...
The old MistServer was running as a service at startup. It worked perfect.

It seems like the new version can't do that? It starts and runs, but can't connect to the web interface on it.

[Jimmy Knudsen]

 Apparently it was a bad(ish) idea just to copy/paste the old config file. I did check the content, but I guess I missed something.

It all looked fine in the web interface, but couldn't connect to the server from OBS.

I had to delete the old (exisiting) streams and re-add them. Now it works.

[Jimmy Knudsen]

I have run into another problem now.

I had my stream up and running and it worked fine.

Then I stopped the stream in OBS, to do a minor tweak. 

When I restarted the stream in OBS the MistServer just shows "Waiting for data..."

I then stopped OBS stream, and restarted MistServer. It STILL shows the above.

Even though the console shows this:

[2024-06-27 15:42:55] MistController (787) ACCS: Session <I5984251c68f332921237660081b7ff5da409813cc97cc8bd3343400e2b1d3d8c> snowman (INPUT:RTMP) from 192.168.1.6 ended after 174s, avg 0KB/s up 276KB/s down. Tags: [UA:FMLE/3.0 (compatible; FMSc/1.0)]

So the server actually registered that the stream has stopped, but is stuck at "Waiting for data..." and the server also thinks it should send it on, as my streaming homepage is stuck at "Stream is waiting for data"

I guess something is stuck on the MistServer, since even restarting it doesn't fix it.

[Jimmy Knudsen]

The fix (for now) was to stop the server, go into \dev\shm, and delete all files with my username (except from the one starting with "MstSCnf")

[Balder Vietor]

Hey Jimmy,

Thanks for the feedback so far. I'll check out the stuck state. as well. It is most likely the same issue where some processes don't properly close, if the connection is still registered as active even though it isn't MistServer will blindly believe that config and claim it's waiting for data without being able to break free from that state. The only things that could solve this would be a nuke api call or deleting the dev/shm manually. 

I do have to admit I forgot to consider going from a 2.18 config to 3.4

The error you had at the beginning: 

[2024-06-27 14:45:32] MistController (1736) FAIL: Could not store connector data!

Would imply it's incapable of writing its configurations to the folder for other processes to read out, so it's no wonder the entire config didn't work at that point. Weird that it happened though, I wouldn't expect an older config to be able to cause something like this, but I'll try and verify this.

With kind regards,

Balder Viëtor
Head of Testing

MistServer

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/mistserver/6e040c14-f12e-4b40-878c-ad21f7c28021n%40googlegroups.com.

[Jimmy Knudsen]

Hi Balder.

If you have a newer version ready you would like to test (currently using 3.3-25-g3422b1dbc Free_cyg64) then let me know.

Especially if you have been able to look into the errors I mentioned earlier in this thread.
Both the problem with left over files, and  the "Could not store connector data!" error.

I still use the same config as I did from the beginning. MistController reports the above error every time I start it, but it seems to run fine afterwards.

Regards

Jimmy Knudsen

[Balder Vietor]

We are squashing some Windows related interface bugs right now. So hopefully I'll have something for you soon.

I could give you the 3.4 full upgrade, but if I recall correctly it actually wouldn't have much changes compared to your current version.

The IBC is getting close though, so chances are this is more of a next week than this week thing.

With kind regards,

Balder Viëtor
Head of Testing

MistServer

To view this discussion on the web visit https://groups.google.com/d/msgid/mistserver/42d510c6-ce33-46b1-96a4-7578ac5133e7n%40googlegroups.com.

[Jimmy Knudsen]

It's fine, just let me know if you need some testing on a small private streaming server done...
We are almost daily 3+ people streaming to each other through a passsword protected homepage using my MistServer, so it's just a few people, but it's better than none ;) 

[M. Weiss (Basspig)]

My intent for using Mistserver is so that I can stream h.265 and drop my bitrate way down so I can stream in other countries that currently only have 1-3mb/s connection with the US.

[Jimmy Knudsen]

Hi Balder

I just updated to v3.4.
I assume the "MistController (766) WARN: Wiped 20 shared memory file(s)" is a solution to remove the leftovers from last launch in the shm folder.

At least it seems to work like it.

As I still use the converted config from the old v2.8, then I still get the "MistController (766) FAIL: Could not store connector data!" error.

If you want a copy of my config to test with, then send me a private message I can reply to (and attach it to).

Other than that error, it seems to run fine.

I haven't tested again, but does v3.4 support being launched as a service like 2.x? v3.3 didn't.

Regards

Jimmy Knudsen

[Balder Vietor]

Hey Jimmy,

We have indeed added a few things. 

Shared memory files being wiped

The wiping of shared memory is in the case that MistServer had leftovers from last time. This is almost always remains of a live stream that was active when it was closing. The order in which files get deleted sadly means that sometimes we leave a bit of streaming buffer behind under Windows, we do want to improve on that, but it's luckily quite minor.

Could not store connector data

This means it wasn't able to store which ports are currently listening/open for MistServer. For in use that isn't a problem, but it does become a problem when it needs to perform a rolling update or crash recovery. It is something we still need to fix, but only affects recovery, not performance.

This one is a higher priority for us, but doesn't impact MistServer itself unless you manage to crash it or want to update it while it's live.

As a service

This one is high up on the list as well, but also the 2.18 method was "broken" quite a while back. We used some (by now) very old QT libraries/versions that are no longer available to us due to QT changing their licensing...

That said, while not fully a service there is an auto-boot method.

If you grab the `MistServer shell` shortcut and copy it over to your `boot` folder Windows will auto-boot MistServer.

The shell should be in `C:\ProgramData\Microsoft\Windows\Start Menu\Programs` .

You can also find it if you write `MistServer` and then right click on the `MistServer Shell` and open the target location. 

Afterwards open your boot folder:

Windows + R

This shortcut would open a place where you can put down a prompt and run it. Fill in:

Shell:common startup

That opens your boot directory, simply copy over the MistServer shell there and it will now auto-boot.

With kind regards,

Balder Viëtor
Head of Testing

MistServer

To view this discussion on the web visit https://groups.google.com/d/msgid/mistserver/ce942491-f744-4707-abce-2dcdfac3c336n%40googlegroups.com.