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.

Reply via email to