Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have set up a trustix machine to be used as a firewall running iptables. I have no other internet services running (other than those used by the system) yet I am having some very bad instabilities. The machine will stay on for about 20 hours and then it will freeze solid not even allowing any network traffic (I can't even ping the internal network interface), the shell won't respond, and the hdd indicator light glows pretty much non-stop. However, if I bounce the machine (using the power button) everything is just fine- for about 20 hours. During boot, I have no problems with the machine receiving its dynamic address from my cable modem and I have no boot errors at all.
I am thinking it might be a driver issue with the nic, but am unsure. As far as I can tell in checking with the BIOS, the system is not overheating. I have kept the system at stock clock speeds as well.
The hwconf file contained the following information about the nic:
I have seen a similar problem once in a similar setup. The problem was caused by the system logs growing until they filled the available space, thus causing the system to hang.
Check if you have logrotate installed and properly configured.
Firewalls are normally configure to not rotate the logs but send them to an external machine, so I'm sure the syslog is not configured to compress and eliminate older logs.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.