Audio streaming with non-default icecast password about raveberry

[raveberry]

The icecast log looks fine.

Your mopidy instance however is loading its configuration from /root/.config/mopidy/mopidy.conf instead of /etc/mopidy/mopidy.conf. Raveberry expects it to be in the latter location, so changes to the config do not reflect in mopidy's behavior. This leads to mopidy trying to connect to the default alsa output, which it is not allowed to, raising the error.

Now you can either make mopidy use the config at /etc/mopidy.conf by deleting your copy in /root, or copy the contents of setup/mopidy_icecast.conf over to the used file in /root. Then mopidy should stream its audio to icecast.

daphne's log says ping: socket: Operation not permitted. ping is used to test internet connection, which is needed to play online music. Raveberry should still work, although only with local music.

[Barborica-Alexandru]

Hey thanks for taking the time to help. I explicitly launched mopidy with the config at /etc/mopidy/mopidy.conf and copied the setup/mopidy_icecast.conf over it. Still getting the same error sans the spotify stuff that is unrelated.

I feel like this is unrelated to raveberry and rather a problem in mopidy so don't let me eat up too much of your time. I can just post an issue over on the mopidy git if you feel like it belongs there.

mopidy --config /etc/mopidy/mopidy.conf 
INFO     2020-05-04 08:58:48,485 [803:MainThread] mopidy.__main__
  Starting Mopidy 3.0.2
INFO     2020-05-04 08:58:48,512 [803:MainThread] mopidy.config
  Loading config from builtin defaults
INFO     2020-05-04 08:58:48,514 [803:MainThread] mopidy.config
  Loading config from file:///etc/mopidy/mopidy.conf
INFO     2020-05-04 08:58:48,515 [803:MainThread] mopidy.config
  Loading config from command line options
INFO     2020-05-04 08:58:48,761 [803:MainThread] mopidy.__main__
  Enabled extensions: spotify, m3u, softwaremixer, stream, http, file
INFO     2020-05-04 08:58:48,762 [803:MainThread] mopidy.__main__
  Disabled extensions: none
INFO     2020-05-04 08:58:48,979 [803:MainThread] mopidy.commands
  Starting Mopidy mixer: SoftwareMixer
INFO     2020-05-04 08:58:48,981 [803:MainThread] mopidy.commands
  Starting Mopidy audio
INFO     2020-05-04 08:58:48,984 [803:MainThread] mopidy.commands
  Starting Mopidy backends: SpotifyBackend, FileBackend, M3UBackend, StreamBackend
INFO     2020-05-04 08:58:49,014 [803:SpotifyBackend-3] mopidy.internal.path
  Creating dir file:///root/.cache/mopidy/spotify
INFO     2020-05-04 08:58:49,015 [803:SpotifyBackend-3] mopidy.internal.path
  Creating dir file:///root/.local/share/mopidy/spotify
INFO     2020-05-04 08:58:49,017 [803:Audio-2] mopidy.audio.actor
  Audio output set to "rgvolume ! audioconvert ! audioresample ! lamemp3enc ! shout2send async=false mount=stream"
ERROR    2020-05-04 08:58:49,400 [803:SpotifyEventLoop] spotify.session
  Spotify login error: <ErrorType.BAD_USERNAME_OR_PASSWORD: 6>
ERROR    2020-05-04 08:58:49,953 [803:SpotifyBackend-3] mopidy_spotify.web
  Authorization failed, not attempting Spotify API request. Please get new credentials from https://www.mopidy.com/authenticate and/or restart Mopidy to resolve this problem.
ERROR    2020-05-04 08:58:49,953 [803:SpotifyBackend-3] mopidy_spotify.web
  OAuth token refresh failed: invalid_client Client not known.
ERROR    2020-05-04 08:58:49,954 [803:SpotifyBackend-3] mopidy_spotify.web
  Failed to load Spotify user profile
INFO     2020-05-04 08:58:49,955 [803:MainThread] mopidy.commands
  Starting Mopidy core
INFO     2020-05-04 08:58:49,972 [803:MainThread] mopidy.commands
  Starting Mopidy frontends: HttpFrontend
INFO     2020-05-04 08:58:49,974 [803:HttpFrontend-11] mopidy.http.actor
  HTTP server running at [::ffff:127.0.0.1]:6680
INFO     2020-05-04 08:58:49,975 [803:MainThread] mopidy.commands
  Starting GLib mainloop
ERROR    2020-05-04 08:58:50,574 [803:MainThread] mopidy.audio.gst
  GStreamer error: Could not connect to server

[raveberry]

You can make some of the Spotify errors go away by deleting the Spotify section in the config, but they shouldn't matter.

There seems to be an issue with the connection to icecast. Can you confirm that it is running and you are able to log in to its inferface at port 8000? Maybe you need to set some additional information in the config, for example:
output = lamemp3enc ! shout2send async=false mount=mopidy ip=127.0.0.1 port=8000 password=hackme (source)
Raveberry expects the default configuration of icecast, I probably should add this information to the documentation.

[Barborica-Alexandru]

YAAAAAY! I didn't use the default passwords for icecast that was the problem. Thanks you're the best!

But yeah you should add that to the documentation.

[raveberry]

Great that it works now, have fun!
Also, I just updated the documentation so people should not run into this problem again.