Read the ReleaseNotes and we will find that suid have changed in 3.5
Le lun. 10 déc. 2018, à 16 h 35, Charles Stroom <[email protected]> a écrit : > Sorry, but below replace "sticky bit" by "suid bit". > > Charles > > Begin forwarded message: > > Date: Mon, 10 Dec 2018 21:10:36 +0100 > From: Charles Stroom <[email protected]> > To: [email protected] > Subject: amanda backup fails, because of wrong suid settings > > > Hi all, > > This is on Linux Opensuse 42.3 with amanda 3.5.1 compiled from tar > file. Today I discovered that amcheck failed to run, while during the > last backup on 2018-12-06 there were no problems with amcheck and > the subsequent amdump. But today I got: > ---- > From: "(Cron Daemon)" <[email protected]> > To: [email protected] > Subject: Cron <amanda@fiume7> amcheck -a daily_lto2 > Date: Mon, 10 Dec 2018 17:52:01 +0100 (CET) > > > ** (process:16780): CRITICAL **: amcheck must not be setuid (0, 37) > ---- > > Odd, but I cleared the sticky bit, and then amcheck produced a normal > output and reported 0 errors. > > However, the subsequent amdump failed: > ---- > From: [email protected] (Amanda Backup) > To: [email protected] > Subject: daily_backup FAIL: AMANDA MAIL REPORT FOR ? 2, 0 > Date: Mon, 10 Dec 2018 18:29:02 +0100 > User-Agent: Heirloom mailx 12.5 7/5/10 > > *** THE DUMPS DID NOT FINISH PROPERLY! > > Org : daily_backup > Config : daily_lto2 > Date : ? 2, 0 > > > > FAILURE DUMP SUMMARY: > driver: FATAL Did not get DATE line from planner > > > STATISTICS: > Total Full Incr. Level:# > -------- -------- -------- -------- > Estimate Time (hrs:min) 0:00 > Run Time (hrs:min) 0:00 > Dump Time (hrs:min) 0:00 0:00 0:00 > Output Size (meg) 0.0 0.0 0.0 > Original Size (meg) 0.0 0.0 0.0 > Avg Compressed Size (%) -- -- -- > DLEs Dumped 0 0 0 > Avg Dump Rate (k/s) -- -- -- > > Tape Time (hrs:min) 0:00 0:00 0:00 > Tape Size (meg) 0.0 0.0 0.0 > Tape Used (%) 0.0 0.0 0.0 > DLEs Taped 0 0 0 > Parts Taped 0 0 0 > Avg Tp Write Rate (k/s) -- -- -- > > > DUMP SUMMARY: > DUMPER STATS TAPER > STATS > HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s > MMM:SS KB/s -------------------------- ---------------------- > --------------------------- > > (brought to you by Amanda version 3.5.1) > ---- > > and when I looked at the amdump.1 file it seemed like a similar uid > problem: ---- > amdump: start at Mon Dec 10 18:31:40 CET 2018 > amdump: datestamp 20181210 > amdump: starttime 20181210183140 > amdump: starttime-locale-independent 2018-12-10 18:31:40 CET > > ** (process:18834): CRITICAL **: planner must not be setuid root > driver: pid 18835 executable /usr/lib/amanda/driver version 3.5.1 > driver: Did not get DATE line from planner > amdump: end at Mon Dec 10 18:31:40 CET 2018 > /var/log/amanda/daily_lto2/amdump.1 (END) > ---- > > Now I got suspicious, because there were no problems a few days ago and > suddenly all this sticky bit business. Has my system been tampered > with? I then compared the file modes of my current amanda installation > with my installation in my previous version of opensuse (42.1, same > 3.5.1 version) and found that indeed in 42.1 amcheck did not have a > sticky bit set (??), but planner (and a couple) > of other amanda programs in /usr/lib/amanda do have sticky bits set. > > Of course I can take the sticky bit of planner away, but I would like > to have an opinion of the more knowledgeable forum. Could there be > another reason why all of a sudden there are these problems? > > Many thanks, > > Charles > > > > > > > -- > Charles Stroom > email: charles at no-spam.stremen.xs4all.nl (remove the "no-spam.") > > > -- > Charles Stroom > email: charles at no-spam.stremen.xs4all.nl (remove the "no-spam.") >
