Fedora 16 64bit : build a VM image based on Fedora , RHEL and CentOS with boxgrinder

[ what’s boxgrinder ]

boxgrinder enables you to build a custom Virtual appliance based on Fedora , RHEL and CentOS for KVM , VMware etc.

- boxgrinder
http://boxgrinder.org/

[root@fc16 ~]# cat /etc/fedora-release Fedora release 16 (Verne) [root@fc16 ~]# uname -ri 3.3.5-2.fc16.x86_64 x86_64

[ installation ]

install boxgrinder and documentation via yum.

[root@fc16 ~]# yum install *boxgrinder*

[ build a VM image with boxgrinder ]

1. create an appliance definition file.

There are sample definition files under /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances
directory.

I am going to build a VM using /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/jeos-f16.appl

make a working directory for boxgrinder and copy jeos-f16.appl to that directory.

[root@fc16 ~]# mkdir Boxgrinder_works [root@fc16 ~]# cd Boxgrinder_works/ [root@fc16 Boxgrinder_works]# cp /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/jeos-f16.appl .

[root@fc16 Boxgrinder_works]# cat jeos-f16.appl name: jeos-f16 os:  name: fedora  version: 16 repos:  - name: "temp-fedora-updates-testing"    mirrorlist: "https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f#OS_VERSION#&arch=#BASE_ARCH#"    ephemeral: true

There are some definition files under  /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/.

[root@fc16 Boxgrinder_works]# ls /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/* /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/gnome-fedora.appl /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/jeos-centos5-files.appl /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/jeos-centos5.appl /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/jeos-centos6.appl /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/jeos-f15.appl /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/jeos-f16-files.appl /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/jeos-f16.appl /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/modular: _hardware_cpus.appl             _packages_squid.appl _hardware_memory.appl           _packages_utils.appl _hardware_partitions_home.appl  _repos_boxgrinder_permanent_noarch.appl _hardware_partitions_root.appl  _repos_testlocal_ephemeral_noarch.appl _os_password.appl               _test_base.appl _packages_groups_base.appl      modular.appl _packages_groups_core.appl

build a Fedora 16’s JeOS image for KVM using a sample definition file ( jeos-f16.appl )

