Skip to main content

[solved] bootloop and crash

Thread needs solution

Hi,

my appliance (vmP v8) had no space left (refer to http://forum.acronis.com/forum/41080#comment-128734)

So removed :
/var/log/messages (he is occupying almost the entire disk space)
/tmp/*

But the appliance failed to start the service (see attachment) :
Code: 14127118 (0xD7900E)
LineInfo: 0x8734D6EB22EADA21

I'm afraid I have to reinstall the appliance?
Thank you!

Attachment Size
pb_acronis.jpg 60.5 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

If there was /tmp/* deleted - this might be the cause of such problems, since there are quite a lot of crucial elements located under /tmp/ folder. There should be only /tmp/core deleted, but not entire contents :(

In the current situation I'd suggested to migrate the settings of your appliance to new freshly-deployed one as described in http://forum.acronis.com/forum/34725#comment-107881 . Also check this thread where this procedure worked for KJSTech user - check it starting from item 8: http://forum.acronis.com/forum/41357#comment-129880

In our investigation of such issues we have found that they are related to the Linux kernel specifics and how it works with specific (not all) network shares, especially if they are located on NAS devices. The 'asamba' module is glitching there and this causes the enormous growth of /var/log/messages file. We seem to have improved the situation and created a build with updated asamba+Linux kernel, however it has some drawbacks with shares in non-domain environment (Windows-based shares are not accessible properly in such environments, however it doesn't affect NAS devices. Of course we will fix this issue before publishing the build). If you'd like to give it a try, please send me a private message, so that I can give you a link to this build.

Edit: just found that the issues with shares access (mentioned above concerning the new build) were related to specific broken machine only (it was part of domain, while DC was inaccessible so nothing could access its shares), so the new build is fine in these aspects.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi,

it's a little bit strange to store system files in /tmp :(

The french support said to backup/restore the entire directory /var/lib/Acronis. And you said only /var/lib/Acronis/vmProtect and Scheduler. Maybe it's not recommanded to restore the entire directory /var/lib/Acronis ?

(I send you a PM)
thank you

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

The /tmp contains also hidden folders which are used for store in encrypted format the credentials for connection to the managed vCenter/ESXi host which is why deleting entire folder is something that should not be done :(

/var/lib/Acronis contains also "License Server" + "NFSStorage" folders and migrating them is not recommended as it may break up the binding of licenses to the hosts on the new appliance. The proper way is to migrate only /var/lib/Acronis/vmProtect + /var/lib/Acronis/Scheduler folders.

P.S. I've sent you a PM with the link to the new build which should prevent the appliance overfill issue.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi There,

same Problem here :( Appliance hangs in a Boot-Loop after reboot. Wasnt able to login to the webinterfacen, then i decided to reboot and now it crashed.

we have two local storage volumes 1TB + 2 TB. the 1TB was quite full, then i decided to create a second Task to the second storage. and also changed the backup task of the first 1TB Storage. and reduced the size of backuped machines from 40 to 25. due to the cleanup rule, space normally should be free up automaticlly (never delete last backup was disabled too) hence i cannot understand why the machine is now broken :(

@Vasily: could you please send me the link for the new build too?

Thank you very much in adance.

Regards

Peter

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Peter,

The problem discussed here is unrelated to the backup storage (1TB or 2TB which you have), but rather it's an issue with the local disks of the virtual appliance (so it doesn't matter that there is no free space on the backup storage). Can you please do the following, so that I can confirm the issue:

1) Detach the local storages (1TB and 2TB) from the virtual appliance in vSphere Client - remove disk/remove from inventory but keep on datastore.
2) Power off the appliance and export it into .ovf template via vSphere client (File->Export->OVF).
3) Upload the exported .ovf/.ova to our FTP server (I will send you the link in a private message)

This is necessary to properly indentify the issue and find out whether the new build should help here or not.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hello Vasily
thanks you, i just contacted the support (few. mins ago) creating a ticket now.
Do you need the ticket number then?

Regards

Peter

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Peter,

Yes, it would be really helpful. Can you please send me the ticket ID in a reply to my private message?

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi VMP, so how was this resolved if I may ask? Can you please post a small overview on what the fix was?