[02:32] <Guest42> hi 
[02:33] <sarnold> hello
[02:33] <Guest42> Anyone can help me  to install amavisd-new please?
[02:33] <Guest42> sarnold Hello
[02:34] <Guest42> I have encontrod an error during instalation
[02:36] <Guest42> I have using this command
[02:36] <Guest42> apt -y install clamav-daemon amavisd-new 
[02:36] <Guest42> Error here
[02:36] <Guest42> Creating/updating amavis user account...
[02:36] <Guest42> Job for amavis.service failed because the control process exited with error code.
[02:36] <Guest42> See "systemctl status amavis.service" and "journalctl -xe" for details.
[02:36] <Guest42> invoke-rc.d: initscript amavis, action "start" failed.
[02:36] <Guest42> ● amavis.service - LSB: Starts amavisd-new mailfilter
[02:36] <Guest42>      Loaded: loaded (/etc/init.d/amavis; generated)
[02:36] <Guest42>      Active: failed (Result: exit-code) since Thu 2021-09-09 01:58:17 UTC; 10ms ago
[02:36] <Guest42>        Docs: man:systemd-sysv-generator(8)
[02:36] <Guest42>     Process: 2861 ExecStart=/etc/init.d/amavis start (code=exited, status=1/FAILURE)
[02:37] <sarnold> Guest42: does amavisd have its own logs in /var/log/ that might say what failed?
[02:37] <sarnold> Guest42: maybe journactl -e   will show you an error message, but I'd expect its own log files to be more useful
[02:40] <Guest42> sarnold Thanks for your suggestion, I will check it
[02:41] <Guest42> There is no error log in /var/log/ for amavis
[02:41] <sarnold> Guest42: dang. maybe just the syslog then?
[02:45] <Guest42> Sep 09 01:58:17 mail.myhostname.com amavis[2861]: Starting amavisd:
[02:45] <Guest42> Sep 09 01:58:17 mail.myhostname.com amavis[2875]: Insecure directory in $ENV{PATH} while running with -T switch at /usr/sbin/amavisd-new line 4353.
[02:45] <Guest42> Sep 09 01:58:17 mail.myhostname.com amavis[2861]: (failed).
[02:45] <Guest42> This lines by  journactl -ex
[02:46] <Guest42> sarnold Insecure directory in $ENV{PATH} while running with -T switch at /usr/sbin/amavisd-new line 4353. 
[02:47] <Guest42> I can't understand the error line!
[02:53] <sarnold> Guest42: oh *wow*
[02:57] <sarnold> Guest42: ok.. so, my guess is that means the permissions or ownership of a directory somewhere on your system isn't right
[02:57] <sarnold> Guest42: and that error message feels like perl has done something very kind and considerate to warn you :)
[02:57] <sarnold> Guest42: now, the complication is that the PATH environment variable can be unique for every single process on the system...
[02:58] <sarnold> Guest42: it's *easy* to see what things look like in your current shell
[02:58] <sarnold> Guest42: but that might not reflect the status in the init script that starts amivisd... so. lets check the easy thing first
[02:58] <sarnold> Guest42: for d in `tr : \\\n <<< "$PATH"` ; do namei -l $d ; done
[02:59] <sarnold> Guest42: oh yeah, also just a plain echo $PATH -- maybe it's got current working directory in it
[03:01] <oerheks> journalctl -eu amavis
[03:01] <sarnold> Guest42: if nothing looks too strange with your current shell, then try adding echo $PATH and ^^ that loop around namei -l  into your /etc/init.d/amavis file -- then systemctl restart amavis -- then check the journal? or syslog? I'm not sure where the output would go. heh.
[03:06] <Guest42> sarnold You are right
[03:06] <Guest42> https://paste.gnome.org/pyjohhjtc/xx8qqa/raw
[03:06] <Guest42> I cant sure 
[03:07] <Guest42> but, I think there is some bin directory with 777! permesion
[03:07] <sarnold> those are symlinks as part of the 'usrmerge' transition
[03:07] <Guest42> I think this line drwxrwxrwx root root bin
[03:07] <sarnold> I wonder if perl knows about those
[03:08] <sarnold> OOOPS
[03:08] <sarnold> Guest42: good thing *you* read this too :)
[03:08] <sarnold> I missed that completely. yeah.
[03:08] <Guest42> oerheks Thanks, it show the some error line.
[03:09] <Guest42> I will try to change that and let you know
[03:09] <sarnold> Guest42: first thing, chmod 755 /usr/bin   -- second thing, figure out if anything was dropped in that directory that shouldn't have been
[03:09] <sarnold> third thing, figure out what changed that mode
[03:13] <Guest42> Wow
[03:13] <Guest42> sarnold you are Great!
[03:14] <Guest42> worked
[03:14] <sarnold> Guest42: it was (probably) perl that pointed out the problem :D
[03:14] <Guest42> Thank you so much
[03:14] <sarnold> and I'm *so* glad you read the output so much more carefully than I did
[03:21] <Guest42> sarnold Your feedback is great, I learned a lot from you.
[03:21] <Guest42> Thank you again
[03:21] <sarnold> Guest42: glad to hear it ;) you're welcome :)