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 2

post #11 of 35
Thread Starter 
Quote:
Originally Posted by Rookie1337 View Post
Now, do you have the SAMBA package in Fedora(forgive me if I'm asking the blatantly obvious I've never used the program)? I can't recall if it came by default in Fedora.

General Question: Are there any terminal commands that he could use to spit out errors or conflicts?
Fedora doesn't by default, but it's one of the first packages I installed. However, the problem is deeper than SAMBA - Fedora is simply not seeing the server, or a possible converse, the server is not responding to Fedora.

The server is at 192.168.1.100. I can reach it fine from any other machine/OS on the network. However, I cannot even ping it from my Fedora install. I tried adding a static route to the server however that has also resulted in the same.
    
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 #12 of 35
Greetz
Again I don;t know Fedora but considering it inherits from RedHat Enterprise it could be that it also inherits an abnormally secure firewall. Check iptables. If you don;t know iptables you could employ a frontend like Firestarter or Guarddog to check or change settings. It is fairly common to disallow ping by default.

As for hard drives you should run "hdparm -i" on the drive to see if it is set by default at high performance. It is not too uncommon to find a few settings set low such as 16 bit addressing instead of 32. If it is set low you can change it with hdparm.
NewMain
(16 items)
 
  
CPUMotherboardGraphicsRAM
Intel i5 - 3550 Asrock Z77 Extreme4 Gigabyte GTX 760  4x2GB Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Seagate SATA 2TB x 2  Plextor PX-891SAW CM-Hyper N520 Slackware 14, Studio KUbuntu, OpenSuSe 12.3, Wi... 
MonitorKeyboardPowerCase
32" Vizio HDTV + DLP Logitech Wireless Corsair HX-850 Antec Sonata I 
MouseMouse PadAudioOther
Razer DeathAdder 2013 dual ESI Juli@ CoolGear ExtSata Enclosure w/ Optical and 3TB S... 
  hide details  
Reply
NewMain
(16 items)
 
  
CPUMotherboardGraphicsRAM
Intel i5 - 3550 Asrock Z77 Extreme4 Gigabyte GTX 760  4x2GB Corsair Vengeance 
Hard DriveOptical DriveCoolingOS
Seagate SATA 2TB x 2  Plextor PX-891SAW CM-Hyper N520 Slackware 14, Studio KUbuntu, OpenSuSe 12.3, Wi... 
MonitorKeyboardPowerCase
32" Vizio HDTV + DLP Logitech Wireless Corsair HX-850 Antec Sonata I 
MouseMouse PadAudioOther
Razer DeathAdder 2013 dual ESI Juli@ CoolGear ExtSata Enclosure w/ Optical and 3TB S... 
  hide details  
Reply
post #13 of 35
Thread Starter 
Update: Disabled SELinux, and I can now access public content from my dyndns account and can SSH into the server from Fedora, however I am still unable to see it on the network, or mount any of the SAMBA shares.
    
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 #14 of 35
Thread Starter 
Getting rather frustrated now. I've also completely disabled the firewall just to see if that was messing something up, but I still can't access the shares.

Whenever I try to mount the shares using:
Code:
mount.cifs //<server>/  /mnt/Smb -o user=turtle
To list all the shares, or if I change it to //<server>/<share>, I get prompted for a password, but no matter what I enter, whether the password is correct or if I just enter a random strong, terminal just hangs at that prompt forever.


ARGH!!!
    
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 #15 of 35
wow... all sorts of scary stuff here....

first of all, a corrupted ISO will likely never install... the rpm installation process has a built-in checksum (along with signature checking). if a RPM is corrupted, it will error out. your initial "slowness" problem was likely rooted in something else, but that doesn't matter now...

first of all, have you verified network connectivity up to layer 3? start at the bottom and move up... if you ping the server, does layer 2 show the proper mac addresses? (run /sbin/arp -an). Does the ping actually get a response? If not, fire up tcpdump on both sides and observe the traffic and troubleshoot...

if you get up to layer 3 working, next figure out if TCP is working... telnet to port 139/TCP and see if you get a complete 3-way handshake.

if you have TCP working, now check the application layer. Make sure your samba server is logging correctly and observe the logs when you try to connect. it will likely tell you why it isn't connecting.

always troubleshoot from the bottom up....
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 #16 of 35
Thread Starter 
Quote:
Originally Posted by BLinux View Post

first of all, have you verified network connectivity up to layer 3? start at the bottom and move up... if you ping the server, does layer 2 show the proper mac addresses? (run /sbin/arp -an). Does the ping actually get a response? If not, fire up tcpdump on both sides and observe the traffic and troubleshoot...

if you get up to layer 3 working, next figure out if TCP is working... telnet to port 139/TCP and see if you get a complete 3-way handshake.
Yes, after disabling SELinux, I can ping the server and get the MAC address fine. I can also SSH into the server just fine.

Quote:
if you have TCP working, now check the application layer. Make sure your samba server is logging correctly and observe the logs when you try to connect. it will likely tell you why it isn't connecting.

always troubleshoot from the bottom up....

After checking /var/log/samba/smbd.log and /var/log/samba/samba.log there is nothing of interest. The only thing shown as an error is a 'Connection reset by peer' line, by the time stamps all line up with when I was using my Win 7 install to make sure it wasn't just Fedora, and then issued a reboot command to the server.

