Still not able to figure out this issue. Have checked all the logs etc. Are 
there some scripts openwisp-config downloads when it connects to the 
openwisp server? I might find some clues there. kernel logs still show up. 
But there are no more user/daemon logs

On Friday, 28 July 2017 22:23:33 UTC+5:30, Federico Capoano wrote:
>
> Usually not unless explicitly configured. In openwrt all these logging 
> operations are run in memory by default to avoid writing on the flash 
> continuosly.
>
> Federico
>
> Il ven 28 lug 2017, 18:29 Saurabh Chakrabarti <[email protected] 
> <javascript:>> ha scritto:
>
>> Apologies. I was unavailable for sometime. I'll check changing the 
>> network configuring once again. Is there any file all the logs go to? I 
>> could probably check that file too.
>>
>>
>> On Friday, 28 July 2017 17:30:08 UTC+5:30, Federico Capoano wrote:
>>
>>> I'm not sure what is causing this since openwisp-config doesn't mess 
>>> with logread, it just calls the logger function a few times. 
>>>
>>> Keep testing your network configurations to see what happens when you 
>>> change LAN, radio, wifi settings (run reload_config after you change these 
>>> configurations), do you see anything on logread?
>>>
>>> Federico
>>>
>> On Fri, Jul 28, 2017 at 1:43 PM Saurabh Chakrabarti <
>>> [email protected]> wrote:
>>>
>> Hi Federico,
>>>>
>>>> Please find responses inline.
>>>>
>>>> Is there anything else I can test?
>>>>
>>>> Regards,
>>>> Saurabh
>>>>
>>>> On Friday, 28 July 2017 16:55:43 UTC+5:30, Federico Capoano wrote:
>>>>>
>>>>> Hi Saurabh,
>>>>>
>>>>> the logs seem ok. How are you getting the log? Just *logread* or *logread 
>>>>> | grep openwisp*?
>>>>>
>>>> logread 
>>>>
>>>>>
>>>>> Is the openwisp_config process running?
>>>>>
>>>> yes. its running 
>>>>
>>>>>
>>>>> Have you noticed any other strange or unexpected behaviour?
>>>>>
>>>> Using this documentation 
>>>> https://wiki.openwrt.org/doc/howto/log.essentials  - I even tried doing
>>>> logger testLog "Blah1" 
>>>> But nothing came up on logread. It came up without openwisp-config
>>>>
>>>>>
>>>>> It's possible everything is working fine, but let me know the answers 
>>>>> to the previous questions so I will be able to tell you with more 
>>>>> confidence.
>>>>>
>>>>> Federico
>>>>>
>>>>>
>>>>>
>>>>> On Friday, July 28, 2017 at 12:57:44 PM UTC+2, Saurabh Chakrabarti 
>>>>> wrote:
>>>>>>
>>>>>> Hi ,
>>>>>>
>>>>>> I have installed openwisp-config and I'm able to register the device 
>>>>>> with the openwisp server(which i installed using ansible).
>>>>>>
>>>>>> But when I do a logread, I do not get any further logs(after openwisp 
>>>>>> registration)
>>>>>>
>>>>>> ..
>>>>>>
>>>>>> Fri Jul 28 07:08:03 2017 daemon.info openwisp: Testing 
>>>>>> configuration...
>>>>>> Fri Jul 28 07:08:05 2017 daemon.info openwisp: Configuration test 
>>>>>> succeded
>>>>>> Fri Jul 28 07:08:07 2017 daemon.info openwisp: Configuration applied 
>>>>>> succesfully
>>>>>> Fri Jul 28 07:08:08 2017 daemon.info openwisp: OpenWISP config agent 
>>>>>> started
>>>>>>
>>>>>> No logs after this.
>>>>>>
>>>>>> Is there anything that is stopping the logs from getting generated? 
>>>>>>
>>>>>> Kindly let me know
>>>>>>
>>>>>> Regards,
>>>>>> Saurabh
>>>>>>
>>>>> -- 
>>>> 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.
>>>>
>>> -- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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