Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Yosemite Java
25-11-2014, 00:05
Post: #21
RE: Yosemite Java
(24-11-2014 21:23)simoncn Wrote:  
(24-11-2014 20:58)rdono61 Wrote:  Thanks. I don't see even a faint yellow color, and certainly not the strong yellow that I saw before loading Yosemite. The log says MinimServer is running, and shows various incorrect date values from CDs I ripped several weeks ago. I just checked the Lightning app for my Auralic Vega/Aries, and now it appears that CDs I ripped today (after the Yosemite upgrade) have in fact been logged onto the Minimserver. Sp perhaps the only difference is that the icon does not turn yellow?

if the Rescan has worked, you will see something like the following in the log:

stopping MinimServer[xxx]
MinimServer[xxx] is stopped
Language setting is 'eng'
starting MinimServer[xxx]
MinimServer[xxx] is running

Do you see this?

Because of technical incompatibilties between Yosemite and Java for Mac OS X, it isn't possible for MinimServer to display the strong yellow colour that it was displaying on previous Mac OS X versions.

I cleared the Log first, then clicked Rescan. Nothing appeared in the Log.
Find all posts by this user
Quote this message in a reply
25-11-2014, 10:51
Post: #22
RE: Yosemite Java
(25-11-2014 00:05)rdono61 Wrote:  I cleared the Log first, then clicked Rescan. Nothing appeared in the Log.

I don't understand how this could happpen. Please try setting the logging level to Debug and leaving the log window open while you click Rescan.
Find all posts by this user
Quote this message in a reply
26-11-2014, 00:41
Post: #23
RE: Yosemite Java
(25-11-2014 10:51)simoncn Wrote:  
(25-11-2014 00:05)rdono61 Wrote:  I cleared the Log first, then clicked Rescan. Nothing appeared in the Log.

I don't understand how this could happpen. Please try setting the logging level to Debug and leaving the log window open while you click Rescan.

Sorry, my Internet has been out all day until now. Here is what was recorded in the log when I did what you suggested:

14:39:44.416 Thread-10: Monitor response: SaveProperty
14:39:44.416 Thread-10: ErrorMsg=
14:39:53.190 Thread-12: Monitor action: GetAllPackageStatus
14:39:53.190 Thread-12: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/9d4fe51a-3c5a-41bf-a701-be53962485ce/Upnp/resource/, clientEndpoint=10.0.0.5:53583
14:39:53.191 Thread-12: Monitor response: GetAllPackageStatus
14:39:53.191 Thread-12: PackageStatusList=minimserver-0.8-update-32,MinimServer 0.8 update,Active+Original,minimserver-0.8-update-42,MinimServer 0.8 update,Active,minimserver-0.8.2,MinimServer,Active+Original
14:39:53.197 Thread-10: Monitor action: GetProperty
14:39:53.197 Thread-10: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/9d4fe51a-3c5a-41bf-a701-be53962485ce/Upnp/resource/, clientEndpoint=10.0.0.5:53585
14:39:53.197 Thread-10: ComponentName=minimserver PropertyName=restartScan
14:39:53.197 Thread-10: Monitor response: GetProperty
14:39:53.197 Thread-10: PropertyValue=true
14:39:53.209 Thread-9: Monitor action: StartContext
14:39:53.209 Thread-9: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/9d4fe51a-3c5a-41bf-a701-be53962485ce/Upnp/resource/, clientEndpoint=10.0.0.5:53586
14:39:53.209 Thread-9: ContextName=context0
14:39:53.209 Thread-9: Monitor action complete: StartContext
14:39:53.209 main: context already started: context0
14:41:07.495 Thread-11: Log action: GetLogDataLength
14:41:07.495 Thread-11: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/9d4fe51a-3c5a-41bf-a701-be53962485ce/Upnp/resource/, clientEndpoint=10.0.0.5:53668
14:41:07.495 Thread-11: Log response: GetLogDataLength
14:41:07.495 Thread-11: DataLength=444557
Find all posts by this user
Quote this message in a reply
26-11-2014, 08:47
Post: #24
RE: Yosemite Java
(26-11-2014 00:41)rdono61 Wrote:  Sorry, my Internet has been out all day until now. Here is what was recorded in the log when I did what you suggested:

Thanks for this. It looks like MinimWatch and MinimServer have somehow got out of sync with each other, possibly because of network issues. Please do the following:

1) In Synology DSM, stop MinimServer
2) On the Mac, exit MinimWatch
3) On the Mac, restart MinimWatch
4) In Synology DSM, restart MinimServer and watch what happens to the minim icon on the Mac. It should change from grey to yellow and then to transparent. After this, clicking Rescan from the minim icon should produce the expected messages in the log.
Find all posts by this user
Quote this message in a reply
26-11-2014, 20:41
Post: #25
RE: Yosemite Java
(26-11-2014 08:47)simoncn Wrote:  
(26-11-2014 00:41)rdono61 Wrote:  Sorry, my Internet has been out all day until now. Here is what was recorded in the log when I did what you suggested:

Thanks for this. It looks like MinimWatch and MinimServer have somehow got out of sync with each other, possibly because of network issues. Please do the following:

1) In Synology DSM, stop MinimServer
2) On the Mac, exit MinimWatch
3) On the Mac, restart MinimWatch
4) In Synology DSM, restart MinimServer and watch what happens to the minim icon on the Mac. It should change from grey to yellow and then to transparent. After this, clicking Rescan from the minim icon should produce the expected messages in the log.

