Description of problem: Azurerus has for some time (a year or so) been complaining at startup that it's startup script is updated. The new script it suggests should be investigated, sanity-checked and adopted for fedora purposes.
Hi, I just build last azureus for f20 locally for Fedora 19 and install it , don't see any message of "startup script is updated", I do remember that message but don't see it now .
azureus-5.0.0.0-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/azureus-5.0.0.0-2.fc19
dont understand why you don't upgrade azureus to 5.2 , instead export script from 5.2
Package azureus-5.0.0.0-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing azureus-5.0.0.0-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-0521/azureus-5.0.0.0-2.fc19 then log in and leave karma (feedback).
azureus-5.0.0.0-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
checking [1] I try understand what update you did , where did you find azureus-5.2.0.0-startupScript.patch ? azureus --closedown seems that stop to working, and now also complains that find plugin.properties [2] also warnings about /usr/share/azureus is not writable !? [1] http://pkgs.fedoraproject.org/cgit/azureus.git/commit/?id=3646517d606e410f477e6890711c5eb9fadc1af8 [2] DEBUG::Wed Jan 29 04:49:06 WET 2014::org.gudy.azureus2.update.UpdaterUtils::writePluginProperties::189: java.io.FileNotFoundException: /usr/share/azureus/plugins/azupdater/plugin.properties (No such file or directory)
Recently update Azureus [azureus-5.2.0.0-2.fc20] to my Fedora 20 installation. After the update, Azureus seems that stop working as [Comment 6], Azureus open window with the warning : /usr/share/azureus in not writable and become unresponsive with several messages as : 1] After several minutes Azureus give me the warning message of Low Memory 1MB free from 125MB ! 2] DEBUG::Mon Feb 03 09:01:21 EET 2014::com.aelitis.azureus.core.networkmanager.impl.utp.UTPConnectionManager::write::1086: Deadlock probably detected java.lang.OutOfMemoryError: Java heap space at org.gudy.azureus2.core3.util.BEncoder.toByteArray(BEncoder.java:468) at org.gudy.azureus2.core3.util.BEncoder.encode(BEncoder.java:71) at org.gudy.azureus2.core3.util.BEncoder.encode(BEncoder.java:57) at org.gudy.azureus2.core3.torrent.impl.TOTorrentImpl.serialiseToByteArray(TOTorrentImpl.java:288) at org.gudy.azureus2.core3.torrent.impl.TOTorrentImpl.serialiseToBEncodedFile(TOTorrentImpl.java:154) 3] DEBUG::Sun Feb 02 20:36:48 EET 2014::com.aelitis.azureus.plugins.upnpmediaserver.UPnPMediaServerContentDirectory::getACF::880: 20:36:49.076 3 stderr java.lang.OutOfMemoryError: GC overhead limit exceeded DEBUG::Sun Feb 02 21:02:09 EET 2014::org.gudy.azureus2.core3.global.impl.GlobalManagerImpl$Checker::runSupport::353: 21:02:15.801 3 stderr java.lang.OutOfMemoryError: GC overhead limit exceeded 21:07:49.605 3 stderr DEBUG::Sun Feb 02 21:07:42 EET 2014::org.gudy.azureus2.pluginsimpl.local.download.DownloadManagerImpl::addListener::832: 21:07:50.127 3 stderr java.lang.OutOfMemoryError: GC overhead limit exceeded 21:07:50.128 3 stderr 21:08:16.021 3 stderr java.lang.OutOfMemoryError: GC overhead limit exceeded --------------------------- Trying to set JAVA_ARGS="-Xmx256m" from 128m to azureus script, has the result to azureus to responsive for few minutes. The solution was to replace azureus script to previous version. Azureus works fine after this ....
(In reply to Michael from comment #7) > The solution was to replace azureus script to previous version. Azureus > works fine after this .... yeah, David Juran , I was about to write that on comment #1 , I had report the script was working correctly , for 5.2.0.0 , so solution for F19 was update Azureus from 5.0 to 5.2 . Now solution is revert startup script to realease version 1 on F20 and update F19 to same of F20 . May I ?
Created attachment 859348 [details] startup script for testing Mikael: That's strange, unless I've done something horribly wrong, those heap-size parameters come straight from the startup script the upstream project is using. (That's what this bug is all about, reverting to the default startup script.) In the attached test script, I've removed the -Xmx parameters (the old script didn't have any either). Could you please give it a try and let me know how it works?
(In reply to Michael from comment #7) > The solution was to replace azureus script to previous version. Azureus > works fine after this .... yeah, David Juran , I was about to write the same. On comment #1 I had report the script was working correctly for 5.2.0.0 , so solution for F19 was update Azureus from 5.0 to 5.2 . Now solution is revert startup script to release version 1 on F20 and update F19 to same of F20 . May I ? (In reply to David Juran from comment #9) > Created attachment 859348 [details] > startup script for testing doesn't fixed the other problems .
Created attachment 859919 [details] propose fix for plugin.properties file not found Looking scripts old and new they aren't much different , APPDIR change to PROGRAM_DIR , so is just change default PROGRAM_DIR ,/usr/share/azureus/ by ~/.azureus/app/
(In reply to David Juran from comment #9) > Created attachment 859348 [details] > startup script for testing > > Mikael: > > That's strange, unless I've done something horribly wrong, those heap-size > parameters come straight from the startup script the upstream project is > using. (That's what this bug is all about, reverting to the default startup > script.) > > In the attached test script, I've removed the -Xmx parameters (the old > script didn't have any either). Could you please give it a try and let me > know how it works? I just try the new script and works until now ! The only warning is : /usr/share/azureus in not writable
azureus-5.0.0.0-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/azureus-5.0.0.0-3.fc19
Package azureus-5.0.0.0-4.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing azureus-5.0.0.0-4.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-2266/azureus-5.0.0.0-4.fc19 then log in and leave karma (feedback).
azureus-5.0.0.0-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.