Breakdown?
-
I've been fiddling with the zigate plugin, as the dongle arrived.. I installed the app from appstore, and saw that the plugin files were not installed properly.
Downloaded the zip files and put all luup files in the cmh_ludl folder. Reloaded luup, and it was in and looking ok
I then entered the IP for it to communicate with the dongle, and reloaded luup.Now the openluup service is running, but i can't get into either altUI or openluup console.
I tried rebooting, stopping and starting the service, no effect.
the logs doesnt seem to be updated either. Now what?
-
Logs updated after the last forced restart. this is all there is, no updates after this.
xxx@xxxxxxxx:/etc/cmh-ludl/logs$ tail -f LuaUPnP_startup.log 2020-12-03 19:39:12.842 openLuup.userdata:: [8956] AutoVirtualThermostat (0.stable) 2020-12-03 19:39:12.842 openLuup.userdata:: [9281] Virtual HTTP Devices (1.0) 2020-12-03 19:39:12.842 openLuup.userdata:: [9194] Switchboard (1.8) 2020-12-03 19:39:12.842 openLuup.userdata:: [ZiGate] ZiGate Gateway (1.0) 2020-12-03 19:39:12.842 openLuup.userdata:: [VeraTelegram] Telegram Plug-in (GitHub.master) 2020-12-03 19:39:12.842 openLuup.userdata:: ...user_data loading completed 2020-12-03 19:39:12.842 openLuup.init:: running _openLuup_STARTUP_ 2020-12-03 19:39:12.842 luup_log:0: startup code completed 2020-12-03 19:39:12.842 openLuup.init:: init phase completed 2020-12-03 19:39:12.842 :: openLuup LOG ROTATION :: (runtime 0.0 days) ^[[A^[[A^C xxx@xxxxxxxx:/etc/cmh-ludl/logs$ tail -f LuaUPnP.log 2020-12-03 19:39:13.566 luup.watch_callback:: 758.urn:upnp-org:serviceId:HVAC_UserOperatingMode1.ModeStatus called [758]avtWatchCallback() function: 0x5605f7b1c1b0 2020-12-03 19:39:13.566 luup.variable_set:: 758.urn:toggledbits-com:serviceId:AutoVirtualThermostat1.DisplayStatus was: Off now: Off #hooks:0 2020-12-03 19:39:13.566 openLuup.io.server:: HTTP:3480 connection from 127.0.0.1 tcp{client}: 0x5605f87c1ff8 2020-12-03 19:39:13.595 luup.variable_set:: 196.urn:upnp-org:serviceId:altui1.DisplayLine2 was: 2.70.50.111 now: 2.70.50.111 [Home] #hooks:0 2020-12-03 19:39:13.595 luup.variable_set:: 1.urn:micasaverde-com:serviceId:HaDevice1.Configured was: EMPTY now: 0 #hooks:0 2020-12-03 19:39:13.595 luup.variable_set:: 10002.urn:micasaverde-com:serviceId:HaDevice1.Configured was: EMPTY now: 0 #hooks:0 2020-12-03 19:39:13.595 luup.variable_set:: 10006.urn:micasaverde-com:serviceId:HaDevice1.Configured was: EMPTY now: 0 #hooks:0 2020-12-03 19:39:13.595 luup.variable_set:: 10304.urn:micasaverde-com:serviceId:SecuritySensor1.ArmedTripped was: EMPTY now: 0 #hooks:0 2020-12-03 19:39:13.595 luup.variable_set:: 10306.urn:micasaverde-com:serviceId:HaDevice1.Configured was: EMPTY now: 0 #hooks:0 2020-12-03 19:39:13.596 luup.io.incoming:: bytes received: 1, status: OK tcp{client}: 0x5605f7fb9758
-
-
@akbooer, this kind of breakdown was a bit difficult to figure out, would it be possible to make openluup detect such an issue or give som clue to whats happening in some log?
It seemed to go into some kind of loop causing it to not respond to anything.. I can see if i can reproduce it in zerobrane, should be just to set port 3480 on some ser2net based plugin.. -
Its was 120.0.0.1:3480, and i assumed that the this collided with Openluup somehow, and was left unhandled?
In any case whis came in the way of openluup initiation, when I came back a few hours later, a message said that openluup couldn't set up webserver, as 3480 was busy.. (this is what made me check user_data.json, and find that i had entered the wrong port number)If thats the case, that eventuality could perhaps throw an error message, and stop the init process?
Say you have some other application running that is using 3480 when you start openluup, my guess is that this would happen in that case too?
-
If port 3480 is in use, on the IP that openLuup is running on, then it will not start, by default. You can, in fact, run openLuup on a different port, and I often do in testing, so that I can run multiple copies on the same machine. It's not for general use, though, since so many plugins have hard-coded the 3480 port, which is what Vera uses.