Web server: Action extension_list_menuitems timed out for subscriber airdcpp-share-monitor #2
Comments
|
Please test version 1.0.1 of the extension to see if it makes any difference Related issue: airdcpp-web/airdcpp-release-validator#14 |
|
Finished one download now and no errors. Will push it and see what happens. |
|
15:50:49] Extensions: Extension airdcpp-share-monitor timed out and was restarted Same as releasevalidator i guess. |
|
the other errors seem to be gone. |
|
There are still a few similar issues left in an external dependency. See yuanchuan/node-watch#107 |
|
Alright. Let me know if i can help |
|
Could you test this version: http://web-builds.airdcpp.net/tmp/airdcpp-share-monitor-1.0.2-beta.1.tgz (use |
|
[12:11:50] Extensions: Extension airdcpp-share-monitor timed out and was restarted Restarted dc after installation. Still the same. |
|
You could also post the extension debug info according to https://github.com/airdcpp-web/airdcpp-webclient/blob/master/.github/CONTRIBUTING.md#extension-related-issues Log files with the |
|
This is from the error log. -20 17:46:12:96] 137 409 Directory is inside an unfinished bundle |
|
That's normal, the output log should be more interesting |
|
Check your mail |
|
What was the time when the extension timed out on that run? |
|
[17:40:33] Extensions: Extension airdcpp-share-monitor timed out and was restarted [17:40:33] Extensions: Extension airdcpp-share-monitor timed out and was restarted |
|
log was created 17:47 |
|
The log starts from 17:40:33. I'd need logs before the timeout to see that what was going on back then. |
|
No older logs but i happens again at 17:48 |
|
What's the exact time with seconds? |
|
[17:47:58] Web server: Disconnecting extension airdcpp-share-monitor because of ping timeout |
|
You could try increasing the socket ping timeout from the Web UI to see if the extension becomes more stable (Settings -> System -> Advanced) |
|
Tested 30s now |
|
Monster restart now. [22:16:36] airdcpp-share-monitor: 15 paths were added for monitoring [22:18:55] Web server: Disconnecting extension airdcpp-share-monitor because of ping timeout [22:23:17] Extensions: Extension airdcpp-share-monitor timed out and was restarted [22:23:41] airdcpp-share-monitor: 15 paths were added for monitoring |
|
Do you have any idea that why it might have started to happen at that point? What were you doing at that time? What's the load (CPU, disks)? |
|
I can see that it was refreshing. The cpu load is high (airdc). Disk load is low. |
|
Im using rclone with remote disks. Can that be it? |
I'm not sure yet. There weren't that many file changes before it timed out based on your log file so I don't know why it would be frozen for that long. Your system specs aren't that bad either. The next thing that you could try would be to download the latest version of node from https://nodejs.org/dist/v15.4.0/node-v15.4.0-win-x64.zip (only replace |
|
node.exe replaced. Lets see what happens. |
|
[15:45:04] Extensions: 4 extensions were loaded (debug mode) [15:47:13] Web server: Disconnecting extension airdcpp-share-monitor because of ping timeout (I have 90s in settings) |
|
Please test the latest version of the extension with the latest application beta build. Actually I just noticed that the timeout values won't currently be saved in the settings file. If you want to test custom timeouts, you should only restart the web server and not the application. It will be fixed in a later build. |
|
Will try |
|
Trying some settings now. But if i try to stop the server in the win app it crashes. Have to do it form the browser. |
|
It would be good to get the crash log |
|
Cant find any crashlog and no crashlog in settings. |
|
Cant see any errors in a few hours now. I have ping time out on 240s and new directory on 240s. Also had a crash when i restarted the webserver from browser. And a note on the updates when it should restart it only shuts down. |
|
If the application freezes, you can follow the instructions at https://www.airdcpp.net/forum/viewtopic.php?f=7&t=447 for getting the necessary information
Do you mean extension updates? |
|
No when i update the app. Is says restart to update but it just shuts down. |
Can really use that debug. It just dies. Boom dead. No frozen client. |
|
Since I can't reproduce those issues and I'm not aware of anyone else experiencing them, you could try doing some troubleshooting, such as testing with a clean installation whether it behaves in the same way. If you have antivirus software (or something similar) running, you could also try disabling them. It would be better to post a new bug report for the application itself if the issue won't go away. I released a new beta build that will also fix saving of the timeout values in the config file. |
|
I can test some stuff. Is not a big issue but always nice to fix bugs. WIll download the beta and test. |
|
Is everything still working fine with the extension? |
|
No 😥. Still the same errors after clean install.
…________________________________
From: maksis <[email protected]>
Sent: Monday, December 28, 2020 10:51:51 PM
To: airdcpp-web/airdcpp-share-monitor <[email protected]>
Cc: faltaren <[email protected]>; Author <[email protected]>
Subject: Re: [airdcpp-web/airdcpp-share-monitor] Web server: Action extension_list_menuitems timed out for subscriber airdcpp-share-monitor (#2)
Is everything still working fine with the extension?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#2 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMEASSV4R4EZTZ2XLTKBP5DSXD4XPANCNFSM4VAY27NQ>.
|
|
Timeouts? With socket ping timeout set to 240 seconds? |
|
Timeouts and crasch when it cant access the log. Yes. Its 240s. The crash is almost always when i start dc. timeouts are random. |
|
You could try the latest version and if it still doesn't work, I would need the same log data as before (.old logs and the respective system log messages). The logging has been improved in the recent versions.
Does the log error happen even on the first time after restarting the computer? What's the error messages? |
|
I have installed and restarted. No errors in the last hour. I dont really remember the times i restarted the computer. But i did this time. Will keep you updated. |
|
No errors since yesterday. Quite high load. Lots of downloads and hashing. |
|
Still no errors. The hashing is much faster to. It was much slower when i upgraded to 4.00. Nice work :) |
|
Damn. Timed out and restarted. From log: [2021-1-3 7:14:45:94] Wake up detected (last alive 32351 ms ago), requesting restart... |
The main thing for me isn't actually to know whether it times out, but to know what was happening when it timed out (and whether it's something than can be avoided). The timeout periods can't be increased indefinitely as the socket will get disconnected at some point in any case if the process is frozen for too long (see airdcpp-web/airdcpp-webclient#356). |
|
Im going to set them in debug and see what happens. But now i had lots of crashes. The api for the rclone remote maxed out. Can that be it? |
|
I have checked the logs and there is a 30s blindspot before the addon is restarted. I cant see any errors before so something is happening there. |
|
You could monitor the CPU usage of the extension process according to https://social.technet.microsoft.com/Forums/lync/en-US/42afb7cd-6cb6-463c-b385-21a97162e3f5/monitoring-cpu-usage-of-individual-processes?forum=winservergen You need to monitor the You should also edit the performance monitor graph settings from Maybe you will get some useful information from the time when the extension timed out. |
|
Had a crasch now and rclone and airdc spiked in cpu at the same time. Node is very flat. No spikes at all. |
|
So sounds like the process just got frozen, maybe because of total system load... Please test the latest version of the extension. It will set the system sleep detection timeout based on the socket ping timeout that you have configured in the application settings. So you if still have ping timeout set to 240 seconds, the extension process can be frozen for the same amount of time before it commits suicide (requests a restart from the application). |
|
thx. ye the load is high. Will try it. |
|
Would you say that the issue has now been fixed? |
|
Yes. Release validator still crasches. But yes share monitor feels stable now. |
Web server: Action extension_list_menuitems timed out for subscriber airdcpp-share-monitor. And it times out so i have to restart it. airDc 4.0
The text was updated successfully, but these errors were encountered: