Mixer module is completely broken

[bugz8unny69]

Hey dev,

Right now, the Mixer module is broken and throws a traceback when trying to push. Going to have to sit down and look into this and determine what's causing this. For now, I've just reverted to Custom RTMP.

Cheers.

[bugz8unny69]

I have to completely disable Mixer, the page fails to render:

/opt/multistreamer/lib/multistreamer/networks/mixer.lua:78: attempt to index local 'res' (a boolean value)

stack traceback:
	/opt/multistreamer/lib/multistreamer/networks/mixer.lua:78: in function 'post'
	/opt/multistreamer/lib/multistreamer/networks/mixer.lua:142: in function 'refresh_access_token'
	/opt/multistreamer/lib/multistreamer/networks/mixer.lua:424: in function 'check_errors'
	/opt/multistreamer/lib/multistreamer/webapp.lua:901: in function 'handler'
	...streamer/lua_modules/share/lua/5.1/lapis/application.lua:130: in function 'resolve'
	...streamer/lua_modules/share/lua/5.1/lapis/application.lua:167: in function <...streamer/lua_modules/share/lua/5.1/lapis/application.lua:165>
	[C]: in function 'xpcall'
	...streamer/lua_modules/share/lua/5.1/lapis/application.lua:173: in function 'dispatch'
	.../multistreamer/lua_modules/share/lua/5.1/lapis/nginx.lua:230: in function 'serve'
	content_by_lua(nginx.conf:69):2: in function <content_by_lua(nginx.conf:69):1>

[k1ck3r]

you have to delete the database entries related to the mixer config. after that you'll be fine. i'm using postgresql and the following selects/deletes handle the issue:

select * from accounts;

23 | 1 | mixer | ed4e581bdafb66567b905ffcd72356a3e40686f3 | user | 2019-02-21 11:26:48 | 2019-02-21 11:26:48 | user |

delete from accounts where id = 23;

after this, may/or may not complain about relations, if so, do the following:

delete from keystore where account_id = 23;

then run delete again from accounts. hope it works for u

[bugz8unny69]

Thanks for the tips! I'll check this out later on.

[a-r-db]

Same bug here.
I had to write a script to resolve this bug each time it appears.

Error
/home/multistreamer/lib/multistreamer/networks/mixer.lua:78: attempt to index local 'res' (a boolean value)
Traceback
stack traceback:
	/home/multistreamer/lib/multistreamer/networks/mixer.lua:78: in function 'post'
	/home/multistreamer/lib/multistreamer/networks/mixer.lua:142: in function 'refresh_access_token'
	/home/multistreamer/lib/multistreamer/networks/mixer.lua:424: in function 'check_errors'
	/home/multistreamer/lib/multistreamer/webapp.lua:901: in function 'handler'
	...streamer/lua_modules/share/lua/5.1/lapis/application.lua:130: in function 'resolve'
	...streamer/lua_modules/share/lua/5.1/lapis/application.lua:167: in function <...streamer/lua_modules/share/lua/5.1/lapis/application.lua:165>
	[C]: in function 'xpcall'
	...streamer/lua_modules/share/lua/5.1/lapis/application.lua:173: in function 'dispatch'
	.../multistreamer/lua_modules/share/lua/5.1/lapis/nginx.lua:230: in function 'serve'
	content_by_lua(nginx.conf:69):2: in function <content_by_lua(nginx.conf:69):1>

[k1ck3r]

check my comments, i'm almost 100% that you are having same problem as i experienced some time ago

[a-r-db]

@k1ck3r
I know but I don't think the end user should need to look under the hood this much when the multi-stream machine stops running.

ssh -t server ~/stream.sh

stream.sh

op="psql postgresql://username:password@localhost:5432/database << EOF
DELETE FROM streams_accounts WHERE account_id IN (SELECT id FROM accounts WHERE network = 'mixer');
DELETE FROM keystore WHERE account_id IN (SELECT id FROM accounts WHERE network = 'mixer');
DELETE FROM accounts WHERE id IN (SELECT id FROM accounts WHERE network = 'mixer' );
\q
EOF"
echo $op
docker exec -it dockermultistreamer_postgresql_1 /bin/bash -c "$op"

[jprjr]

Started to investigate this, noticed that line 78 of the mixer module didn't match up with what's in the repo.

OP is using a manual install of multistreamer, but I got clued in everybody else is using the Docker image.

My Makefile rule for updating the docker-compose file was/is broken, I updated the version in there. Try pulling down the latest docker-compose.

I think you may still get the error but at least we'll all be looking at the same code.