I have a rather peculiar problem in the past 2 weeks. I have a network setup with a linux box acting as a gateway (It is exposed to the internet). Also, there are 2 additional machines that are connected to the gateway (and are not exposed to the outside world). (The gateway has a NAT setup to route traffic to/from the internal machines).
I am also hosting 2 websites on the external gateway so that it can be accessed from the outside world. I work on either of the 2 internal machines and sometimes ssh to the external gateway (from my internal machine) for any maintenance work. Recently, there were times when
1) I was NOT able to ssh to the gateway.
2) I was NOT able to access any of the websites hosted on the gateway (apache is the webserver used).
3) I AM able to access the internet as usual (i.e., the network traffic is routed properly and as usual).
There is an additional problem. i.e, when i connect my monitor, keyboard and mouse to the gateway machine, the display does not come up. :-(.
So all I am left to do is to REBOOT the system (which I heard is not a common practice in the LINUX/UNIX world). As a matter of fact, everything is OK after a REBOOT. I mean the display is there, I am able to access the internet from the internal machines, SSH to the gateway works fine and webservers are accessible.
I looked into all the log files for any suspicious activity, but could not find one. I am still worried that it could be a security issue that someone could just hack into the system and TURN off the ssh daemon and things like that.
Please let me know if you have any ideas on whatz going on??
Thank you very much.
-Ceeeyem.
Hello reborg, i checked the system logs for any messages related to power save mode, but it does not have any of them except for the usual messages that get logged when a system boots up. i mean , these logs are the result of my reboots mentioned earlier.
Linux <hostname> 2.6.11-1.1369_FC4 #1 Thu Jun 2 22:55:56 EDT 2005 i686 i686 i386 GNU/Linux
2) running
dmesg
on the gateway machine does not return any sensible results. For example, multiple lines like the one below is repeated.
IN=eth1 OUT= SRC=0.0.0.0 DST=255.255.255.255 LEN=304 TOS=0x00 PREC=0x00 TTL=128 ID=0 PROTO=UDP SPT=68 DPT=67 LEN=284
APMSCRIPTS=/etc/sysconfig/apm-scripts
# make an entry in the logfiles whenever the percentage of
# battery power changes below the value specified here
LOGPERCENTCHANGE=10
# warn on specified remainig battery percentage, use negative values
# to disable this feature
WARNPERCENT=5
# use -W to warn all users in a critical power state
ADDPARAMS="-W"
# if you have problems with your X display after returning from suspend mode
# give CHANGEVT the number of the virtual terminal your X-Server runs on
#CHANGEVT="7"
# If you set this to yes, the clock will be synced with the hardware clock
# when the computer returns from suspend mode.
CLOCK_SYNC="yes"
# Some broken BIOSes, like those found in early Gericom 3xC notebooks,
# won't wake up harddisks from suspend to disk unless they're set to PIO mode
# and 16-bit.
# Don't activate the following two lines unless you're getting
# "hda: lost interrupt" after returning from a suspend to disk.
#HDPARM_AT_SUSPEND="-q -X0 -q -c0 -q -d0 -q -u0 -q -S0"
#HDPARM_AT_RESUME="-q -X66 -q -c1 -q -d1 -q -u1 -q -S30"
# the error-beep of your terminal might be set to the default values after a
# resume so set TERMINALBEEP to "yes" to restore the values in
# /etc/sysconfig/keyboard
TERMINALBEEP="no"
# if your sound sometimes doesn't work after a resume set RESTORESOUND to "yes";
# this will kill all sound applications, remove and start the $SOUNDMODULES
# again, and, if you also set $RESTORESOUNDPROGS to "yes", restart the
# sound applications as the correct user and on the correct display
RESTORESOUND="no"
RESTORESOUNDPROGS="no"
# some services might need restarting after a suspend/resume cycle - for
# example, named will shut down if all network interfaces go down.
# Any valid service (as in "ls /etc/init.d/") can be listed, and will be
# restarted if it was running at suspend time.
RESTORESERVICES="named amd"
# I got frequent problems mainly with scsi-pcmcia-cards on the cardbus. Use
# PCMCIARESTART="yes" to stop the whole pcmcia-subsystem on a suspend and
# to start it again after a resume. This can slow down your suspend and resume
# process. Use PCMCIAWAIT to wait with the suspend until the pccard is removed
# from the system.
# Some BIOSes are too buggy to handle cardctl suspend and cardctl resume
# properly, in these cases cardctl eject and cardctl insert can be used instead.
# However, this actually ejects the card on hardware supporting it, so if
# the BIOS isn't buggy, it shouldn't be used. Set PCMCIABIOSBUG to yes if
# you are experiencing problems with PCMCIA cards after a resume.
# Since buggy BIOSes seem to be far more common than hardware that can eject
# PCMCIA cards (and it doesn't make a difference on systems that don't have
# either), it is enabled by default.
PCMCIARESTART="no"
PCMCIABIOSBUG="yes"
PCMCIAWAIT="no"
# Set ANACRON_ON_BATTERY to yes if you want to run anacron after a resume even
# if you're on battery power.
ANACRON_ON_BATTERY="no"
# Set LOCK_X to yes if you want to lock all your X displays at suspend
LOCK_X="no"
# If NET_RESTART is set to yes, the network will be shut down at suspend and
# restarted at resume.
# This is especially useful if you're using DHCP, but usually won't hurt.
NET_RESTART="yes"
# If NETFS_RESTART is set to yes, NFS filesystems will be unmounted at
# suspend, and remounted at resume (if possible).
NETFS_RESTART="yes"
# If you wish to stop any services when going to battery power (and restart them when
# going to line power), list them in POWER_SERVICES.
# Any service started using the init scripts can be listed (the APM script runs
# "/sbin/service ... stop" for each of the services).
# If you want to stop/restart any services that are not started by the init system,
# use an apmcontinue script.
#POWER_SERVICES="atd crond"
# If you wish to stop any services when running short of battery power (and restart them when
# going to line power), list them in LOWPOWER_SERVICES.
# Any service started using the init scripts can be listed (the APM script runs
# "/sbin/service ... stop" for each of the services).
# If you want to stop/restart any services that are not started by the init system,
# use an apmcontinue script.
LOWPOWER_SERVICES="atd crond"
# Some broken BIOSes (e.g. the ones found in Toshiba Satellite Pro 4600
# Notebooks) need some time to settle down before really entering suspend
# mode.
#
# If your BIOS is broken, uncomment the line below, and possibly change the
# value (e.g. "5s = Wait 5 seconds before allowing to suspend").
#DELAYSUSPEND="3s"
# If your machine supports using cpufreq to change its speed, you can enable
# this to support changing the cpu frequence to performance or powersave
# based on whether or not you are currently on AC power or battery power
#CPUFREQ="no"