Hi,
the error looks like due to the failed mysql connection that creates the
variable conn which is used to rollback in case of error. To be quite
honest the rollback is unnecessary when there is no writing to the
database, but the problem for you is the failed connection.
Are the DPM password files readable?
cheers
alessandra
PS the error John sees is harmless.
On 18/11/2015 12:03, Matt Doidge wrote:
> I've tried to test it out at Lancaster but no joy - we have a SL6
> headnode with 1.8.9, but I'm having no joy running the dump script
> manually:
>
> Traceback (most recent call last):
> File "dpm_dump_.py1115", line 171, in <module>
> dump_data(conn_data, options)
> File "dpm_dump_.py1115", line 74, in dump_data
> conn.rollback()
> UnboundLocalError: local variable 'conn' referenced before assignment
>
>
> I've not installed any extra python packages so I could be missing
> something there. I had no trouble getting older versions of the
> dpm_dump.py script to work (i.e. pre the 2015/07/03 update) though.
>
> I was hoping this would be a low hanging fruit! Any thoughts would be
> appreciated.
>
> Cheers,
> Matt
>
> On 18/11/15 10:54, John Hill wrote:
>> I've just tested this on the smallest of my space tokens
>> (ATLASSCRATCHDISK). I have DPM 1.8.8 on a SL5 SE. Hence I had to install
>> "python26" and python26-mysqld" to allow the script to work. I then get:
>>
>> # python26 dpm_dump.py -t dump_151115 -p
>> /dpm/hep.phy.cam.ac.uk/home/atlas/atlasscratchdisk/rucio -a 3
>> All done!
>> Exception _mysql_exceptions.InterfaceError: (0, '') in <bound method
>> SSCursor.__del__ of <MySQLdb.cursors.SSCursor object at 0x1b73f6d0>>
>> ignored
>>
>> This takes about 10 minutes for a 31TB space token (13.2TB used). I am
>> assuming that the exception doesn't affect the dump as it occurs after
>> the "All done!", and because there are 326k lines in the dump file.
>>
>> Incidentally, the dump is just a list of files.
>>
>> John
|