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

Errors from MarshalJSON *signaling.AsyncMessage: unexpected end of JSON input #642

Closed
tecycloud opened this issue Jan 22, 2024 · 7 comments

Comments

@tecycloud
Copy link

I set up the high performance backend. But I always get errors from MarshalJSON.

[...]
backend_server.go:855: Error processing {"type":"message","message":{"data":{"type":"chat","chat":{"refresh":true}}}} for room a8qnhdzk: json: error calling MarshalJSON for type *signaling.AsyncMessage: unexpected end of JSON input
[...]
[...]
room.go:561: Could not publish session left message in room vvdqzjy9: json: error calling MarshalJSON for type *signaling.AsyncMessage: unexpected end of JSON input
[...]

Does anyone have any idea where this error is coming from?

@malehovich
Copy link

same error ((

@SaadYasir
Copy link

I had the same issue. when you build there are two files in bin proxy and signaling. I simply changed the ownership for both to the user (the one which is configured in systemd for the service), and it worked.

@Simthem
Copy link

Simthem commented Feb 7, 2024

Same issue, changed ownership of proxy and signaling files, upgrade go, resinstall all from scratch on another server : nothing change .. Don't understand what I'm doing wrong .. Even with all my firewall rules bypassed or with allow = all option, I have every time the same error.

And the json given seems to have a correct format (in logs, don't when it's "unmarshalled") ..

PHP : 8.2
Web server : Nginx 1.22.1
BDD : 10.11.4
Janus : 0.14.1
USRSCTP : 0.9.5.0
Nats : 2.2.1
Alpine : 3.19.0 (but tried with 3.18 and same error)

Until the 28.0.2 Nextcloud version all was ok but with oldest signaling, nats, janus and usrsctp version and with another high backend server that have the old version, all is ok (without sip dial-out protocol cause it's unsupported with it).

@fancycode
Copy link
Member

Please check if the solution from #180 (run make clean before building) resolves the issue for you.

@SaadYasir
Copy link

SaadYasir commented Feb 7, 2024

I am using following
PHP: 8.1
Janus: 0.11.8
Go: 1.21.6
NATS: 2.10.9
NGINX: 1.18.0
after the error,
first run make clean
then build again

@Simthem
Copy link

Simthem commented Feb 7, 2024

Oh ok !! So sorry, I did not find this issue :/ sorry for the disturb and thanks a lot ! :)

@fancycode
Copy link
Member

Ok, closing then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants