Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dennis in FL]

I have two Macs,  I was using a 2020 Intel iMac with a NAS server for the music files and it couldn't survive 24 hours without crashing.   I also have a Mac Mini with an Apple M1 chip and tried it instead ( I saved a backup with the iMac and restored on the mini)  and same thing.....it crashed sometime in the evening hours. 

Looking for suggestions.

[JimH]

Update the NAS firmware.

[Dennis in FL]

Update the NAS firmware.

It is on auto update......and it is the latest (Synology Sept 11 Version: 7.2.2-72806 )

[bob]

Likely a corrupted media file.
Check the MC log.

[Dennis in FL]

Well, I took a short break to evacuate due to Hurricane Milton.

No damage of any consequence !!!

So I started MC in a Mac server and also ran a client on an iMac.   

They both crashed and the last log entries were about sharing plugins and DLNA stuff (if this is video, I set up TV only as a curiosity and I never use it - so I can remove the TV components )

I cut and pasted the very bottom of the log and I have no clue what it means.   

Also attached the full logs of both macs (client labled as such- other file is mac mini server)

I took a peek at DLNA settings and changed both Audio and Video to ORIGINAL and am now testing this new setting to see if it crashes.

Client:


0015153: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0015154: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Start
0015154: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Reading 5274 bytes from message body
0015155: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Finish (1 ms)
0015155: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.50.31: NOTIFY: http://192.168.50.15:52102/eventSub
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Start
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Transport state was 0 changing to 0
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Finish (0 ms)
0015155: 123145545089024: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
0015155: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (1 ms)
0015155: 123145545089024: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 43


Server:

0015153: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0015154: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Start
0015154: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Reading 5274 bytes from message body
0015155: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Finish (1 ms)
0015155: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.50.31: NOTIFY: http://192.168.50.15:52102/eventSub
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Start
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Transport state was 0 changing to 0
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Finish (0 ms)
0015155: 123145545089024: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
0015155: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (1 ms)
0015155: 123145545089024: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 43

[JimH]

Was the power out?

Try powering all computers and network devices off, waiting a few minutes, then re-starting the network first, then other devices.

[Dennis in FL]

Was the power out?

Try powering all computers and network devices off, waiting a few minutes, then re-starting the network first, then other devices.

Yes post hurricane the power was off for days.   I had everything on UPS battery and nice shutdowns before power loss.

But what I'm describing is a pre-hurricane problem, pre-power loss problem that continued after restoration of power

The probelm has been, everything seems OK and music plays correctly for a while.   Then it crashes.   When I use a client MC with a library from a server MC...they both crash.   

However, my small changes to the DLNA settings seems to be working for a while now.   I changed the output format to ORIGINAL and so far--no crash.   In the past, it rarely lasted 8 hours doing nothing.

[JimH]

That might be a conversion problem on the server.  A different codec might work.

[bob]

The Apple crash report should be useful, when you get one next time copy and paste it here.
The logs aren't showing anything much out of the ordinary, however the client log appears to show you have 2 active network interfaces on the same lan, is that the case?
What DLNA devices do you have on the network?
What other DLNA capable programs are you running on either Mac?

[Dennis in FL]

>> The Apple crash report should be useful, when you get one next time copy and paste it here.

OK


>>The logs aren't showing anything much out of the ordinary, however the client log appears to show you have 2 active network interfaces on the same lan, is that the case?

I think that's the way my iMac reports using both WiFi and Ethernet --- each has a separate IP address.  I have forgotten why I do  that but there was some APP that required WiFi.   I can probably just use ethernet.


>>What DLNA devices do you have on the network?

I have a WiiM Ultra preamp and an LG TV .... I never use the TV.

>>What other DLNA capable programs are you running on either Mac?

I have a Raspi 4 running Ropieee with DLNA turned off.  I use it to feed Airplay into the WiiM

 I have Tidal which uses Tidal Connect and I have QOBUZ which I'm not using now.

I think Plex has DLNA (not sure) but although I have the server running on the same machine as MC, I rarely use it.

JRiver MC lists only the WiiM and Sonos speakers in Playing now

[bob]

>> The Apple crash report should be useful, when you get one next time copy and paste it here.

OK


>>The logs aren't showing anything much out of the ordinary, however the client log appears to show you have 2 active network interfaces on the same lan, is that the case?

I think that's the way my iMac reports using both WiFi and Ethernet --- each has a separate IP address.  I have forgotten why I do  that but there was some APP that required WiFi.   I can probably just use ethernet.


>>What DLNA devices do you have on the network?

I have a WiiM Ultra preamp and an LG TV .... I never use the TV.

>>What other DLNA capable programs are you running on either Mac?

I have a Raspi 4 running Ropieee with DLNA turned off.  I use it to feed Airplay into the WiiM

 I have Tidal which uses Tidal Connect and I have QOBUZ which I'm not using now.

