QUESTION Trouble getting Incredible PBX running in Hyper-V

Discussion in 'General' started by Tim Schoeller, Sep 11, 2018.

  1. Tim Schoeller

    Tim Schoeller New Member

    Joined:
    Oct 14, 2016
    Messages:
    4
    Likes Received:
    0
    I would like to get Incredible PBX with GV running in Hyper-V. It is the hypervisor I have available and am familiar with.

    I have tried the following install images:
    IncrediblePBX13-13.iso - Installs fine but after the final reboot a line of purple green static appears during bootup and the boot process freezes. No longer able to boot to the OS.
    CentOS-6.10-x86_64-minimal.iso - Same as above.
    CentOS-7-x86_64-Minimal-1804.iso - Boots and installs fine but Asterisk does not seem to function. Status7 script reports Asterisk as DN and -bash: asterisk: command not found.

    I searched the install log for clues and came up with the following:

    ***********************************************************
    The existing menuselect.makeopts file did not specify
    that 'res_digium_phone' should not be included. However, either some
    dependencies for this module were not found or a
    conflict exists.

    Either run 'make menuselect' or remove the existing
    menuselect.makeopts file to resolve this issue.
    ***********************************************************

    make: *** [menuselect.makeopts] Error 255
    chown: cannot access ‘/var/run/asterisk’: No such file or directory
    Redirecting to /bin/systemctl start asterisk.service
    Failed to start asterisk.service: Unit not found.
    sed: can't read /etc/init.d/asterisk: No such file or directory
    sed: can't read /etc/asterisk/asterisk.conf: No such file or directory
    sed: can't read /etc/asterisk/asterisk.conf: No such file or directory
    Redirecting to /bin/systemctl restart asterisk.service
    Failed to restart asterisk.service: Unit not found.
    --2018-09-10 19:21:36--
    I verified that the referenced path does not exist. /var/run appears to be a symbolic link
    /etc/asterisk/asterisk.conf does exist.

    Linux is quite new for me - any tips/pointers would be much appreciated
     

    Attached Files:

    #1 Tim Schoeller, Sep 11, 2018
    Last edited: Sep 11, 2018
  2. David Foxworth

    Joined:
    Oct 26, 2013
    Messages:
    32
    Likes Received:
    11
    You only sent the log file created on the first run of the IncrediblePBX install script. All it shows is a lot of packages being installed. There is another log file created when you run the IncrediblePBX install script a second time after the reboot that would contain more information as to what went wrong...
     
  3. Tim Schoeller

    Tim Schoeller New Member

    Joined:
    Oct 14, 2016
    Messages:
    4
    Likes Received:
    0
    The board refused to accept the larger 2nd log file due to size. Sounds like that is the log which may shed some light. I will try splitting it.
     
  4. atsak

    atsak Guru

    Joined:
    Sep 7, 2009
    Messages:
    1,709
    Likes Received:
    150
    For the first two problems:

    Interrupt the boot process at the kernel selection screen.
    Press a to modify it
    Remove the words rhgb quiet at the end of the kernel launch command
    Press enter

    Boot (you'll see the funny splash screen but it will proceed)

    Login with root

    nano -w /etc/grub.conf
    Find the kernel launch commands (there are two in mine for some reason). Remove the rhgb quiet again (from both I guess)
    Save.

    Reboot to test.

    Disable VMQ in the Hyper V Network adapter properties.
    If you take advantage of the auto-updater for Incredible PBX you might have to do these steps again to clean up the grub.conf file.
     

Share This Page