Softaculous


Topic : Broken Virtualizor install on Centos 7 with KVM.


Posted By: tekoa on June 29, 2015, 3:18 pm
The installation instructions provided at http://www.virtualizor.com/wiki/Install_KVM do not work with a fresh install of Centos 7.

You have to stop firewalld (and disable it) in order to connect at all on https://x.x.x.x:4085 .

Then I get a page that says "A 50X error has occured", which probably means a 501 error or some other 50x error.

Please tell me what other information is missing from the instructions.



Posted By: tekoa on June 29, 2015, 4:28 pm | Post: 1
Okay.  The 50x error was apparently caused by the optional lvg parameter. When I first did the install I put lvg=vg when running install.sh .  When I ran install.sh again without the lvg=vg the 50x error disappeared and I was able to use the Admin panel.

Centos 7 also renames the network adapter from eth0 to a name starting with en---- .  This new name can be found by running the command  'ip addr' on the command line. Centos set mine to enp9s0 . 

I entered enp9s0 instead of the default eth0 in Virtualizor Admin > Configuration > Master Settings > Network Adapter.  Then I ran 'service virtnetwork start' as instructed on the Virtualizor Admin Panel. This was the result:

  [root]# service virtnetwork start
  sh: ifconfig: command not found
  sh: ifconfig: command not found
  sh: route: command not found
  Failed to start viifbr0 ... Restarting normal network

It also failed to start the normal network and terminated my connection to the server.  I'll have to ask the datacenter to reboot the server.

A minimal install of Centos 7 doesn't include ifconfig.  To install ifconfig you need to enter 'yum install net-tools' on the command line.

What else is missing from the Virtualizor installation instructions ?

Posted By: tekoa on June 29, 2015, 4:45 pm | Post: 2
Even after rebooting, I cannot connect at all to the server.  I have requested the datacenter either uninstall Virtualizor using the instructions at http://www.virtualizor.com/wiki/Uninstall_Virtualizor  or connect a KVM so I can uninstall and try again.

Posted By: tekoa on June 29, 2015, 5:17 pm | Post: 3
When I reinstalled Virtualizor I tried again to use the optional lvg parameter.  It apparently wants the the vg specified as  /dev/vg.  The correct syntax for my installation was
./install.sh email=your@email.com kernel=kvm lvg=/dev/vg

After installing net-tools on the server, which provides the ifconfig and route commands required by 'service virtnetwork start' (and re-entering the name of my network interface in the Virtualizor config, as above) the 'service virtnetwork start' successfully starts the viifbr0 bridge required by a KVM vps.

Posted By: tekoa on June 29, 2015, 6:19 pm | Post: 4
Well, scratch my previous comment about the correct syntax for the lvg parameter.  Although Virtualizor initially recognized my /dev/vg storage, when I went to add a VPS it had somehow added an extra slash to the storage address, so it wouldn't work. The fix was to go to the Storage page in Virtualizor Admin and remove the storage, then re-add the storage without the extra slash.

Posted By: tekoa on June 29, 2015, 6:28 pm | Post: 5
My first KVM VPS has now been added.

I can access the VPS using SSH from the host server command line and using the Virtualizor VNC.  I can ping the VPS IP from the host and ping the host IP from the VPS.

The VPS says "connect: Network is unreachable" when trying to ping from the VPS to IP's on the internet. 

From the Internet the VPS IP does not respond at all to pings, HTTP, or SSH.

Are there any more missing instructions for installing on Centos 7?

Posted By: jevingala on July 1, 2015, 5:55 am | Post: 6
Hi,

First of all the installation command should include only the volume group name and not the path like /dev/vg.
Just while adding the storage on panel you need to provide your storage path 
eg: /dev/vg

And for the ip issue which is not getting connected to the internet,
you can open a support ticket so that we can check the issue on your server and fix it.


-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/

Posted By: tekoa on July 2, 2015, 12:57 am | Post: 7
Thank you for the quick response to my support ticket.  The vps is now working fine, after re-creating it.

For others who may be having problems, my connectivity problems were due to not entering the vps IP's into an IP pool before using them.  The settings in the IP pool are required by Virtualizor for connecting a KVM vps.

Posted By: jevingala on July 2, 2015, 7:10 am | Post: 8
Hi,

Yes,the ips need to be in the ip pool to make them work.



-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/

Posted By: RajAgarwal on November 14, 2017, 4:36 pm | Post: 9
Hi,

I am facing the same issue of connecting the VPS using putty.

IPs are added in IP pool

