What's new

Entware Transmission stopped working

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

kman

Regular Contributor
Hi All, after the latest updates to entware packages, Mar 15, 2023, Transmission has stopped loading. I don't see anything in the sys log except the following:

Code:
Mar 16 22:58:39 admin: Failed to start transmission-daemon from .

Running it from command line, it also mentions failed.
Code:
admin@RT-AX86U-C280:/tmp/mnt/merlin/entware/etc/transmission# /opt/etc/init.d/S88transmission restart
 Starting transmission-daemon...              failed.

Any idea what could have caused this and how to resolve?

Thanks.
 
Running it directly I see the following:

Code:
admin@RT-AX86U-C280:/tmp/mnt/merlin/entware/bin# ./transmission-daemon
./transmission-daemon: error while loading shared libraries: libssl.so.1.1: wrong ELF class: ELFCLASS32
 
Running it from command line, it also mentions failed.
Code:
admin@RT-AX86U-C280:/tmp/mnt/merlin/entware/etc/transmission# /opt/etc/init.d/S88transmission restart
 Starting transmission-daemon...              failed.

Any idea what could have caused this and how to resolve?
Try running the script with the debug flag. It might show some clues as to what the problem is and someone else can help you. I don't use Transmission so I can provide only initial troubleshooting steps.

Bash:
sh -x /opt/etc/init.d/S88transmission restart
 
Running it directly I see the following:

Code:
admin@RT-AX86U-C280:/tmp/mnt/merlin/entware/bin# ./transmission-daemon
./transmission-daemon: error while loading shared libraries: libssl.so.1.1: wrong ELF class: ELFCLASS32
Ah, it looks like the same problems related to the recent Entware packages upgrade.

 
Right, it appears to be the same issue but according to the suggestion, I need to re-install program.

The solution is to re-install program, which brings you the same version of program, but right relations between dependent files.

I've tried 'opkg install --force-reinstall transmission-daemon' but still error. Any ideas?
 
FIXED - at least a workaround. Per the other threads, I reinstalled libcurl and that worked.
Code:
opkg install --force-reinstall libcurl

Thought process - used 'whatdepends' to determine usage of libopenssl. From there, just reinstalled libcurl
Code:
admin@RT-AX86U-C280:/tmp/mnt/merlin/entware/etc/transmission# opkg whatdepends libopenssl
Root set:
  libopenssl
What depends on root set
        pixelserv-tls 2.4-2     depends on libopenssl
        libcurl 7.86.0-1        depends on libopenssl
        transmission-daemon 3.00-19     depends on libcurl
        transmission-web 3.00-19        depends on transmission-daemon

For next time, remember to shut down Transmission prior to updating packages.

EDIT: formatting and added context.

UPDATE: if encryption is enabled in Transmission, it's crashing. See log.

Code:
Mar 17 01:07:02 kernel: potentially unexpected fatal signal 11.
Mar 17 01:07:02 kernel: CPU: 2 PID: 13003 Comm: transmission-da Tainted: P           O    4.1.52 #2
Mar 17 01:07:02 kernel: Hardware name: Broadcom-v8A (DT)
Mar 17 01:07:02 kernel: task: ffffffc029cc4140 ti: ffffffc022d58000 task.ti: ffffffc022d58000
Mar 17 01:07:02 kernel: PC is at 0x7f7e40c9c4
Mar 17 01:07:02 kernel: LR is at 0x4175b4
Mar 17 01:07:02 kernel: pc : [<0000007f7e40c9c4>] lr : [<00000000004175b4>] pstate: 80000000
Mar 17 01:07:02 kernel: sp : 0000007f7df93fd0
Mar 17 01:07:02 kernel: x29: 0000007f7df93fd0 x28: 7fffffffffffffff
Mar 17 01:07:02 kernel: x27: 0000007f7804cf90 x26: 000000003eeadcf0
Mar 17 01:07:03 kernel: x25: 746f727020746e65 x24: 72726f5474694213
Mar 17 01:07:03 kernel: x23: 0000000000451e98 x22: 0000000000000000
Mar 17 01:07:03 kernel: x21: 0000000000453598 x20: 0000000000000014
Mar 17 01:07:03 kernel: x19: 0000000000000000 x18: 0000000000000000
Mar 17 01:07:03 kernel: x17: 000000000047a5e8 x16: 0000007f7e40c9b0
Mar 17 01:07:03 kernel: x15: 0000007f78000090 x14: 0000000000000013
Mar 17 01:07:03 transmission-daemon[13001]: tr_crypto_utils OpenSSL error: error:0308010C:digital envelope routines::unsupported (crypto-utils-openssl.c:189)
Mar 17 01:07:03 kernel: x13: 6e7c8ec8dedbd255 x12: b96b61c59469a7c4
Mar 17 01:07:03 kernel: x11: 0000000000000018 x10: 0101010101010101
Mar 17 01:07:03 kernel: x9 : cb7e726f0e2d840b x8 : 613b7cff3a2fd580
Mar 17 01:07:03 kernel: x7 : dedbd255b96b61c5 x6 : 0000007f7df94080
Mar 17 01:07:03 kernel: x5 : 0000000000000007 x4 : 0000000000000000
Mar 17 01:07:03 kernel: x3 : 0000000000000003 x2 : 0000007f780008d0
Mar 17 01:07:03 kernel: x1 : 0000000000000014 x0 : 0000000000000000
 
Last edited:
The only thing that has worked for me is to make sure that the Peer Listening port in the Transmission GUI is closed. If I allow it to be open it will crash every time.
 

This is transmission package with debian patch for openssl3 compatibility. Please test, if you need anther arch - report here.
can't load the GUI with the aarch64

404: Not Found​

Couldn't find Transmission's web interface files!

Users: to tell Transmission where to look, set the TRANSMISSION_WEB_HOME environment variable to the folder where the web interface's index.html is located.

Package Builders: to set a custom default at compile time, #define PACKAGE_DATA_DIR in libtransmission/platform.c or tweak tr_getClutchDir() by hand.
 
Last edited:
@zyxmon

Any clues for below warning ?

transmission-daemon[5433]: UDP Failed to set receive buffer: requested 4194304, got 1048576 (tr-udp.c:97)
 
Any clues for below warning ?

transmission-daemon[5433]: UDP Failed to set receive buffer: requested 4194304, got 1048576 (tr-udp.c:97)
It's fine, it was as long as I can remember. You may tweak net.core.rmem_max, net.core.wmem_max to avoid this warning. Or just ignore it.
 
The previous package version transmission-daemon_3.00-19a works! But there are reports it has memory leaks. Here is another one (based on gentoo patch) -
and

Do we install on top of previous 19a release or shall we uninstall 19a first ?

Can the memory tweak for net.core.rmem_max, net.core.wmem_max cause any memory issue to AX86 router if applied ?
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top