Manjaro machine freezes when qbittorrent runs

[jamjar]

I seem to have stabilized my system (it has up- and downloaded torrents at greater than normal usage for some 12 days without crashing).

Toward that, I did the following three things (in the order presented), which I hesitate to call a “fix” (for reasons mentioned), but somebody might find them useful.

1. Resolve a hostname conflict as described in:

@jamjar

My /etc/hosts have (relevantly):

::1        localhost ip6-localhost ip6-loopback
ff02::1    ip6-allnodes
ff02::2    ip6-allrouters
# This host address
127.0.1.1  jar-d
10.200.17.51    jar-d

–where 10.200.17.51 jar-d are the I.P. address and computer name of the VM in question.

Two circumstances confuse a causal analysis:

• The conflict had long predated a sudden increase in crashing incidence (every five minutes of active download at near ISP-maximum bandwidth), which prompted me to post here.
• The resolution of the conflict brought the incidence back to what it had been before (once every few days and not dependent on active download).

So I conclude that the conflict was probably the cause of the high incidence crashing but not of the low incidence crashing.

2. Give VM a low performance network adapter.

See: A way to choke network bandwidth used by qbittorrent during an integrity check?

But the fix was responding to a different problem.

3. Disable avahi-daemon:

@Mirdarthos

As far as I know, someone might know better than me, but as far as I know, Avahi doesn’t really seem necessary for you, so disable it:

sudo systemctl disable --now avahi-daemon

Which has ended the Mar 28 21:06:55 jar-d avahi-daemon[630]: Host name conflict, retrying with jar-d-2 type of warning in the journalctl log and also ended the low incidence crashing (for some 12 days at least).

But the following circumstance makes causation murky:

• All my other Manjaro machines have that type warning without crashing.

So we might have to say that an enabled avahi-daemon causes crashing only if a torrent client is running.

What was most useful to my investigation was this command:

@Mirdarthos

hen some system logs might help:

journalctl --priority=warning..crit --no-pager --boot=0

Where:

• The --priority=warning..err argument limits the output to warnings and errors only;
• --no-pager formats the output nicely for use here, on the forum;
• the --boot=0 argument limits the messages to be from the current boot.

I will continue to observe my system and, if it goes without incident for another couple weeks, choose a solution to close the post.