[root@fc16 Boxgrinder_works]# boxgrinder-build jeos-f16.appl --os-config format:qcow2 I, [2012-05-15T00:12:45.600999 #4575]  INFO -- : Validating appliance definition from jeos-f16.appl file... I, [2012-05-15T00:12:45.603516 #4575]  INFO -- : Appliance definition is valid. I, [2012-05-15T00:12:45.613775 #4575]  INFO -- : Building 'jeos-f16' appliance for x86_64 architecture. I, [2012-05-15T00:12:45.622250 #4575]  INFO -- : Resolving packages added to jeos-f16 appliance definition file... I, [2012-05-15T00:13:21.232120 #4575]  INFO -- : All additional packages for jeos-f16 appliance successfully resolved. I, [2012-05-15T00:13:21.232524 #4575]  INFO -- : Building jeos-f16 appliance... supermin helper [00000ms] whitelist = (not specified), host_cpu = x86_64, kernel = (null), initrd = (null), appliance = (null) supermin helper [00000ms] inputs[0] = /usr/lib64/guestfs/supermin.d checking modpath /lib/modules/3.3.4-1.fc16.x86_64 is a directory picked vmlinuz-3.3.4-1.fc16.x86_64 because modpath /lib/modules/3.3.4-1.fc16.x86_64 exists checking modpath /lib/modules/3.3.4-3.fc16.x86_64 is a directory picked vmlinuz-3.3.4-3.fc16.x86_64 because modpath /lib/modules/3.3.4-3.fc16.x86_64 exists checking modpath /lib/modules/3.3.5-2.fc16.x86_64 is a directory picked vmlinuz-3.3.5-2.fc16.x86_64 because modpath /lib/modules/3.3.5-2.fc16.x86_64 exists supermin helper [00000ms] finished creating kernel supermin helper [00001ms] visiting /usr/lib64/guestfs/supermin.d supermin helper [00073ms] visiting /usr/lib64/guestfs/supermin.d/base.img supermin helper [00080ms] visiting /usr/lib64/guestfs/supermin.d/daemon.img supermin helper [00098ms] visiting /usr/lib64/guestfs/supermin.d/hostfiles supermin helper [03203ms] visiting /usr/lib64/guestfs/supermin.d/init.img supermin helper [03605ms] finished creating appliance supermin helper [00000ms] whitelist = (not specified), host_cpu = x86_64, kernel = /tmp/guestfs.qPBEet/kernel, initrd = /tmp/guestfs.qPBEet/initrd, appliance = /tmp/guestfs.qPBEet/root supermin helper [00000ms] inputs[0] = /usr/lib64/guestfs/supermin.d checking modpath /lib/modules/3.3.4-1.fc16.x86_64 is a directory picked vmlinuz-3.3.4-1.fc16.x86_64 because modpath /lib/modules/3.3.4-1.fc16.x86_64 exists checking modpath /lib/modules/3.3.4-3.fc16.x86_64 is a directory picked vmlinuz-3.3.4-3.fc16.x86_64 because modpath /lib/modules/3.3.4-3.fc16.x86_64 exists checking modpath /lib/modules/3.3.5-2.fc16.x86_64 is a directory picked vmlinuz-3.3.5-2.fc16.x86_64 because modpath /lib/modules/3.3.5-2.fc16.x86_64 exists supermin helper [00000ms] finished creating kernel supermin helper [02620ms] finished mke2fs supermin helper [02621ms] visiting /usr/lib64/guestfs/supermin.d supermin helper [02621ms] visiting /usr/lib64/guestfs/supermin.d/base.img supermin helper [06528ms] visiting /usr/lib64/guestfs/supermin.d/daemon.img supermin helper [06576ms] visiting /usr/lib64/guestfs/supermin.d/hostfiles supermin helper [18756ms] visiting /usr/lib64/guestfs/supermin.d/init.img supermin helper [29206ms] finished creating appliance W, [2012-05-15T00:19:50.063980 #4575]  WARN -- : Loading SELinux policy failed. SELinux may be not fully initialized. I, [2012-05-15T00:22:32.786026 #4575]  INFO -- : Executing post operations after build... I, [2012-05-15T00:22:35.250434 #4575]  INFO -- : Base image for jeos-f16 appliance was built successfully.

It took around 15 minutes to build the VM in my environment.

the VM image will be built under the working directory where you issue boxgrinder-build command.

[root@fc16 fedora-plugin]# pwd /root/Boxgrinder_works/build/appliances/x86_64/fedora/16/jeos-f16/1.0/fedora-plugin [root@fc16 fedora-plugin]# ls jeos-f16-sda.qcow2  jeos-f16.xml

[root@fc16 fedora-plugin]# file *.qcow2 jeos-f16-sda.qcow2: QEMU QCOW Image (v2), 1078984704 bytes [root@fc16 fedora-plugin]# cat jeos-f16.xml <image>  <name>jeos-f16</name>  <domain>    <boot type='hvm'>      <guest>        <arch>x86_64</arch>      </guest>      <os>        <loader dev='hd'/>      </os>      <drive disk='jeos-f16-sda.qcow2' target='hda'/>    </boot>    <devices>      <vcpu>1</vcpu>      <memory>262144</memory>      <interface/>      <graphics/>    </devices>  </domain>  <storage>    <disk file='jeos-f16-sda.qcow2' use='system' format='qcow2'/>  </storage> </image>

start the VM

[root@fc16 fedora-plugin]# qemu-kvm jeos-f16-sda.qcow2 -m 256

well ,,, what’s root user’s credential ???


it seems that root user’s credentials are “boxgrinder-pw”.