Posted By: quickbooks2018 on November 28, 2017, 8:15 am | Post: 10
systemctl status virtualizor.service
‚óŹ virtualizor.service - Virtualizor Service
  Loaded: loaded (/etc/systemd/system/virtualizor.service; enabled; vendor preset: disabled)
  Active: failed (Result: timeout) since Tue 2017-11-28 12:32:14 PKT; 36min ago
  Process: 1899 ExecStart=/etc/init.d/virtualizor start (code=killed, signal=TERM)

Nov 28 12:30:44 asim.centos7.local systemd[1]: Starting Virtualizor Service...
Nov 28 12:32:14 asim.centos7.local systemd[1]: virtualizor.service start operation timed out. Terminating.
Nov 28 12:32:14 asim.centos7.local systemd[1]: Failed to start Virtualizor Service.
Nov 28 12:32:14 asim.centos7.local systemd[1]: Unit virtualizor.service entered failed state.
Nov 28 12:32:14 asim.centos7.local systemd[1]: virtualizor.service failed.

Posted By: quickbooks2018 on November 28, 2017, 8:16 am | Post: 11
/etc/init.d/virtualizor status
php-fpm (pid 2163) is running...
nginx (pid 2176) is running...
SUCCESS! MySQL running (2552)

Posted By: quickbooks2018 on November 28, 2017, 8:16 am | Post: 12
/etc/init.d/virtualizor restart
Stopping php-fpm: Done...
Stopping nginx: Done...
Shutting down MySQL. SUCCESS!



Posted By: quickbooks2018 on November 28, 2017, 10:49 am | Post: 13
Dear Support,

virtualizor.service - Virtualizor Service
  Loaded: loaded (/etc/systemd/system/virtualizor.service; enabled; vendor preset: disabled)
  Active: failed (Result: timeout) since Tue 2017-11-28 15:36:02 PKT; 5min ago
  Process: 3537 ExecStart=/etc/init.d/virtualizor start (code=killed, signal=TERM)

Nov 28 15:34:31 asim.centos7.local systemd[1]: Starting Virtualizor Service...
Nov 28 15:36:02 asim.centos7.local systemd[1]: virtualizor.service start operation timed out. Terminating.
Nov 28 15:36:02 asim.centos7.local systemd[1]: Failed to start Virtualizor Service.
Nov 28 15:36:02 asim.centos7.local systemd[1]: Unit virtualizor.service entered failed state.
Nov 28 15:36:02 asim.centos7.local systemd[1]: virtualizor.service failed.




- The start-up result is done.
Nov 28 15:36:01 asim.centos7.local systemd[1]: Starting Session 36 of user root.
-- Subject: Unit session-36.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-36.scope has begun starting up.
Nov 28 15:36:01 asim.centos7.local CROND[3575]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virt
Nov 28 15:36:02 asim.centos7.local systemd[1]: virtualizor.service start operation timed out. Terminating.
Nov 28 15:36:02 asim.centos7.local systemd[1]: Failed to start Virtualizor Service.
-- Subject: Unit virtualizor.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit virtualizor.service has failed.
--
-- The result is failed.
Nov 28 15:36:02 asim.centos7.local systemd[1]: Unit virtualizor.service entered failed state.
Nov 28 15:36:02 asim.centos7.local systemd[1]: virtualizor.service failed.
Nov 28 15:36:02 asim.centos7.local polkitd[830]: Unregistered Authentication Agent for unix-process:3531:171124 (system bus name :1.99, objec
Nov 28 15:36:11 asim.centos7.local dhcpd[1605]: DHCPREQUEST for 192.168.1.4 from f4:0e:22:df:5c:1f via viifbr0: unknown lease 192.168.1.4.
Nov 28 15:36:11 asim.centos7.local dhcpd[1605]: DHCPREQUEST for 192.168.1.4 from f4:0e:22:df:5c:1f via wlp9s0: unknown lease 192.168.1.4.
Nov 28 15:36:26 asim.centos7.local dhcpd[1605]: DHCPREQUEST for 192.168.1.4 from f4:0e:22:df:5c:1f via viifbr0: unknown lease 192.168.1.4.
Nov 28 15:36:26 asim.centos7.local dhcpd[1605]: DHCPREQUEST for 192.168.1.4 from f4:0e:22:df:5c:1f via wlp9s0: unknown lease 192.168.1.4.
Nov 28 15:36:38 asim.centos7.local dhcpd[1605]: DHCPREQUEST for 192.168.1.4 from f4:0e:22:df:5c:1f via viifbr0: unknown lease 192.168.1.4.
Nov 28 15:36:38 asim.centos7.local dhcpd[1605]: DHCPREQUEST for 192.168.1.4 from f4:0e:22:df:5c:1f via wlp9s0: unknown lease 192.168.1.4.
lines 2598-2624/2624 (END)



Kindly guide

Powered By AEF 1.0.8 © 2007-2008 Electron Inc.