Unable to start Xserver on Centos7 - gnome

I am struggling to set a desktop environment on a Centos 7.2 Server. I connect to the server in following way:-
Though putty ssh onto a jump box with my user Then from the jump box
ssh onto the Centos 7.2 server using my id
I have installed and tried below desktops:
Gnome Desktop --> Couldn't make it work (finally did a sudo yum groupremove of it)
Cinnamon --> still struggling
Have installed following packages:-
sudo yum --enablerepo=epel -y install cinnamon*
sudo yum install xorg*
I keep getting below error on startx:-
xauth: file /home/ma357577/.serverauth.4007 does not exist
(EE)
Fatal server error:
(EE) PAM authentication failed, cannot start X server.
Perhaps you do not have console ownership?
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Couldn't get a file descriptor referring to the console
I have tried to
rename /etc/pam.d/xserver (but in absence of this it falls back to /etc/pam.d/other hence is completely restricted)
and change the xserver file as below:-
\#%PAM-1.0
auth sufficient pam_rootok.so
\#auth required pam_console.so
auth sufficient pam_console.so nullok
account required pam_permit.so nullok
session optional pam_keyinit.so force revoke
none of the changes seem to work. Searched a lot on google but still stuck.
Eagerly seeking help on this! Thanks in advance.
Regards
Rohan

Check out this instruction Configuring VNC Server
You want to use xined service.

Related

When “vagrant up” it says “It appears your machine doesn't support NFS” (Debian jessie)

Issue
when vagrant up it says "It appears your machine doesn't support NFS"
Setups
Debian GNU/Linux 8 (jessie)
Vagrant 1:2.0.0
Virtualbox 5.1.30 r118389
Detail
After using apt-get to update and upgrade the system, I basically followed the instruction from the Mediawiki page, since I wanted to install Mathoid to render LaTeX equations locally for mediawiki page.
However, when I vagrant up it echos the following:
It appears your machine doesn't support NFS, or there is not an
adapter to enable NFS on this machine for Vagrant. Please verify
that `nfsd` is installed on your machine, and try again. If you're
on Windows, NFS isn't supported. If the problem persists, please
contact Vagrant support.
I checked if nfsd is correctly working on the host, and it says it's enabled.
# /etc/init.d/nfs-kernel-server status
nfs-kernel-server.service - LSB: Kernel NFS server support
Loaded: loaded (/etc/init.d/nfs-kernel-server)
Active: active (running) since Sun 2017-10-15 07:56:32 -02; 2 weeks 0 days ago
CGroup: /system.slice/nfs-kernel-server.service
??1277 /usr/sbin/rpc.mountd --manage-gids
I also tried google, and did not find a solution that fits my problem and I couldn't find any hint to resolve this. For instance, I tried to install the package
sudo apt-get install nfs-common
But it has been already installed.
Thank you in advance.
The command mentioned below works for linux mint 18.3:
sudo apt-get install nfs-common nfs-kernel-server
For Windows users seeing that error, run the following command to add support for NFS for Vagrant:
vagrant plugin install vagrant-winnfsd
The GitHub repo for this plugin is found here.
Also, to see the currently installed Vagrant plugins run this:
vagrant plugin list
Can be fixed by adding any exports to /etc/exports.
by :
modprobe nfs
modprobe nfsd
then running vagrant, which will add /etc/exports, then reloading
kernel-server and restarting vagrant.
issue http://jb-blog.readthedocs.io/en/latest/posts/0021-vagrant-nfs-problems.html
instead of installed NFS cos really no supported :
Try just removing type: nfs from the vagrant_synced_folders
More : https://www.vagrantup.com/docs/synced-folders/nfs.html

Qt for Embedded Linux data directory is not owned by user 0: /tmp/qtembedded-0