I.E. - nothing in the logs. This is what appears in Dolphin after disabling both SELinux and the firewall entirely (yes, the sever's name is Syrup. Inside joke.):



And I cannot get any further. CLI mounting still results in a hung terminal (with nothing appearing in the logs) and I'm getting a bit more frustrated. Everything else with this install has gone somewhat smoothly after the initial re-install, but this is just becoming a bit of a migraine.
    
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 #17 of 35
Quote:
Originally Posted by TurboTurtle View Post
After checking /var/log/samba/smbd.log and /var/log/samba/samba.log there is nothing of interest. The only thing shown as an error is a 'Connection reset by peer' line, by the time stamps all line up with when I was using my Win 7 install to make sure it wasn't just Fedora, and then issued a reboot command to the server.
Ok, can you make sure you have an entry like this in your smb.conf file:

log file = /var/log/samba/%m.log

this tells samba to create a log file *per* machine connecting. That way, you have a dedicated log file for the machine that is having issues. restart samba.

the other thing haven't told me is can you connect to TCP port 139? or TCP port 445? (using telnet or netcat)

finally, on your next connection attempt, can you run a tcpdump on both sides? do full packet capture and analyze them in wireshark or similar tool. Or, post them and I can download and take a look.
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 #18 of 35
Thread Starter 
Quote:
Originally Posted by BLinux View Post
Ok, can you make sure you have an entry like this in your smb.conf file:

log file = /var/log/samba/%m.log

this tells samba to create a log file *per* machine connecting. That way, you have a dedicated log file for the machine that is having issues. restart samba.
Done. Upon trying to connect again, the log file is created but is, however, empty.

Quote:
the other thing haven't told me is can you connect to TCP port 139? or TCP port 445? (using telnet or netcat)

finally, on your next connection attempt, can you run a tcpdump on both sides? do full packet capture and analyze them in wireshark or similar tool. Or, post them and I can download and take a look.

Telnet works fine.

Ran tcpdump on both sides. Server side, the file is empty. Client (Fedora) side generated a few entries, it's attached if you want to take a look.
    
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 #19 of 35
Quote:
Originally Posted by TurboTurtle View Post
Telnet works fine.

Ran tcpdump on both sides. Server side, the file is empty. Client (Fedora) side generated a few entries, it's attached if you want to take a look.
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)
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 #20 of 35
Quote:
Originally Posted by TurboTurtle View Post
I want to get accustom to a Red Hat-based distro for a possible job in the near future.
Are they Redhat desktops or headless Redhat servers?

Running Fedora isn't really going to help if they are using headless Redhat servers, and it doesn't really give you a proper RHEL experience for desktop either.

Go HERE and register and you'll be given an evaluation licence (it's free) and then just select "download software" to download a 30 day trial version of whatever Redhat Enterprise Linux you are going to use at your new job (ie. RHEL Server, RHEL AS, RHEL ES, RHEL WS).

Crimson Basilisk
(25 items)
 
  
CPUMotherboardGraphicsGraphics
Intel i7 2600K @ 5.1Ghz AsRock Extreme4 Gen3 Palit GTX 680 Jetstream 2GB Palit GTX 680 Jetstream 2GB 
RAMRAMHard DriveHard Drive
G.Skill F3-12800CL9D-8GBXL G.Skill F3-12800CL9D-8GBXL Sandisk Extreme 120GB SSD Sandisk Extreme 120GB SSD 
Hard DriveOptical DriveCoolingCooling
WD Caviar "Black" 1TB SATAII LG WH14NS40 Blu-ray Burner XSPC Rasa CPU (Acetal) Black RX360 Triple Fan Radiator 
CoolingCoolingOSMonitor
XSPC DDC Two BayRes BMaverick Laing DDC (MCP350) Windows 7 Ultimate x64 Philips 201B 21" CRT 
MonitorKeyboardPowerCase
ViewSonic VX922 19" LCD Diamond Digital Black Antec True Power 750w Antec LanBoy Air Red 
MouseMouse PadAudioOther
Epic Gear Meduza (By GEIL) Steel Series QCK+ XL Asus Xonar DX ROCCAT Kave 5.1 Surround Sound Gaming Headset 
Other
Sennheiser hd555 
  hide details  
Reply
Crimson Basilisk
(25 items)
 
  
CPUMotherboardGraphicsGraphics
Intel i7 2600K @ 5.1Ghz AsRock Extreme4 Gen3 Palit GTX 680 Jetstream 2GB Palit GTX 680 Jetstream 2GB 
RAMRAMHard DriveHard Drive
G.Skill F3-12800CL9D-8GBXL G.Skill F3-12800CL9D-8GBXL Sandisk Extreme 120GB SSD Sandisk Extreme 120GB SSD 
Hard DriveOptical DriveCoolingCooling
WD Caviar "Black" 1TB SATAII LG WH14NS40 Blu-ray Burner XSPC Rasa CPU (Acetal) Black RX360 Triple Fan Radiator 
CoolingCoolingOSMonitor
XSPC DDC Two BayRes BMaverick Laing DDC (MCP350) Windows 7 Ultimate x64 Philips 201B 21" CRT 
MonitorKeyboardPowerCase
ViewSonic VX922 19" LCD Diamond Digital Black Antec True Power 750w Antec LanBoy Air Red 
MouseMouse PadAudioOther
Epic Gear Meduza (By GEIL) Steel Series QCK+ XL Asus Xonar DX ROCCAT Kave 5.1 Surround Sound Gaming Headset 
Other
Sennheiser hd555 
  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