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

Exception in Controller::worker() #61

Closed
deisi opened this issue May 18, 2016 · 11 comments
Closed

Exception in Controller::worker() #61

deisi opened this issue May 18, 2016 · 11 comments

Comments

@deisi
Copy link

deisi commented May 18, 2016

Since last update ( I think I jumped from v 0.4.1 but im not 100% sure) to 0.7.0 my raspberry client cant connect any more. On the client I see:

May 18 07:11:25 rapi2 snapclient[2889]: Connected to 172.16.1.117 
May 18 07:11:26 rapi2 snapclient[2889]: Exception in Controller::worker(): sum timeout exceeded 10s

In the systemd logs and on the server I get:

May 18 08:58:53 serv snapserver[1272]: StreamServer::NewConnection: 172.16.1.83
May 18 08:58:54 serv snapserver[1272]: 2016-05-18 08-58-54 [Err] Exception in StreamSession::reader(): read_some: End of file
May 18 08:58:54 serv snapserver[1272]: 2016-05-18 08-58-54 [out] onDisconnect:
May 18 08:58:54 serv snapserver[1272]: Exception in StreamSession::reader(): read_some: End of file

I also run a client instance on the same machine as the server. This client does work without error message.

For wat its worth, I use Arch Linux on both machines (client raspberry pi, server x86) and the packages are compiled from source.

@badaix
Copy link
Owner

badaix commented May 18, 2016

Are you sure that client and server are both on 0.7?
Did you make clean after pulling the latest version?

@deisi
Copy link
Author

deisi commented May 19, 2016

You are completely right, the updated didnt work. Thanks a lot.

@deisi deisi closed this as completed May 19, 2016
@ivanbalashov239
Copy link

@deisi @badaix have the same issue, fresh installation raspberry Arch linux and x64 Manjaro(Arch distribution) both have 0.10.0-2 version builded from aur
on client

Jan 16 01:35:26 jarvis snapclient[20550]: Connected to 192.168.1.187
Jan 16 01:35:28 jarvis snapclient[20550]: Exception in Controller::worker(): sum timeout exceeded 10s

and
on server x64

Jan 15 22:27:25 alarmpi snapserver[4728]: Exception in StreamSession::reader(): read_some: End of file
Jan 15 22:27:26 alarmpi snapserver[4728]: StreamServer::NewConnection: 192.168.1.2

clients on android(two smartphones works ok) server runned on x64 works with clients on androids and client on x64 machine gives the same issue.

Any ideas what i've faced?

@deisi
Copy link
Author

deisi commented Feb 2, 2017

uff, I currently have a broken rpi and cant test. In any case, I will change back to debian, because I hat too much trouble with Arch on ARM.

So no, Idear sry.

@stephanedaviet
Copy link

I get exactly the same problem with 2 freshly install Snapcast 0.11.1 installed from Arch AUR:

  • exact same version on streaming server and client,
  • client on server itself (loopback) works,
  • client on my laptop don't with the error messages indicated by @seniorivn.

@deisi
Copy link
Author

deisi commented Apr 2, 2017

hey how you start the client? From systemd?
Try starting it maual with:
snapclient and see if it works

If it works, you might have the same problem as I just described in #229

If this is the problem It would be interesting to hear if you are using pulseaudio as well.

@stephanedaviet
Copy link

Ok, further testing with two clients both running Arch (same dist on the server too):

  • Raspberry Pi without PulseAudio: works flawlessly launched in command line with or without daemon mode, and launched through systemd,
  • Laptop with PulseAudio: works when launched in command line with or without daemon, not when launched through systemd (errors indicated above).

So, it seems it is linked in some way to #229.

@christf
Copy link

christf commented Jun 23, 2017

I am having this issue with 0.11.1 without pulseaudio.
in my raspbian installation this was due to the home directory of the snapclient user not existing and not being writable to th snapclient user. after creating the directory /var/lib/snapclient and chowning it to the snapclient user, everything works like a charm.
This may be an issue of the snapclient package...

Update: here is the command:
mkdir /var/lib/snapclient
chown snapclient /var/lib/snapclient

@menghan
Copy link

menghan commented Jul 13, 2017

I also encountered this problem with exactly the same log, use @christf 's fix and it works.

@atze09
Copy link

atze09 commented Aug 16, 2017

Hello menghan and christf,

I have the same problem, what is the code you use to get this working?
i tried "sudo` chown -c snapsclient /var/lib/snapclient/"
But that does not work.
Can you please help me?
i am using version 0.11.1.
Thank you in advance

@menghan
Copy link

menghan commented Oct 20, 2017

@atze09 sorry for the late response.

The fix command: mkdir /var/lib/snapclient; chown snapclient /var/lib/snapclient works for me as 0.11.1. Since snapcast has newer release, I think it best to try the latest release.
Fix commands working for 0.11.1 may not works for the latest.

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

7 participants