check your settings in the global parameters for: network.lock.timeout Lock wait timeout (seconds) while implementing network
On Fri, Jun 14, 2019 at 1:07 PM Dmitry Berezhnoy <d.berezh...@emzior.ru> wrote: > Somebody else can help? We also increased network.lock.timeout but it was > useless. > > ср, 12 июн. 2019 г. в 00:40, Andrija Panic <andrija.pa...@gmail.com>: > > > Based on the " > > > > > https://github.com/apache/cloudstack/blob/1d05fead49f5c856257a741b07122f5633d2e359/framework/db/src/main/java/com/cloud/utils/db/Merovingian2.java#L121:L154 > > " > > I'm not quite sure it's a configurable thing. I don't see any parameter > > with that value or i.e. half of that... > > > > Perhaps someone else can advice > > > > > > On Mon, 10 Jun 2019 at 22:16, Dmitry Berezhnoy <d.berezh...@emzior.ru> > > wrote: > > > > > Yep, we use CloudStack as testing platform for our product and we want > to > > > create VMs and networks ASAP via scripts, so we don't see any > restriction > > > for that from physical platform or hypervisor, why CloudStack can't do > > > that? We want just find and increase 300 seconds parameters from this > > > message "Timed out on acquiring lock account2 . Waited for > 300seconds", > > > can you help us with it? > > > > > > пн, 10 июн. 2019 г. в 21:59, Andrija Panic <andrija.pa...@gmail.com>: > > > > > > > In mgmt log you have 904 createNetwork API calls !!! > > > > Don't you think it's a bit too much ??? > > > > > > > > Check who is nailing your API, since your log looks really funny in > > that > > > > regards - either some automation or denial of service thing or > > something > > > > else (on client side) really wrong. > > > > > > > > Cheers > > > > > > > > On Mon, 10 Jun 2019 at 19:25, Dmitry Berezhnoy < > d.berezh...@emzior.ru> > > > > wrote: > > > > > > > > > Hi Andrija, > > > > > > > > > > https://yadi.sk/d/BNOQFeCN86szxw - agent.log > > > > > https://yadi.sk/d/5UdQ4RExJ-VfmA - management-server.log > > > > > It is fresh installation with using for some days. > > > > > > > > > > Dmitry > > > > > > > > > > пн, 10 июн. 2019 г. в 17:44, Andrija Panic < > andrija.pa...@gmail.com > > >: > > > > > > > > > > > Hi Dmitry, > > > > > > > > > > > > if not mistaken, this might have something to do with DB - can > you > > > > please > > > > > > post whole log, on pastebin or similar ? > > > > > > > > > > > > Is this a fresh installation (test) or a running production for > > some > > > > > time ? > > > > > > > > > > > > Andrija > > > > > > > > > > > > On Mon, 10 Jun 2019 at 14:55, Dmitry Berezhnoy < > > > d.berezh...@emzior.ru> > > > > > > wrote: > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > Just tried cloudstack 4.11.2 and got the error due to create > > > network. > > > > > In > > > > > > > cloudstack logs we got the message: "Timed out on acquiring > lock > > > > > account2 > > > > > > > . Waited for 300seconds" (please read the attachment for more > > > > > details). > > > > > > > Which parameter defines this 300 seconds, where we can increase > > it? > > > > Any > > > > > > > ideas? > > > > > > > > > > > > > > Thanks in advance for the help, > > > > > > > Dmitry. > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Andrija Panić > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Andrija Panić > > > > > > > > > > > > > -- > > > > Andrija Panić > > >
