Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Actions don't run on Prey 1.3.3 for Windows (HS:node-actions-bug) #56

Closed
ghost opened this issue Dec 11, 2014 · 4 comments
Closed

Actions don't run on Prey 1.3.3 for Windows (HS:node-actions-bug) #56

ghost opened this issue Dec 11, 2014 · 4 comments
Assignees
@tomas
Labels
bug priority: critical

Comments

@ghost
Copy link

ghost commented Dec 11, 2014

Actions are pushed from the user's Prey account, but are not run on the Windows machine. Here's the log.

  ████████████████ ████████████████ ████████████████ ██            ██
  ██            ██ ██               ██            ██ ██            ██
  ██            ██ ██               ████████████████ ██            ██
  ██            ██ ██               ██               ██            ██
  ████████████████ ██               ████████████████ ████████████████
  ██                                                               ██
  ██                                                 ████████████████

  PREY 1.3.3 spreads its wings!
  Current time: Thu Dec 11 2014 15:22:37 GMT+0000 (GMT Standard Time)
  Running with PID 2212 as CHRISKOREK_PC_ over Node.js v0.10.32 on a ia32 windows system (6.1.7601)

    error Thu, 11 Dec 2014 15:22:38 GMT Error: getaddrinfo ENOTFOUND
   notice Thu, 11 Dec 2014 15:22:38 GMT Lost connection. Trying to connect...
     info Thu, 11 Dec 2014 15:22:38 GMT [triggers] Watching: connection, network, power
     info Thu, 11 Dec 2014 15:22:38 GMT [actions] Starting trigger: connection
     info Thu, 11 Dec 2014 15:22:38 GMT [actions] Running: connection
     info Thu, 11 Dec 2014 15:22:38 GMT [actions] Starting trigger: network
     info Thu, 11 Dec 2014 15:22:38 GMT [actions] Starting trigger: power
     info Thu, 11 Dec 2014 15:22:44 GMT [control-panel] Queueing check-ins every 20 minutes.
   notice Thu, 11 Dec 2014 15:22:44 GMT [control-panel] Checking for existing port mappings...
     info Thu, 11 Dec 2014 15:22:44 GMT Plugin loaded: control-panel
     info Thu, 11 Dec 2014 15:22:44 GMT 1 plugins loaded with 0 errors.
     info Thu, 11 Dec 2014 15:22:44 GMT Initialized.
     info Thu, 11 Dec 2014 15:22:44 GMT [control-panel] Queueing check-ins every 0.5 minutes.
     info Thu, 11 Dec 2014 15:22:44 GMT [actions] Running: network
     info Thu, 11 Dec 2014 15:22:44 GMT [actions] Running: power
     warn Thu, 11 Dec 2014 15:22:47 GMT [control-panel] Unable to sync settings.
     info Thu, 11 Dec 2014 15:22:47 GMT [providers] private_ip already in progress.
    error Thu, 11 Dec 2014 15:22:47 GMT Error: Network seems to be down. Check your connection and try again.
     info Thu, 11 Dec 2014 15:22:49 GMT [control-panel] No previously mapped ports found.
    error Thu, 11 Dec 2014 15:22:50 GMT Error: Command failed: 
     info Thu, 11 Dec 2014 15:23:00 GMT [reports] Gathering status report.
     info Thu, 11 Dec 2014 15:23:00 GMT [reports] Gathering status report.
     info Thu, 11 Dec 2014 15:23:00 GMT [providers] logged_user already in progress.
     info Thu, 11 Dec 2014 15:23:00 GMT [providers] active_access_point already in progress.
     info Thu, 11 Dec 2014 15:23:00 GMT [providers] battery_status already in progress.
    error Thu, 11 Dec 2014 15:23:02 GMT [reports] Unable to get logged_user: No logged user detected. No logged user found.
    error Thu, 11 Dec 2014 15:23:02 GMT [reports] Unable to get logged_user: No logged user detected. No logged user found.
     info Thu, 11 Dec 2014 15:23:02 GMT [reports] Report gathered: status
     info Thu, 11 Dec 2014 15:23:02 GMT [control-panel] Posting event
     info Thu, 11 Dec 2014 15:23:02 GMT [reports] Report gathered: status
     info Thu, 11 Dec 2014 15:23:02 GMT [control-panel] Posting event
     info Thu, 11 Dec 2014 15:23:03 GMT [reports] Gathering status report.
    error Thu, 11 Dec 2014 15:23:05 GMT [reports] Unable to get logged_user: No logged user detected. No logged user found.
     info Thu, 11 Dec 2014 15:23:05 GMT [reports] Report gathered: status
     info Thu, 11 Dec 2014 15:23:05 GMT [control-panel] Posting event
   notice Thu, 11 Dec 2014 15:23:06 GMT [control-panel] Checking for existing port mappings...
     info Thu, 11 Dec 2014 15:23:11 GMT [control-panel] No previously mapped ports found.
     info Thu, 11 Dec 2014 15:23:11 GMT [control-panel] Attempting to map external port 30335
     info Thu, 11 Dec 2014 15:23:16 GMT [control-panel] Got status 200 from server: Ok mate.

     info Thu, 11 Dec 2014 15:23:17 GMT [control-panel] Got status 200 from server: Ok mate.

     info Thu, 11 Dec 2014 15:23:20 GMT [control-panel] Port 30335 mapped. Starting push handler.
     info Thu, 11 Dec 2014 15:23:24 GMT [control-panel] Updating notification ID...
     info Thu, 11 Dec 2014 15:23:26 GMT [control-panel] Queueing check-ins every 20 minutes.
   notice Thu, 11 Dec 2014 15:23:26 GMT [control-panel] Ready to receive push notifications.
     info Thu, 11 Dec 2014 15:23:27 GMT [control-panel] Got status 200 from server: Ok mate.

     info Thu, 11 Dec 2014 15:23:49 GMT [reports] Gathering status report.
    error Thu, 11 Dec 2014 15:23:49 GMT [reports] Unable to get logged_user: No logged user detected. No logged user found.
     info Thu, 11 Dec 2014 15:23:50 GMT [reports] Report gathered: status
     info Thu, 11 Dec 2014 15:23:50 GMT [control-panel] Posting event
     info Thu, 11 Dec 2014 15:23:51 GMT [control-panel] Got status 200 from server: Ok mate.

     info Thu, 11 Dec 2014 15:25:49 GMT [reports] Gathering status report.
     info Thu, 11 Dec 2014 15:25:50 GMT [reports] Report gathered: status
     info Thu, 11 Dec 2014 15:25:50 GMT [control-panel] Posting event
     info Thu, 11 Dec 2014 15:25:51 GMT [control-panel] Got status 200 from server: Ok mate.