[root@fc16 modular]# pwd /usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.10.1/integ/appliances/modular [root@fc16 modular]# cat _os_password.appl name: os-password summary: create password os:  name: dummy-os  version: 14  password: boxgrinder-pw post:  base:    - "/bin/echo 'true' > /os-password-boxgrinder-test"  ec2:    - "/bin/echo 'true' > /os-password-ec2-boxgrinder-test"  vmware:    - "/bin/echo 'true' > /os-password-vmware-boxgrinder-test"  virtualbox:    - "/bin/echo 'true' > /os-password-virtualbox-boxgrinder-test"

user : root
pass : boxgrinder-pw



nice tool !
You could build your custom virtual appliances easily with boxgrinder.

Fedora 16 : small tips : monitoring tools : nethogs , latencytop , atop

[root@fc16 ~]# cat /etc/fedora-release Fedora release 16 (Verne) [root@fc16 ~]# uname -ri 3.3.1-3.fc16.x86_64 x86_64

[ nethogs ]

nethogs shows network bandwidth per process
You might identify which processes are using how much bandwidth.

install nethogs via yum

[root@fc16 ~]# yum install nethogs -y

nethogs “device name”



[ latencytop ]

latencytop displays system latency , for example , what kind of latency is occurring in your system , identify the cause of latency in your system.

[root@fc16 ~]# yum install -y latencytop

just type latencytop

# latencytop

[ atop ]

atop is a similar to “top”

# yum install -y atop

just type “atop”



write the output of "atop" to a file

[root@fc16 ~]# atop -w atop.raw  10 3

atop -w “filename” “interval” “# of samples”

[root@fc16 ~]# file atop.raw atop.raw: data

read the file

[root@fc16 ~]# atop -r atop.raw

You might want to use atop in combination with cron when monitoring your system periodically.

Fedora 16 : bootchart ( visualize boot sequences )

bootchart visualizes boot sequences.

[ install ]

# cat /etc/fedora-release Fedora release 16 (Verne) # uname -ri 3.2.7-1.fc16.x86_64 x86_64

You can install it via yum

# yum search bootchart

bootchart and bootchart-daemon packages will be installed.

# rpm -ql bootchart-daemon /etc/bootchartd.conf /etc/dracut.conf.d/bootchartd.conf /lib/bootchart /lib/bootchart/bootchart-collector /lib/bootchart/tmpfs /lib/systemd/system/bootchart-done.service /lib/systemd/system/bootchart-done.timer /lib/systemd/system/bootchart.service /sbin/bootchartd <snip>

[ how to use ]

- configuration file

/etc/bootchart.conf ( no need to edit )

# Tarball for the various boot log files BOOTLOG_DEST=/var/log/bootchart.tgz # Whether to automatically generate the boot chart once the boot logger # completes.  The boot chart will be generated in $AUTO_RENDER_DIR. # Note that the bootchart package must be installed. AUTO_RENDER="yes" # Image format to use for the auto-generated boot chart # (choose between png, svg and eps). AUTO_RENDER_FORMAT="png" # Output directory for auto-generated boot charts AUTO_RENDER_DIR="/var/log"

- edit grub.cfg

add writable permission

[root@fc16 ~]# chmod u+w /boot/grub2/grub.cfg

add “init=/sbin/bootchard” in grub.cfg

39 menuentry 'Fedora Linux, with bootchartd' --class fedora --class gnu-lin     39 ux --class gnu --class os {     40         load_video     41         set gfxpayload=keep     42         insmod gzio     43         insmod part_msdos     44         insmod btrfs     45         set root='(hd0,msdos3)'     46         search --no-floppy --fs-uuid --set=root 61b367fb-2790-407f-a071-          46 262e8b857fb9     47         echo    'Loading Linux 3.2.7-1.fc16.x86_64 ...'     48         linux   /boot/vmlinuz-3.2.7-1.fc16.x86_64 root=UUID=61b367fb-279          48 0-407f-a071-262e8b857fb9 ro rd.md=0 rd.lvm=0 rd.dm=0 quiet rhgb rd.luks=          48 0 LANG=ja_JP.UTF-8  KEYTABLE=jp106 reboot=b,a init=/sbin/bootchartd     49         echo    'Loading initial ramdisk ...'     50         initrd  /boot/initramfs-3.2.7-1.fc16.x86_64.img     51 }