I think Plex has DLNA (not sure) but although I have the server running on the same machine as MC, I rarely use it.

JRiver MC lists only the WiiM and Sonos speakers in Playing now

Usually the only reason to have wifi and ethernet on at the same time is to use airdrop. My dev machine has that. It doesn't seem to affect the running MC adversely but it will likely be broadcasting SSDP on both interfaces.
Seeing the 1900 port socket in use makes me think that you have another DLNA program running on the Mac though that really shouldn't cause a crash.

[Dennis in FL]

MC on both Macs are both running perfectly now all morning.  Before I changed the DLNA settings it would have crashed by now.   I used to have ORIGINAL as I think DFF or DSF on audio when it was crashing.

Fingers crossed

[Dennis in FL]

MC crashed overnight.   Both the server and the client.   I force quit both and only the server produced an Apple crash report (attached with MC log).

Is this the old Time Machine Issue?   I have both Macs on a early morning daily backup.


But the crash is not only in the evening.  I have had crashes maybe an hour after beginning to play a song.   Yesterday it survived many hours before crashing

[EnglishTiger]

Is this the old Time Machine Issue?   I have both Macs on a early morning daily backup.

It may well be Time Machine or Spotlight as both of them are Notorious for using up a lot of Disk Space for no obvious reason.

[bob]

MC crashed overnight.   Both the server and the client.   I force quit both and only the server produced an Apple crash report (attached with MC log).

Is this the old Time Machine Issue?   I have both Macs on a early morning daily backup.


But the crash is not only in the evening.  I have had crashes maybe an hour after beginning to play a song.   Yesterday it survived many hours before crashing

Force quit?
So neither is actually "crashing". You are calling hanging a crash?

[Dennis in FL]

Yes….hanging…..

[bob]

Yes….hanging…..

Probably something to do with sleep settings and network activity.
You could check your system preferences->energy saver settings.

[Dennis in FL]

Probably something to do with sleep settings and network activity.
You could check your system preferences->energy saver settings.

No...I'm running the JRiver server on a headless Mac Mini (M1 chip) and it has other 24/7 software running so I disabled any energy savers.   And plus, it hangs during the day as well.   I thought it had to do with the client server handshaking.   I have a ASUS ZenWiFi AX (XT8) Router system and it is blazing fast and has no trouble sending 4K video from the NAS to my Apple TV.

Anyway, I just transferred the MC server to a Raspi 5 and played some music from the iMac client.   It was working but had some significant dropouts - I guess the Pi doesn't have enough oomph.   So I decided to go back to the MC server on the Mac Mini and when I clicked on the client's library choice for the mini they both hung.  I'll attach the Apple crash report to this post.

[bob]

No...I'm running the JRiver server on a headless Mac Mini (M1 chip) and it has other 24/7 software running so I disabled any energy savers.   And plus, it hangs during the day as well.   I thought it had to do with the client server handshaking.   I have a ASUS ZenWiFi AX (XT8) Router system and it is blazing fast and has no trouble sending 4K video from the NAS to my Apple TV.

Anyway, I just transferred the MC server to a Raspi 5 and played some music from the iMac client.   It was working but had some significant dropouts - I guess the Pi doesn't have enough oomph.   So I decided to go back to the MC server on the Mac Mini and when I clicked on the client's library choice for the mini they both hung.  I'll attach the Apple crash report to this post.

The crash report isn't useful when there is a force quit involved.
Are you running it in Media Server only mode when headless?

[Dennis in FL]

Not sure what you mean? 

Do you mean is the MC the only software running?  No

Or is there a setting in MC that should be turned on to make it a server only?

[Dennis in FL]

see screenshot attached

[JimH]

Maybe you said but are your files on a removable Drive?

[JimH]

A Raspberry Pi is fast enough for any audio.  And most video.

[Dennis in FL]

Maybe you said but are your files on a removable Drive?

No...the audio files are on a NAS Synology server and the MC settings, logs, etc are on the Mac Mini internal SSD or the NAS server.

[Dennis in FL]

A Raspberry Pi is fast enough for any audio.  And most video.

I know...that's why I thought there was something amiss with my DLNA settings or possibly with the communication of a MC server/client.   I'll try the Raspi all alone without the client and see if I get dropouts.

[Dennis in FL]

The crash report isn't useful when there is a force quit involved.
Are you running it in Media Server only mode when headless?

Now it crashed when I was closing it --- no forced quit this time (report attached)

[bob]

Not sure what you mean? 

Do you mean is the MC the only software running?  No

Or is there a setting in MC that should be turned on to make it a server only?

On window and Mac you can set MC to server only mode when starting (in settings under startup).
That will prevent any UI interaction (dialog boxes, etc).

[Dennis in FL]

I just saw that for the first time...thanks....

I just set it for server and am rebooting.

[Dennis in FL]

On window and Mac you can set MC to server only mode when starting (in settings under startup).
That will prevent any UI interaction (dialog boxes, etc).