Ugh. This keeps getting worse. When I tried to restart MinimServer, I got a window that says:
"Failed to run service package. Java installation seems to be corrupted. Reinstall Java system package." I started to follow the steps for reinstalling Java from your website, but they no longer seem to match what is on the Oracle Java site to which the link takes you. Java is now in version 8, though I don't know whether Synology has upgraded to it. I did not see a reference to SE 7 upgrade 51 or Linux ARM v6-v7 Hard Float ABM. (I did see those when I first installed Java to install MinimServer, which is how I was able to install it initially.)
Help!
Find all posts by this user
Quote this message in a reply
26-11-2014, 20:59
Post: #26
RE: Yosemite Java
(26-11-2014 20:41)rdono61 Wrote:  
(26-11-2014 08:47)simoncn Wrote:  
(26-11-2014 00:41)rdono61 Wrote:  Sorry, my Internet has been out all day until now. Here is what was recorded in the log when I did what you suggested:

Thanks for this. It looks like MinimWatch and MinimServer have somehow got out of sync with each other, possibly because of network issues. Please do the following:

1) In Synology DSM, stop MinimServer
2) On the Mac, exit MinimWatch
3) On the Mac, restart MinimWatch
4) In Synology DSM, restart MinimServer and watch what happens to the minim icon on the Mac. It should change from grey to yellow and then to transparent. After this, clicking Rescan from the minim icon should produce the expected messages in the log.

Ugh. This keeps getting worse. When I tried to restart MinimServer, I got a window that says:
"Failed to run service package. Java installation seems to be corrupted. Reinstall Java system package." I started to follow the steps for reinstalling Java from your website, but they no longer seem to match what is on the Oracle Java site to which the link takes you. Java is now in version 8, though I don't know whether Synology has upgraded to it. I did not see a reference to SE 7 upgrade 51 or Linux ARM v6-v7 Hard Float ABM. (I did see those when I first installed Java to install MinimServer, which is how I was able to install it initially.)
Help!

Sorry. It appears that I figured out how to reinstall Java, and have restarted MinimServer. As you predicted, the clef icon went to yellow, then transparent. The log now has many entries, the last of which are as follows:

11:55:39.133 Thread-10: PropertyNames=.name,.version,.update,.updatePackage
11:55:39.133 Thread-10: Monitor response: GetAllPackageProperties
11:55:39.133 Thread-10: PackagePropertyList=minimserver-0.8-update-32,Active+Original,MinimServer 0.8 update,32,minimserver-0.8.1a.jmupd,minimserver-*,minimserver-0.8-update-42,Active,MinimServer 0.8 update,42,minimserver-0.8.1a.jmupd,minimserver-*,minimserver-0.8.2,Active+Original,MinimServer,0.8.2,minimserver-0.8.1a.jmupd,
11:55:39.145 Thread-11: Monitor action: GetProperty
11:55:39.145 Thread-11: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/ab0894bd-2a35-43c6-9702-95be004f1220/Upnp/resource/, clientEndpoint=10.0.0.5:53788
11:55:39.145 Thread-11: ComponentName=minimserver PropertyName=checkedUpdates
11:55:39.145 Thread-11: Monitor response: GetProperty
11:55:39.145 Thread-11: PropertyValue=
11:55:39.644 Thread-12: Monitor action: CheckPackage
11:55:39.644 Thread-12: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/ab0894bd-2a35-43c6-9702-95be004f1220/Upnp/resource/, clientEndpoint=10.0.0.5:53792
11:55:39.644 Thread-12: PackageName=minimserver-0.8-update-42 RequiredPackages={ge}minimserver-0.8.1 ConflictPackages={le}minimserver-0.8-update-17
11:55:51.320 Thread-9: Log action: GetLogDataLength
11:55:51.320 Thread-9: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/ab0894bd-2a35-43c6-9702-95be004f1220/Upnp/resource/, clientEndpoint=10.0.0.5:53804
11:55:51.320 Thread-9: Log response: GetLogDataLength
11:55:51.320 Thread-9: DataLength=834398
11:55:51.330 Thread-10: Monitor action: GetProperty
11:55:51.330 Thread-10: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/ab0894bd-2a35-43c6-9702-95be004f1220/Upnp/resource/, clientEndpoint=10.0.0.5:53805
11:55:51.330 Thread-10: ComponentName= PropertyName=logLevel
11:55:51.331 Thread-10: Monitor response: GetProperty
11:55:51.331 Thread-10: PropertyValue=debug
11:55:58.181 Thread-11: Log action: GetLogStart
11:55:58.181 Thread-11: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/ab0894bd-2a35-43c6-9702-95be004f1220/Upnp/resource/, clientEndpoint=10.0.0.5:53813
11:55:58.181 Thread-11: Log response: GetLogStart
11:55:58.181 Thread-11: StartPosition=340000
11:55:59.921 Thread-12: Log action: GetLogStart
11:55:59.921 Thread-12: version=1, adapter=10.0.0.39, uriPrefix=http://10.0.0.39:9791/ab0894bd-2a35-43c6-9702-95be004f1220/Upnp/resource/, clientEndpoint=10.0.0.5:53822
11:55:59.922 Thread-12: Log response: GetLogStart
11:55:59.922 Thread-12: StartPosition=340000

So going back to the original issue with Yosemite, what should I do, if anything for now? Thanks again...
Find all posts by this user
Quote this message in a reply
26-11-2014, 21:55
Post: #27
RE: Yosemite Java
(26-11-2014 20:59)rdono61 Wrote:  Sorry. It appears that I figured out how to reinstall Java, and have restarted MinimServer. As you predicted, the clef icon went to yellow, then transparent. The log now has many entries, the last of which are as follows:

So going back to the original issue with Yosemite, what should I do, if anything for now? Thanks again...

It sounds like everything is working OK now. You should set the logging level back to Info and enjoy the music! Smile
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)