-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.2.2 possible runaway on openwrt r18xxx #11
Comments
Hello, From what I read, the user is using the script wrong. They're not supposed to use Login fail with status The fix for the first issue is implemented in the script as follows: it will try to logout the account first, and then try to login again. Sometimes we need to logout several times before it will successfully login again. And sometimes in the nth try, we get another error, which then trigger Regarding the |
ok, thankyou kopijahe very much for the input + feedback sorry to have 'jumped to conclusion' about your script (dnsmasq problems must be ujail related or something ~ not directly a runaway issue with the script) |
Hello, iam user in that question. it seems i misunderstood your parameter regarding -z switch. i just want to print output from the script (berhasil login atau tidak) to syslog message. Originally, i run the script with cron tab to manually execute in periodic time (with -z switch). Therefore, i thought it is just a matter moving the command from cron tab to rc.local. |
@zakeru46: just FYI, Also, Telkom is known to mess with In fact, I removed it from kopijahe 1.9.9. Maybe use OpenDNS or Quad9 IPs for connection tracking instead? |
hello
just reporting a possible runaway issue on openwrt master
(likely due to 2.2.2 (could be 2.2.1 also I suppose) but I could be wrong... could be a master thing from the last few months)
https://forum.openwrt.org/t/rpi4-community-build/69998/1973?u=wulfy23
basically, it seems like a condition occurs where your script enters a (fast) loop
not sure of it's 'bouncing' with mwan or something...
dnsmasq goes crazy and just reloads continuously...
feel free to close this if i'm wrong, as i'm not a user of your script it could be
user error... but I still think your script (or mwan?) can use a 'backoff'+log/better-detect
looping (if my findings are correct)
i'm not sure if 'noresolv' or dns problems are also causing / playing a part in this
The text was updated successfully, but these errors were encountered: