Error running report in VM

Thanks Craig, I'll try that.

The file is pretty large, I'll try a default cfg.
1 CPU is set.
RAM is currently 512, will try at 768mb.

If it still fails I'll try the vmware server and the OVF that you offer.

Where should I look for documentation for commands and using the app, such as you supplied above?
I'm a linux novice, using this as I had trouble trying to get the source running on windows.

Thanks.

Lighthouse <no-reply@lighthouseapp.com> writes:

There is a README file in the zip archive. It has the logins for the VM
and the app.

I have been testing with a config of about 5k lines. Is your config
significantly larger?

The VM you DLed should work in VMWare Server BTW. I believe it is only
ESX that wants, or works better with, the OVF version of the VM.

My config backup is 185kb (yeah, I know)

I haven't yet tried it in VMserver but will be doing so tomorrow.
Thanks for all your assistance so far.
I'll keep reporting back as it goes.

Pete.

Lighthouse <no-reply@lighthouseapp.com> writes:

Well, the one I test with is 254K

It takes awhile, but it runs.

Does the error happen quickly, or does it chug along for awhile before throwing it?

The page displays the processing bar on the bottom of the submission window and then throws the error.
About 20 seconds.

Within vmwareserver v2, I'm having trouble resetting the eth0 interface.
It's getting its IP from somewhere other than our dhcp.

when trying to change it via sudo, I have no success.
Is the flint\flint user an admin on this virtual appliance?

Never mind, got it sorted.
DHCP now working properly - vmware server issue with not having the right netwrk interface setting used. Now on bridged mode and working.

I still have the same error when running the report.
Have tried a 46kb file and it also fails.

I will have to try updating redis I think.

The device is a pix 525.
Is flint suitable for this?

When I strip out all the names and access rules, the config processes properly.
I'll go through it now and remove sections one by one to find the error and report back.

Lighthouse <no-reply@lighthouseapp.com> writes:

That is what we run here and test with our config frequently.

When you start the VM, leave the wmare console window up, and then in another
window, load your rules. You should see some output to your console. If
you can send me a stack trace I can trac this down.

Alternatively, our next release will handle alot of this error reporting
much better. We're getting ready to cut that release today hopefully.

Ok, I got a lead on this from another user who triggered it while running our devel version of Flint.

I think his bag had to do with the handling of a "static" command. However, you mentioned it was something in the names and access-list commands.

If you run upgrade to Flint 1.0.5, either by downloading the new VM, or by logging into your VM as flint/flint and doing:

cd flint
git pull
rake reset
rake install
rake app

Then when you get this error you should ge ta nice juicy stacktrace you can mail to me 8^)

Thanks Craig.
I'm back after the long weekend and will give it a whirl.

While waiting for the latest vm app to download, I tried your update procedure.
I've attached the backtrace results.

I'll carry on with the app download and try that version as well.

Craig, having successfully run the report after removing all "name " entries from the running-config, I think this is less a bug with Flint than it not able to properly process some of the descriptions we use.

While the ASDM software allows and properly returns the values in the description fields, we may be using reserved or unexpected charaters in our config that flint has trouble with.
I've tested for this by manually deleting all "description " entries that appear after the Names entires in the config.

It will be a task for me to a: track down exactly which one is errant, b: determine if Cisco have any documentation on whether any of these are considered reserved characters/words.

I think we can count this as resolved and would like to thank you for your help.
If you'd like any more feed back on what I find, please let me know.

Thanks.
Pete.

Don't try and track it down.

It's a parser error for handling of the name command. We barf on ALL descriptions, not just your weird ones, if they are weird.

Working on a fix now

Cool.

I realise it's a work in progress and might have been the case.
The "remark" lines in the ACL rules process just fine.

Ok, so I made some changed to the lexer and parser which should allow it to handle the description and remark options properly. You can get it by upgrading to the 1.0.6 release, using the same process I described above.

Let me know if that fixed your bug.

Can you please update the bug when 1.0.6 is released.

Just downloaded the current from your site and it's still 1.0.5
git pull also shows I have the latest version.

The link found here doesn't indicate which version is available.
http://runplaybook.com/p/11

Thanks.

1.0.6 is available now.