SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a problem with Slacware 10.1 on IBM xSeries 200.
While I am scanning ports from another PC, server restarts, like someone switch his power off, and than on.
There is no about this in logs.
The module for Ethernet is correct.
I have no idea why its happen.
When I installed Win 2000 amd scan ports everything was fine.
I saw the same behaviour some time ago, but this was
a Macintosh machine running OSX 10.2 that did reboot
when I tried to scan its open ports, this happened once
though, so I didn't search deeper
Well I did what you write. I have added your roule to the iptables.
When I restarted server and started scanning servers ports from another PC , nothing happens. All is working fine. The server didn't restart.
I have some logs in syslog about network packets.
I have removed this roule from iptables, and restarted server.
Then I scanned ports and server restarts!
I built some easy firewall, in which i deny any connection to my servers ethernet.
Now when i am scanning my servers ports from another PC, i still have this problem. Server restarts automaticly.
I have no idea what to do.
I have even bought new ethernet card, but it didn't help.
1. I have added - *.* /dev/tty12 - to my syslog.conf file - now I can see all logs on my screen.
2. When I scanned my servers ports from another PC about 20 times, each time it restarts whitout any information in syslog. But when I added ad.1 line in syslog.conf and watch the screen of my server, I saw for a very short time some two lines before server restarts.
I don't know why, but this lines in syslog from the screen haven't write in the file in /var/log/messages or /var/log/syslog!
3. I have tried to start scanning ports, and then to stop doing that as fast as possible to write down this lines.
Here they are:
sshd[...]: Did not receive identification string from 192.168.5.11
in.identd[...]: started
This two lines are only on my screen!!! I cant find them in my /var/log/ files
I have still this problem with scanning my servers ports. Each time I do it, server restarts.
--------------
Slackware 9.x update: With the advent of the hotplug feature in Slackware, spontanious reboots may occur. If this happens to you, try disabling hotplug on startup:
chmod -x /etc/rc.d/rc.hotplug
until you isolate the driver that is causing the problem and put it in /etc/hotplug/blacklist.
---------------
...your Q. came up.
before you switch off hotplug, save the output of " lsmod "
so you know what modules are loaded normally.
afterwards just load the module(s) for your network, and scan the ports to check...
well...it's not exactly describing your problem there, more a possibility.
as it sais...
-------------
With the advent of the hotplug feature in Slackware, spontanious reboots may occur.
-------------
i would just try it and if no luck there's just one less possibility.
( though i woudn't know many more clues atm.)
I was following this thread and I have some info that may be useful.
Awhile ago I had a server that due to a power surge got its power supply damaged, but not enough that it would not boot. However, is I scanned the machine it would reboot just like yours. I put a UPS (to smooth the noise and electrical pics) and ... it worked!!
So I purchased another power supply and that was the end of it.
I first thought that was a hardware problem but it said that it could not
reproduce this behaviour from win 2000 system installed on that
machine, moreover setting an iptable log rule avoided the restart
while scanning the ports...
For me it is a netcard driver problem but I can be wrong (more likely)
rafal_, you said that setting a deny iptable rule does not fix the problem,
could you post this rule ? Also the server has only one netcard interface ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.