1541 Views 12 Replies Latest reply: Oct 2, 2009 12:05 AM by mike.habermeier
Just throwing out some thoughts here...
Any other info in the Logs, like Applefileservice, Directoryservice, Application crash logs like Quark or PShop?
Have you cleared caches, fixed permissions and such? If not, I like Applejack...
After installing, reboot holding down CMD+s, then when the prompt shows, type in...
Then let it do all 5 of it's things.
At least it'll eliminate some questions if it doesn't fix it.
Tried tweaking the sysctl variables yet?
i have allready installed AppleJack. I installed AppleJack to all customers i work with.
After AppleJack it works for about a week or something. But this is only a sujective feeling from my own. Maybe caches i thougt.
I tweaked the Network parameters to half duplex, full duplex and so on. Not helping. In all the log files i can not see any other infos. not in the system.log or something else.
Thank your for your help. Maybe we can figure it out together. I really end up here
What do you mean with sysct variables ??
Sorry, poor eyesight when I typed sysct, meant... The sysctl variables like...
Not certain these work for Network, or just Internet !??
The settings shown below are given in a good faith there is not at all any guarantee that it will work perfectly for you.
Lets give it a try and run the following commands from the command line:
sysctl -w net.inet.tcp.delayed_ack=0
sysctl -w net.inet.tcp.mssdflt=1460
sysctl -w kern.ipc.maxsockbuf=131070
sysctl -w net.inet.tcp.sendspace=65535
sysctl -w net.inet.tcp.recvspace=65535
sysctl -w net.inet.tcp.newreno=1
A word on MTU or mssdflt...
Different Servers may have different MTUs, and that can cause Havoc, here's some guides on that issue...
Setting MTU size is a process of trial-and-error: start with the maximum value of 1500, then reduce the size until the problem goes away. Using one of these values is likely to solve problems caused by MTU size:
• 1500. The largest Ethernet packet size; it is also the default value. This is the typical setting for non-PPPoE, non-VPN connections. The default value for NETGEAR routers, adapters and switches.
• 1492. The size PPPoE prefers.
• 1472. Maximum size to use for pinging. (Bigger packets are fragmented.)
• 1468. The size DHCP prefers.
• 1460. Usable by AOL if you don't have large email attachments, etc.
• 1430. The size VPN and PPTP prefer.
• 1400. Maximum size for AOL DSL.
• 576. Typical value to connect to dial-up ISPs.
Another way to change the MTU is by...
sudo ifconfig en0 mtu 1460
Or whatever interface for en0, or different mtu value.
These will all be lost with a restart, but might help in diagnosing.
Starting to sound like some flakey HW with the week or so going good !???
this is a interesting information.
but i tried the setting the MTU. For a day or something like that.
I often heard about problems with CISCO Switches and MTU sizes.
So that was the first thing i tried.
But i didn´t try the sysctl commands. This seems interesting.
I will give this a try. I am not sure if this helps for networks and not only
for working with internet
Sorry my english is not so good. I am from germany. What do you mean with "flakey HW"
When I am driving back from the customer i thougt on the cisco switches.
This is one of the things i did not change. Maybe i will give this a try and
change one switch to a HP Procurve or a Level One Switch. What do you mean about this ?
Very very thanx for your help and this conversation.
hes basically giving instructions on how to use the dbg debugger to debug part of the kernel and track down what operation and cause is generating your panic.
here is the reference document about using dbg i think he was trying to link to:
here are the debugger kits youll need:
hopefully youl be able to gifure it out betwen what the guy from the list outlines and the reference document.
I don thave time to review them fully myself and break it down for you, but if i have time later tonight i will. Maybe Phil or someone can help in te meantime... if not your on your own till later this afternoon. Sorry