Menu
▾
▴
1 Attachments
#1 Xalt with directdb injection with new objects query?
I was installing xalt to see how it works
In short the transmission via files works and can be translated to the DB with the python script.
But with the file transmission via directdb fails only if the object is new,if its an existing object it will happily inject the information directly into the database.
I've recorded what I've done so I wondering if you could shed some light on this or point me in the right direction.
Cheers then, Ashley
Related
Ashley,
I am sorry you are experiencing trouble with the directdb mode. That is functionality that has been working in production since version 0.5 (or earlier.) There are at least 2 sites I know of using the directdb mode in production without any issue.
I see that you are using version 0.6 and that should work. I will attempt a complete reinstall locally and see if I run into any problems, but it may take me a few days to get there. I have cc’ed my colleagues to keep them in the loop.
Mark Fahey
Ashley,
I assume the link entries are working fine in the directdb mode since you didn't mention anything about it?
Mark
Ashley,
I have tested XALT 0.7.1 on a local cluster and I do not find any problems with the directdb mode. I do not see the link_to_db() error you reported. There are a few ways forward if you have the time: try a newer version of XALT or help us debug the problem as we don't know your environment. Again, we are sorry you are having trouble and will help if we can.
Mark
I repeated the test on a different OS i.e. Centos6.7 had it work fine vs SLES11SP4
The only difference I see is possibly the LUA everything else was built with the same versions (Lmod, Python), both system LUA seems to be 5.1
But Centos provide the inbuilt support with provided back ported packages i.e. lua filesystem, bit32 & posix
With SLES, only the core LUA packages where available, so the external modules lua filesystem, bit32 and posix was custom built against it (But that kind of odd if it was as they would be using the same dependency for file and directed)
But I'm going to give it a poke again once I get some time.
Cheers then, Ashley
From: "Mark R. Fahey" markrfahey@users.sf.netamp#109;amp#97;amp#114;amp#107;amp#114;amp#102;amp#97;amp#104;amp#101;amp#121;amp#64;amp#117;amp#115;amp#101;amp#114;amp#115;amp#46;amp#115;amp#102;amp#46;amp#110;amp#101;amp#116;
Reply-To: "[xalt:tickets]" 1@tickets.xalt.p.re.sf.netamp#49;amp#64;amp#116;amp#105;amp#99;amp#107;amp#101;amp#116;amp#115;amp#46;amp#120;amp#97;amp#108;amp#116;amp#46;amp#112;amp#46;amp#114;amp#101;amp#46;amp#115;amp#102;amp#46;amp#110;amp#101;amp#116;
Date: Thursday, 7 April 2016 12:27 AM
To: "[xalt:tickets]" 1@tickets.xalt.p.re.sf.netamp#49;amp#64;amp#116;amp#105;amp#99;amp#107;amp#101;amp#116;amp#115;amp#46;amp#120;amp#97;amp#108;amp#116;amp#46;amp#112;amp#46;amp#114;amp#101;amp#46;amp#115;amp#102;amp#46;amp#110;amp#101;amp#116;
Subject: [xalt:tickets] #1 Xalt with directdb injection with new objects query?
Ashley,
I have tested XALT 0.7.1 on a local cluster and I do not find any problems with the directdb mode. I do not see the link_to_db() error you reported. There are a few ways forward if you have the time: try a newer version of XALT or help us debug the problem as we don't know your environment. Again, we are sorry you are having trouble and will help if we can.
Mark
[tickets:#1]https://sourceforge.net/p/xalt/tickets/1/ Xalt with directdb injection with new objects query?
Status: open
Milestone: 1.0
Created: Thu Mar 31, 2016 07:33 AM UTC by Ashley Chew
Last Updated: Mon Apr 04, 2016 04:25 PM UTC
Owner: nobody
Attachments:
I was installing xalt to see how it works
In short the transmission via files works and can be translated to the DB with the python script.
But with the file transmission via directdb fails only if the object is new,if its an existing object it will happily inject the information directly into the database.
I've recorded what I've done so I wondering if you could shed some light on this or point me in the right direction.
Cheers then, Ashley
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/xalt/tickets/1/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Tickets: #1
Hi Mark
Looks like it working now
I had automated the installtion via a script so I went back to basics.
Basically the module environment in my centos is a simplistic, ie straight module paths where as in our test SLES SP4 environment its more akin similar to a Cray Environment ie multiple compiler enviornments.
So the reverse map to trace to ie modules for SLES was incorrect and was correct for CENTOS.
And I think you get a NULL value which threw it out via the directdb
So adjust my script to account for multiple base module compilers now it works with the git version
Cheers then, Ashley