Once the user runs C:\Windows\Prey\current\bin\prey -a as an admin on the command prompt, actions work fine. Here's the log for that.

  ████████████████ ████████████████ ████████████████ ██            ██
  ██            ██ ██               ██            ██ ██            ██
  ██            ██ ██               ████████████████ ██            ██
  ██            ██ ██               ██               ██            ██
  ████████████████ ██               ████████████████ ████████████████
  ██                                                               ██
  ██                                                 ████████████████

  PREY 1.3.3 spreads its wings!
  Current time: Thu Dec 11 2014 21:55:37 GMT+0000 (GMT Standard Time)
  Running with PID 1880 as CHRISKOREK_PC_ over Node.js v0.10.32 on a ia32 windows system (6.1.7601)

    error Thu, 11 Dec 2014 21:55:38 GMT Error: getaddrinfo ENOTFOUND
   notice Thu, 11 Dec 2014 21:55:38 GMT Lost connection. Trying to connect...
     info Thu, 11 Dec 2014 21:55:38 GMT [triggers] Watching: connection, network, power
     info Thu, 11 Dec 2014 21:55:38 GMT [actions] Starting trigger: connection
     info Thu, 11 Dec 2014 21:55:38 GMT [actions] Running: connection
     info Thu, 11 Dec 2014 21:55:38 GMT [actions] Starting trigger: network
     info Thu, 11 Dec 2014 21:55:38 GMT [actions] Starting trigger: power
     info Thu, 11 Dec 2014 21:55:46 GMT [control-panel] Queueing check-ins every 20 minutes.
   notice Thu, 11 Dec 2014 21:55:46 GMT [control-panel] Checking for existing port mappings...
     info Thu, 11 Dec 2014 21:55:46 GMT Plugin loaded: control-panel
     info Thu, 11 Dec 2014 21:55:46 GMT 1 plugins loaded with 0 errors.
     info Thu, 11 Dec 2014 21:55:46 GMT Initialized.
     info Thu, 11 Dec 2014 21:55:46 GMT [control-panel] Queueing check-ins every 0.5 minutes.
     info Thu, 11 Dec 2014 21:55:46 GMT [actions] Running: network
     info Thu, 11 Dec 2014 21:55:46 GMT [actions] Running: power
    error Thu, 11 Dec 2014 21:55:46 GMT Error: Command failed: 
     info Thu, 11 Dec 2014 21:55:46 GMT [providers] active_access_point_name already in progress.
     info Thu, 11 Dec 2014 21:55:46 GMT [providers] private_ip already in progress.
     warn Thu, 11 Dec 2014 21:55:47 GMT [control-panel] Unable to sync settings.
     warn Thu, 11 Dec 2014 22:00:52 GMT [control-panel] Got 1 commands.
     info Thu, 11 Dec 2014 22:00:52 GMT [actions] Starting action: alert
     info Thu, 11 Dec 2014 22:00:53 GMT [control-panel] Posting response
     info Thu, 11 Dec 2014 22:00:53 GMT [actions] Running: alert
     info Thu, 11 Dec 2014 22:00:53 GMT [actions] Stopped: alert
     info Thu, 11 Dec 2014 22:00:54 GMT [control-panel] Posting response

