Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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 a Linux Slackware 8.1 server acting as my firewall/gateway to the Internet. On two occasions, I have got up to use the Internet in the morning only to find out that I have no access. I go to check my Linux server and it's completely shutdown and turned off. Very strange. I check the weather the night before and there was no storm. I am wondering if someone has hacked my system and shut the system down. The sever is brand new and I haven't had any hardware related problems. I doubt there is anything wrong with the hardware. This isn't a consistent problem, it's only happened a couple of times. Anyone have any ideas? I do have ACPI compiled into my kernel if that helps.
Anything in the logs leading up to the shutdown moment? Verified the integrity of whatever is on the system? Checked physical conditions? Ram, CPU's whatever else in slots seated firmly, power cabling OK?
All the physical conditions seem fine. I can't see anything in the log. The other day, after this post, I did see the syslog daemon restarted 4 times in a row.
I'm having similar problems. I'm actually suspecting kernel panics (don't ask - see my thread on iptables losing packets, also found a serious bug in the ipt_ULOG code for the 2.4 series of kernels, suspect it's fixed in some version after 2.4.18).
It might also be DMA freezing up - there is a workaround in the kernel, but I have no idea how efficient it is. And as logging seems to be the first thing to go ... The first I usually see the machine is down is when I attempt to ssh into it.
Any ideas? btw, it's an old pentium 200 mmx machine, so it's not all the newest hardware, it can't switch off automatically and a reboot fixes the problem. And any hacker will have a really hard time getting into that machine, unless there is some unknown exploit for ssh2 (the only publicly available service). Unless of course, as I suspect the netfilter code is all haywire ...
buttnutt: does the system do a "clean" shutdown? Could you add a line (w/o quotes and note TAB) "*.*<TAB>/var/log/catchall", touch /var/log/catchall and restart syslog to see if it will log more info?
If nothing shows up in the next few days I'll prolly decide to move this question to another, hopefully more appropriate, forum.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.