I added the new boot lines for bootchartd.
please take care of editing grub.cfg.

reboot the OS

# reboot

check the boot options.

# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.2.7-1.fc16.x86_64 root=UUID=61b367fb-2790-407f-a071-262e8b857fb9 ro rd.md=0 rd.lvm=0 rd.dm=0 quiet rhgb rd.luks=0 LANG=ja_JP.UTF-8 KEYTABLE=jp106 reboot=b,a init=/sbin/bootchartd

bootchard logs are stored under /var/log directory.

[root@fc16 ~]# ls /var/log/bootchart.* /var/log/bootchart.png  /var/log/bootchart.tgz

Fedora 16 : freenx error : xrdb: Connection refused , can’t open display

After upgrading to a newer kernel and boot that kernel on Fedora 16 64bit , I can’t always connect to Fedora 16 from Windows NX client.

Fedora 16 64bit

freenx-server-0.7.3-23.fc16.x86_64

Windows 7 64bit NX client : 3.5.0-7

NX Client error logs.

NX> 203 NXSSH running with pid: 5888 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 285 Setting the preferred NX options NX> 200 Connected to address: 192.168.11.150 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) NX> 105 hello NXCLIENT - Version 3.2.0 NX> 134 Accepted protocol: 3.2.0 NX> 105 SET SHELL_MODE SHELL NX> 105 SET AUTH_MODE PASSWORD NX> 105 login NX> 101 User: hattori NX> 102 Password: NX> 103 Welcome to: fc16.localdomain user: hattori NX> 105 listsession --user="hattori" --status="suspended,running" --geometry="1280x1024x32+render" --type="unix-gnome" NX> 127 Sessions list of user 'hattori' for reconnect: Display Type             Session ID                       Options  Depth Screen         Status      Session Name ------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------ NX> 148 Server capacity: not reached for user: hattori NX> 105 startsession  --link="lan" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="Fedora16%20notebook" --type="unix-gnome" --geometry="1024x768" --client="winnt" --keyboard="pc105/us" --screeninfo="1024x768x32+render" NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) NX> 700 Session id: fc16.localdomain-3000-D6D8E6C7FC1E5BE64B128ADD311F7FFD NX> 705 Session display: 3000 NX> 703 Session type: unix-gnome NX> 701 Proxy cookie: f9d2c96a45538be6010e66c640e2f1d8 NX> 702 Proxy IP: 192.168.11.150 NX> 706 Agent cookie: f9d2c96a45538be6010e66c640e2f1d8 NX> 704 Session cache: unix-gnome NX> 707 SSL tunneling: 1 NX> 105 /usr/libexec/nx/nxserver: line 1585:  1941 Terminated              sleep $AGENT_STARTUP_TIMEOUT NX> 596 Session startup failed. NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/hattori/.nx/F-C-fc16.localdomain-3000-D6D8E6C7FC1E5BE64B128ADD311F7FFD/session". You might also want to try: ssh -X myserver; /usr/libexec/nx/nxnode --agent to test the basic functionality. Session log follows: Can't open /var/lib/nxserver/db/running/sessionId{D6D8E6C7FC1E5BE64B128ADD311F7FFD}: No such file or directory. NX> 1006 Session status: closed NX> 1001 Bye. mv: cannot stat `/var/lib/nxserver/db/running/sessionId{D6D8E6C7FC1E5BE64B128ADD311F7FFD}': No such file or directory /usr/libexec/nx/nxserver: line 578: kill: (1615) - No such process NX> 280 Exiting on signal: 15

edit node.conf to debug

[root@fc16 ~]# egrep -i nx_log /etc/nxserver/node.conf | grep -v ^# NX_LOG_LEVEL=6 NX_LOGFILE=/var/log/nx/nxserver.log

make nxserver.log file and change an owner of that file to nx.nx ( user.group )

