Hi, I'm getting closer to having Amanda 2.5.2p1 working on my Cobalt Raq-4i system which now runs StrongBolt OS (based on CentOS 4.4). The amandad client running on the Cobalt system was complaining about /etc/amandates not existing even though I don't think it gets used. On this Sunblade 1000 system the /etc/amandates file never gets touched when the client runs on it each night.
Anyway sorted that out, and last night's run logged these messages in the main amanda report generated on the tape server host machine: ziri /dev/hda6 lev 0 FAILED [no size line match in /sbin/dump output] ziri /dev/hda2 lev 0 FAILED [no size line match in /sbin/dump output] ziri /dev/hda1 lev 0 FAILED [no size line match in /sbin/dump output] and I noticed that the amcheck run a few hours ago (I schedule it for 4 pm) reported this: Amanda Backup Client Hosts Check -------------------------------- ERROR: ziri: [could not access /dev/hda6 (/dev/hda6): Permission denied] ERROR: ziri: [could not access /dev/hda2 (/dev/hda2): Permission denied] ERROR: ziri: [could not access /dev/hda1 (/dev/hda1): Permission denied] which is rather strange as I've already made sure, as far as I'm aware, that the disk devices are in the same group (sys) as the 'amanda' user (and 'amanda' is included in group 'sys' in the /etc/group file on the Cobalt machine). Any idea what the problem might be? I've overlooked something simple... Just trying to figure out what it is. 8-) I've attached the client debug file from the main run at 12.45 am this morning, and the amandad debug files from the 0045 run and the 4 pm amcheck run this afternoon. Craig. -- Craig Dewick ([EMAIL PROTECTED]). http://lios.apana.org.au/~craig RailZone Australia: http://www.railzone.org ([EMAIL PROTECTED]) The SunShack: http://www.sunshack.org ([EMAIL PROTECTED]) ClassicSaab: http://www.classicsaab.net ([EMAIL PROTECTED])
sendsize.20080613004502.debug
Description: Binary data
amandad.20080613004502.debug
Description: Binary data
amandad.20080613160501.debug
Description: Binary data
