[ixpmanager] MRTG graphs broken for one customer

[Tom Duff]

I just pored through all the database tables trying to find any
differences between the trouble customer and all the other customers.
I came up with nothing.

So, I deleted the port completely from the bad customer record, and
made a brand new customer record, and added the same old port to the
new record. The graphs now generate. No idea why.

--Tom

On Sat, Nov 10, 2018 at 8:49 AM Tom Duff <tom.duff at gmail.com> wrote:
>
> The customer's physical port is set to Connected, and the switch is
> definitely set to active.
>
> --Tom
>
> On Thu, Nov 8, 2018 at 9:14 AM Barry O'Donovan <barry.odonovan at inex.ie> wrote:
> >
> >
> > Tom,
> >
> > We've added a missing graph troubleshooting section here:
> >
> > https://docs.ixpmanager.org/grapher/mrtg/#troubleshooting
> >
> > Does it help at all?
> >
> >   - Barry
> >
> > Tom Duff wrote on 08/11/2018 00:43:
> > > No worries, I just renamed the switch :)
> > >
> > > The port is "connected" and the customer is "Normal". Everything looks
> > > similar to the other customers when I compare them
> > >
> > > Now that the switch is renamed, the API call works, and I *do* see the
> > > customer port in question in that json output.  The MRTG conf file
> > > generator still doesn't have that customer's port in the output though
> > > :-\
> > >
> > > --Tom
> > >
> > >
> > > On Wed, Nov 7, 2018 at 3:31 PM Nick Hilliard <nick at inex.ie> wrote:
> > >>
> > >> oops, that's a bug - fix in commit #118ff19.  If you want to check out what the API says, feel free to manually patch this on your installation.  If you do this, you'll need to revert the patch the next time you upgrade ('git checkout routes/apiv4-auth-superuser.php').  Context diff available here:
> > >>
> > >> https://github.com/inex/IXP-Manager/commit/118ff19b75f94782977cf90a2c068dc0e28bb283.diff
> > >>
> > >>
> > >> Was this customer's port set up so that everything is enabled?
> > >>
> > >> Nick
> > >>
> > >> Tom Duff 7 November 2018 at 18:12
> > >> That provisioner API URL gives me a 404 error (when I add the correct
> > >> switch name, sw1.phl1 in there).
> > >>
> > >> Generating a RC config works, so the API seems to be ok (i.e
> > >> http://x.x.x.x/api/v4/router/gen-config/rc1-lan1-ipv6 works) - but it
> > >> doesnt seem to like the
> > >> "provisioner/layer2interfaces/switch-name/sw1.phl1.json" bit.
> > >>
> > >> This is on 4.8.0
> > >>
> > >> --Tom
> > >> Nick Hilliard 6 November 2018 at 08:27
> > >>
> > >>
> > >> If you're running v4.7, you should upgrade to v4.8.  There is a bug in 4.7 which causes this to happen.
> > >>
> > >> Nick
> > >> Tom Duff 6 November 2018 at 07:51
> > >> I've run into a head-scratcher here and I was wondering if anyone has
> > >> had this experience before - Every customer has graphs except for one.
> > >> For that one customer, the graphs show up as broken images. My MRTG
> > >> daemon is running and it works fine, but my problem appears to be with
> > >> how customer data is generated into the mrtg.cfg file. The missing
> > >> customer isn't being included when the config file is generated.
> > >>
> > >> I've checked that the customer's switchport is correct on the switch
> > >> page, that the correct physical port is allocated and the virtual
> > >> interface is correct. I checked that there was no "Date Left" on the
> > >> account record, and everything is set to "Active" or "Connected".
> > >> Everything is basically identical to every other customer (switch
> > >> config included).
> > >>
> > >> I've also tried deleting the customer's port configurations (phys and
> > >> virt) and re-adding them. Still no luck. I've toggled all sorts of
> > >> settings back and forth numerous times, but to no avail. I've
> > >> allocated them a brand new port that wasn't theirs, and still nothing.
> > >> Their customer record just seems to be skipped over when "php artisan
> > >> grapher:generate-configuration -B mrtg" is called.
> > >>
> > >> Has anyone seen this before? Any help would be appreciated. I've now
> > >> spent several hours trying to figure this out.
> > >>
> > >> --Tom
> > >> _______________________________________________
> > >> INEX IXP Manager mailing list
> > >> ixpmanager at inex.ie
> > >> Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager
> > >>
> > >>
> > > _______________________________________________
> > > INEX IXP Manager mailing list
> > > ixpmanager at inex.ie
> > > Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager
> > >
> >
> >
> > --
> >
> > Kind regards,
> > Barry O'Donovan
> > INEX Operations
> >
> > https://www.inex.ie/support/
> > +353 1 531 3339
> >
> >