Jun
23
2013
0

Fedora 15, 16, 17, 18 missing system-config-network GUI – SOLVED

Recently Fedora has been a nightmare for me. Anyone that’s seen(the fairly new) GNOME 3 knows what I’m talking about.  Their design team must have dreamed up the next iteration of GNOME with only a tablet in mind.  The giant icons and dependency on keyboard shortcuts make it a must for a 7″ inch screen and a few swipes.

For daily use on desktop computers at work GNOME 3 is garbage though – everyone hates it. It’s barely better than the Windows 8 interface.  I’m sorry; yeah I went there, and I only say that because Microsoft jammed all those tiles and the desktop into the same freaking UI.  Even GNOME 3 designers missed that pit of snakes!

But happy days are here again! I have found(with some tweaking) the MATE Desktop offers a very similar but updated version of the GNOME 2 desktop I loved in Fedora 14.  One nagging problem is that I hate NetworkManager for server use.  It’s okay for laptops, but when I need to custom edit some interfaces for a Asterisk PBX or Virtual Server I want the good ol’ ‘system-config-network’ over a SSH -X session.  After a quick ‘yum install system-config-network’ I thought I was in business… only to discover that only the command line version was installed.  After a little googling I discovered a utility that could download the source package.  I rebuilt the package with ‘–with gui’ switch as suggested on a forum.  The result produced the ‘system-config-network-tui-1.6.10-1.fc18.noarch.rpm’.  I installed the packaged and the GUI works! This tutorial uses Fedora 18, but could be adapted for 15,16,17, and 19.

(more…)

Jul
02
2010
2

Fedora 13 mount Error Solved

I recently upgraded to Fedora 13(and was quite pleased) only to discover my backup SATA drive would not mount.  I got the generic, ‘mount: /dev/sdb1 already mounted or /home/matt/backup busy’ error message.  Hours of googling and one reinstall later I solved the problem.

Goals of this Post:

– Fix SATA drive mount error: mount: /dev/sdb1 already mounted or /home/matt/backup busy

(more…)

Feb
28
2009
0

UPDATE: Using Multiple interfaces with KVM and Xen

I had a system crash with blinking keyboard lights. The error has something to do with either ACPI power states or the bridge interface. On my system setting br1 to DHCP causes some kind of issue when using DHCP, here is my log:

Feb 26 03:25:29 mattcom1 dhclient: DHCPREQUEST on br1 to 255.255.255.255 port 67
Feb 26 03:25:29 mattcom1 ntpd[2188]: Listening on interface #22 eth0_rename, 192.168.1.254#123 Enabled
Feb 26 03:25:29 mattcom1 avahi-daemon[2374]: Registering new address record for fe80::20a:5eff:fe45:7eca on eth1.*.
Feb 26 03:25:30 mattcom1 avahi-daemon[2374]: Registering new address record for fe80::20a:5eff:fe45:7eca on br1.*.
Feb 26 03:25:31 mattcom1 ntpd[2188]: Listening on interface #23 br1, fe80::20a:5eff:fe45:7eca#123 Enabled
Feb 26 03:25:32 mattcom1 dhclient: DHCPREQUEST on br1 to 255.255.255.255 port 67
Feb 26 03:25:32 mattcom1 kernel: ————[ cut here ]————
Feb 26 03:25:32 mattcom1 kernel: WARNING: at net/core/dev.c:1505 skb_gso_segment+0×6e/0×153() (Tainted: P )
Feb 26 03:25:32 mattcom1 kernel: Hardware name:
Feb 26 03:25:32 mattcom1 kernel: Modules linked in: sit tunnel4 udf fuse bridge stp bnep sco l2cap bluetooth sunrpc ipv6 cpufreq_ondemand acpi
_cpufreq dm_multipath kvm_intel kvm uinput snd_ens1371 gameport snd_rawmidi snd_ac97_codec ac97_bus nvidia(P) snd_seq_dummy snd_seq_oss snd_se
q_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd iTCO_wdt e1000e iTCO_vendor_support soundcore ppdev 3c59x
firewire_ohci snd_page_alloc firewire_core i2c_i801 parport_pc mii floppy parport i2c_core pcspkr crc_itu_t ata_generic pata_acpi sha256_gener
ic cbc aes_i586 aes_generic dm_crypt crypto_blkcipher [last unloaded: microcode]

then later…

Feb 26 03:52:06 mattcom1 kernel: qemu-kvm[10261]: segfault at 1df ip 080afcb8 sp bfed6898 error 4 in qemu-kvm[8047000+175000]
Feb 26 03:52:06 mattcom1 avahi-daemon[2374]: Withdrawing address record for fe80::3c3b:13ff:fedb:cfcb on vnet0.
Feb 26 03:52:06 mattcom1 kernel: br1: port 2(vnet0) entering disabled state
Feb 26 03:52:06 mattcom1 kernel: device vnet0 left promiscuous mode
Feb 26 03:52:06 mattcom1 kernel: br1: port 2(vnet0) entering disabled state
Feb 26 03:52:07 mattcom1 ntpd[2188]: Deleting interface #27 vnet0, fe80::3c3b:13ff:fedb:cfcb#123, interface stats: received=0, sent=0, dropped
=0, active_time=1289 secs

So I set br1 to a static IP and seems to work, though since it is a bridge I don’t see why it needs an IP address anyways… so turn it off by editing the bridge and the real interface to have no IP.

-Matt

/etc/sysconfig/network-scripts/ifcfg-br:

DEVICE=br1
TYPE=Bridge
ONBOOT=yes
BOOTPROTO=static
NM_CONTROLLED=no

Dec
09
2008
14

FreeNX failure in Fedora 9 + 10 default setup SOLVED

I’ve been having a bunch of problems with FreeNX since an upgrade in Fedora 8.  Since then I have not been able to get the default setup to work on fedora 9 or 10.  The problem is that the logs from FreeNX and Nomachine indicate several errors totally unrelated to the connection failure.

Here are the symptoms:

– SSH authentication successful

– DSA key passes fine

Nomachine log from Windows XP client:

NX> 203 NXSSH running with pid: 3308
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.1.254 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER – Version 3.2.0-73 OS (GPL, using backend: 3.2.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: mattnx
NX> 102 Password:
NX> 103 Welcome to: mattcom1 user: mattnx
NX> 105 listsession –user=”mattnx” –status=”suspended,running” –geometry=”1680x1050x32+render” –type=”unix-gnome”
NX> 127 Sessions list of user ‘mattnx’ for reconnect:

Display Type             Session ID                       Options  Depth Screen         Status      Session Name
——- —————- ——————————– ——– —– ————– ———– —————————–
NX> 148 Server capacity: not reached for user: mattnx
NX> 105 startsession  –link=”lan” –backingstore=”1″ –encryption=”1″ –cache=”16M” –images=”64M” –shmem=”1″ –shpix=”1″ –strict=”0″ –composite=”1″ –media=”0″ –session=”fedora10home” –type=”unix-gnome” –geometry=”1024×768″ –client=”winnt” –keyboard=”pc102/en_US” –screeninfo=”1024x768x32+render”
NX> 1000 NXNODE – Version 3.2.0-73 OS (GPL, using backend: 3.2.0)
NX> 700 Session id: mattcom1-1000-1C6F198B66C712B066D30A14269FD76E
NX> 705 Session display: 1000
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: 39a5af5faf2df5a8425bb311f873d83f
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 39a5af5faf2df5a8425bb311f873d83f
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 105 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/mattnx/.nx/F-C-mattcom1-1000-1C6F198B66C712B066D30A14269FD76E/session”. You might also want to try: ssh -X myserver; /usr/libexec/nx/nxnode –agent to test the basic functionality. Session log follows:
/usr/libexec/nx/nxserver: line 1531:  5052 Terminated              sleep $AGENT_STARTUP_TIMEOUT
NX> 1006 Session status: closed
Can’t open /var/lib/nxserver/db/running/sessionId{1C6F198B66C712B066D30A14269FD76E}: No such file or directory.
mv: cannot stat `/var/lib/nxserver/db/running/sessionId{1C6F198B66C712B066D30A14269FD76E}’: No such file or directory
NX> 1001 Bye.
/usr/libexec/nx/nxserver: line 562: kill: (4746) – No such process
NX> 280 Exiting on signal: 15

So every freenx forum under the sun advises you to run a couple commands to check your installation.  Let me point out that 90% of that advise is bullshit.  Doing a search for ‘$AGENT_STARTUP_TIMEOUT’ in google turns up many people concerned about this message.  The general advise for checking the server goes like this, “enable logging in the ‘/etc/nxserver/node.conf’, check output from ‘/usr/libexec/nx/nxagent’ command, check output from ‘/usr/libexec/nx/nxloadconfig –check’ command.”  Lets go through these one by one.

1.  Enable logging on the freenx server.

If you correctly installed your client DSA key you already probably know that the main configuration file for freenx is located in the ‘/etc/nxserver’ directory.  Freenx assumes the defaults unless you specifically edit the ‘node.conf.sample’ and save it as ‘node.conf’.

[root@mattcom1 nxserver]# ls /etc/nxserver/
client.id_dsa.key  node.conf~        server.id_dsa.pub.key  users.id_dsa.pub
node.conf          node.conf.sample  users.id_dsa

[root@mattcom1 nxserver]# nano node.conf.sample

#########################################################################
# Logging directives
#########################################################################
# This directives controls the verbosity of the server-wide log.
# 0: No Logging
# 1: Errors
# 2: Warnings
# 3: Important information
# 4: Server – Client communication
# 5: Information
# 6: Debugging information
# 7: stderror of some applications
NX_LOG_LEVEL=7
#
# By setting this to 0 the nxserver might be a bit faster, but passwords can be found in the log files.
NX_LOG_SECURE=1
#
# Before turning logging on, please make sure that NX_LOGFILE is
# writeable for the “nx” user
NX_LOGFILE=/var/log/nx/nxserver.log

Remember to make sure the ‘nx’ user has permissions to write logs to the specified directory.

3.  Testing nxagent

Freenx makes use of nxagent(a virtual xserver) that acts as a proxy for nx connections to open and manage remote X desktops.  Lets run the command and see if we get an error.

[root@mattcom1 nxserver]# nxagent
Error: Aborting session with ‘Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again’.
Session: Aborting session at ‘Tue Dec  9 01:19:04 2008’.
Session: Session aborted at ‘Tue Dec  9 01:19:04 2008’.

This got me thinking.  After a lot of dead leads attempting to solve a bogus command $PATH issue, I thought maybe nx was just fine and this was xorg or xserver issue.  So I double checked and installed additional xorg fonts.  Then I had a brain storm.  What if I log out of X to run level 3(command prompt)?  So I logged out of my Linux nxserver and attempted to open a freenx session from my windows xp client(nomachine).  It worked…  I realized that it worked the whole time as long you’re not logged into X windows on the server.

I began scouring the Nomachine NX documentation.  After doing some research I noticed that under the nxagent documentation virtual xserver connections where by default opened on TCP port 1000.  So I thought it was entirely reasonable that the real xserver might be opening a session on the same port causing a conflict between xorg xserver and the nxagent.

This proved to be correct.  I changed a directive in the node.conf to fix the problem.  I changed ‘DISPLAY_BASE=1000’ to ‘DISPLAY_BASE=1001’.  Now I can login to remote NX sessions even if the server running FreeNX has it’s desktop running.

Freenx now works!