search

airdcpp-web / airdcpp-release-validator

AirDC++ extension that performs various validations for release directories
1 stars 3 forks source link

Web server: Action queue_bundle_finished_hook timed out for subscriber airdcpp-release-validator #14

Closed bluboyo closed 3 years ago

bluboyo commented 3 years ago

I get this error multiple times a day. Restart dosent help. What info do you need from me?

maksis commented 3 years ago

Does it happen with all finished bundles? Is the system under high load or is there something else special happening during that? Do you get similar errors with all extensions (you could also try installing the search sites extension)?

bluboyo commented 3 years ago

Most of them yes. Yes the system is under high load. The share monitor is a problem to. Extensions: Failed to start the extension airdcpp-share-monitor: Failed to initialize the extension log and Web server: Action extension_list_menuitems timed out for subscriber airdcpp-share-monitor, xtensions: Extension airdcpp-share-monitor timed out and was restarted. I have the search sites installed. Want me to test it?

maksis commented 3 years ago

The timeout for scanning the bundle is one minute, so the system must be really unresponsive if the scan times out. What's causing the high load and are you able to test it with lighter load? What are your system specs?

bluboyo commented 3 years ago

I stopped all downloads and now it scans fine (for now). The disks are under 100% load at times. Its an old intel system. 4 core i5 3,3ghz. ssd systemdisk. Windows 10. 32gb ddr 3 ram.

bluboyo commented 3 years ago

I finshed one download now. Got this error Extensions: Failed to start the extension airdcpp-share-monitor: Failed to initialize the extension log. File is used by another process. Had to restart the share monitor

maksis commented 3 years ago

If the disk load is so high that one minute just simply isn't enough for scanning the bundle, I don't see many other options than increasing the timeout. As the current hook timeouts are hardcoded, that would require changes in the application itself. The best solution might be to add separate timeout settings for each hook type.

bluboyo commented 3 years ago

I think that would be good.

maksis commented 3 years ago

Please try it with the latest beta application (Settings -> Miscellaneous -> Update channel). It changes the default timeout from one minute to two minutes. If it's still not enough, you may increase the timeout from the Web UI (Settings -> System -> Advanced -> Bundle downloaded).

bluboyo commented 3 years ago

[11:08:45] Extensions: Failed to start the extension airdcpp-share-monitor: Failed to initialize the extension log C:\Users*****\Documents\AirDC++\extensions\airdcpp-share-monitor\logs\output.log:

Used by another process.

Im testing the timeouts. 240s now.

maksis commented 3 years ago

This fix is only for the release validator, not share monitor. Changing the timeout won't make any difference with share monitoring.

bluboyo commented 3 years ago

Aha then 2m was enough

From: maksis notifications@github.com Sent: Sunday, December 20, 2020 11:14:47 AM To: airdcpp-web/airdcpp-release-validator airdcpp-release-validator@noreply.github.com Cc: faltaren falt84@hotmail.com; Author author@noreply.github.com Subject: Re: [airdcpp-web/airdcpp-release-validator] Web server: Action queue_bundle_finished_hook timed out for subscriber airdcpp-release-validator (#14)

This fix is only for the release validator, not share monitor. Changing the timeout won't make any difference with share monitoring.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/airdcpp-web/airdcpp-release-validator/issues/14#issuecomment-748588055, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMEASSS6UW3G3PTSYXF5BF3SVXFBPANCNFSM4VAYVKCA.

maksis commented 3 years ago

Looks like this can be closed now