Re: update install

On Mon, Mar 3, 2014 at 9:59 AM, Courtney, Wrolf <[email protected]> wrote:
> Sure did. I could not edit my provisioning requisitions. This was for my test box, so I eventually did a clean reinstall of OpenNMS, edited in my local changes again, and voila. I had only just installed 1.12.3, so installing 1.12.5 was not as tragic for me as it sounds. I did not want to take up bandwidth on opennms-install trying to debug it when a simple reinstall would get the job done.

What does 'could not edit' mean?  And is your provisioning requisition
large?  A setting for 'org.eclipse.jetty.server.Request.maxFormKeys'
was added to opennms.properties at some point.  If you kept your old
file instead of merging your changes (I usually use meld for this),
you might not have picked it up, but the new install would have had
it.

-- 
   Les Mikesell
     [email protected]

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-install mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-install