[openwisp] Logread is not working after Configuration status becomes 'error'

2017-11-08 Thread Ramesh K
Hi, My configuration got status as 'error', when i ssh to my device and to trace log it shows Log not found. root@(none):~# logread Failed to find log object: Not found Failed to find log object: Not found Failed to find log object: Not found Failed to find log object: Not found Failed to

Re: [openwisp] Re: Introduction

2017-11-08 Thread Federico Capoano
Hi Aarnav, I would schedule it for 4:30 am. Take a look at this file to understand how to implement it: https://github.com/openwisp/ansible-openwisp2/blob/master/tasks/cron.yml Thanks for your contribution! Federico On Wed, Nov 8, 2017 at 11:48 AM Aarnav Bos wrote: >

[openwisp] Re: Introduction

2017-11-08 Thread Aarnav Bos
Hey, so I took a look at this issue: https://github.com/openwisp/ansible-openwisp2/issues/24 . And I implemented the solution on my VPS. Is there a specific time the cronjob needs to run? Do I submit a PR? On Wednesday, October 25, 2017 at 4:59:13 AM UTC-4, Aarnav Bos wrote: > > I'll take a