v4 displays no data. install and validation seemed to go OK...

[lakester]

Installed on DD-WRT 41586 on a Linksys WRT1900ACS.
Installed on /tmp/mnt/sda1..., since that's where dd-wrt REALLY wants to mount the USB drive.
Installation and validation appeared to go OK. Turned off SFE per installation instructions.
Have re-booted many times since.
The client side of the app seems to work OK..., but it appears that the cron job(s) are failing to collect data.

ls /tmp/yamon shows the following:

-rw-r--r-- 1 root root 114 Aug 9 11:53 hourly_2020-08-09.js
-rw-r--r-- 1 root root 89 Aug 9 11:53 lastseen.js
-rw-r--r-- 1 root root 317 Aug 9 11:53 mac-ip.txt
-rw-r--r-- 1 root root 0 Aug 9 11:53 raw-traffic-2020-08-09-11.txt
-rw-r--r-- 1 root root 7556 Aug 9 11:53 validation.log
-rw-r--r-- 1 root root 22848 Aug 9 11:53 yamon.log

It is Aug 11th..., so it appears that no files have been touched since installation. I've tried doing a chmod 666 on all of them..., we shall see. Since it appears that everything runs as root..., it probably won't matter.

Interestingly..., when I go to the DD-WRT(Administration->Management) page, I see that cron is enabled..., but nothing shows up in the cron job text box. I don't know if it should or shouldn't in the case of yamon..., just mentioning it.

I've gone ahead and pasted the contents of /tmp/cron.d/yamon_jobs into the text box, hit "Save" and "Apply Settings" to see if that has any effect. It appears that the "cron_jobs" file was created. Will report back in a couple of hours if things start working or not.

[lakester]

Waited until past the top of the hour..., and it appears that no cron jobs were fired off.

[lakester]

So..., tested cron. Simply isn't working. Have posted on dd-wrt forums to see if there are any answers..., but for now, it looks like YaMon v4 on DD-WRT build 41586 (WRT1900ACS) is gonna be dead in the water.

[abhijitat]

Try updating the DDWRT build to latest (currently 44627) build. some DD wrt build around 41586 had issues with cron, though the service was running, it was not running cron jobs, the change was in corntab folder. current build runs fine.