P2P stops on Windows periodically [production]

[kurmanbekova6]

• Windows OS

[crioto]

I need to know how to reproduce this and what's happening in p2p at this moment. Better to run p2p daemon manually and collect output

[kurmanbekova6]

Ok. I will collect output and will attach.

[crioto]

Thank you. Please don’t forget to set log level to `debug`

…

On Jan 14, 2019, at 11:25 AM, Aiperi ***@***.***> wrote: Ok. I will collect output and will attach. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#1217 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAo9qzfQOiB-AIgCdy_XRjXuZYTbi5tgks5vC_iSgaJpZM4Z7QV1>.

[kurmanbekova6]

1. How to reproduce this issue:
   Need to monitor p2p's behavior.
   After turning on machine, p2p worked 1h 17 min. and got stopped.
   After that every 15-20-25 min.

2. After adding ssh key, all environments state failed, even if p2p was running.
   
   Before adding key:
   
   After adding key:
   

If you require any further information, let me know.

p2p_debug.zip

[crioto]

Thank you, Aiperi. I will start working on a fix.

…

On Jan 14, 2019, at 1:24 PM, Aiperi ***@***.***> wrote: How to reproduce this issue: Need to monitor p2p's behavior. After turning on machine, p2p worked 1h 17 min. and got stopped. After that every 15-20-25 min. After adding ssh key, all environments state failed, even if p2p was running. <https://user-images.githubusercontent.com/9501291/51097467-7c811380-17ee-11e9-945f-e7274794445e.png> Before adding key: <https://user-images.githubusercontent.com/9501291/51097476-8e62b680-17ee-11e9-865a-38a72df2f2b1.PNG> After adding key: <https://user-images.githubusercontent.com/9501291/51097477-8e62b680-17ee-11e9-9fb3-4407dc00583e.PNG> If you require any further information, let me know. p2p_debug.zip <https://github.com/subutai-io/p2p/files/2754066/p2p_debug.zip> — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#1217 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAo9q8qDtSGSMNN-NO_XFGIYdH7TfQVqks5vDBSqgaJpZM4Z7QV1>.

[kurmanbekova6]

Monitored p2p's behavior on master, p2p did not get stopped. Also, after machine's sleep, p2p is coming back.

[crioto]

Thank you, Aiperi. Let’s test the same for some time, to make sure it works ok. There might be other bugs that lead to the same problem

…

On Jan 18, 2019, at 1:45 PM, Aiperi ***@***.***> wrote: Monitored p2p's behavior on master, p2p did not get stopped. Also, after machine's sleep p2p coming back. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#1217 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAo9q7bEItscrYtx6cwMjzOTYhQwY4yvks5vEV-OgaJpZM4Z7QV1>.

[kurmanbekova6]

Mike, after machine's sleeping mode, p2p did not start automatically. Need to start manually.

[crioto]

Any logs related to this problem?

…

On Jan 22, 2019, at 8:01 PM, Aiperi ***@***.***> wrote: Mike, after machine's sleeping mode, p2p did not start automatically. Need to start manually. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#1217 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAo9qyeA5-MNYi_DFpk4oCmdlnZMmV5Tks5vFv2AgaJpZM4Z7QV1>.