Hi Marc, I'd recommend sticking with slurmdbd, rather than going to straight to mysql. The extra layer of the dbd probably gives you more in the long run (better reporting, and if you have multiple clusters it's more scalable to have one dbd talk to the database).
In that light, I'd say the error is probably something to do with the settings required for accounting_storage/mysql vs accounting_storage/slurmdbd. The entry for AccountingStoragePass in the man page suggests that your setup is looking for a munge socket at that setting -- hence your 'no such file' error. Paddy On Tue, Apr 15, 2014 at 12:28:56AM -0700, Marc Vecsys wrote: > Hi > my accounting was working with slurmdbd but not anymore with mysql. > i saw post with similar error, but that was bugs, I don't know what's wrong > Thanks for your help. > marc > > works fine on all machines: > munge -n | unmunge > > config: > AccountingStorageType=accounting_storage/mysql > AccountingStorageHost=msfdev-msf.AAA.dmz > #AccountingStorageLoc=/home/MSF/slurm/slurm_job_accounting.txt > AccountingStorageEnforce=associations,limits,qos > AccountingStorageUser=slurm > AccountingStoragePass=PASSWORD > > command > [root@frontal1 slurm]# sudo -u client1 sbatch -o /home/MSF/slurm/%j.log -e > /home/MSF/slurm/%j.log -M msf -A transcription /home/MSF/slurm/test.sh > sbatch: error: Munge encode failed: Failed to access "PASSWORD": No such > file or directory (retrying ...) > sbatch: error: Munge encode failed: Failed to access "PASSWORD": No such > file or directory (retrying ...) > sbatch: error: Munge encode failed: Failed to access "PASSWORD": No such > file or directory > sbatch: error: authentication: Socket communication error > sbatch: error: Batch job submission failed: Protocol authentication error -- Paddy Doyle Trinity Centre for High Performance Computing, Lloyd Building, Trinity College Dublin, Dublin 2, Ireland. Phone: +353-1-896-3725 http://www.tchpc.tcd.ie/
