MinimServer Forum / MinimServer / Support v / Often Linn Kazoo cannot see MinimServer

Post Reply 
Often Linn Kazoo cannot see MinimServer
16-03-2021, 10:40
Post: #9
vilmos Offline
Junior Member
**
 		Posts: 10
Joined: Mar 2021
Reputation: 0
RE: Often Linn Kazoo cannot see MinimServer
I got an answer from AVM. They say that the Fritz!Box does NOT do IGMP Snooping.

I also noted that after doing a Refresh from the MinimWatch menu, not only the icon gets grey but an open MinimWatch log window is closed. When Watch comes back I see the following messages in the log window (level: trace):

10:38:37.647 Thread-7: ListDeviceType:jminim.org:Monitor21: device added for udn 0b646803-bfb8-49dd-83de-e20551dfbf1b: org.openhome.net.controlpoint.CpDevice@171eb2c8
10:38:37.647 Thread-7: Upnp.Location: http://192.168.177.2:9791/0b646803-bfb8-...device.xml
10:38:37.647 Thread-7: Upnp.DeviceXml: <?xml version="1.0" encoding="utf-8"?><root xmlns="urn:schemas-upnp-org:device-1-0"><specVersion><major>1</major><minor>0</minor></specVersion><device><deviceType>urn:jminim-org:device:Monitor2:1</deviceType><friendlyName>Monitor Service 2</friendlyName><manufacturer>jminim.org</manufacturer><modelName>MonitorService2</modelName><UDN>uuid:0b646803-bfb8-49dd-83de-e20551dfbf1b</UDN><serviceList><service><serviceType>urn:jminim-org:service:Monitor2:2</serviceType><serviceId>urn:jminim-org:serviceId:Monitor2</serviceId><SCPDURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/Upnp/jminim.org-Monitor2-2/service.xml</SCPDURL><controlURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Monitor2-2/control</controlURL><eventSubURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Monitor2-2/event</eventSubURL></service><service><serviceType>urn:jminim-org:service:Log2:1</serviceType><serviceId>urn:jminim-org:serviceId:Log2</serviceId><SCPDURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/Upnp/jminim.org-Log2-1/service.xml</SCPDURL><controlURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Log2-1/control</controlURL><eventSubURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Log2-1/event</eventSubURL></service></serviceList></device></root>
10:38:37.647 Thread-7: Upnp.FriendlyName: Monitor Service 2
10:38:37.656 Thread-7: Upnp.PresentationUrl: null
10:38:37.657 Thread-7: ObserverService: device added for udn 0b646803-bfb8-49dd-83de-e20551dfbf1b: org.openhome.net.controlpoint.CpDevice@171eb2c8
10:38:37.657 Thread-7: ObserverService: calling addRef for device org.openhome.net.controlpoint.CpDevice@171eb2c8
10:38:37.657 Thread-7: deviceAdded: adding device org.openhome.net.controlpoint.CpDevice@171eb2c8
10:38:37.657 Thread-4: DeviceAddedAction starting
10:38:37.657 Thread-4: addDeviceMonitor: device org.openhome.net.controlpoint.CpDevice@171eb2c8 state PENDING_ADD
10:38:37.657 Thread-4: initializing DeviceMonitor
10:38:37.657 Thread-4: device type is Monitor Service 2
10:38:37.657 Thread-4: checking remote runtime version
10:38:37.663 Thread-4: remote runtime version is 2.0.136
10:38:37.664 Thread-4: TrayCallback: discovered remote device
10:38:37.664 Thread-4: TrayCallback: adding ServerControl
10:38:37.664 AWT-EventQueue-0: TrayView: creating tray icon
10:38:37.664 AWT-EventQueue-0: TrayView: created tray icon
10:38:37.664 Thread-4: ServerControl: listenerAdded called with RuntimeProxy
10:38:37.670 Thread-4: ServerControl: runtime version is 2.0.136
10:38:37.675 Thread-7: ListServiceType:jminim.org:Monitor21: device added for udn 0b646803-bfb8-49dd-83de-e20551dfbf1b: org.openhome.net.controlpoint.CpDevice@5eba70be
10:38:37.675 Thread-7: Upnp.Location: http://192.168.177.2:9791/0b646803-bfb8-...device.xml
10:38:37.675 Thread-7: Upnp.DeviceXml: <?xml version="1.0" encoding="utf-8"?><root xmlns="urn:schemas-upnp-org:device-1-0"><specVersion><major>1</major><minor>0</minor></specVersion><device><deviceType>urn:jminim-org:device:Monitor2:1</deviceType><friendlyName>Monitor Service 2</friendlyName><manufacturer>jminim.org</manufacturer><modelName>MonitorService2</modelName><UDN>uuid:0b646803-bfb8-49dd-83de-e20551dfbf1b</UDN><serviceList><service><serviceType>urn:jminim-org:service:Monitor2:2</serviceType><serviceId>urn:jminim-org:serviceId:Monitor2</serviceId><SCPDURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/Upnp/jminim.org-Monitor2-2/service.xml</SCPDURL><controlURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Monitor2-2/control</controlURL><eventSubURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Monitor2-2/event</eventSubURL></service><service><serviceType>urn:jminim-org:service:Log2:1</serviceType><serviceId>urn:jminim-org:serviceId:Log2</serviceId><SCPDURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/Upnp/jminim.org-Log2-1/service.xml</SCPDURL><controlURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Log2-1/control</controlURL><eventSubURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Log2-1/event</eventSubURL></service></serviceList></device></root>
10:38:37.675 Thread-7: Upnp.FriendlyName: Monitor Service 2
10:38:37.675 Thread-7: Upnp.PresentationUrl: null
10:38:37.675 Thread-7: ObserverService: device added for udn 0b646803-bfb8-49dd-83de-e20551dfbf1b: org.openhome.net.controlpoint.CpDevice@5eba70be
10:38:37.679 Thread-4: ServerControl: resource host is minimworld.com
10:38:37.679 Thread-4: starting DeviceMonitor org.jminim.lib.ObserverService$DeviceMonitor@51aa3853
10:38:37.679 Thread-4: DeviceMonitor.start: subscribing monitorProxy org.jminim.ohnet.CpProxyJminimOrgMonitor22@760ad50
10:38:37.679 Thread-4: DeviceAddedAction ended
10:38:37.679 Thread-7: ObserverService: ignoring added device with udn 0b646803-bfb8-49dd-83de-e20551dfbf1b and state ADDED
10:38:37.685 Thread-7: ListServiceType:jminim.org:Log21: device added for udn 0b646803-bfb8-49dd-83de-e20551dfbf1b: org.openhome.net.controlpoint.CpDevice@647dbd0c
10:38:37.685 Thread-7: Upnp.Location: http://192.168.177.2:9791/0b646803-bfb8-...device.xml
10:38:37.685 Thread-7: Upnp.DeviceXml: <?xml version="1.0" encoding="utf-8"?><root xmlns="urn:schemas-upnp-org:device-1-0"><specVersion><major>1</major><minor>0</minor></specVersion><device><deviceType>urn:jminim-org:device:Monitor2:1</deviceType><friendlyName>Monitor Service 2</friendlyName><manufacturer>jminim.org</manufacturer><modelName>MonitorService2</modelName><UDN>uuid:0b646803-bfb8-49dd-83de-e20551dfbf1b</UDN><serviceList><service><serviceType>urn:jminim-org:service:Monitor2:2</serviceType><serviceId>urn:jminim-org:serviceId:Monitor2</serviceId><SCPDURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/Upnp/jminim.org-Monitor2-2/service.xml</SCPDURL><controlURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Monitor2-2/control</controlURL><eventSubURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Monitor2-2/event</eventSubURL></service><service><serviceType>urn:jminim-org:service:Log2:1</serviceType><serviceId>urn:jminim-org:serviceId:Log2</serviceId><SCPDURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/Upnp/jminim.org-Log2-1/service.xml</SCPDURL><controlURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Log2-1/control</controlURL><eventSubURL>/0b646803-bfb8-49dd-83de-e20551dfbf1b/jminim.org-Log2-1/event</eventSubURL></service></serviceList></device></root>
10:38:37.685 Thread-7: Upnp.FriendlyName: Monitor Service 2
10:38:37.685 Thread-7: Upnp.PresentationUrl: null
10:38:37.685 Thread-7: ObserverService: device added for udn 0b646803-bfb8-49dd-83de-e20551dfbf1b: org.openhome.net.controlpoint.CpDevice@647dbd0c
10:38:37.685 Thread-7: ObserverService: ignoring added device with udn 0b646803-bfb8-49dd-83de-e20551dfbf1b and state ADDED
10:38:37.686 Thread-769: AllComponentStatusChanged: notifyChange time=1615887517686
10:38:37.686 Thread-769: AllContextStatusChanged: notifyChange time=1615887517686
10:38:37.686 Thread-769: PropertyUpdatesChanged: notifyChange time=1615887517686
10:38:37.686 Thread-769: MonitorInitialEvent: notifyChange time=1615887517686
10:38:37.686 Thread-4: MonitorInitialEventAction starting
10:38:37.686 Thread-4: cancelling monitorCheckInitAction for DeviceMonitor org.jminim.lib.ObserverService$DeviceMonitor@51aa3853
10:38:37.686 Thread-4: initial value of AllContextStatus=runtimeContext,Running,consoleContext,Running,context0,Running,​watchContext,Running,monitorContext,Running,ohnetContext,Running,httpContext,Run​ning
10:38:37.686 Thread-4: initial value of AllComponentStatus=runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,​console,org.jminim.lib.ConsoleService,consoleContext,Running,minimserver,com.min​imserver.Server,context0,Running,watch,com.minimserver.lib.WatchService,watchCon​text,Running,monitor,org.jminim.lib.MonitorService,monitorContext,Running,ohnet,​org.jminim.lib.OhNetService,ohnetContext,Running,http,org.jminim.lib.HTTPService​,httpContext,Running
10:38:37.686 Thread-4: DeviceMonitor notifyComponent: name=runtime, type=org.jminim.lib.RuntimeService, context=runtimeContext, status=Running
10:38:37.686 Thread-4: DeviceMonitor notifyContext: name=runtimeContext, status=Running
10:38:37.686 Thread-4: DeviceMonitor notifyComponent: name=console, type=org.jminim.lib.ConsoleService, context=consoleContext, status=Running
10:38:37.686 Thread-4: DeviceMonitor notifyContext: name=consoleContext, status=Running
10:38:37.686 Thread-4: DeviceMonitor notifyComponent: name=minimserver, type=com.minimserver.Server, context=context0, status=Running
10:38:37.686 Thread-4: ServerControl: monitoring server component minimserver, context context0
10:38:37.690 Thread-4: ServerControl: componentRunning event for minimserver
10:38:37.690 Thread-4: DeviceMonitor notifyContext: name=context0, status=Running
10:38:37.690 Thread-4: ServerControl: contextRunning event for context0
MinimServer[mini] is running
10:38:37.693 Thread-4: removing default tray icon
10:38:37.693 Thread-4: TrayView: removing tray icon
10:38:37.693 AWT-EventQueue-0: trayIcon popupMenu is java.awt.PopupMenu[popup0,label=,tearOff=false,isHelpMenu=false]
10:38:37.694 Thread-4: TrayView: waiting for X11 events
10:38:37.694 Thread-4: disposed popupMenu peer after 0 retries
10:38:37.694 Thread-4: got trayIcon peer
10:38:37.694 Thread-4: trayIcon peer class is sun.lwawt.macosx.CTrayIcon
10:38:37.694 Thread-4: trayIcon messageDialog is null
10:38:37.694 Thread-4: TrayView: removed tray icon
10:38:37.694 Thread-4: TrayView: adding tray icon
10:38:37.701 Thread-4: TrayView: added tray icon
10:38:37.701 AWT-EventQueue-0: TrayView: displaying tray icon tooltip: MinimServer[mini] is running
10:38:37.701 Thread-4: TrayView: running checkUpdates
10:38:37.701 Thread-4: TrayView.checkUpdates: adding update view for MinimServer[mini]
10:38:37.701 Thread-4: ServerControl: checkNewVersion action
10:38:37.701 Thread-794: TrayControl: running doCheckUpdates
10:38:37.701 Thread-794: TrayControl.doCheckUpdates: checking update offers for MinimServer[mini]
10:38:37.712 Thread-794: ServerControl.readCheckedUpdates: checkedUpdates=
10:38:37.712 Thread-4: doNextCheckNow: lastNewVersionCheck lastCheckedTime=0
10:38:37.716 Thread-794: ServerControl.checkOffer: updateFile=minimserver-2.jmupd
10:38:37.717 Thread-794: getUpdatePackages: updateFile=minimserver-2.jmupd
10:38:37.721 Thread-4: getNonUpdatePackages result=[MinimServer]
10:38:37.721 Thread-794: PackageManager: setting resourcePrefix to http://minimworld.com/
10:38:37.721 Thread-4: getProgramProperty progName=MinimServer propName=.newVersion result=
10:38:37.721 Thread-4: getProgramProperty progName=MinimServer propName=.newVersionURL result=
10:38:37.721 Thread-4: getProgramProperty progName=MinimServer propName=.versionUpdate result=
10:38:37.721 Thread-4: getProgramProperty progName=MinimServer propName=.versionUpdateURL result=
10:38:37.721 Thread-4: getProgramProperty progName=MinimServer propName=.update result=minimserver-2.jmupd
10:38:37.721 Thread-4: getUpdateProperties: updateFile=minimserver-2.jmupd
10:38:37.721 Thread-4: PackageManager: cached resourcePrefix is http://minimworld.com/
10:38:37.803 Thread-794: ServerControl.isPackageRequired: packageName=minimserver-update-187
10:38:37.803 Thread-794: isPackageRequired: minimserver-update-187 is already installed
10:38:37.803 Thread-794: TrayControl.doCheckUpdates: removing update view for MinimServer[mini]
10:38:37.803 Thread-794: TrayControl.doCheckUpdates: updateViews is empty
10:38:37.808 Thread-4: getProgramProperty progName=MinimServer propName=.version result=2.0.18
10:38:37.808 Thread-4: getNewVersionInfo: newVersion= name=MinimServer
10:38:37.808 Thread-4: DeviceMonitor notifyComponent: name=watch, type=com.minimserver.lib.WatchService, context=watchContext, status=Running
10:38:37.808 Thread-4: DeviceMonitor notifyContext: name=watchContext, status=Running
10:38:37.808 Thread-4: DeviceMonitor notifyComponent: name=monitor, type=org.jminim.lib.MonitorService, context=monitorContext, status=Running
10:38:37.808 Thread-4: DeviceMonitor notifyContext: name=monitorContext, status=Running
10:38:37.808 Thread-4: DeviceMonitor notifyComponent: name=ohnet, type=org.jminim.lib.OhNetService, context=ohnetContext, status=Running
10:38:37.808 Thread-4: DeviceMonitor notifyContext: name=ohnetContext, status=Running
10:38:37.808 Thread-4: DeviceMonitor notifyComponent: name=http, type=org.jminim.lib.HTTPService, context=httpContext, status=Running
10:38:37.808 Thread-4: DeviceMonitor notifyContext: name=httpContext, status=Running
10:38:37.808 Thread-4: initial value of PropertyUpdates=watch.serverView:1615887232144
10:38:37.808 Thread-4: DeviceMonitor notifyPropertyUpdate: name=watch.serverView
10:38:37.808 Thread-4: ServerControl: propertyUpdated event for watch.serverView
10:38:37.810 Thread-4: initialized DeviceMonitor org.jminim.lib.ObserverService$DeviceMonitor@51aa3853
10:38:37.810 Thread-4: MonitorInitialEventAction ended
10:38:41.680 Thread-1: MonitorCheckInitializedAction starting
10:38:41.680 Thread-1: monitorCheckInitialized: org.jminim.lib.ObserverService$DeviceMonitor@51aa3853
10:38:41.680 Thread-1: MonitorCheckInitializedAction ended
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Often Linn Kazoo cannot see MinimServer - vilmos - 16-03-2021 10:40

Forum Jump:


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

Contact Us | MinimServer Home | Return to Top | Return to Content | Lite (Archive) Mode | RSS Syndication