|
|
Re: cannot login after installing XFCE desktop remotely in Fedora 22 [message #52305 is a reply to message #52267] |
Mon, 25 January 2016 18:05 |
ura_Soul
Messages: 6 Registered: November 2015
|
Junior Member |
|
|
so i am informed that this may be an issue originating in the fact that the version of openVZ being used by the host i am with is only supporting older kernel versions and there is an incompatibility between newer OSs, firewallD and these older kernels.
since i don't actually run openVZ myself, i am ignorant of some of the details, but from my research it appears that i am unable to use X2go server/client to remotely connect to ALL recent OS versions that i have tested, probably due to this incompatibility between kernel versions, the OS and openVZ.
this answer provided to me on the askfedora site, suggests that openVZ is running an old kernel:
Quote:The short answer to this is that OpenVZ does not support many systemd operating systems.
The longer explanation to this is because OpenVZ allows your host to set up "containerized" VPS's for clients. All of the individual containers are dependent on the OpenVZ software. However, OpenVZ is running a version of the kernel around 2.6.x if I recall correctly. Because of this, OpenVZ has to backport many of the systemd features into sysvinit, which is... very messy.
There is no immediate solution to using firewalld in a OpenVZ machine. The same problem exists for CentOS 7. You can see more information in this thread that has a workaround solution that may work for you (it used to work for me, but it doesn't anymore).
For now, you will be better off using KVM or using an older version of Fedora with OpenVZ (and by old, I mean really old, for Fedora).
is that correct? if so, when will this be resolved? surely i am missing something here, right?
|
|
|
|
Re: cannot login after installing XFCE desktop remotely in Fedora 22 [message #52308 is a reply to message #52307] |
Wed, 27 January 2016 21:19 |
ura_Soul
Messages: 6 Registered: November 2015
|
Junior Member |
|
|
thanks for responding here. i can start a fedora 22 or fedora 23 VM without issues, yes.
and yes, until i install X2goserver (which installs firewallD) i can reboot and login again without problem, yes.
your understanding is accurate.
after running uname -a, i see the version is:
2.6.32-042stab113.11
Quote:what new services are set to run after you install XFCE and x2goserver that are not running before?
the only packages and services that are installed and thus set to run after i install XFCE are those added by installing XFCE, which is a LONG list.. too many to easily type out here. Network manager is in there and firewall-config, lots of libraries and many other packages i don't know much about.
i did just run a test of installing firewallD before i installed XFCE and i could reboot and login ok, so it is not just firewallD / ebtables on their own that are causal here. the problem occurs whether or not i install x2goserver.
Quote:after it becomes unreachable, can your VM be entered by using vzctl from the node?
i do not have access to the node as i am a user of a webserver that is run by a third party, so i am not able to directly answer your question here. i can access the server via the 'emergency console' access that is provided by the host's control panel, so the VM is not totally unreachable - if that is what you are wanting to know.
|
|
|
Re: cannot login after installing XFCE desktop remotely in Fedora 22 [message #52309 is a reply to message #52308] |
Thu, 28 January 2016 23:18 |
Ales
Messages: 330 Registered: May 2009
|
Senior Member |
|
|
Your provider is running the current stable vzkernel, which is a good sign. Also, from what you've said, it seems that your container reboots even after XFCE is installed, but it looses the connectivity to the outside world. In other words, looks like a configuration issue that arises from the newly installed packages.
The existence of the emergency console simplify things quite a bit. I'd start by comparing the firewall and networking configuration, before and after. I can't be more specific than that, sorry. This situation requires troubleshooting.
[Updated on: Thu, 28 January 2016 23:19] Report message to a moderator
|
|
|
|
|