Transmission crash

[mistert]

Hi all, from time to time I find transmission server stoped. Consequently I go web ui and click on "start server" in transmission tab.

Is it a known bug ? Is there a way to get notified when transmission server goes down ?

Thank you for reading.

[fvdw-sl 18.3 (isp2)]

[Jocko]

Hi

Transmission client may use a large part of the nas memory according to download files number or peers number or transfer speed...
And when there is no enough free memory,its process is killed by by the kernel

Currently there is no notification about this event but you can create it yourself by writing a script which wil check if a transmission process is running and otherwise send a mail (of course you have to configure notification settings).
Then add a cron job which will run your shell at every hour for example

But I go to look at if I can implement it easily

[mistert]

Thanks for your answer, appreciated.

[Jocko]

Hi

It is done...

So you have to install the last patch for version 18.3 : http://plugout.net/viewtopic.php?f=7&p=39925#p39925

New-tr-menu.jpg

[mistert]

You're so fast, didn't had the time to look at a script yet ! Thank you ! I will instal last patch asap.

edit:Fail: zip file can't be used with this control code (7433)

[Jocko]

Hi what way did you use ?

Patch ID (7433) must be used only if you had installed patch 03 previously

Otherwise you have to use the old way :

How to install the patch (only if you do not have yet installed patch03):
- Save the attached zip archive in the file share 'fvdw'[1]
- Go to the upload patch menu of the web interface
- Select the file in the first field (click on the small button "...")
- Put in the second field (control code) the following code : "unzip" (without quotes)

After installing it, web interface will be relaoded but you have to reboot the nas to complete fully patch installation (linked with fs check feature)

[1] If you did not create it yet, you need to create first a share "fvdw" (use the menu 'File share')

So control code is unzip

Note: I made a minor change on the sent message. So please to use the latest version (7 oct 2025)

[mistert]

thank you for the guidances, fvdw-sl-18.3-patch04-07oct2025 installed. Issue with notification set up though. Set up properly I think. When sending a test email, got "email sent" but email not received :hammerhead

[Jocko]

Hi

if you use a gmail address it is the expected behaviour. Since 2 years now, Google blocks sent messages if the connection does not use its own authentication mechanism. Currently I did not yet look at how to implement it as I nearly think it is not possible by using openssl. On the user side you have no notification.

otherwise look at if the test message is not detected as a spam message

[mistert]

Spam is the first thing I thought about :punk Nevermind I will use another mail provider ;)
edit: same issue with another mail provider :hammerhead

[Jocko]

Did you search on the Net what are the right settings with your provider (port SMTP server....)?