[root@fc16 ~]# touch /var/log/nx/nxserver.log [root@fc16 ~]# chown nx.nx /var/log/nx/nxserver.log

see logs.

[root@fc16 .nx]# cd /home/hattori/.nx/ [root@fc16 .nx]# ls F-C-fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D  cache-gnome [root@fc16 .nx]# cd F-C-fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D/ [root@fc16 F-C-fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D]# ls authority  options  pids  scripts  session

can’t open display :3000.

[root@fc16 F-C-fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D]# cat session xrdb: Connection refused xrdb: Can't open display ':3000' ** (gnome-session:3381): WARNING **: ディスプレイをオープンできません:

xrdb: Connection refused …. why ? …
before upgrading to the newer kernel , I could connect to the Fedora w/o problems.

[root@fc16 failed]# cat /var/log/nx/nxserver.log -- NX SERVER START: -c /usr/libexec/nx/nxserver - ORIG_COMMAND= -- NX SERVER START:  - ORIG_COMMAND= Info: Using fds #4 and #3 for communication with nxnode. HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) NX> 105 hello NXCLIENT - Version 3.2.0 NX> 134 Accepted protocol: 3.2.0 NX> 105 SET SHELL_MODE SHELL NX> 105 SET AUTH_MODE PASSWORD NX> 105 login NX> 101 User: hattori NX> 102 Password: Info: Auth method: ssh hattori@127.0.0.1's password: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) NX> 716 Slave mode started successfully. nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) nxnode_reader: NX> 716 finished nxnode_reader: NX> 1001 Bye. NX> 103 Welcome to: fc16.localdomain user: hattori NX> 105 listsession --user="hattori" --status="suspended,running" --geometry="1280x1024x32+render" --type="unix-gnome" NX> 127 Sessions list of user 'hattori' for reconnect: Display Type             Session ID                       Options  Depth Screen         Status      Session Name ------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------ NX> 148 Server capacity: not reached for user: hattori NX> 105 startsession  --link="lan" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="Fedora16%20notebook" --type="unix-gnome" --geometry="1024x768" --client="winnt" --keyboard="pc105/us" --screeninfo="1024x768x32+render" &link=lan&backingstore=1&encryption=1&cache=16M&images=64M&shmem=1&shpix=1&strict=0&composite=1&media=0&session=Fedora16 notebook&type=unix-gnome&geometry=1024x768&client=winnt&keyboard=pc105/us&screeninfo=1024x768x32+render&clientproto=3.2.0&login_method=SSH&user=hattori&userip=192.168.11.5&uniqueid=8041B6AC6751F47AD9EF47BC2DA52E8D&display=3000&host=127.0.0.1 nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) server_nxnode_echo: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) nxnode_reader: NX> 700 Session id: fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D nxnode_reader: NX> 705 Session display: 3000 server_nxnode_echo: NX> 700 Session id: fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D nxnode_reader: NX> 703 Session type: unix-gnome NX> 700 Session id: fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D nxnode_reader: NX> 701 Proxy cookie: 331206324b12d4063f2d05078b623ea6 server_nxnode_echo: NX> 705 Session display: 3000 nxnode_reader: NX> 702 Proxy IP: 192.168.11.150 server_nxnode_echo: NX> 703 Session type: unix-gnome NX> 705 Session display: 3000 NX> 703 Session type: unix-gnome nxnode_reader: NX> 706 Agent cookie: 331206324b12d4063f2d05078b623ea6 nxnode_reader: NX> 704 Session cache: unix-gnome server_nxnode_echo: NX> 701 Proxy cookie: 331206324b12d4063f2d05078b623ea6 nxnode_reader: NX> 707 SSL tunneling: 1 server_nxnode_echo: NX> 702 Proxy IP: 192.168.11.150 NX> 701 Proxy cookie: 331206324b12d4063f2d05078b623ea6 NX> 702 Proxy IP: 192.168.11.150 server_nxnode_echo: NX> 706 Agent cookie: 331206324b12d4063f2d05078b623ea6 server_nxnode_echo: NX> 704 Session cache: unix-gnome server_nxnode_echo: NX> 707 SSL tunneling: 1 NX> 706 Agent cookie: 331206324b12d4063f2d05078b623ea6 NX> 704 Session cache: unix-gnome NX> 707 SSL tunneling: 1 nxnode_reader: /usr/libexec/nx/nxnode: 606 行:  3359 Terminated              PATH="$PATH_BIN:$PATH" $COMMAND_NXAGENT $P $R -name "NX - $user@$SERVER_NAME:$display - $session (GPL Edition)" -option "$USER_FAKE_HOME/.nx/C-$sess_id/options" $B $FP $AGENT_EXTRA_OPTIONS_X :$display 2>&3 /usr/libexec/nx/nxnode: 606 行:  3359 Terminated              PATH="$PATH_BIN:$PATH" $COMMAND_NXAGENT $P $R -name "NX - $user@$SERVER_NAME:$display - $session (GPL Edition)" -option "$USER_FAKE_HOME/.nx/C-$sess_id/options" $B $FP $AGENT_EXTRA_OPTIONS_X :$display 2>&3 nxnode_reader: NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/hattori/.nx/F-C-fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D/session". You might also want to try: ssh -X myserver; /usr/libexec/nx/nxnode --agent to test the basic functionality. Session log follows: NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/hattori/.nx/F-C-fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D/session". You might also want to try: ssh -X myserver; /usr/libexec/nx/nxnode --agent to test the basic functionality. Session log follows: NX> 105 nxnode_reader: xrdb: Connection refused xrdb: Connection refused nxnode_reader: xrdb: Can't open display ':3000' xrdb: Can't open display ':3000' nxnode_reader: nxnode_reader: ** (gnome-session:3381): WARNING **: ディスプレイをオープンできません: ** (gnome-session:3381): WARNING **: ディスプレイをオープンできません: nxnode_reader: NX> 1006 Session status: closed NX> 1006 Session status: closed server_nxnode_echo: NX> 596 Session startup failed. NX> 596 Session startup failed. server_nxnode_echo: NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/hattori/.nx/F-C-fc16.localdomain-3000-8041B6AC6751F47AD9EF47BC2DA52E8D/session". You might also want to try: ssh -X myserver; /usr/libexec/nx/nxnode --agent to test the basic functionality. Session log follows: session_close 8041B6AC6751F47AD9EF47BC2DA52E8D server_nxnode_echo: NX> 1006 Session status: closed nxnode_reader: NX> 1001 Bye. NX> 1001 Bye. server_nxnode_echo: NX> 1001 Bye. Info: Closing connection to slave with pid 2754. Info: Closing connection to slave with pid 2754.

