Disk full? Are you monitoring the servers health? Might want to try rebooting the billing server, do a snapshot before though.
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Aug 5, 2015 12:45 AM, "That One Guy /sarcasm" <thatoneguyst...@gmail.com> wrote: > bandwidth gathering seems to be functional, probes are busted, about every > tenth click on reprobe gives me a green box, but it never populates the > probes. I rebooted the bmu when the mirror was still present and probes > worked during the resync, but failed again at some point, subsequent > reboots would not replicate the temporary functionality. > > I cannot find any devices, customer or infrastructure that are working, so > it seems the entire module is failing, not just hanging at some point in > the polling as best I can tell > > On Tue, Aug 4, 2015 at 11:35 PM, Josh Luthman <j...@imaginenetworksllc.com > > wrote: > >> So probes are what's busted? What about bandwidth collection? >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> On Aug 5, 2015 12:31 AM, "That One Guy /sarcasm" < >> thatoneguyst...@gmail.com> wrote: >> >>> anybody using powercode and your monitoring is dead? Hopefully its just >>> us and not systemic. Apparently they tested and they can kick probes off on >>> the back end, its just not logging. real time tools work, so its not a >>> communication issue, we didnt make any system changes near the failure. >>> The entire network monitoring component seems to be croaked. Ive removed >>> mirrors, minimized down to a single bmu, synchronized, restarted BMUs, >>> restarted the billing server, cussed and got drunk, nothing seems to work. >>> I cant say Im all that excited with responsiveness at bertram since the >>> coup so Im reaching out to the community hoping somebody has this happen >>> occasionally and its something like running some archaic linux command and >>> burning sage. >>> Our customer facing staff is bright as a brick when it comes to using >>> the statuses as it is and this is going to be a disaster, no matter how >>> much i try to show them. We have 3/4 technical staff tied up all day >>> tomorrow migrating an office domain so that coupled with the inevitable >>> hangover is going to make this situation salty >>> >>> -- >>> If you only see yourself as part of the team but you don't see your team >>> as part of yourself you have already failed as part of the team. >>> >> > > > -- > If you only see yourself as part of the team but you don't see your team > as part of yourself you have already failed as part of the team. >
