Skip to main content

X11 Forwarding - DISPLAY not SET when trying to run xclock

in order to use PuTTY with X11 FW feature you will need to follow these instructions:

1. in PuTTY configuration -> go to Connection settings -> SSH -> X11
    check the Enable X11 forwarding

2. check /etc/ssh/sshd_config  that X11 forwarfing flag set to yes
    if not - change to yes and restart sshd service
[root]# service sshd restart

3. open your server terminal using putty


4. check DISPLAY parameter by typing  ##echo $DISPLAY
    you should get:  localhost:10.0 (or something similar)


5. open Xming on your local machine (your PC)


6. type xclock command and you should see it

common problems that you can face during your xclock configuration experience and solutions:


if xclock is not found in your Linux server -> install xorgs-X11-apps rpm:
[root]# yum install xorg-x11-apps


xclock command gives Can't open display output
[root]# xclock
Error: Can't open display: localhost:10.0
-> probably you are missing xorg-x11-xauth
fix it by  
[root]# yum install xorg-x11-xauth


xclock command gives Cannot convert string output
[root]# xclock
Warning: Cannot convert string "" to type XftFont
-> you need to install these rpms


[root]# yum install fontconfig-devel
[root]# yum install xorg-x11-font-utils
[root]# yum install liberation-sans-fonts















Comments

Post a Comment

Popular posts from this blog

Missing command :fuser Prerequisite check "CheckSystemCommandAvailable" failed

When trying to apply patch you may face this error the solution is described below. ERROR: bash-4.2$ ../opatch apply Oracle Interim Patch Installer version 12.2.0.1.5 Copyright (c) 2016, Oracle Corporation.  All rights reserved. Oracle Home       : /oracle/app/oracle/product/12.1.0 Central Inventory : /oracle/app/oracle/oraInventory    from           : /oracle/app/oracle/product/12.1.0/oraInst.loc OPatch version    : 12.2.0.1.5 OUI version       : 12.1.0.2.0 Log file location : /oracle/app/oracle/product/12.1.0/cfgtoollogs/opatch/opatch2016-07-27_16-27-44PM_1.log Verifying environment and performing prerequisite checks... Prerequisite check "CheckSystemCommandAvailable" failed. The details are: Missing command :fuser Prerequisite check "CheckSystemCommandAvailable" failed. The details are: Missing command :fuser Prerequisite ...
1 comment
Read more

ORA-27104: system-defined limits for shared memory was misconfigured

I faced this error while trying to restore & recover of a PDB (pluggable database) part of the log file and the solution is described here below: log: initialization parameters used for automatic instance: db_name=CDB db_unique_name=gbux_pitr_PDB1_CDB compatible=12.1.0.2.0 db_block_size=8192 db_files=200 diagnostic_dest=/oracle/app/oracle _system_trig_enabled=FALSE sga_target=1888M processes=200 db_create_file_dest=/oracle/auxilary log_archive_dest_1='location=/oracle/auxilary' enable_pluggable_database=true _clone_one_pdb_recovery=true #No auxiliary parameter file used starting up automatic instance CDB RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 07/31/2016 16:22:20 RMAN-04014: startup failed: ORA-27104: system-defined limits for shared...
6 comments
Read more

ora-65035 while create pluggable database from another one

or : ORA-21000: error number argument to raise_application_error of -65035 is out of range Cause: this error caused because of an unrecoverable transaction in the source DB. Solution: 1. either stop and start your pluggable source DB 2. identify the open transaction and kill it if you can. use this query to do so: select * from v$transaction t,v$session  s where t.ses_addr = s.saddr;
Post a Comment
Read more