Hi Vinh, currently openwisp2 is focused on configurations only (although we are going to add a few new modules soon thanks to the amazing work GSoC students are doing <https://summerofcode.withgoogle.com/organizations/5694014226432000/>), so that status attribute refers to the status of the configuration:
- *modified* means the configuration has not been applied to the device yet - *running *means the configuration has been applied successfully - *error *means the configuration has been applied but because of a misconfiguration has been rollbacked by openwisp-config Is it clear? A simple monitoring module is on our roadmap. With such a module we will be able to know the network status of our devices (if reachable or not, get an overview of dynamic information like DHCP addresses or other statisticsa nd so on). Federico On Friday, June 16, 2017 at 10:04:15 AM UTC+2, Nguyễn Vinh wrote: > > Hi Fed, > I have question for STATUS. > > > <https://lh3.googleusercontent.com/-xfkk_C5nbpo/WUOQrwHkFJI/AAAAAAAAAHE/fiZF8Z3lirYCPb41UKVpo1rIjeV8R-9EACLcBGAs/s1600/1.PNG> > STATUS is running althought i poweroff my device. > > On Tuesday, June 6, 2017 at 10:15:24 PM UTC+7, Federico Capoano wrote: >> >> Hi Wylis, >> >> did you solve your problem with the missing lua dependency? >> >> Federico >> >> >> On Friday, May 26, 2017 at 6:28:41 PM UTC+2, Federico Capoano wrote: >>> >>> Try this: >>> >>> opkg install luafilesystem >>> >>> Although it's strange it didn't get pulled in as a dependency. >>> >>> In general, users that decide to keep OpenWISP start compiling their own >>> images after a while, which is the best option if you intend to deploy many >>> devices. >>> >>> F. >>> >>> >>> On Fri, May 26, 2017 at 6:25 PM <[email protected]> wrote: >>> >>>> Yes, i do still have the anonymous version. Yes i did initially have a >>>> problem with the opkg install, but then i added the feed to my build and i >>>> no longer saw any issues. However, your autoname script is complaining >>>> about some lfs.lua things. So it seems i am still having a problem with >>>> luafilesystem. Fixing that is the next step in fixing this, so i'll >>>> concentrate on that. thanks! >>>> >>>> here is my session: >>>> >>>> root@OpenWrt:/tmp/openwisp# openwisp-uci-autoname >>>> lua: /usr/sbin/openwisp-uci-autoname:6: module 'lfs' not found: >>>> no field package.preload['lfs'] >>>> no file './lfs.lua' >>>> no file '/usr/share/lua/lfs.lua' >>>> no file '/usr/share/lua/lfs/init.lua' >>>> no file '/usr/lib/lua/lfs.lua' >>>> no file '/usr/lib/lua/lfs/init.lua' >>>> no file './lfs.so' >>>> no file '/usr/lib/lua/lfs.so' >>>> no file '/usr/lib/lua/loadall.so' >>>> stack traceback: >>>> [C]: in function 'require' >>>> /usr/sbin/openwisp-uci-autoname:6: in main chunk >>>> [C]: ? >>>> >>>> >>>> >>>> On Friday, May 26, 2017 at 7:59:00 AM UTC-4, Federico Capoano wrote: >>>> >>>>> You said you have: >>>>> >>>>> config system >>>>> option hostname OpenWrt >>>>> option timezone UTC >>>>> option ttylogin 0 >>>>> >>>>> Which is an anonymous configuration block, put by default by OpenWRT, >>>>> which unfortunately doesn't play well with remote management systems that >>>>> need to override specific (hence named) sections. >>>>> >>>>> That's why, according to this line: >>>>> >>>>> https://github.com/openwisp/openwisp-config/blob/master/openwisp-config/files/sbin/openwisp-uci-autoname.lua#L39 >>>>> >>>>> That section should be renamed as: >>>>> >>>>> config system *'system'* >>>>> option hostname OpenWrt >>>>> option timezone UTC >>>>> option ttylogin 0 >>>>> >>>>> Bold mine, denotes the name of the section. >>>>> >>>>> Without that name, it is not possible to automatically change that >>>>> configuration block, but only to add a new configuration block, which may >>>>> be discarded by UCI (the software which manages all these configuration >>>>> files). >>>>> >>>>> Do you still have the anonymous version? >>>>> >>>>> If yes, what happens if you run this command? >>>>> >>>>> openwisp-uci-autoname >>>>> >>>>> The expected result is to have the "system" config block renamed as >>>>> "system". >>>>> >>>>> I remember you were having problems installing openwisp-config, maybe >>>>> some dependencies (like lua) were not installed and something is not >>>>> working as expected. >>>>> >>>>> Federico >>>>> >>>>> >>>>> On Fri, May 26, 2017 at 1:46 PM <[email protected]> wrote: >>>>> >>>>>> the content of the tar.gz now has the new hostname. the tarball has >>>>>> etc/config/system in it. >>>>>> >>>>>> so again, i did restart and there is a pause on the "now applying >>>>>> it..." line, but /etc/config/system does not change. Is there some >>>>>> additional logging i can turn on? If not, i will add some to see what >>>>>> its >>>>>> doing. I do know that MERGE_CONFIG=1. >>>>>> >>>>>> thanks >>>>>> >>>>>> >>>>>> >>>>>> On Friday, May 26, 2017 at 3:06:25 AM UTC-4, Federico Capoano wrote: >>>>>> >>>>>>> To make it download again you can do: >>>>>>> >>>>>>> rm /tmp/openwisp/checksum >>>>>>> /etc/init.d/openwisp_config restart; logread -f >>>>>>> >>>>>>> What is the content of the tar.gz now? >>>>>>> >>>>>>> Federico >>>>>>> >>>>>>> Il ven 26 mag 2017, 02:51 <[email protected]> ha scritto: >>>>>>> >>>>>> Thanks for the things to check. Yes the UUID and key are correct. >>>>>>>> configuration.tar.gz does contain what is in the preview which I >>>>>>>> included >>>>>>>> before. However, maybe it was an old download? Previously i did get >>>>>>>> an >>>>>>>> error that it could not apply the configuration. Then it said it was >>>>>>>> successful, but no change was made. i moved the tarball to another >>>>>>>> name >>>>>>>> and i'm wondering if there is a way to make it download again? >>>>>>>> >>>>>>>> i stopped and started the openwisp_config, but its still not >>>>>>>> logging a download. >>>>>>>> >>>>>>>> I changed the hostname and it eventually did download. How long is >>>>>>>> the timer that its on checking for a new configuration? >>>>>>>> >>>>>>>> It downloaded a new tarball, but again did not apply it, even after >>>>>>>> logging "applied succesfully". Any ideas? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Thursday, May 25, 2017 at 10:32:12 AM UTC-4, Federico Capoano >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> HI wylis, >>>>>>>>> >>>>>>>>> it's very strange, I've never got such a report. >>>>>>>>> >>>>>>>>> It may seem obvious but could you ensure the device is registered >>>>>>>>> with the right UUID and key (check /etc/config/openwisp) and the >>>>>>>>> configuration you are editing in the controller is the right one? >>>>>>>>> >>>>>>>>> Could you take a look at what is in >>>>>>>>> /tmp/openwisp/configuration.tar.gz? >>>>>>>>> >>>>>>>>> Federico >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thursday, May 25, 2017 at 2:56:28 PM UTC+2, >>>>>>>>> [email protected] wrote: >>>>>>>>>> >>>>>>>>>> Hi, my device is showing up on the web page and the config is: >>>>>>>>>> >>>>>>>>>> package system >>>>>>>>>> >>>>>>>>>> config system 'system' >>>>>>>>>> option hostname 'OpenEdge' >>>>>>>>>> option timezone 'EST5EDT,M3.2.0,M11.1.0' >>>>>>>>>> option zonename 'America/New York' >>>>>>>>>> >>>>>>>>>> config timeserver 'ntp' >>>>>>>>>> list server '0.openwrt.pool.ntp.org' >>>>>>>>>> list server '1.openwrt.pool.ntp.org' >>>>>>>>>> list server '2.openwrt.pool.ntp.org' >>>>>>>>>> list server '3.openwrt.pool.ntp.org' >>>>>>>>>> option enable_server '0' >>>>>>>>>> option enabled '1' >>>>>>>>>> >>>>>>>>>> I saw these logs on the device: >>>>>>>>>> >>>>>>>>>> Thu May 25 12:50:21 2017 daemon.info openwisp: Local >>>>>>>>>> configuration outdated >>>>>>>>>> Thu May 25 12:50:21 2017 daemon.info openwisp: Downloading >>>>>>>>>> configuration from controller... >>>>>>>>>> Thu May 25 12:50:22 2017 daemon.info openwisp: Configuration >>>>>>>>>> downloaded, now applying it... >>>>>>>>>> Thu May 25 12:50:22 2017 daemon.info openwisp: Service openwisp >>>>>>>>>> has been reloaded via procd/ubus >>>>>>>>>> Thu May 25 12:50:22 2017 daemon.info openwisp: OpenWISP config >>>>>>>>>> agent received reload trigger >>>>>>>>>> Thu May 25 12:50:27 2017 daemon.info openwisp: Testing >>>>>>>>>> configuration... >>>>>>>>>> Thu May 25 12:50:27 2017 daemon.info openwisp: Configuration >>>>>>>>>> test succeded >>>>>>>>>> Thu May 25 12:50:28 2017 daemon.info openwisp: Configuration >>>>>>>>>> applied succesfully >>>>>>>>>> Thu May 25 12:50:28 2017 daemon.info openwisp: OpenWISP config >>>>>>>>>> agent started >>>>>>>>>> >>>>>>>>>> But the system settings are unchanged: >>>>>>>>>> >>>>>>>>>> root@OpenWrt:/etc/config# cat system >>>>>>>>>> config system >>>>>>>>>> option hostname OpenWrt >>>>>>>>>> option timezone UTC >>>>>>>>>> option ttylogin 0 >>>>>>>>>> >>>>>>>>>> config timeserver ntp >>>>>>>>>> list server 0.openwrt.pool.ntp.org >>>>>>>>>> list server 1.openwrt.pool.ntp.org >>>>>>>>>> list server 2.openwrt.pool.ntp.org >>>>>>>>>> list server 3.openwrt.pool.ntp.org >>>>>>>>>> option enabled 1 >>>>>>>>>> option enable_server 0 >>>>>>>>>> >>>>>>>>>> Why would this be? >>>>>>>>>> >>>>>>>>>> Thanks again! >>>>>>>>>> >>>>>>>>> -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
