Heming, Is flowvisor run by the flowvisor user? The binary assumes that there is a flowvisor user, and that flowvisor is run as such.
Cheers. -- Ali On May 29, 2012, at 2:26 PM, Heming Wen wrote: > Hi Ali, > > Thank you for the clarification about the db vs. json config change. Now with > dumpConfig. So that problem is fixed. > > As for the root/sudo requirements, it seems to be a Java-related error with > the database. It pretty much says that as a standard user I only have > read-only permission to the database. Of course it goes away if I sudo or am > the root itself. A simple apt-get remove and install wasn't enough to fix > that problem but I can live with it for now. I have the impression, as you > suggested, that if I remove it completely and reinstall, it will work as > intended. > > Thank you for your swift reply, > Heming > ________________________________________ > From: Ali Al-Shabibi [ali.al-shab...@stanford.edu] > Sent: May 29, 2012 15:04 > To: Heming Wen > Cc: openflow-discuss@lists.stanford.edu > Subject: Re: New Flowvisor JSON configuration file not writing > >> Hi Ali, > > Hi Heming, > >> >> I was using the binary for Flowvisor on 32-bit Ubuntu 10.04. It used to work >> fine. With the recent automatic update to the new version, it is no longer >> working the same as before. First of all, it seems I cannot run flowvisor >> nor fvconfig generate unless I am under sudo/root, which doesn't seem to be >> the case before the upgrade. Then, I cannot get the JSON configuration file >> to actually save the modification I made through fvctl. > > So, as is mentioning in the upgrade documents (both UPGRADING and > https://openflow.stanford.edu/display/DOCS/Installation+Guide), the > configuration is no longer saved at every update you perform. But, the > contents of the db are updated and you do not need to pass the config file as > a parameter to flowvisor anymore. If you do choose to pass the config file as > a parameter the db contents will be overwritten with the config in the config > file. It is recommended to use fvctl dumpConfig <configfile> to dump your > config file while flowvisor is running. > >> >> >> Do you know if this is caused by a broken update? Should I reinstall >> flowvisor from the source? When flowvisor was using xml, I didn't have this >> problem. Only after the transition to JSON through the automatic binary >> update this behavior started happening. > > If you are upgrading by binary, I would recommend you remove flowvisor > completely from your system before installing the new version. The transition > to JSON modifies quite a few things in the flowvisor install tree, so it > would probably be easier to start from scratch. > > Let me know how it goes. > >> >> Thanks! >> >> Heming > _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
