lmtinit error

32 views
Skip to first unread message

Andreas Davour

unread,
Feb 9, 2011, 8:36:50 AM2/9/11
to lmt-d...@googlegroups.com

I have installed lmt and are now trying to prepare the mysql db. Then I get
this error:
# lmtinit -a cfs-l
lmtinit: error creating database filesystem_cfs-l: You have an error in your
SQL syntax; check the manual that corresponds to your MySQL server version for
the right syntax to use near '-l' at line 1

Any feedback on that error?

/andreas
--
Systems Engineer
PDC Center for High Performance Computing
CSC School of Computer Science and Communication
KTH Royal Institute of Technology
SE-100 44 Stockholm, Sweden
Phone: 087906658
"A satellite, an earring, and a dust bunny are what made America great!"

Jim Garlick

unread,
Feb 9, 2011, 8:49:24 AM2/9/11
to lmt-d...@googlegroups.com
Hi Andreas,

Sounds like bug. Possibly we need to change lmt so that any characters
in file system names that mysql doesn't like for database names get translated.

I have opened an issue in the lmt google code site to track this and will
look more closely later today:

http://code.google.com/p/lmt/issues/detail?id=48&colspec=ID%20Type%20Status%20Owner%20Summary

Jim

> --
> You received this message because you are subscribed to the Google Groups "lmt-discuss" group.
> To post to this group, send email to lmt-d...@googlegroups.com.
> To unsubscribe from this group, send email to lmt-discuss...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/lmt-discuss?hl=en.
>
>

davour

unread,
Feb 9, 2011, 8:51:28 AM2/9/11
to lmt-discuss
On Feb 9, 2:49 pm, Jim Garlick <garlick....@gmail.com> wrote:
> Hi Andreas,
>
> Sounds like bug.  Possibly we need to change lmt so that any characters
> in file system names that mysql doesn't like for database names get translated.
>
> I have opened an issue in the lmt google code site to track this and will
> look more closely later today:
>
> http://code.google.com/p/lmt/issues/detail?id=48&colspec=ID%20Type%20...

Excellent. Thanks Jim.

/andreas

Jim Garlick

unread,
Feb 9, 2011, 10:50:06 AM2/9/11
to lmt-d...@googlegroups.com
Andreas,
I have a fix checked in - looks like all that was needed were quotes in
the sql commands used to manipulate database names.
Is it possible for you to verify by exporting directly from the svn trunk or
would you like me to build you a test .src.rpm to try?
I'd like to make everything works for you before I tag a real release.
Jim

davour

unread,
Feb 9, 2011, 4:11:25 PM2/9/11
to lmt-discuss
On Feb 9, 4:50 pm, Jim Garlick <garlick....@gmail.com> wrote:
> Andreas,
> I have a fix checked in - looks like all that was needed were quotes in
> the sql commands used to manipulate database names.
> Is it possible for you to verify by exporting directly from the svn trunk or
> would you like me to build you a test .src.rpm to try?
> I'd like to make everything works for you before I tag a real release.

It would be great if you could provide a rpm for testing.

/andreas

Jim Garlick

unread,
Feb 9, 2011, 4:32:07 PM2/9/11
to davour, lmt-discuss

OK, here you go. Please let me know how it goes.
If the .src.rpm is too new for your rpm, then try the attached tarball:
untar
./configure
make rpm
and look for built rpms in ./rpm

Jim


lmt-3.1.1-2test.src.rpm
lmt-3.1.1.tar.gz

davour

unread,
Feb 10, 2011, 6:01:29 AM2/10/11
to lmt-discuss


On Feb 9, 10:32 pm, Jim Garlick <garl...@llnl.gov> wrote:
> On Wed, Feb 09, 2011 at 01:11:25PM -0800, davour wrote:
> > On Feb 9, 4:50�pm, Jim Garlick <garlick....@gmail.com> wrote:
> > > Andreas,
> > > I have a fix checked in - looks like all that was needed were quotes in
> > > the sql commands used to manipulate database names.
> > > Is it possible for you to verify by exporting directly from the svn trunk or
> > > would you like me to build you a test .src.rpm to try?
> > > I'd like to make everything works for you before I tag a real release.
>
> > It would be great if you could provide a rpm for testing.
>
> OK, here you go.  Please let me know how it goes.
> If the .src.rpm is too new for your rpm, then try the attached tarball:
>  untar
>  ./configure
>  make rpm
> and look for built rpms in ./rpm

OK, I have deployed the patched version and can now create the db, and
lmtinit works as intended.

Now lmtsh also shows both _DATA and _AGGREGATE_ tables getting
populated. Thanks!

/andreas
Reply all
Reply to author
Forward
0 new messages