Cool!
On Thu, 3 Oct 2019, 21:02 Fariborz Navidan, wrote:
> Thank you very much! Finally, I could start management server normally.
>
> Thanks.
>
> On Thu, Oct 3, 2019 at 9:26 PM Andrija Panic
> wrote:
>
> > It seems easier than I thought...
> >
> > stop mgmt server
> > Rollback DB with your sta
Thank you very much! Finally, I could start management server normally.
Thanks.
On Thu, Oct 3, 2019 at 9:26 PM Andrija Panic
wrote:
> It seems easier than I thought...
>
> stop mgmt server
> Rollback DB with your statement shared in some of the previous emails (and
> after that please make DB b
It seems easier than I thought...
stop mgmt server
Rollback DB with your statement shared in some of the previous emails (and
after that please make DB backup immediately, just for the sake of having
one...)
Again, perform that manual template install with:
- From mgmt, mount the Secondary Stor
MariaDB [cloud]> select max(id) from vm_template;
+-+
| max(id) |
+-+
| 390 |
+-+
Can we have a chat session to investigate together?
On Thu, Oct 3, 2019 at 8:27 PM Andrija Panic
wrote:
> do for me:
>
> select max(id) from vm_template:
>
> i might need more info late
do for me:
select max(id) from vm_template:
i might need more info later...
On Thu, 3 Oct 2019 at 18:25, Andrija Panic wrote:
> Can you share logs during this last attempt?
>
> I'll try to craft some SQL additions for your vm_template and
> template_store_ref tables while also manually downloa
The ID for SystemVM Template (KVM) is 3 and there is two references in
template_store_ref:
MariaDB [cloud]> select * from template_store_ref where template_id=3;
+-+--+-+-+-+--+--+--
Can you share logs during this last attempt?
I'll try to craft some SQL additions for your vm_template and
template_store_ref tables while also manually downloading and unpacking the
file to specific folder on Secondary Storage...
Andrija
On Thu, 3 Oct 2019 at 16:55, Fariborz Navidan wrote:
>
My cloud is down for 2 days. I would really appreciate if you can help me
fix the issue.
On Thu, Oct 3, 2019 at 4:44 PM Fariborz Navidan
wrote:
> Any idea?
>
> On Thu, Oct 3, 2019 at 2:09 PM Fariborz Navidan
> wrote:
>
>> I did the steps exactly but still same error. It first says cannot
>> upg
Any idea?
On Thu, Oct 3, 2019 at 2:09 PM Fariborz Navidan
wrote:
> I did the steps exactly but still same error. It first says cannot upgrade
> database with no further sql errors stated. Thn says cannot find System VM
> template for KVM. It look likes system vm template 4.11.3 is installed only
I did the steps exactly but still same error. It first says cannot upgrade
database with no further sql errors stated. Thn says cannot find System VM
template for KVM. It look likes system vm template 4.11.3 is installed only
for router!
MariaDB [cloud]> select * from vm_template where name like '
- ake sure mgmt is stopped (you can leave it on 4.13 if not
already downgraded), stop cloudstack-agents on KVM hosts.
- Rollback DB with your SQL statements, that you shared a few emails ago
(unfortunately after this 4.12 is NOT possible to work normally...)
-Download the new systemVM template - i
I cannot rollback DB to 4.12. How can I download 4.11.3 and and register in
DB?
On Wed, Oct 2, 2019 at 9:43 PM Andrija Panic
wrote:
> There's a GitHub issue about this (perhaps you or some colleague?)
>
> Did you register 4.11.3 (not 4.13) systemVM template? Documentation has
> just been updated
There's a GitHub issue about this (perhaps you or some colleague?)
Did you register 4.11.3 (not 4.13) systemVM template? Documentation has
just been updated... Sorry for this.
i..e. downgrade packages to 4.12, make sure your DB is rolled back, start
4.12 normally, register 4.11.3 systemVM templat
Any idea?
On Wed, Oct 2, 2019 at 3:59 PM Fariborz Navidan
wrote:
> Yes, It was clean 4.12 installation.
>
> On Wed, Oct 2, 2019 at 3:52 PM Andrija Panic
> wrote:
>
>> "was this a clean 4.12 install, then later upgrade - or was it previously
>> 4.11.x then 4.12 etc?"
>>
>> On Wed, 2 Oct 2019 at
Yes, It was clean 4.12 installation.
On Wed, Oct 2, 2019 at 3:52 PM Andrija Panic
wrote:
> "was this a clean 4.12 install, then later upgrade - or was it previously
> 4.11.x then 4.12 etc?"
>
> On Wed, 2 Oct 2019 at 14:20, Fariborz Navidan
> wrote:
>
> > Which question?
> >
> > I have sent past
"was this a clean 4.12 install, then later upgrade - or was it previously
4.11.x then 4.12 etc?"
On Wed, 2 Oct 2019 at 14:20, Fariborz Navidan wrote:
> Which question?
>
> I have sent pastebin link. I lost 4.12 backup accidentally. I am trying to
> make 4.13 upgrade successfully. I do run follow
Which question?
I have sent pastebin link. I lost 4.12 backup accidentally. I am trying to
make 4.13 upgrade successfully. I do run following commands before upgrade
retry:
[root@fr-kvm1 ~]# cat rollback.sql
delete from guest_os_hypervisor where guest_os_id >= 277;
delete from guest_os where id >
It was not designed to rollback on its own, you are expected to rollback DB
yourself (DB restore) and try again if needed.
But you have not answered my question.
On Wed, 2 Oct 2019, 13:50 Fariborz Navidan, wrote:
> In my experience, if DB upgrade fails, it does not fully rolls back
> remaining
In my experience, if DB upgrade fails, it does not fully rolls back
remaining 4.13's schema upgraded partially and upon next restart it does
not check existence of 4.13's table or columns causing SQL errors
complaining about tables or columns already exists.
On Wed, Oct 2, 2019 at 3:14 PM Andrija
was this a clean 4.12 install, then later upgrade - or was it previously
4.11.x then 4.12 etc?
On Wed, 2 Oct 2019 at 12:21, Fariborz Navidan wrote:
> https://pastebin.com/2EFm0jaW
>
> On Wed, Oct 2, 2019 at 1:19 PM Andrija Panic
> wrote:
>
> > (backup, backup, backup...)
> >
> > Can you send th
https://pastebin.com/2EFm0jaW
On Wed, Oct 2, 2019 at 1:19 PM Andrija Panic
wrote:
> (backup, backup, backup...)
>
> Can you send the full logs (passtebin or similar please, not in email) ?
>
> Andrija
>
(backup, backup, backup...)
Can you send the full logs (passtebin or similar please, not in email) ?
Andrija
22 matches
Mail list logo
