No... it's pretty simple at this point. You'd need to check on it every so often. In the next release, I'm planning on making it do a check every 60 seconds or so to determine if rules need to be reapplied. And might possibly also build something into VPNMON-R3 that would be able to call on KILLMON to reapply its rules. I've not decided yet.
That would be great, when a new release comes out, I assume, need to uninstall current and install new release from AMTM.?No... it's pretty simple at this point. You'd need to check on it every so often. In the next release, I'm planning on making it do a check every 60 seconds or so to determine if rules need to be reapplied. And might possibly also build something into VPNMON-R3 that would be able to call on KILLMON to reapply its rules. I've not decided yet.
It would just over-install on top of it... easy-peasy.
It's hard to tell what's going on from the image you pasted... but try disabling Wireguard... perhaps it's getting out over that. Also, disable your VPN killswitch on the VPN client slot web UI side? Try to make this as clean as possible... remember, if you enable/disable/restart anything major, like firewall or other VPN/WG interfaces, it could possibly mess with the iptables, and bork your settings... which would require you to disable/re-enable the KILLMON killswitch settings.
Good morning, what would cause the timeout errors below.No... it's pretty simple at this point. You'd need to check on it every so often. In the next release, I'm planning on making it do a check every 60 seconds or so to determine if rules need to be reapplied. And might possibly also build something into VPNMON-R3 that would be able to call on KILLMON to reapply its rules. I've not decided yet.
Does it do this each time you run the script? Do you have a lack of resources available? Have you looked at the top/htop utility? Have you rebooted? You may need to uninstall/reinstall the "timeout" command?
What do you mean by "whenever I perform a command"? Can you give an example? Are you seeing any other kinds of errors in your syslog?
I forced a reinstall, rebooted the router, still receiving timeouts, but after mulitple timeout messages the command does complete
nothing in syslog
I've not seen that error in relation to timeout, but that's because I've never really used timeout for anything. The error message is generic (EAGAIN) and often means the system is overloaded in some way. That's usually too many running processes or there's a hardware issue causing IOs (or some other form of interrupt) to queue up. The timeout man page says:
EAGAIN Temporary error during kernel allocation of timer
structures.This type of error usually indicates that the process has reached the limit of some particular system resource as defined by the kernel limits (see "ulimit -a"). In the case of the "timeout" command, it could be that the maximum number of pending signals was reached at some point, or perhaps the maximum number of processes was reached.
[ -n "$(pidof timeout)" ] && cat "/proc/$(pidof timeout | awk -F ' ' '{print $1}')/limits"cat "/proc/$(pidof dnsmasq | awk -F ' ' '{print $1}')/limits"By itself I don't think
limits would provide the necessary information. It's unlikely the process is changing its maximum limits so they'll be the same as every other process.# cat /proc/1/limits
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 2097152 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 3647 3647 processes
Max open files 1024 4096 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 3647 3647 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited usstatus, in particular SigQ.# for pid in $(pidof timeout); do grep SigQ /proc/$pid/status; doneYes, good point. When I ran the command "ulimit -a" on my RT-AC86U, no entry for "pending signals" was found at all. I ran the same command in more recent AX-class models running F/W 388.6_2 versions and no "pending signals" entry was listed either, so the alternative to get all current limits was to execute a command like this one:
cat "/proc/$(pidof dnsmasq | awk -F ' ' '{print $1}')/limits"
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!