Looks like max.project.cpus global config is missing in your cloud.config DB table. It either comes with fresh 4.1 install, or gets inserted as a part of 4.0-4.1 DB upgrade by "schema-40to410.sql" .
I'm not sure how the code handles intermediate DB upgrades within the same branch (4.1 in your case); and if it does at all. You might double check schema-40to410.sql and see what else is missing in your setup. -Alena. On 4/22/13 5:03 PM, "Nikita Gubenko" <[email protected]> wrote: >It was 4.1 originally, but I've upgraded it several times to fresh 4.1 >snapshot > > >On Tue, Apr 23, 2013 at 4:02 AM, Alena Prokharchyk < >[email protected]> wrote: > >> Nikita, is it a freshly installed 4.1, or the upgraded version? >> >> On 4/22/13 4:59 PM, "Nikita Gubenko" <[email protected]> wrote: >> >> >Hi >> >Im using 4.1 snapshot build and can't change max.project.cpus >> >2013-04-23 03:58:00,707 ERROR >> >[cloud.configuration.ConfigurationManagerImpl] (catalina-exec-18:null) >> >Missing configuration variable max.project.cpus in configuration table >> >2013-04-23 03:58:00,707 ERROR >> >[cloud.configuration.ConfigurationManagerImpl] (catalina-exec-18:null) >> >Invalid configuration option, name: max.project.cpus, value:100 >> >2013-04-23 03:58:00,713 INFO [cloud.api.ApiServer] >> >(catalina-exec-18:null) >> >Invalid configuration variable. >> > >> >Is it a bug? >> >Thanks >> > >> >-- >> >Best Regards, Nikita Gubenko >> > >> >> >> > > >-- >Best Regards, Nikita Gubenko >