Okay so I'm very new at all of this so please forgive me if I don't provide enough information but feel free to ask for more.
I had to install ParaView from source on my linux system. ParaView requires Qt to be installed to be able to compile and install it. So I installed Qt on my linux system from source as well (version 4.8.6 to be precise). My ParaView is now installed but I can't seem to run it. The first time I tried I got the following output:
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
No Qt for Embedded Linux server appears to be running.
If you want to run this program as a server,
add the "-qws" command-line option.
When I ran it as sudo, I got the following output:
Qt for Embedded Linux data directory is not owned by user 0: /tmp/qtembedded-0
I have no idea what this means or how to fix it, any help will be much appreciated.
Extra info: I installed ParaView version 4.4
my Qt dir is /usr/local/Trolltech/QtEmbedded-4.8.6/bin
my ParaView dir is /usr/local/bin
I couldn't find anything on google or on here and that's why I'm asking.
If you want to run this program as a server,
add the "-qws" command-line option.
You really need this; append it to the line where you call your binary. When trying to start it on a machine that runs X11 you'll need QVFb installed and running, too, plus support for it (graphics, mouse and keyboard) compiled into the Qt libs.
I strongly advise against starting with root privileges.
It seems that you ran the application under the user, then killed it, switched to root and tried to run it again.
You can just remove the temporary folder.
rm -rf /tmp/qtembedded-0
I just removed
rm -rf /tmp/qtembedded-0
and then restarted the framebuffer and it works for me.
Mistake: I changed the permission of /tmp/qtembedded-0 while framebuffer was running.

ApacheDS unable to start correctly

I recently installed ApacheDS on a Ubuntu server 12.04 LTS,
when I start it via
sudo /etc/init.d/apacheds-[...]-default start
it gives me this output :
chown: invalid user: `#user#:apacheds'
Unknown id: #user#
I installed ApacheDS using the binary installer downloaded from the official website. I also used the default settings for everything during the installation.
Is there a work around or a way to make ApacheDS start correctly ?
Thanks

Cannot edit sendmail configuration on Red Hat Enterprise Linux 5.3

Have been through 10 or so Red Hat Enterprise Linux servers to update some sendmail configuration options and finally got to a 5.3 release server that is missing the sendmail-cf package and the server has no RHN access etc.
Tried searching online for a suitable RPM to manually install but can't seem to locate one?
[root# ~]# make -C /etc/mail make: Entering directory `/etc/mail'
WARNING: 'sendmail.mc' is modified. Please install package sendmail-cf to update your configuration.
make: Leaving directory `/etc/mail'
Help please?
The server does not need to have direct access to RHN. If you have '10 or so Red Hat Enterprise Linux servers', then I assume you also have a the subscriptions for them. You can login to your RHN account, download the sendmail-cf RPM for RHEL 5.3, copy it to the server and install it from there with yum.

Cannot display xclock program on xserver client - Mobaxterm

I am using Mobaxterm(free version) on a windows 7 desktop to connect to a SUSE 11 Enterprise server on AWS. I am trying to display the xclock program on my xtrem client but I get an error saying 'Error: Can't open display:'. I have used the following syntax to set the display on the server:
export DISPLAY=<IP_addr>:0.0
SUSE 11 does not come with xclock by default so I had to download it and install it.
The hosts file on my PC has the localhost entry commented out, I am not sure if that would make a difference. Any ideas on how to debug this? Thanks.
Fixed!
Earlier I was just looking at xclock program's error msg. But when I scanned Mobaxterms client terminal's output, I found the following msg:
X11 forwarding request failed on channel 0
After some google hunting, found that one of the reasons this happens is when xauth package is not installed on the remote server. So, I checked and found that to be the case. This is the command I ran:
zypper in -name xorg*
This command tells you if the package is installed and if any dependencies exist. The package comes bundled with the xclock program. So zypper uninstalled the other xclock I had installed from another source and replaced it with the right version.
Link to package info:
https://www.suse.com/LinuxPackages/packageRouter.jsp?product=server&version=11&service_pack=&architecture=i386&package_name=xorg-x11-xauth
I also modified a file called /etc/ssh/sshd_config as root. The following lines need to be uncommented:
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes
And X11UseLocalhost was changed to 'no'. I also changed my security group on AWS to let inbound traffic on port 6000. I am not sure if that matters.
After this mobaxterm automatically set my display parameter to localhost and I was able to run xclock on the remote server and see it on my local PC desktop.

Resources