Comment 1 for bug 730210

Hi Mathiu,

Thank you for taking the time to report bugs and trying to make PowerNap better.

Now, I don't quite seem to understand your scenario. So just let me get this straight.

1. You configured PowerNap to listen to a TCP Monitor.
2. You started powernap and it became idled and after 300 seconds of inactivity it performed the action.
2. The action is *powersave* that run all the scripts in /etc/pm/power.d/ and /usr/lib/pm-utils/power.d/ to reduce power consumption while running the machine.
3. You SSH into the machine and PowerNap takes recover action by running the scripts again, *but* your SSH session failed?

Please specify your scenario. Please also enable DEBUG=3 in the config, try to reproduce the bug and attach the following:
  - /etc/powernap/config
  - /var/log/powernap.log
  - /var/log/powernap.err

Now, if you configure a TCP monitor for port 22 and you SSH into that machine *before* PowerNap put the machine into powersave mode (ACTION_METHOD=0), then the machine will *never* enter into PowerSave monitor until the SSH session is lost and the machine is detected as being inactive after the desired time.

Now, if you have the TCPMonitor configured for ssh, and the machine *is* in PowerSave mode, whenever you SSH in, the machine should take recover action by running the scripts. And you should be able to continue to use your machine without any issue, even with SSH.

I've tested this again (and has been tested in various machines previously):

1. Configure PowerNap for TCPMonitor.
2. Wait till PowerNap enters into PowerSave Mode.
3. SSH into machine
4. PowerNap takes recover action after detection of SSH connection.
5. SSH Connection continue as normal (without the issues you are mentioning above).

Now, try to reproduce the issue again and run 'watch ethtool eth0' in a different terminal and observe the behavior.

When PowerNap enters into PowerSave mode (2), you should see something like:

        Supported ports: [ TP MII ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
 Supports auto-negotiation: Yes
 Advertised link modes: Not reported

When you SSH into machine after machine is in PowerSave mode (3) you should see something like:

 Supported ports: [ TP MII ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full

I'm marking this bug as incomplete after the required information is provided!