Thank you. But I don’t think I can do anything about that because this forum preserves all the edits. I can only hope nobody wants my movie files badly enough to get through to my LAN.
From that, I may presume you don’t believe disabling the avahi-daemon would have fixed that problem?
If the issue is network related - I suggest you disable IPv6 on the system.
The reason behind is the numerous errors with avahi daemon trying to assign IPv6 - it can be done from Network Manager the IPv6 tab - set Method: Disabled
Have you tried changing the vm network from dhcp to bridge ?
Perhaps disable avahi - I think it has been mentioned above somewhere
Is there a version of one of these commands (or some other) I could run before the system crashes again, to see whether it was having trouble (i.e. generating such lines as Host name conflict, retrying with jar-d-3248 but somehow managing to stay up).
An ideal command would give me only the lines generated after the last crash and relating to some trouble the system was having.
I am sorry. I thought the command was only for diagnosing a crash because that was the only time I ever used it. Thanks for actually answering my clueless questions.
You’d already given me the command in your very first reply! Thanks.
Thank you. After disabling avahi-daemon (following the last crash), I don’t seem to get any more lines similar to: Host name conflict, retrying with jar-d-3248.
Were there some other lines pointing to IPv6 as a potential culprit?
Another thing I’ve found out, my other Manjaro VMs (which do not have a torrent client running and never crash) are also quietly stacking up such lines as: Apr 03 12:23:09 jar-m avahi-daemon[653]: Host name conflict, retrying with jar-m-5705 (see the whopping 5705).
Maybe that line in the affected machine is not a clue to why it is crashing.
Of course, it’s also possible that it is the cause but does not have an opportunity to do its work when no torrent client is present.
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.
Resolve a hostname conflict as described in:
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.
But the fix was responding to a different problem.
Disable 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:
I will continue to observe my system and, if it goes without incident for another couple weeks, choose a solution to close the post.