Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No session info exception causes server to crash #1813

Closed
1 of 3 tasks
dyc3 opened this issue Nov 7, 2024 · 0 comments · Fixed by #1814
Closed
1 of 3 tasks

No session info exception causes server to crash #1813

dyc3 opened this issue Nov 7, 2024 · 0 comments · Fixed by #1814
Labels
bug Something isn't working uncomfirmed Bug has not yet been confirmed, do not start a fix.

Comments

@dyc3
Copy link
Owner

dyc3 commented Nov 7, 2024

Current Behavior

logs:

	2024-11-06 22:33:55.241	
2024-11-07 03:33:55 config info Loading config from /app/env/base.toml
	
	
2024-11-06 22:33:53.515	
(Use `node --trace-warnings ...` to show where the warning was created)
	
	
2024-11-06 22:33:53.515	
(node:356) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time.
	
	
2024-11-06 22:33:51.378	
2024/11/07 03:33:51 INFO SSH listening listen_address=[fdaa:2:8629:a7b:95:62d0:bdec:2]:22 dns_server=[fdaa::3]:53
	
	
2024-11-06 22:33:51.291	
Machine started in 1.049s
	
	
2024-11-06 22:33:51.196	
 INFO [fly api proxy] listening at /.fly/api
	
	
2024-11-06 22:33:51.190	
 INFO Preparing to run: `docker-entrypoint.sh yarn workspace ott-server run start-lean` as root
	
	
2024-11-06 22:33:51.189	
 INFO starting statics vsock server
	
	
2024-11-06 22:33:51.092	
 INFO Starting init (commit: 693c179a)...
	
	
2024-11-06 22:33:50.331	
2024-11-07T03:33:50.331807177 [01JB6Y9C0048RR9D1JCWB6QJ88:main] Running Firecracker v1.7.0
	
	
2024-11-06 22:33:42.678	
[270893.309216] reboot: Restarting system
	
	
2024-11-06 22:33:42.677	
 WARN could not unmount /rootfs: EINVAL: Invalid argument
	
	
2024-11-06 22:33:42.668	
 INFO Starting clean up.
	
	
2024-11-06 22:33:42.653	
 INFO Main child exited normally with code: 1
	
	
2024-11-06 22:33:42.570	
Node.js v18.20.4
	
	
2024-11-06 22:33:42.570	
at async authTokenMiddleware (file:///app/server/ts-out/auth/index.js:64:22)
	
	
2024-11-06 22:33:42.570	
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
	
	
2024-11-06 22:33:42.570	
at Object.getSessionInfo (file:///app/server/ts-out/auth/tokens.js:20:15)
	
	
2024-11-06 22:33:42.570	
Error: No session info found
	
	
2024-11-06 22:33:42.570	
^
	
	
2024-11-06 22:33:42.570	
throw new Error(`No session info found`);
	
	
2024-11-06 22:33:42.570	
file:///app/server/ts-out/auth/tokens.js:20

Expected Behavior

shouldn't crash from auth failure

Steps To Reproduce

unknown

Environment

  • This happens on the official site, opentogethertube.com
  • This happens using a self-hosted version.
  • I'm using the docker image.

Room name or URL

No response

Video URL

No response

Anything else?

No response

@dyc3 dyc3 added bug Something isn't working uncomfirmed Bug has not yet been confirmed, do not start a fix. labels Nov 7, 2024
@dyc3 dyc3 closed this as completed in #1814 Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working uncomfirmed Bug has not yet been confirmed, do not start a fix.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant