Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › Fresh Install of Fedora 14 Very Sluggish
New Posts  All Forums:Forum Nav:

Fresh Install of Fedora 14 Very Sluggish - Page 3

post #21 of 35
Just use any distro, it's mainly the software that you'll be using that you want to get used to. Such as a LAMP setup or something, that's what really counts.
Current Rig
(14 items)
 
  
CPUMotherboardGraphicsRAM
FX-8350 4.6GHz@1.44v GA-990FXA-UD3 R4.0 HD 7950 (1100/1450) 8G Muskin DDR3 1866@8CLS 
Hard DriveOptical DriveOSMonitor
1TB WD LiteOn DVD-RW DL Linux/Windows 19" Phillips TV 1080p 
PowerCaseMouseMouse Pad
OCZ 600W Generic Junk Logitech MX400 Generic Junk 
Audio
SBL 5.1 
  hide details  
Reply
Current Rig
(14 items)
 
  
CPUMotherboardGraphicsRAM
FX-8350 4.6GHz@1.44v GA-990FXA-UD3 R4.0 HD 7950 (1100/1450) 8G Muskin DDR3 1866@8CLS 
Hard DriveOptical DriveOSMonitor
1TB WD LiteOn DVD-RW DL Linux/Windows 19" Phillips TV 1080p 
PowerCaseMouseMouse Pad
OCZ 600W Generic Junk Logitech MX400 Generic Junk 
Audio
SBL 5.1 
  hide details  
Reply
post #22 of 35
Quote:
Originally Posted by mushroomboy View Post
Just use any distro, it's mainly the software that you'll be using that you want to get used to. Such as a LAMP setup or something, that's what really counts.
that's true to a certain extent, especially if the job requires mostly application administration. however, if it involves OS specific stuff, it would be advantageous to learn about the distro specific management styles. For example, learning yum/rpm (RHEL/CentOS) vs apt/dpkg (Debian) vs pkgadd (Solaris)... are all very different and require some knowledge/experience if you're going to do anything beyond basic package install/uninstall such as resolving dependency issues, verifying signatures, querying file ownership, etc.
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
post #23 of 35
Quote:
Originally Posted by BLinux View Post
that's true to a certain extent, especially if the job requires mostly application administration. however, if it involves OS specific stuff, it would be advantageous to learn about the distro specific management styles. For example, learning yum/rpm (RHEL/CentOS) vs apt/dpkg (Debian) vs pkgadd (Solaris)... are all very different and require some knowledge/experience if you're going to do anything beyond basic package install/uninstall such as resolving dependency issues, verifying signatures, querying file ownership, etc.
Yes and no, most package management systems are all about the same. Mainly you have to learn the file paths. Although RPMs have a very different structure, if you know basic linux structure it's not hard to figure things out. The main part is learning where things go, the differences between /usr /var /opt /lib ect... That and how the OS structures system components. Although most administration for any server station is going to generally be easy as far as the system goes, as most server based software tends to be updated less unless it's for security to keep stability up.

[edit] Don't get me wrong though, you are right, if he is going to be using RH/Fedora for his work he should definitely use it to be familiar. He can still get similar knowledge using another distro and software though.
Edited by mushroomboy - 1/2/11 at 6:47pm
Current Rig
(14 items)
 
  
CPUMotherboardGraphicsRAM
FX-8350 4.6GHz@1.44v GA-990FXA-UD3 R4.0 HD 7950 (1100/1450) 8G Muskin DDR3 1866@8CLS 
Hard DriveOptical DriveOSMonitor
1TB WD LiteOn DVD-RW DL Linux/Windows 19" Phillips TV 1080p 
PowerCaseMouseMouse Pad
OCZ 600W Generic Junk Logitech MX400 Generic Junk 
Audio
SBL 5.1 
  hide details  
Reply
Current Rig
(14 items)
 
  
CPUMotherboardGraphicsRAM
FX-8350 4.6GHz@1.44v GA-990FXA-UD3 R4.0 HD 7950 (1100/1450) 8G Muskin DDR3 1866@8CLS 
Hard DriveOptical DriveOSMonitor
1TB WD LiteOn DVD-RW DL Linux/Windows 19" Phillips TV 1080p 
PowerCaseMouseMouse Pad
OCZ 600W Generic Junk Logitech MX400 Generic Junk 
Audio
SBL 5.1 
  hide details  
Reply
post #24 of 35
Thread Starter 
Quote:
Originally Posted by BLinux View Post
Did telnet work for 445/TCP? I'm asking because based on the sniffer output, the 3-way handshake on 445/TCP never competed... a syn packet is sent, and never gets the syn-ack.

I'm assuming 192.168.1.103 is the client and 208.68.143.55 is the server? (i'm basing my assumption on the DNS query and the 445/TCP connection attempt.

Get 445/TCP working first... it needs to at least get a TCP RST packet for the SMB client to give up on 445/TCP and re-try on 139/TCP... or just connect on 445/TCP (samba is capable of that)
No, the server is 192.168.1.100. There isn't anything in the logs showing it aside from a ping I ran concurrently to trying to mount the SAMBA share.

I'll try 445 once I get home tonight.
    
CPUMotherboardGraphicsRAM
Core i7 970 @ 4.0 GHz 1.22 Vcore Asus Rampage II Gene GTX 260 216SP G.SKILL PI 3x2gb DDR3 1600 @ 7-8-7-24 
Hard DriveOSMonitorPower
2x 500gb Seagates RAID 0, 1x 500gb non-RAID Windows 7 Professional x64 ASUS 24'' VH242H / Spectre 24'' WS Corsair 750TX 
Case
Corsair 300R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Core i7 970 @ 4.0 GHz 1.22 Vcore Asus Rampage II Gene GTX 260 216SP G.SKILL PI 3x2gb DDR3 1600 @ 7-8-7-24 
Hard DriveOSMonitorPower
2x 500gb Seagates RAID 0, 1x 500gb non-RAID Windows 7 Professional x64 ASUS 24'' VH242H / Spectre 24'' WS Corsair 750TX 
Case
Corsair 300R 
  hide details  
Reply
post #25 of 35
Thread Starter 
Quote:
Get 445/TCP working first... it needs to at least get a TCP RST packet for the SMB client to give up on 445/TCP and re-try on 139/TCP... or just connect on 445/TCP (samba is capable of that)
Connecting via 445 hangs forever. I've gone so far as to set a chain in iptables to accept any source to any destination and it still hasn't resolved it.

Thoughts?
    
CPUMotherboardGraphicsRAM
Core i7 970 @ 4.0 GHz 1.22 Vcore Asus Rampage II Gene GTX 260 216SP G.SKILL PI 3x2gb DDR3 1600 @ 7-8-7-24 
Hard DriveOSMonitorPower
2x 500gb Seagates RAID 0, 1x 500gb non-RAID Windows 7 Professional x64 ASUS 24'' VH242H / Spectre 24'' WS Corsair 750TX 
Case
Corsair 300R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Core i7 970 @ 4.0 GHz 1.22 Vcore Asus Rampage II Gene GTX 260 216SP G.SKILL PI 3x2gb DDR3 1600 @ 7-8-7-24 
Hard DriveOSMonitorPower
2x 500gb Seagates RAID 0, 1x 500gb non-RAID Windows 7 Professional x64 ASUS 24'' VH242H / Spectre 24'' WS Corsair 750TX 
Case
Corsair 300R 
  hide details  
Reply
post #26 of 35
Quote:
Originally Posted by TurboTurtle View Post
Connecting via 445 hangs forever. I've gone so far as to set a chain in iptables to accept any source to any destination and it still hasn't resolved it.

Thoughts?
Ok, that's the problem... 445/TCP isn't getting through at all.. it needs to at least get a TCP RST or an actual connection... without even a TCP RST packet, it will just hang and doesn't timeout and move on to 139/TCP.

Drop all iptables rules on the client machine and server (iptables -F INPUT, iptables -F OUTPUT) or on Fedora "/sbin/service iptables stop".
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
post #27 of 35
Thread Starter 
Quote:
Originally Posted by BLinux View Post
Ok, that's the problem... 445/TCP isn't getting through at all.. it needs to at least get a TCP RST or an actual connection... without even a TCP RST packet, it will just hang and doesn't timeout and move on to 139/TCP.

Drop all iptables rules on the client machine and server (iptables -F INPUT, iptables -F OUTPUT) or on Fedora "/sbin/service iptables stop".
Done. No change.

Interesting fact: nmap reports port 445/TCP open server side.

So..with anything capable of blocking the port(s) being disabled...what the heck could be causing this?
    
CPUMotherboardGraphicsRAM
Core i7 970 @ 4.0 GHz 1.22 Vcore Asus Rampage II Gene GTX 260 216SP G.SKILL PI 3x2gb DDR3 1600 @ 7-8-7-24 
Hard DriveOSMonitorPower
2x 500gb Seagates RAID 0, 1x 500gb non-RAID Windows 7 Professional x64 ASUS 24'' VH242H / Spectre 24'' WS Corsair 750TX 
Case
Corsair 300R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Core i7 970 @ 4.0 GHz 1.22 Vcore Asus Rampage II Gene GTX 260 216SP G.SKILL PI 3x2gb DDR3 1600 @ 7-8-7-24 
Hard DriveOSMonitorPower
2x 500gb Seagates RAID 0, 1x 500gb non-RAID Windows 7 Professional x64 ASUS 24'' VH242H / Spectre 24'' WS Corsair 750TX 
Case
Corsair 300R 
  hide details  
