flowvisor crashes with "'Statement' already closed." warning

[chaos-bbn]

Our flowvisor-0.8.17 instance shut down under normal utilization. The only unusual syslog messages were:

Mar 17 15:03:02 tulum -1>Mar 17 15:03:02 flowvisor: WARN none : 'Statement' already closed. "
Mar 17 15:03:02 tulum -1>Mar 17 15:03:02 flowvisor: INFO none : Shutting down config database. "

[jbsbbn]

Did Chaos say that this was fixed? For GENI purposes, I think we'd just as soon not have a 0.8.18, and have the next upgrade we ask folks to do be to 1.0. Is it fixed in both?

[alshabib]

It's fixed but has not pushed to the repo. I should be able to push this regardless of what version you use though. Would that be ok for you?

Ali Al-Shabibi (sent from handheld)

On 19 mars 2013, at 08:34, Josh Smift [email protected] wrote:

Did Chaos say that this was fixed? For GENI purposes, I think we'd just as soon not have a 0.8.18, and have the next upgrade we ask folks to do be to 1.0. Is it fixed in both?

— Reply to this email directly or view it on GitHubhttps://github.com/OPENNETWORKINGLAB/flowvisor/issues/184#issuecomment-15121560 .

[jbsbbn]

Sure, I think it's fine to push it into the repo. Mostly I'm just trying to avoid any more 0.8.x releases, since I think only GENI cares about 0.8 any more, and I think we don't want anyone to upgrade beyond 0.8.17. Put pushing it into the repo, and building a new 1.0.x build, sounds good.