random 100% cpu usage from nowservice

Hello,

Could you please confirm what version of macOS you are using? We will perform some tests internally after you provide the version, the service should not be taking 100% CPU at all.

Could you also send an export of the diagnostic logs (under the Help menu), either via PM or to ticket@devolutions.net .

Best regards,

Hi Richard,
im running Mac OS X 10.15.7
the problem i have is i cant send you logs because the isnt any to send?!
ive checked the waykagent.log but those logs are only date stamped AFTER i run the wayk agent application the is nothing in between?
the nowservice is already running in the background with 100% cpu?
same with the waykhost.log, date stamp was 3 days ago, when i last switched my laptop on?
EDIT: i have also just realised i have posted this bug report using my business account instead of my normal personal one (simonsmith5521)
Regards
Simon

Hi Richard,
ok i found all the log files
i have deleted them all, restarted laptop, its then recreated them all and currently its at 1% cpu as expected,
the minute its at 100% again, ill copy logs and then email them over!
Regards
Simon

Hi Simon

The key file in this case would be the service log, it's at

/Library/Application Support/Wayk/logs/NowService.log

Thanks and kind regards,

Hi Richard,
amazingly it took a long time to get to 100% again
however it just randomly decided to do it now after i resumed my mac from sleep (i closed the screen then opened it like 30mins later)
i have PM you the log file
EDIT: last few log lines if helpful

2021-05-27 16:47:31 wayk_rust::den::wrapper [DEBUG] - Exited Den::register_host_v3 successfully
2021-05-27 16:47:31 common::logging [DEBUG] - Identity after Register 936835
2021-05-27 16:47:31 common::logging [INFO] - Verify msg... (callId=0).
2021-05-27 16:47:32 common::logging [INFO] - << Verify Response
2021-05-27 16:47:32 common::logging [INFO] - Verify message (callId=0) succeeded in 26 ms
2021-05-27 16:47:32 NowService::service::callbacks [DEBUG] - den_client_on_state_change called - state=Connected
2021-05-27 16:47:32 NowService::service [INFO] - Source ID: 936835
2021-05-27 16:47:32 common::logging [DEBUG] - signalling worker thread
2021-05-27 16:47:32 common::logging [DEBUG] - curl url: https://wayk.link/key/xxxxx (proxy: )
2021-05-27 16:47:32 common::logging [DEBUG] - /Library/Application Support/Wayk/branding.zip matches hash xxxxx, nothing to do
2021-05-27 16:47:32 common::logging [DEBUG] - curl url: https://wayk.link/key/xxxxx (proxy: )
2021-05-27 16:47:32 NowService::service [DEBUG] - Den url: wss://remote.xxxxx.com
2021-05-27 16:47:32 NowService::service [DEBUG] - den_client_on_state_change finished successfully
2021-05-27 16:47:32 NowService::service::callbacks [DEBUG] - den_client_on_state_change successfully finished
2021-05-27 16:47:32 common::logging [WARN] - NowTimerQueue_Insert: timer 0x00007f810d828158 already in queue: 0x00007f810d0130b0 (current: 0x00007f810d0130b0)

Regards
Simon

Hi Simon

Thanks for the logs and sorry, I should've read your initial message more closely. 2021.1.2 had a regression that was corrected by 2021.1.3.

You can let us know if you still see the issue after updating, but I expect it to be fixed.

Do you have auto updates enabled? I'm curious why you didn't automatically get the updated version.

Thanks and kind regards,

Hi Richard
the latest online and downloads shows 2021.1.2?
but the release notes show 2021.1.3?
dos somebody forget to update the website/download server haha
regards
simon

Hi Richard

the latest online and downloads shows 2021.1.2?

but the release notes show 2021.1.3?



did somebody forget to update the website/download server haha

also I’m getting no notifications for any updates either?

regards

simon

Hey Simon

This was an oversight on the deployment, it should be fixed now.

Thanks and kind regards,

Hi Richard,
both wayk agent and wayk client popped up saying the was an update available for 2021.1.3
so I have installed them ( installed them manually though as i throught wayk agent should of autoupdated itself? )
case of wait and see if the cpu usage happens again thanks!
Regards
Simon

Hey Simon

Good news!

The auto update defaults to (IIRC) checking once every 24 hours. So it might take that long to be automatically applied.

Let us know if you still experience a problem.

Thanks again and sorry for the inconvenience,