Command prompt shows shell change message to zsh (ref#G4IC9G)

Support
1

What is the operating system of your Roon Server host machine?

· MacOS

What kind of device are you using to perform the login?

· Mac

Where are you trying to login?

· I can't log into Roon

Have you been redirected to [https://account.roon.app](https://account.roon.app) (the Roon login page) in your browser?

· No

Different device

· I am able to switch to the diffrent device

Are you still facing the issue on the different device

· No, the issue remains the same

Record the timestamp

· it occurs almost every time i switch on my Mac. i tried to work around by searching for RAAT but that should not be a solution

Describe the issue

a cmd prompt pops up with message "the default interactive shell now is zsh"

Describe your network setup

MacMini IOS Monterey 12.7.6, Linksys router and Fritzbox 7530

2

Hey @mcvandijk66,

Welcome to the community! We’re happy to have you here. Thanks for the detailed notes as well. We were able to review a fresh set of Roon Server logs, and they told a clear story.

The good news is that your Roon account and login are actually working fine. Across your logs, virtually every login to our servers succeeded; the handful that didn’t were brief momentary hiccups right after your Mac starts up (before the network is fully ready) and a couple of temporary server-side blips on our end. So this isn’t a password or account problem, and you shouldn’t need the (account.roon.app) login page to resolve it.

What the logs do show is the real cause of your trouble: Roon Server keeps losing the connection to its own audio engine (RAATServer) shortly after your Mac boots. The reason is that your Mac mini’s IP address is changing between restarts, the logs show it appearing as both 192.168.178.22 and 192.168.178.62 on different startups. When the address changes, Roon Server tries to reach its audio engine at the old address, fails, and the zone drops out.

That’s exactly why searching for RAAT temporarily brings things back, you’re forcing Roon to rediscover it. It’s a good instinct, but you’re right that it shouldn’t be necessary, and the steps below should stop it from happening.

A likely contributor is that you have two routers in play (the Linksys and the Fritzbox 7530). That kind of setup can create two networks and unstable addressing, which is what we’re seeing here. I’d suggest, in order:

  1. Give the Mac mini a fixed address. In your Fritzbox, assign the Mac mini a static/reserved IP (sometimes called "Always assign this network device the same IP address"). This alone usually stops the drop-outs.
  2. Use a single network connection on the Mac mini. If both Wi-Fi and Ethernet are active, turn one off, wired Ethernet is best, so Roon binds to one stable address.
  3. Simplify the two-router setup if possible. Ideally only one device should be handing out IP addresses. Putting the Linksys (or the Fritzbox) into bridge/access-point mode so everything lives on one network will make Roon much more reliable long term.
On the separate issue, the "the default interactive shell is now zsh" window that appears when you switch on your Mac, that's a macOS message, not a Roon error, and it doesn't affect playback.

It usually means Roon Server is being launched at startup by a small script or Terminal command rather than the app itself. If you’d like, tell me how you have Roon Server set to start automatically (a Login Item, a script, etc.) and I’ll walk you through switching it to launch the RoonServer app directly, which makes the message go away.

Try the network steps above and let me know how it goes, happy to stay on this with you. :raising_hands:

3

Hey @mcvandijk66,

Just checking in on this. Have you had a chance to try the network changes we mentioned, especially giving the Mac mini a fixed IP in the Fritzbox and using just one network connection on the Mac, ideally Ethernet? If you’re still seeing the RAATServer drop out, we’d also like to know whether the Linksys and Fritzbox are both still handing out addresses, and whether the “default interactive shell is now zsh” message is still appearing at startup. Let us know what you’re seeing, and we can take it from there.

Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.

4

Hi,

Thank you for informing. I have fixed the IP adres in the Fritzbox, indeed. It was already connected through Ethernet and WiFi was switched off. So this is the only unstable factor.

I have not been able to check if Roon is stable, though. I can try tomorrow evening. I will let you know the outcome.

Michel

5

the above should have been sent to you yesterday, but apparently I didn’t read well and just replied to the mail. That did not work.

I just restarted the MacMini and a bit in slow motion Roon started without a fault message. So this might have been the correct solution.

If Roon is still not stable in time, I will issue a new ticket.

thanks for the support!

6

Hey @mcvandijk66,

Thanks for the update. It sounds like the fixed IP and the restart may have done the trick, and that is a good sign. Please let us know how Roon is performing after you have had a chance to test it a bit more. If it stays stable, we will treat that as the likely resolution and close this one out. Enjoy the music!

7

Hmmm, the last two days I switched the Mac on and off, with Roon starting up perfectly, but just after today’s update Roon can’t find its server anymore. Same fault.

Last login: Tue Aug 4 19:54:15 on console

The default interactive shell is now zsh.

To update your account to use zsh, please run ‘chsh ~s /bin/zsh’.

For more details, please visit Use zsh as the default shell on Mac - Apple Support.

I checked if anyhow the Fritzbox changed IP settings, but it didn’t.

Any other suggestions?

Greetings, Michel

8

Hello @mcvandijk66

Good news, and apologies for the timing on this one.

What you hit on 4 August was not your network and not your Fritzbox settings. The 2.71 update released that day contained a bug that prevented Roon Server from starting on macOS 12 and 13 specifically. Your Mac mini runs Monterey 12.7.6, so it was affected. Macs on macOS 14 and later were not, which is why this looked so unpredictable.

We released a hotfix on 6 August that fixes it: Roon 2.71 build 1683. Full details are here:

Please download Roon Server for macOS from

and install it over your existing copy. Nothing is lost by doing this, your database, playlists and settings all stay in place.

Once you are on 1683, Roon Server should start normally again on boot.

On the separate matter of the zsh message: that is unrelated to any of this, and it is harmless. It is macOS telling you about a change to its default shell, and it appears because Roon Server is being launched at startup by a Terminal command or a small script rather than by the app itself. If you would like it gone, please tell us how you have Roon Server set to start automatically, whether that is a Login Item, a script, or something else, and we will show you how to switch it to launching the app directly.

Please let us know once you are on build 1683 and whether everything comes up cleanly.