Posted: Sat Aug 08, 2020 5:46 Post subject: symlinks
According to the Help section of the YAMon website, it says that the symlinks should be in tmp/www/ directory. Not sure if OpenWRT and DD-WRT works the same way, but since we are using DD-WRT firmware and having the symlinks in tmp/www/ directory actually makes the program work correctly in my case. After running the start.sh command I have not rebooted my router so everything has been okay so far.
So, the code you put up, "/etc/init.d/yamon4 enable" Should I run this code with Putty if the symlinks are not present? Or should I add that code to the Commands sections in the DD-WRT interface and save to run at startup?
Joined: 06 Feb 2020 Posts: 167 Location: Maharashtra, India
Posted: Thu Sep 24, 2020 15:32 Post subject:
Appologies for asking but, will work on YAMon be started in near future i.e. year 2020. I had many issues using 4.0.7, eagerly waiting for update. mainly device list and colours not being saved. TOtals for the day going in TB's. Unknown device continuously being shown. hidden devices appearing in list etc.
not enforcing or hurting anybody's sentiments here, just a innocent question.
Posted: Sat Oct 03, 2020 18:12 Post subject: Thanks and rookie question
Many thanks to Al and all those who have contributed to this thread. I have been using DD-WRT but am new to YAMon.
My install of YAMon4 on an R7000 (build 43324) was successful on the first shot thanks to all of your contributions.
I have read all of the replies to this topic and have reviewed a subset of the scripting but am not sure how to stop YAMon4 so I can safely edit users.js.
I can see the routine for StopScheduledJobs() in /opt/YAMon4/Includes/start-stop.sh but am not sure how to invoke that routine.
Posted: Wed Oct 07, 2020 12:03 Post subject: Re: Startup Command for DD-WRT
anchit02 wrote:
The startup code that works, and runs "start.sh" after the router reboot is:
Code:
sh /opt/YAMon4/start.sh &
The above code is courtesy of msantos2007
This works for a TP-Link WDR3600 v1 with firmware r34929M
Just to confirm:
1. Is this to resolve the issue of YAMon4 stopping each day and causing hourly/daily data file gaps if not restarted?
2. Did you put this in your startup commands in the GUI instead of the default placed there by YAMon4?
My issue that I'm trying to resolve is that it seems like YAMon4 stops running every day overnight and I wake up to hourly data gaps.
Joined: 04 Oct 2020 Posts: 12 Location: 127.0.0.1, Virginia, USA
Posted: Wed Nov 11, 2020 20:14 Post subject:
Had YAMon working for a couple of days and then it started to not gather data. I purged the YAMon folder and reinstalled YAMon4 entirely after running the clear-iptables.sh.
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? _________________ cyberdeath
GameSurge IRC Operator
If any of you are still fighting quirks in V4 there is the option to use 3.4.7 until Al finds his way back here and fixes them.
With the exception of oddities in users.js editing 3.4.7 has been very stable for months now. I use a 256GB type C USB SSD to avoid stick issues.
Link in my Sig. _________________ 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
Last edited by ddaniel51 on Sat Nov 14, 2020 3:19; edited 1 time in total
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.
Thank you for your reply. I installed 3.4.7 and it seems to be doing better!
Question: I see you mentioned 3.4.7 and 3.4.8, what are the differences? I didn't see a changelog.
_________________ 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
Hey folks, I was also getting the same error:
"Saving your updated settings to the database failed with error message: error: ?!?"
I tried a lot of things to try and fix this. Including reinstalling the entire dang thing from scratch.
However, the thing that actually seemed to work is restarting my computer!! I'm not sure why exactly that worked. Perhaps, there's some temporary system file created that causes the issue?
Other steps that I also did:
- Disable the auto save feature in "Database integration"
- Delete cache for my browser
Not sure if those helped at all, but the issue didn't resolve until I restarted.
I'm also having problems with YAMon randomly deciding to stop collecting data a few hours after it's started. I'm not sure what could be causing it either as I've stared completely from scratch with it!
