Now when I try to enable the database feature it creates an endless loop saying it was unable to write to the database and "error: ?!?"
I have tried requesting keys and inserting them into config.file but this issue persists. Any ideas on how I could troubleshoot?
I've also been having the issue with "error: ?!?", glad to hear I'm not alone. I've been trying to read all of the help documentation & threads trying to see if this was a common issue that already had trouble shooting steps or if I could figure out what may be happening.
I've been successfully using the database feature for months, but first noticed the error on Monday. I tried deleting my database key from config.file and requesting a new one and putting that into the config.file, but the error still persisted, so I reverted back to my old key. I'm not sure what the next steps to troubleshoot are.
The chrome developer console shows this as the error pops up:
Quote:
Access to XMLHttpRequest at 'http://usage-monitoring.com/db/svSettings.php' from origin 'http://10.0.0.1' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
I'm a bit over my head, but I'm planning on looking into what CORS policy is and see if I can figure out how that may be affecting this.
CORS is Cross Origin Resource Sharing. It's basically security on the server side to prevent unwanted parties from accessing resources on a server. It's not something you can modify from the user side. If I took a guess, they probably implemented CORS recently (knowingly or not) and may have whitelisted something common like "192.168.1.1" which might work for them but not others who are using a different IP for their router or a local hostname.
So I'm curious, is anyone who is experiencing this error, like me, have a router that is accessed by an address other than 192.168.1.1, or if those using 192.168.1.1 are also having error?
If YAMon needs help with this, please let me know.
I've been having the same error on a 2 year old installation running 3.x
Couldn't get rid of it so I upgraded to 4 migrating data. Same issue.
So I wiped the data and started fresh .... same issue.
So now a fresh install goes in loop since it seems it can't save the basic setup. So once the initial "welcome" setup is done, it restart ... forever ...
As a result I can't use Yamon at all anymore.
I'll try to reinstall 3.4.7 as pointed. Keep you posted.
Ok so when I included the key it started to fail again. The problem is then directly related to Yamon calling the mother base.
I know it sounds obvious but it could have been some local DB too.
Thing is I removed the key from the config.file and restarted but it didn't help.
I looked for the key using a wide grep command but could not find it anywhere. This is strange we can't roll back to no key ...
I'll reboot the router to see it that bring any change.
After change of the config.file to now contain the "_dbkey" anymore and a complete restart of Yamon 3.4.7 it is back working.
The issue remaining is that we can't use the db sync for cross devices anymore. But at least the tool is fully functional.
Few things I've learned:
- Yamon 4 must be trying to save things in the remote db systematically, which explain it failing all the time.
- On DD-WRT to restart Yamon the script (shutdown.sh) doesn't do the trick since the router still run httpd daemon. Once shutdown script have done it's job I usually kill the httpd daemon and then start the startup.sh script. Another option, more radical, would be to reboot the router.
- It doesn't seem there are other places where this dbkey is stored. Even in /tmp
I hope Yamon is still supported, I've sent an email now 2 or 3 weeks ago to the creator with still no news.
Right, using the Yamon with the remote db (dbkey) should work fine since it's not connecting to the Yamon hosted db server and just saving the data locally.
Also, it seems to me that Yamon doesn't connect to the db immediately, even after rerunning the start script. So initially it appears to "work" after configuring the db setting and restarting, but eventually it breaks when it can't connect.
I don't know if you mean you literally kill httpd, but if so that's not necessary. You can run
Code:
stopservice httpd
and then
Code:
startservice httpd
to restart the webserver.
If you just need to restart Yamon, I think running the start.sh script is sufficient. However, as mentioned above, I don't think it looks for that db change immediately.
I have not tried to contact him, but Al_C seems to be alive and well, but due to COVID has changed focus to the creation and maintenance of a chrome extension related to remote learning for schools. He's also a teacher at a school in Canada. There appears to be a Facebook group dedicated to that project, which you can find, and makes in interesting read. I'm figuring he'll be back when he has time, and won't respond until he does. Until then I'm just glad YaMon is still working
I got YAMon 4.0.6 up and running today on my fresh DD-WRT install on my Netgear R6400 router. Everything looks like it installed correctly, but I am also getting that database save failure message every time I load the report AND I'm not getting any data collection. It doesn't show any devices nor any usage. What can I check?
I got YAMon 4.0.6 up and running today on my fresh DD-WRT install on my Netgear R6400 router. Everything looks like it installed correctly, but I am also getting that database save failure message every time I load the report AND I'm not getting any data collection. It doesn't show any devices nor any usage. What can I check?
Remove the dbkey, reboot the router to clear the tables and give it 24 hours to stabilize and populate.
Since V4 operates from a set of Cron tasks it is not nearly as responsive as 3.4.7.
Personally, I went back to 3.4.7 and am happy with it despite a couple of its' quirks. _________________ Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php
I've been running Yamon v3 for a few years now, but keep getting niggly small problems, and this morning I appear to have lost all data.. So I was wondering if v4 is stable enough to start using?
I know development (and this thread) of either has more or less stopped, but as there isnt really an alternative out there I dont think I have much choice, if I want to view more detailed stats.
I cured my corruption and data problems when I switched from various USB sticks to a Type C USB SSD. It may seem a bit of overkill but the reliability has been worth it.
I split the ssd into 2 partitions labeled opt and jffs and haven't had any problems with them going on three years now. _________________ Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php
I installed 4.0.7 a couple of times, but nothing works.. No synlinks created, no crontab entries.. im going back to latest v3.. Then I'll try to repoint so that it picks up the old data.. It seems to be there, just not displaying..
Is this the end? Is there a way to host DB ourselves?
Remove the DB key in config.file and pretend it was never there. _________________ Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php
