• 6.8.0 RC1 VM's won't reboot after shutdown, can't download diagnostics but log availabe

    1812

    By 1812

      • Closed Minor

    After shutting down a vm from within the vm's operating system, the vm will not restart and instead gives the following error:

      

    Hook script execution failed: internal error: Child process (LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ /etc/libvirt/hooks/qemu 'JR Desktop' prepare begin -) unexpected exit status 127: php: error while loading shared libraries: libicui18n.so.65: cannot open shared object file: No such file or directory

    1232436168_ScreenShot2019-10-18at12_51_45PM.png.72e77ec174ee56d55e938028a7823202.png

     

    This occurs with both vm's on the server.

     

    When attempting to download diagnostics from the webGUI, the following screen appears:

     

    59680981_ScreenShot2019-10-18at12_55_30PM.thumb.png.3f490cbb2f47328e2b7890e5f156d963.png

     

    no diagnostics are then downloaded and the screen sits indefinitely.

     

    pressing the log tab shows

     

    660075740_ScreenShot2019-10-18at12_52_57PM.thumb.png.924e359f0331289756077815b3f49ad8.png

     

    and when entering "diagnostics" into a terminal window the following error occurs

      

    Last login: Fri Oct 18 12:42:20 -0400 2019 on /dev/pts/1.
root@Twins:~# diagnostics
/usr/bin/php: error while loading shared libraries: libicui18n.so.65: cannot open shared object file: No such file or directory
root@Twins:~#

    1393710540_ScreenShot2019-10-18at12_54_24PM.png.b354f0c448f31df247e763ed2e1dc7c2.png

     

    I was able to download the syslog from the webgui: twins-syslog-20191018-1655.zip

     

    Rebooting the server allows vm's to start and also allows access to diagnostics. Here are diagnostics after reboot (not that they are helpful but rather to show that they are available): twins-diagnostics-20191018-1708.zip

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    1812

    Update: can't duplicate this today and vm's operate as expected. Maybe my server was just having a massive brain fart or something.... 

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.