Discussion:
[Users] unable to connect to virtuozzo
Mark Johanson
2017-09-24 21:37:57 UTC
Permalink
If I am not using Virtuozzo as a hypervisor, is openvz 7 going to even be possible for use?

#prlctl list
Login failed: Unable to connect to Virtuozzo. You may experience a connection problem or the server may be down. Contact your Virtuozzo administrator for assistance.

We happen to use SolusVM as our hypervisor for openvz currently. I started looking at openvz 7 as the next major upgrade for our nodes, but when using most the commands listed in the docs for openvz 7 I get the above failed command. If prlctl and the such are the next version of controls for openvz 7 and going forward, does this mean that without using vituozzo as your hypervisor your going to be out of luck?

Thanks,
Scott Dowdle
2017-09-24 21:52:54 UTC
Permalink
Greetings,

----- Original Message -----
Post by Mark Johanson
If I am not using Virtuozzo as a hypervisor, is openvz 7 going to
even be possible for use?
#prlctl list
Login failed: Unable to connect to Virtuozzo. You may experience a
connection problem or the server may be down. Contact your Virtuozzo
administrator for assistance.
We happen to use SolusVM as our hypervisor for openvz currently. I
started looking at openvz 7 as the next major upgrade for our nodes,
but when using most the commands listed in the docs for openvz 7 I
get the above failed command. If prlctl and the such are the next
version of controls for openvz 7 and going forward, does this mean
that without using vituozzo as your hypervisor your going to be out
of luck?
I'm not sure what you are referring to with "using vituozzo as your hypervisor". Everything is in the kernel they ship.

Are you running the commands as a user or as root? You need to be root.

OpenVZ 7 works out of the box so I'm not sure what you did wrong. Can you provide more details?

TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
Mark Johanson
2017-09-24 22:39:27 UTC
Permalink
Hello,

Sorry if my terminology is wrong, when I refer to virtuozzo I mean the paid stuff not openvz. All though now I suppose there really is no difference between them.

The vzctl commands (ie vzctl list) work and list a running vm:

#vzlist
CTID NPROC STATUS IP_ADDR HOSTNAME
178 11 running XXX.XXX.XXX.XXX server.example.com

but the other command errors everytime:

cache #prlctl list
Login failed: Unable to connect to Virtuozzo. You may experience a connection problem or the server may be down. Contact your Virtuozzo administrator for assistance.

I would not be surprised if I have it all messed up. Its the first one I have built and its nothing like I am use to using (all this extra kvm networking and stuff is confusing for a node I only need to be openvz)

Settings that are set in the ve-*.conf files that aren't complainign they are not set when building a vm.

2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter privvmpages not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter shmpages not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numproc not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter physpages not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter vmguarpages not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numflock not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numpty not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numsiginfo not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numfile not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numiptent not set

PRIVVMPAGES="65536:69632"
SHMPAGES="21504:21504"
NUMPROC="240:240"
PHYSPAGES="0:unlimited"
VMGUARPAGES="33792:unlimited"
OOMGUARPAGES="26112:unlimited"
NUMTCPSOCK="360:360"
NUMFLOCK="188:206"
NUMPTY="100:100"
NUMSIGINFO="256:256"
TCPSNDBUF="1720320:2703360"
TCPRCVBUF="1720320:2703360"
OTHERSOCKBUF="1126080:2097152"
DGRAMRCVBUF="262144:262144"
NUMOTHERSOCK="360:360"
DCACHESIZE="3409920:3624960"
NUMFILE="9312:9312"
AVNUMPROC="1000:1000"
NUMIPTENT="1000:1000"

Even tried switchign them to just all unlimited with the same complaints.

So yes, I would not be surprised if a fresh install is all messed up for me.
Post by Scott Dowdle
Greetings,
----- Original Message -----
Post by Mark Johanson
If I am not using Virtuozzo as a hypervisor, is openvz 7 going to
even be possible for use?
#prlctl list
Login failed: Unable to connect to Virtuozzo. You may experience a
connection problem or the server may be down. Contact your Virtuozzo
administrator for assistance.
We happen to use SolusVM as our hypervisor for openvz currently. I
started looking at openvz 7 as the next major upgrade for our nodes,
but when using most the commands listed in the docs for openvz 7 I
get the above failed command. If prlctl and the such are the next
version of controls for openvz 7 and going forward, does this mean
that without using vituozzo as your hypervisor your going to be out
of luck?
I'm not sure what you are referring to with "using vituozzo as your hypervisor". Everything is in the kernel they ship.
Are you running the commands as a user or as root? You need to be root.
OpenVZ 7 works out of the box so I'm not sure what you did wrong. Can you provide more details?
TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
_______________________________________________
Users mailing list
https://lists.openvz.org/mailman/listinfo/users
Dmitry Mishin
2017-09-25 06:03:32 UTC
Permalink
Hello,

