Our clustername does not have a "-" but the hostname does. Does the slurmdbd accounting try to create a table name based on the hostname or clustername only?
-SS- -----Original Message----- From: slurm-users [mailto:slurm-users-boun...@lists.schedmd.com] On Behalf Of Matthew BETTINGER Sent: Thursday, January 17, 2019 12:22 PM To: Slurm User Community List <slurm-users@lists.schedmd.com> Subject: Re: [slurm-users] SlurmDBD setup with mysql Not Sure if this is related but we ran into an issue configuring accounting because our clustername had a '-' in the name . This is an illegal character for table names in mariadb, or used to be. On 1/17/19, 11:07 AM, "slurm-users on behalf of Sajesh Singh" <slurm-users-boun...@lists.schedmd.com on behalf of ssi...@amnh.org> wrote: Trying to setup accounting using the MySQL backend and I am getting errors from the slurmctld and slurm tools when trying to interact with the accounting database. Tried starting in debug as well, but could not see anything else that could point to what could be causing this issue. I have followed all steps listed at: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fslurm.schedmd.com%2Faccounting.html&data=02%7C01%7Cssingh%40amnh.org%7C2ce165cc81124026896108d67ca068b0%7Cbe0003e8c6b9496883aeb34586974b76%7C0%7C0%7C636833425733660582&sdata=MzWBFh24AktsBE6zHl1a%2FMEXd78BCK57u0%2Bl%2Fl%2Fn7kw%3D&reserved=0 The DBD daemon starts up without error as can be seen from the logs: Slurmdbd.log: [2019-01-17T10:18:40.365] chdir to /var/tmp [2019-01-17T10:18:40.367] slurmdbd version 18.08.4 started Though in the slurmctld.log file I am seeing the following: [2019-01-17T10:19:40.024] error: Persistent Conn: read: No error [2019-01-17T10:19:40.024] error: Persistent Conn: only read 117 of 2613 bytes [2019-01-17T10:19:40.025] error: Persistent Conn: read: No error [2019-01-17T10:19:40.025] error: Persistent Conn: only read 117 of 2613 bytes [2019-01-17T10:19:40.025] error: Persistent Conn: read: No error [2019-01-17T10:19:40.025] error: Persistent Conn: only read 119 of 1375731712 bytes [2019-01-17T10:19:40.025] error: Persistent Conn: read: No error [2019-01-17T10:19:40.025] error: Persistent Conn: only read 117 of 2613 bytes [2019-01-17T10:19:40.025] error: slurm_persist_conn_open: Failed to unpack persistent connection init resp message from 127.0.0.1:3306 [2019-01-17T10:19:40.025] error: slurmdbd: Sending PersistInit msg: No error I do restart all services in the order of munge, dbd, slurmctld after config changes. The relevant configs are as follows: slurmdbd.conf: AuthType=auth/munge DbdAddr=127.0.0.1 DbdHost=localhost DbdPort=7031 SlurmUser=slurm LogFile=/var/log/slurmdbd.log PidFile=/var/run/slurmdbd.pid StorageType=accounting_storage/mysql StorageHost=localhost StoragePort=3306 StoragePass=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx StorageUser=slurm StorageLoc=slurm_acct_db slurm.conf: AccountingStorageType=accounting_storage/slurmdbd AccountingStorageHost=127.0.0.1 AccountingStoragePort=3306 AccountingStorageUser=slurm AccountingStorageEnforce=limits AccountingStoreJobComment=YES AcctGatherNodeFreq=30 ClusterName=ares JobAcctGatherFrequency=30 JobAcctGatherType=jobacct_gather/linux We are running Slurm 18.04 on CentOS 7 with MariaDB as the backend. -SS-
