the1_ts
Members
-
Joined
-
Last visited
-
As its not been checked lately. Today I did this clean up method and its worked perfectly. rm /var/log/pwfail/YourIPaddress
-
I am running 7.12 and have an old user.script left over from when nchan would kill the UI regularly. It simply runs /etc/rc.d/rc.nginx restart I have found since the 7.12 update that the nginx inside my apprise container is being stopped at the same time the nginx restart script is run. I have looked at the rc.nginx script and its being caught as line 739 pkill -f $NGINX is not checking if it is an nginx from the host OS or a container. Only my apprise container runs a nginx by full path /usr/bin/nginx so is the only one being killed by this, all other container run nginx are being left intact as the path doesn't match. I think the PID of the still running /usr/bin/nginx processes should be checked to make sure that they don't have a cgroup associated (running in container) then killed or if possible use the namespace checking built in to pkill. But the cleanest way may be also to fix nginx_waitfor_shutdown to wait only for the OS nginx processes as that would speed up the rc file since container nginx will remain active always. Great that the nchan memory issue is fixed and I can remove that user.script for nginx restart. Many Thanks, Paul
-
I run a 2 pihole system, the dhcp issues can be worked around by having the static dhcp leases the same for both piholes (using whatever method you prefer), but dynamic ranges should not clash. Therefore anything with a static lease gets the same IP from either pihole and anything that is truly dynamic will get a lease from the unique range for the first to answer pihole. pihole1 = 192.168.0.41 - 192.168.0.140 pihole2 = 192.168.0.141 - 192.168.0.240 This appears simpler and safer than stopping/starting DHCP on keepalived failover. Admittedly I run 95% static but have not had issues with static dhcp leases or dynamic in 5+ years.
-
Any chance of adding MyRepos https://myrepos.branchable.com/ which is perl based along with vcsh http:// https://github.com/RichiH/vcsh which is just bash script. They are used to control Multiple Repositories (git, svn, mercurial) and to keep dotfiles in git repos and control keeping them updated on all your systems. Since mr is controlled by one file ~/.mrconfig, adding that in via the go script would be minimal recovery at restart times.
