Bug #3635
closed
Apinger does't start after upgrade to 2.1.3-RELEASE
0%
Description
After upgrading 3 routers to version 2.1.3 today, on one of the routers apinger can't be started.
It's the only x64 machine.
2.1.3-RELEASE (amd64)
built on Thu May 01 15:52:13 EDT 2014
FreeBSD 8.3-RELEASE-p16
Logs are of no help, this is the only thing in general log that I see.
May 3 14:10:54 php: /status_services.php: Removing static route for monitor 81.198.68.228 and adding a new route through 10.125.0.1
May 3 14:10:54 php: /status_services.php: Removing static route for monitor 81.198.68.229 and adding a new route through 172.17.2.2
If I understand correctly gateway failover is dependant on apinger for up/down and packet loss results, so it could get nasty...
I smell a bug in x64 version... :)
Updated by Chris Buechler almost 10 years ago
- Status changed from New to Feedback
- Target version deleted (
2.1.3)
not true that it doesn't work in general. try starting it manually, what output does it get?
Updated by Kirill Harkin almost 10 years ago
'manually' as in 'from console'?
If so, I can't find where is apinger service located.
This also didn't work:
service apinger start
apinger does not exist in /etc/rc.d or the local startup
directories (/usr/local/etc/rc.d)
Although, /var/etc/apinger.conf is present, so it must be somewhere...
By starting apinger without service output is:
apinger
[May 05 23:19:28] Couldn't read config ("/usr/local/etc/apinger.conf").
P.S. Can't find apinger in repository, so don't know how to reinstall.
http://files.pfsense.org/packages/8/All/
Updated by Chris Buechler almost 10 years ago
run: apinger -c /var/etc/apinger.conf
Updated by Kirill Harkin almost 10 years ago
[2.1.3-RELEASE][root@ic1.sohoset.com]/root(3): apinger -c /var/etc/apinger.conf
[2.1.3-RELEASE][root@ic1.sohoset.com]/root(4): apinger
[May 06 22:21:48] Couldn't read config ("/usr/local/etc/apinger.conf").
[2.1.3-RELEASE][root@ic1.sohoset.com]/root(5):
Updated by Kirill Harkin almost 10 years ago
20 days and noone has any fresh ideas on this... :(
Well on opening post I mentioned that it could get nasty. And guess what!? It did! :)
VoIP service didn't switch to Tier 2 when Tier 1 went down. :(
Anyway logical thinking an debugging was jumpstarted by "You're dead if it's not fixed".
Problem core: upgrade to 2.1.3 deleted WHEEL group from /etc/group (O_o) and without it apinger can't start
Problem solution: adding 'wheel:*:0:root' back to /etc/group
Just to be safe: linking configurations 'ln -s /var/etc/apinger.conf /usr/local/etc/apinger.conf'
Voilà! APINGER up and running.
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Rejected
there is no general bug here. Upgrades don't delete any groups, and of tens of thousands of systems that have upgraded to 2.1.3 and/or newer, haven't seen this elsewhere.