[root@fc16 failed]# pwd /var/lib/nxserver/db/failed [root@fc16 failed]# [root@fc16 failed]# cat sessionId{8041B6AC6751F47AD9EF47BC2DA52E8D} sessionName=Fedora16 notebook display=3000 status=Failed startTime=1329407510 foreignAddress=192.168.11.5 sessionRootlessMode=0 type=unix-gnome sessionId=8041B6AC6751F47AD9EF47BC2DA52E8D creationTime=1329407510 userName=hattori serverPid= screeninfo=1024x768x32+render geometry=1024x768 host=127.0.0.1 shadowcookie=none

after removing /home/hattori/.nx/* directory , I can connect to the Fedora.

[root@fc16 .nx]# rm -rf * [root@fc16 .nx]# ls

nnn , strange behavior … I use same display number ( :3000 )
cache problem ???

[root@fc16 ~]# cat /var/log/nx/nxserver.log -- NX SERVER START: -c /usr/libexec/nx/nxserver - ORIG_COMMAND= -- NX SERVER START:  - ORIG_COMMAND= Info: Using fds #4 and #3 for communication with nxnode. HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) NX> 105 hello NXCLIENT - Version 3.2.0 NX> 134 Accepted protocol: 3.2.0 NX> 105 SET SHELL_MODE SHELL NX> 105 SET AUTH_MODE PASSWORD NX> 105 login NX> 101 User: hattori NX> 102 Password: Info: Auth method: ssh hattori@127.0.0.1's password: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) NX> 716 Slave mode started successfully. nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) nxnode_reader: NX> 716 finished nxnode_reader: NX> 1001 Bye. NX> 103 Welcome to: fc16.localdomain user: hattori NX> 105 listsession --user="hattori" --status="suspended,running" --geometry="1280x1024x32+render" --type="unix-gnome" NX> 127 Sessions list of user 'hattori' for reconnect: Display Type             Session ID                       Options  Depth Screen         Status      Session Name ------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------ NX> 148 Server capacity: not reached for user: hattori NX> 105 startsession  --link="lan" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="Fedora16%20notebook" --type="unix-gnome" --geometry="1024x768" --client="winnt" --keyboard="pc105/us" --screeninfo="1024x768x32+render" &link=lan&backingstore=1&encryption=1&cache=16M&images=64M&shmem=1&shpix=1&strict=0&composite=1&media=0&session=Fedora16 notebook&type=unix-gnome&geometry=1024x768&client=winnt&keyboard=pc105/us&screeninfo=1024x768x32+render&clientproto=3.2.0&login_method=SSH&user=hattori&userip=192.168.11.5&uniqueid=6F2CB10EAF10D873348ECE739A042D6F&display=3000&host=127.0.0.1 nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) server_nxnode_echo: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0) nxnode_reader: NX> 700 Session id: fc16.localdomain-3000-6F2CB10EAF10D873348ECE739A042D6F nxnode_reader: NX> 705 Session display: 3000 server_nxnode_echo: NX> 700 Session id: fc16.localdomain-3000-6F2CB10EAF10D873348ECE739A042D6F nxnode_reader: NX> 703 Session type: unix-gnome NX> 700 Session id: fc16.localdomain-3000-6F2CB10EAF10D873348ECE739A042D6F nxnode_reader: NX> 701 Proxy cookie: 766f194bee78d16500ccd0c2f201a260 server_nxnode_echo: NX> 705 Session display: 3000 nxnode_reader: NX> 702 Proxy IP: 192.168.11.150 server_nxnode_echo: NX> 703 Session type: unix-gnome nxnode_reader: NX> 706 Agent cookie: 766f194bee78d16500ccd0c2f201a260 NX> 705 Session display: 3000 NX> 703 Session type: unix-gnome nxnode_reader: NX> 704 Session cache: unix-gnome server_nxnode_echo: NX> 701 Proxy cookie: 766f194bee78d16500ccd0c2f201a260 nxnode_reader: NX> 707 SSL tunneling: 1 server_nxnode_echo: NX> 702 Proxy IP: 192.168.11.150 NX> 701 Proxy cookie: 766f194bee78d16500ccd0c2f201a260 NX> 702 Proxy IP: 192.168.11.150 server_nxnode_echo: NX> 706 Agent cookie: 766f194bee78d16500ccd0c2f201a260 server_nxnode_echo: NX> 704 Session cache: unix-gnome server_nxnode_echo: NX> 707 SSL tunneling: 1 NX> 706 Agent cookie: 766f194bee78d16500ccd0c2f201a260 NX> 704 Session cache: unix-gnome NX> 707 SSL tunneling: 1 nxnode_reader: NX> 1009 Session status: starting NX> 1009 Session status: starting server_nxnode_echo: NX> 1009 Session status: starting nxnode_reader: NX> 710 Session status: running nxnode_reader: NX> 1002 Commit nxnode_reader: NX> 1006 Session status: running NX> 710 Session status: running NX> 1002 Commit NX> 1006 Session status: running server_nxnode_echo: NX> 710 Session status: running server_nxnode_echo: NX> 1002 Commit NX> 105 session_status 6F2CB10EAF10D873348ECE739A042D6F Running server_nxnode_echo: NX> 1006 Session status: running bye Bye NX> 999 Bye