I had high hopes.  I set the MC for server on the Mac Mini and rebooted it.  Sure enough, MC was running.   And I ran played a couple of half hour symphonies from a iMac client without issue.   

So I decided to let it sit there doing nothing and sure enough when I checked this morning it had hung and I needed to force quit.

This is getting frustrating.   Are there any apps MC doesn't play nice with?   I don't remember any of this happening with MC 32.  I'm going to try running MC solo on the iMac and forgetting about the Mac Mini and server mode.

[Dennis in FL]

I ran MC solo on one Mac and it was doing fine all day yesterday but this morning it had hung.   I suspect Time Machine interference.   

I have a Raspi and a Windows machine......I'll try one of them while still using the NAS for the files tonight.  I have other Mac Apps runing 24/7 with NAS files (like Emby) that don't hang.

This time was different, however.  When I force quit MC, the Mac immediately blkew up and I had a black screen.   I had to hit the power button.

I can't remember anything like this with MC 32.

[Dennis in FL]

On window and Mac you can set MC to server only mode when starting (in settings under startup).
That will prevent any UI interaction (dialog boxes, etc).

One of the things I love is the ability to save and restore a library across platforms.

I saved the library on my Mac and restored it on my Windows 11 machine

And then I imported the same NAS library used on the Mac and let MC run overnight

It survived.  No hanging.  No crashes.   All is well.

Definitely a Mac issue.

I need the Mac to either be a client or a server.  I can have the WIndows machine be a server with the Mac as a client (haven't tested that yet).   

Years ago I had dropouts when the Mac was running Time Machine and all Macs do a backup overnight. 


Any suggestions on tracking down the issue?   

[Dennis in FL]

On window and Mac you can set MC to server only mode when starting (in settings under startup).
That will prevent any UI interaction (dialog boxes, etc).

I think I may have stumbled on something.   This morning my Windows version was also hanging.   But the attached screenshot is what was on monitor.   I had accidentally included an SACD ISO file.   I have been extracting DSF files from the ISOs and this one had slipped through the cracks.   

Seems there's an endless loop there.   

I'm going to double check if there are any more iso files and then rerun the Mac version to see if that's it.

[Dennis in FL]

It isn't just ISO....FLAC is also repeating

[Dennis in FL]

Last night I tested a Windows MC server with a Mac client and the Windows server was fine this morning and the Mac hung requiring a force quit.   The strange repeating above of the iso and flac files also occurs with wav files. 

[bob]

Last night I tested a Windows MC server with a Mac client and the Windows server was fine this morning and the Mac hung requiring a force quit.   The strange repeating above of the iso and flac files also occurs with wav files.

It should like your library has a loop of duplicate entries in it. Are you using the portable library function? You might have trouble with that and auto-import paths

[Dennis in FL]

It should like your library has a loop of duplicate entries in it. Are you using the portable library function? You might have trouble with that and auto-import paths

No...not using the portable library ....just regular old library.   But I did save the library in a Mac and restore it in a Windows MC. 

It is exclusively FLAC, ISO or WAV files.   I've seen no repeats in DSF, MP3, ALAC, etc.

I suspect it is something in the restore of the library is buggy.   I'm going to try a brand new Library on the same NAS files and see if they repeat.
 

[Dennis in FL]

OK...I created a brand new library and used the same NAS files as the library above with all the repeating entries.

And it was fine.   The example I used is the repeating Ashkenazy Prelude.   I attached a screenshot from both the Library reloaded on Windows from a Mac and a brand new library but using the same NAS file folders

I'm using some simple display rules like sorting based on artist and composition but nothing that should affect file type.

If I go back to the Mac with the original library (backed up and restored to windows) it does not repeat (also attached)

[Dennis in FL]

Yesterday I created a bare bones library on the Mac using the MC defaults but still using the NAS files.

This morning all was well and it is not duplicating the files as above.

So I suspect it is something with the customized views (almost all in Classical music album displaying) in the library that causes so many bugs. 

I had been using that library on my mac as far back as MC 30 or 31 without issue.   

I am thinking it may be prudent to start from scratch although that would be a major pain.

[Dennis in FL]

I started from scratch and everything has been working correctly until today - I had a crash.   

[bob]

I started from scratch and everything has been working correctly until today - I had a crash.

What were you doing when it crashed? Are you using media network at all?

[Dennis in FL]

No...I wasn't using MC at the time of the crash.

Interesting...after I restarted Media Center,  all my classical music was missing.   No files at all.   But other genres were there....Pop, jazz, etc.

After trying running auto-import and just about everything else I could think of, I did a restore of my last backup and all my classical was back again.

Update:  It crashed while I was typing this.   This time it was playing music and I had just finished checking Customized View settings as I suspected MC doesn't like something there.   

I didn't save the iMac report unfortunately.   But I attach the log

And it just crashed again...this time I got the Mac crash report.   Attached