Actions won't run once the system is restarted.
@ghost ghost added the bug label Dec 11, 2014
@ghost ghost assigned tomas Dec 11, 2014
@ghost ghost changed the title v1.3.3 doesn't perform actions unless "prey -a" is running v1.3.3 doesn't perform actions unless "prey -a" is running (HS:node-actions-bug) Dec 11, 2014
@ghost ghost changed the title v1.3.3 doesn't perform actions unless "prey -a" is running (HS:node-actions-bug) Actions don't run on Prey 1.3.3 for Windows (HS:node-actions-bug) Dec 16, 2014
@ghost
Copy link
Author

ghost commented Dec 16, 2014

I created a duplicate. Sorry. The message on the other issue was:

Message and Lock actions aren't run on some Windows machines. Still trying to find a pattern. For now it's only happened on Windows 7. Windows 8 and 8.1 seem to be working fine. The prey.log files look fine, and instructions are received by the client, but for reason are not run. Is there a way to troubleshoot this?

Here's an example log.

  ████████████████ ████████████████ ████████████████ ██            ██
  ██            ██ ██               ██            ██ ██            ██
  ██            ██ ██               ████████████████ ██            ██
  ██            ██ ██               ██               ██            ██
  ████████████████ ██               ████████████████ ████████████████
  ██                                                               ██
  ██                                                 ████████████████

  PREY 1.3.3 spreads its wings!
  Current time: Tue Dec 16 2014 14:27:25 GMT-0500 (Eastern Standard Time)
  Running with PID 4108 as ASCJ7JZTY1_ over Node.js v0.10.32 on a x64 windows system (6.1.7601)

     info Tue, 16 Dec 2014 19:27:25 GMT [triggers] Watching: connection, network, power
     info Tue, 16 Dec 2014 19:27:25 GMT [actions] Starting trigger: connection
     info Tue, 16 Dec 2014 19:27:25 GMT [actions] Running: connection
     info Tue, 16 Dec 2014 19:27:25 GMT [actions] Starting trigger: network
     info Tue, 16 Dec 2014 19:27:25 GMT [actions] Starting trigger: power
     warn Tue, 16 Dec 2014 19:27:25 GMT [control-panel] Not configured. Waiting for user input...
     info Tue, 16 Dec 2014 19:27:25 GMT [actions] Running: network
     info Tue, 16 Dec 2014 19:27:25 GMT [actions] Running: power
     info Tue, 16 Dec 2014 19:27:35 GMT [control-panel] Reloading config...
     info Tue, 16 Dec 2014 19:27:45 GMT [control-panel] Reloading config...
     info Tue, 16 Dec 2014 19:27:55 GMT [control-panel] Reloading config...
     info Tue, 16 Dec 2014 19:27:55 GMT [control-panel] Queueing check-ins every 20 minutes.
   notice Tue, 16 Dec 2014 19:27:55 GMT [control-panel] Checking for existing port mappings...
   notice Tue, 16 Dec 2014 19:27:56 GMT [control-panel] Updating value of auto_connect to true
     info Tue, 16 Dec 2014 19:28:00 GMT [control-panel] No previously mapped ports found.
     info Tue, 16 Dec 2014 19:28:00 GMT [control-panel] Attempting to map external port 30335
    error Tue, 16 Dec 2014 19:28:38 GMT [control-panel] Unable to map port: Could not locate gateway on time.
     info Tue, 16 Dec 2014 19:28:38 GMT [control-panel] Queueing check-ins every 0.5 minutes.
     warn Tue, 16 Dec 2014 19:29:08 GMT [control-panel] Got 1 commands.
     info Tue, 16 Dec 2014 19:29:09 GMT [reports] Gathering status report.
     info Tue, 16 Dec 2014 19:29:09 GMT [reports] Report gathered: status
     info Tue, 16 Dec 2014 19:29:09 GMT [control-panel] Posting data
     info Tue, 16 Dec 2014 19:29:10 GMT [control-panel] Got status 200 from server: OK
     warn Tue, 16 Dec 2014 19:43:09 GMT [control-panel] Got 2 commands.
     info Tue, 16 Dec 2014 19:43:09 GMT [actions] Starting action: alert
     info Tue, 16 Dec 2014 19:43:09 GMT [control-panel] Posting response
     info Tue, 16 Dec 2014 19:43:09 GMT [actions] Running: alert
     info Tue, 16 Dec 2014 19:43:09 GMT [actions] Stopped: alert
     info Tue, 16 Dec 2014 19:43:09 GMT [reports] Gathering status report.
     info Tue, 16 Dec 2014 19:43:10 GMT [reports] Report gathered: status
     info Tue, 16 Dec 2014 19:43:10 GMT [control-panel] Posting data
     info Tue, 16 Dec 2014 19:43:10 GMT [control-panel] Posting response
     info Tue, 16 Dec 2014 19:43:10 GMT [control-panel] Got status 200 from server: OK

@ghost ghost mentioned this issue Dec 16, 2014
Closed
@ghost
Copy link
Author

ghost commented Dec 17, 2014

According to a customer,

You do see a prey_lock.exe process start and close while the Lock device action is running, but it never actually displays anything. It is kind of weird because it does disable the Windows Task Manager [...] At this time, I have rolled back to the 0.6.4 client to see if there were any policies on the computer that may be causing the issue, but the older client did work to some extent.

@tomas
Copy link
Contributor

tomas commented Dec 29, 2014

This was fixed on the v1.3.4 release.

@tomas tomas closed this as completed Dec 29, 2014
@ghost
Copy link
Author

ghost commented Dec 29, 2014

Users notified. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tomas tomas

Labels
bug priority: critical
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tomas @raliste