Willkommen › Foren › LogoControl › LogoControl Crashes after time
- Dieses Thema hat 14 Antworten sowie 5 Stimmen und wurde zuletzt vor vor 7 Jahren, 7 Monaten von
DuBMicX aktualisiert.
-
AutorBeiträge
-
12. Februar 2017 um 13:29 #3290
DuBMicX
TeilnehmerEveryday my LogoControl random stops running and i get this error in the logs
12/02/2017 01:09:38: Globale nicht behandelte Ausnahme aufgetreten: System.NullReferenceException: Object reference not set to an instance of an object at System.ServiceModel.Dispatcher.ListenerLoopManager.ProcessRequest (IReplyChannel reply, System.ServiceModel.Channels.RequestContext rc) [0x00000] in <filename unknown>:0 at System.ServiceModel.Dispatcher.ListenerLoopManager.TryReceiveRequestDone (IAsyncResult result) [0x00000] in <filename unknown>:0 (no inner exception)
Hope you can help me out
14. Februar 2017 um 13:28 #3295admin
AdministratorWhich version of mono are you using? Can you remember what you did at 12/02/2017 01:09:38? The exception leads to some problem in the ServiceModel Dispatcher, which is serving the WebUI and the REST-Webservice. That means there was some HTTP-request initiated either by you (by using the WebUI) or some 3rd party service (like the NetIO App using the REST-Webservice). Are you able to reproduce the crash in some way? Random/sporadic errors are hard to find…
15. März 2017 um 22:23 #3371Roman
TeilnehmerHello I can reproduce that bug
Unhandled Exception:
System.NullReferenceException: Object reference not set to an instance of an object
at System.ServiceModel.Dispatcher.ListenerLoopManager.ProcessRequest (System.ServiceModel.Channels.IReplyChannel reply, System.ServiceModel.Channels.RequestContext rc) [0x0005c] in <8cdac92fdd4b495ba10570db10926ad4>:0
at System.ServiceModel.Dispatcher.ListenerLoopManager.TryReceiveRequestDone (System.IAsyncResult result) [0x0001a] in <8cdac92fdd4b495ba10570db10926ad4>:0
at (wrapper managed-to-native) System.Runtime.Remoting.Messaging.AsyncResult:Invoke (System.Runtime.Remoting.Messaging.AsyncResult)
at System.Runtime.Remoting.Messaging.AsyncResult.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <8f2c484307284b51944a1a13a14c0266>:0
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0This happens when mono/mvc/razor try to connect WCF
2. Juli 2017 um 0:28 #3488DuBMicX
TeilnehmerAnd how can i fix that Roman?
17. Juli 2017 um 22:06 #3496DuBMicX
TeilnehmerPlease?
23. Juli 2017 um 22:49 #3497rob
TeilnehmerDear DubMicX it would help if you answer the questions asked.
Give us any idea of what you did at the date and time of the called crash, Is it a specific action that always gives a crash?
What action? Action from what programm?Tell us the used mono version.
I have had hundreds of errors by trying to connect my Domoticz server to LogoControl, all caused by myself, I used the wrong REST parameters or messed up the config.xml… What did you do?
23. Juli 2017 um 23:41 #3498DuBMicX
TeilnehmerHomebridge is getting the state of the outputs of my logo trougt LogoControl and sending on off signals ill give u mu config.xml and the config where the REST parameters are in it, sometimes this error happens and sometimes it runs without problem for a few days
Config.xml:
<?xml version="1.0" encoding="utf-8"?> <configuration> <settings> <plc id="LOGO1" type="Logo8" ip="192.168.1.25" /> <httpWebservice port="8088" /> <httpsWebservice port="8080" username="admin" passwordHash="c5b7932a4ad4734941370dd837cd2c1873c9a596" hashSalt="1d5sd131" /><!-- generate your SHA1 password hash here: http://www.sha1generator.de --> <valueTextConverter></valueTextConverter> </settings> <infrastructure> <group name="Switches"> <!-- Switches --> <device id="1" name="Music" type="light"> <!-- Stopcontact Muziek --> <attribute id="1" name="Status" plc="LOGO1" address="2.0"></attribute> <method id="1" name="off" plc="LOGO1" address="0.0" /> <method id="2" name="on" plc="LOGO1" address="1.0" /> </device> <device id="2" name="Lights" type="light"> <!-- Lichten --> <attribute id="1" name="Status" plc="LOGO1" address="2.1"></attribute> <method id="1" name="off" plc="LOGO1" address="0.1" /> <method id="2" name="on" plc="LOGO1" address="1.1" /> </device> <device id="3" name="Gang" type="light"> <!-- Lichten Gang --> <attribute id="1" name="Status" plc="LOGO1" address="2.2"></attribute> <method id="1" name="off" plc="LOGO1" address="0.2" /> <method id="2" name="on" plc="LOGO1" address="1.2" /> </device> <device id="4" name="Lock Timer" type="light"> <!-- Lock Timer --> <attribute id="1" name="Status" plc="LOGO1" address="2.3"></attribute> <method id="1" name="off" plc="LOGO1" address="0.3" /> <method id="2" name="on" plc="LOGO1" address="1.3" /> </device> <device id="5" name="Deur" type="light"> <!-- Deur --> <attribute id="1" name="Status" plc="LOGO1" address="2.4"></attribute> <method id="1" name="off" plc="LOGO1" address="0.4" /> <method id="2" name="on" plc="LOGO1" address="1.4" /> </device> <device id="6" name="Leds" type="light"> <!-- Leds --> <attribute id="1" name="Status" plc="LOGO1" address="2.5"></attribute> <method id="1" name="off" plc="LOGO1" address="0.5" /> <method id="2" name="on" plc="LOGO1" address="1.5" /> </device> <device id="7" name="SensorCheck" type="light"> <!-- SensorCheck --> <attribute id="1" name="Status" plc="LOGO1" address="2.6"></attribute> <method id="1" name="off" plc="LOGO1" address="0.6" /> <method id="2" name="on" plc="LOGO1" address="1.6" /> </device> <device id="8" name="Indicate Lights" type="light"> <!-- Indicatie lichten --> <attribute id="1" name="Status" plc="LOGO1" address="2.7"></attribute> <method id="1" name="off" plc="LOGO1" address="0.7" /> <method id="2" name="on" plc="LOGO1" address="1.7" /> </device> <!-- END Switches --> </group> </infrastructure> </configuration>
homebrdige config.json
{ "bridge": { "name": "Studio", "username": "CC:22:3D:E3:CE:35", "port": 51826, "pin": "028-05-688" }, "description": "Domotica", "accessories": [ { "accessory": "MagicHome", "name": "LEDs", "ip": "192.168.1.57", "setup": "RGBWW", "purewhite": false, "switchHandling": "realtime", "http_method": "GET", "on_url": "http://localhost:8088/rest/devices/6/methods/2", "off_url": "http://localhost:8088/rest/devices/6/methods/1", "status_url": "http://localhost:8088/rest/devices/6/attributes/1/value" }, { "accessory": "Http", "name": "Audio", "switchHandling": "realtime", "http_method": "GET", "on_url": "http://localhost:8088/rest/devices/1/methods/2", "off_url": "http://localhost:8088/rest/devices/1/methods/1", "status_url": "http://localhost:8088/rest/devices/1/attributes/1/value", "service": "Outlet" }, { "accessory": "Http", "name": "Licht", "switchHandling": "realtime", "http_method": "GET", "on_url": "http://localhost:8088/rest/devices/2/methods/2", "off_url": "http://localhost:8088/rest/devices/2/methods/1", "status_url": "http://localhost:8088/rest/devices/2/attributes/1/value", "service": "Light" }, { "accessory": "Http", "name": "Gang", "switchHandling": "realtime", "http_method": "GET", "on_url": "http://localhost:8088/rest/devices/3/methods/2", "off_url": "http://localhost:8088/rest/devices/3/methods/1", "status_url": "http://localhost:8088/rest/devices/3/attributes/1/value", "service": "Light" }, { "accessory": "Http", "name": "Deur", "switchHandling": "realtime", "http_method": "GET", "on_url": "http://localhost:8088/rest/devices/5/methods/2", "off_url": "http://localhost:8088/rest/devices/5/methods/1", "status_url": "http://localhost:8088/rest/devices/5/attributes/1/value", "service": "LockMechanism" }, { "accessory": "Http", "name": "AlarmNotify", "switchHandling": "realtime", "http_method": "GET", "on_url": "http://localhost:8088/rest/devices/7/methods/2", "off_url": "http://localhost:8088/rest/devices/7/methods/1", "status_url": "http://localhost:8088/rest/devices/7/attributes/1/value", "service": "Switch" },{ "accessory": "Http", "name": "IndicateLights", "switchHandling": "realtime", "http_method": "GET", "on_url": "http://localhost:8088/rest/devices/8/methods/2", "off_url": "http://localhost:8088/rest/devices/8/methods/1", "status_url": "http://localhost:8088/rest/devices/8/attributes/1/value", "service": "Switch" },{ "accessory": "Http", "name": "DeurTimer", "switchHandling": "realtime", "http_method": "GET", "on_url": "http://localhost:8088/rest/devices/4/methods/2", "off_url": "http://localhost:8088/rest/devices/4/methods/1", "status_url": "http://localhost:8088/rest/devices/4/attributes/1/value", "service": "Switch" }], "platforms": [] }
Thnx for the answear man! 😀
25. Juli 2017 um 8:36 #3499jphermans
TeilnehmerHave you installed the homebridge on the same server as logocontrol?
If yes maybe this could be causes the error. I am setting up a server now for homebridge and will test this.
I’l come back later to this topic. (tot later)25. Juli 2017 um 10:33 #3500DuBMicX
TeilnehmerYes! & i did it on a seperated raspberry pi but it was really slow then till homebridge reacted and thank you, tot dan 🙂
25. Juli 2017 um 11:11 #3501jphermans
TeilnehmerWhat version did you use for node? I get always a error and when I look at your json file I see that Logocontrol and homebridge are running on the same pi. Is that correct? Maybe that causes the crashes sometimes. Did you also load a plugin for logocontrol?
25. Juli 2017 um 11:14 #3502DuBMicX
TeilnehmerI’m running node v4.0.0 & yes thats correct & yes i have a self modified plugin i can send it to you if you want
25. Juli 2017 um 11:18 #3503jphermans
TeilnehmerI am running a second Linux server for the homebridge but I get errors. Will try it again with node v4.0.0 and with the plugin of you.
Send it to jphermansatgmailcom.
Then I will continue to look further.
Thanks.25. Juli 2017 um 12:00 #3504DuBMicX
TeilnehmerCheck you inbox 🙂
25. Juli 2017 um 12:02 #3505jphermans
TeilnehmerReceived, will look at it and will come back later.
25. Juli 2017 um 12:04 #3506DuBMicX
Teilnehmerthank you!!
-
AutorBeiträge
- Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.