Reply
post #28 of 35
Quote:
Originally Posted by TurboTurtle View Post
Done. No change.

Interesting fact: nmap reports port 445/TCP open server side.

So..with anything capable of blocking the port(s) being disabled...what the heck could be causing this?
can you run the following commands on *both* server and client and post them?

/sbin/ip addr show
/sbin/ip route show
netstat -tnlp
iptables -vnL

thanks....
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
post #29 of 35
Thread Starter 
Quote:
Originally Posted by BLinux View Post
can you run the following commands on *both* server and client and post them?

/sbin/ip addr show
/sbin/ip route show
netstat -tnlp
iptables -vnL

thanks....

Sorry for the delay, been incredibly busy the last two days.

Logs are in the RAR archive attached. Everything named appropriately.

Thanks.
    
CPUMotherboardGraphicsRAM
Core i7 970 @ 4.0 GHz 1.22 Vcore Asus Rampage II Gene GTX 260 216SP G.SKILL PI 3x2gb DDR3 1600 @ 7-8-7-24 
Hard DriveOSMonitorPower
2x 500gb Seagates RAID 0, 1x 500gb non-RAID Windows 7 Professional x64 ASUS 24'' VH242H / Spectre 24'' WS Corsair 750TX 
Case
Corsair 300R 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Core i7 970 @ 4.0 GHz 1.22 Vcore Asus Rampage II Gene GTX 260 216SP G.SKILL PI 3x2gb DDR3 1600 @ 7-8-7-24 
Hard DriveOSMonitorPower
2x 500gb Seagates RAID 0, 1x 500gb non-RAID Windows 7 Professional x64 ASUS 24'' VH242H / Spectre 24'' WS Corsair 750TX 
Case
Corsair 300R 
  hide details  
Reply
post #30 of 35
Quote:
Originally Posted by TurboTurtle View Post
Sorry for the delay, been incredibly busy the last two days.

Logs are in the RAR archive attached. Everything named appropriately.

Thanks.
No problem. I looked over the files....

are you actively using IPv6? I noticed something a little strange, and I'm wondering if you can disable IPv6 and see if anything changes? The server's netstat -tnpl is:

tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1178/portmap
tcp 0 0 0.0.0.0:45264 0.0.0.0:* LISTEN 1485/rpc.mountd
tcp 0 0 0.0.0.0:4242 0.0.0.0:* LISTEN 3365/sshd
tcp 0 0 192.168.86.1:53 0.0.0.0:* LISTEN 1705/named
tcp 0 0 192.168.35.1:53 0.0.0.0:* LISTEN 1705/named
tcp 0 0 0.0.0.0:4949 0.0.0.0:* LISTEN 2864/munin-node
tcp 0 0 192.168.1.100:53 0.0.0.0:* LISTEN 1705/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 1705/named
tcp 0 0 0.0.0.0:58677 0.0.0.0:* LISTEN 1191/rpc.statd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 3365/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1888/cupsd
tcp 0 0 0.0.0.0:3128 0.0.0.0:* LISTEN 2018/(squid)
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2787/exim4
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 1705/named
tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:56867 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:548 0.0.0.0:* LISTEN 2054/afpd
tcp 0 0 0.0.0.0:901 0.0.0.0:* LISTEN 2024/inetd
tcp 0 0 192.168.1.100:9095 0.0.0.0:* LISTEN 1526/python
tcp 0 0 192.168.1.100:9001 0.0.0.0:* LISTEN 1526/python
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 2345/mysqld
tcp6 0 0 :::80 :::* LISTEN 1647/apache2
tcp6 0 0 :::4242 :::* LISTEN 3365/sshd
tcp6 0 0 :::21 :::* LISTEN 15180/proftpd: (acc
tcp6 0 0 :::53 :::* LISTEN 1705/named
tcp6 0 0 :::22 :::* LISTEN 3365/sshd
tcp6 0 0 ::1:631 :::* LISTEN 1888/cupsd
tcp6 0 0 ::1:25 :::* LISTEN 2787/exim4
tcp6 0 0 ::1:953 :::* LISTEN 1705/named
tcp6 0 0 ::1:4700 :::* LISTEN 2052/cnid_metad
tcp6 0 0 :::445 :::* LISTEN 19146/smbd
tcp6 0 0 :::9090 :::* LISTEN 1647/apache2
tcp6 0 0 :::139 :::* LISTEN 19146/smbd

Notice how 139/TCP and 445/TCP are only listed under tcp6 and not normal "tcp" ... I'm not sure exactly "why" that is, but it would be nice to see those ports under "tcp"... and I'm wondering if disabling IPv6 and restarting the service would do that. Can you give that a try?
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux, Unix
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › Fresh Install of Fedora 14 Very Sluggish