Please check that prl-disp service is up & running.

Thank you,
Dmitry.
Post by Mark Johanson
Hello,
Sorry if my terminology is wrong, when I refer to virtuozzo I mean the
paid stuff not openvz. All though now I suppose there really is no
difference between them.
#vzlist
CTID NPROC STATUS IP_ADDR
HOSTNAME
178 11 running XXX.XXX.XXX.XXX server.example.com
cache #prlctl list
Login failed: Unable to connect to Virtuozzo. You may experience a
connection problem or the server may be down. Contact your Virtuozzo
administrator for assistance.
I would not be surprised if I have it all messed up. Its the first one I
have built and its nothing like I am use to using (all this extra kvm
networking and stuff is confusing for a node I only need to be openvz)
Settings that are set in the ve-*.conf files that aren't complainign they
are not set when building a vm.
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter privvmpages not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter shmpages not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numproc not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter physpages not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter vmguarpages not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numflock not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numpty not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numsiginfo not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numfile not set
2017-09-24T15:54:32-0400 vzctl : CT 174 : UB parameter numiptent not set
PRIVVMPAGES="65536:69632"
SHMPAGES="21504:21504"
NUMPROC="240:240"
PHYSPAGES="0:unlimited"
VMGUARPAGES="33792:unlimited"
OOMGUARPAGES="26112:unlimited"
NUMTCPSOCK="360:360"
NUMFLOCK="188:206"
NUMPTY="100:100"
NUMSIGINFO="256:256"
TCPSNDBUF="1720320:2703360"
TCPRCVBUF="1720320:2703360"
OTHERSOCKBUF="1126080:2097152"
DGRAMRCVBUF="262144:262144"
NUMOTHERSOCK="360:360"
DCACHESIZE="3409920:3624960"
NUMFILE="9312:9312"
AVNUMPROC="1000:1000"
NUMIPTENT="1000:1000"
Even tried switchign them to just all unlimited with the same complaints.
So yes, I would not be surprised if a fresh install is all messed up for me.
Post by Scott Dowdle
Greetings,
----- Original Message -----
Post by Mark Johanson
If I am not using Virtuozzo as a hypervisor, is openvz 7 going to
even be possible for use?
#prlctl list
Login failed: Unable to connect to Virtuozzo. You may experience a
connection problem or the server may be down. Contact your Virtuozzo
administrator for assistance.
We happen to use SolusVM as our hypervisor for openvz currently. I
started looking at openvz 7 as the next major upgrade for our nodes,
but when using most the commands listed in the docs for openvz 7 I
get the above failed command. If prlctl and the such are the next
version of controls for openvz 7 and going forward, does this mean
that without using vituozzo as your hypervisor your going to be out
of luck?
I'm not sure what you are referring to with "using vituozzo as your
hypervisor". Everything is in the kernel they ship.
Are you running the commands as a user or as root? You need to be root.
OpenVZ 7 works out of the box so I'm not sure what you did wrong. Can
you provide more details?
TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
_______________________________________________
Users mailing list
https://lists.openvz.org/mailman/listinfo/users
_______________________________________________
Users mailing list
https://lists.openvz.org/mailman/listinfo/users
Mark Johanson
2017-09-25 14:00:34 UTC
Permalink
Hello Dmitry,

Restarting prl-disp did fix the prlctl issues. Will see if I can figure out some of the other issues, like why some templates will build and others error saying none of the settings are set.

Thanks,
Post by Mark Johanson
Hello,
Please check that prl-disp service is up & running.
Thank you,
Dmitry.
_______________________________________________
Users mailing list
https://lists.openvz.org/mailman/listinfo/users
Mark Johanson
2017-09-24 21:56:33 UTC
Permalink
So did not mean SolusVM as the hypervisor. Long day and lots of head beating trying to get things working in OpenVZ 7.
Post by Mark Johanson
If I am not using Virtuozzo as a hypervisor, is openvz 7 going to even be possible for use?
#prlctl list
Login failed: Unable to connect to Virtuozzo. You may experience a connection problem or the server may be down. Contact your Virtuozzo administrator for assistance.
We happen to use SolusVM as our hypervisor for openvz currently. I started looking at openvz 7 as the next major upgrade for our nodes, but when using most the commands listed in the docs for openvz 7 I get the above failed command. If prlctl and the such are the next version of controls for openvz 7 and going forward, does this mean that without using vituozzo as your hypervisor your going to be out of luck?
Thanks,
_______________________________________________
Users mailing list
https://lists.openvz.org/mailman/listinfo/users
Loading...