You seem to be executing YaST from either the user “root” or some other SysAdmin user.
If I remove the file ‘/var/log/YaST2/nohup.out’ and execute “yast2” from a “root” Konsole window, I don’t see any error and, the file isn’t created – until such time as I run one of the YaST Network modules – which then recreates (touches) the file.
Also, there ain’t no related error message in the systemd Journal.
So, the question is, what’s removing the file ‘/var/log/YaST2/nohup.out’?
It can only be a system process.
Do you have a system batch job or systemd service which performs housekeeping on the ‘/var/log’ directories?
This is a fairly vanilla install – I’m not aware of anything that should be performing housekeeping on /var/log, I certainly haven’t added anything with that explicit goal.
I was able to restore a snapshot with the issue preserved, and now that I have some idea what I’m looking for, I can report that there is no /var/log/YaST2 directory at all, (which would explain why touch would have failed.)
Which leaves me with 2 questions:
Why isn’t it there / when was it deleted? (I may just have to go through a complete reinstall and set up and audit rule for any activity on that folder.)
Why does invoking a module directly recreate it, but launching yast2 by itself not?
Simply execute, as the user “root”, “zypper install –force yast2-core” to recreate the missing directory.
But, it’s still a mystery as to why that system directory got deleted in the first place.
Please supply us with the following information:
> zypper repos --uri
Once we’ve verified that, your system’s list of openSUSE related repositories is correct, we can give you some hints to check the validity of your system’s installation.