You said:

Can anyone explain to me what I'm doing wrong, and how to fix this?

Well, there are some questions to be exammined here:

• What message do you get when you run the perl code outside of your CGI environment?
• What happens when you run your CGI code with the Perl code stubbed out? (Mock up a set of return values and return them with out benefit of any DB calls.)
• What is 'process 2754'? And which call in glibc is going walk-about? Glibc is the Gnu implementation of the C Standard Interfaces library and it sounds like there is a low-level system call with somthing funny in the parameter list.

You have a three part contraption here involving CGI, a Database engine, and some Perl gluing the various part together. You need to isolate which leg of the tripod is broken. If I was to offer a wild guess, I bet that something being passed to the DBI driver is wonky. But I wouldn't bet my mornng cup of coffee on it.