[ixpmanager] MRTG graphs broken for one customer

[Tom Duff]

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

On Wed, Nov 7, 2018 at 12:55 PM Nick Hilliard (INEX) <nick at inex.ie> wrote:
>
> Hm, strange.  That sounds like a configuration problem then.
>
> Are the Physical Interface Settings for the customer ports set to "Connected" state, rather than e.g. Quarantine or Awaiting X-Connect?  Have you set the Customer Status on the customer overview page to be "Normal"?  Is the C
>
> It might be instructure to see what the API says.  If you log into IXP Manager, then open the following URL:
>
> https://your-ixp-m-url.com/api/v4/provisioner/layer2interfaces/switch-name/xxx-yyy.json
>
> ... where xxx-yyy is the "Switch Name" field in the switch configuration dialog, and https://your-ixp-m-url.com/ is the URL+URI of your IXP Manager installation (e.g. www.inex.ie/ixp/ in the case of INEX).
>
> This should output a json data structure containing all your customer port configs.  If the port of the customer in question isn't there, then it's a config problem.
>
> Nick
>
> Tom Duff 7 November 2018 at 01:05
> OK! So I did a little reading and found how to fix my artisan issue:
>
> sudo -u $MY_WWW_USER bash -c "HOME=${IXPROOT}/storage && cd
> ${IXPROOT} && php ./composer.phar install --no-dev"
>
> That being said, now that I'm running 4.8.0, that one customer's
> graphs are still broken, and generating the mrtg config yields the
> same result - the customer in question isn't being written into the
> mrtg config file. I'm back to square one. (But at least I'm up to
> date!)
>
> Any other ideas to get artisan to spit this config file out properly?
>
> Thanks as always,
>
> --Tom
> Tom Duff 7 November 2018 at 00:43
> Thanks Nick, I was on 4.7. I just attempted to update to 4.8, got all
> the way through the Upgrade Instructions page in the docs, and
> everything was fine until I got to the "Updating Composer
> Dependancies" section (after item #12, and after "Updating Bower
> Dependancies"). TBH it wasn't clear if I needed to do these steps or
> not. Unfortunately, artisan seems to be completely broken now, with a
> really nasty red error message that reads "In DuskServiceProvider.php
> line 43: It is unsafe to run Dusk in production.". Any artisan command
> spits that same error message. I'm not familiar enough with what I've
> done to try and fix it (was blindly pasting in the commands from the
> page), but I haven't done anything outside of what was on the page to
> try and fix it, I figured I'd check with the list first. Any
> suggestions?
>
> Thanks,
>
> --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
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager
> 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
>
>