'invalid pointer' with ODBC on CentOS 7
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm running into an 'invalid pointer' with ODBC on a CentOS 7 machine while developing a new Asterisk (PBX) configuration.
A previous server with identical set-up (unixODBC version 2.3.1) works fine. But when I re-install everything on a new server, I get the following error while testing the ODBC connection.
# isql -v asterisk-connector
*** Error in `isql': munmap_chunk(): invalid pointer: 0x0000000001cb2728 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7f5d4)[0x7f476735d5d4]
/usr/lib64/libmyodbc5.so(MySQLGetPrivateProfileStringW+0x104)[0x7f47605563c4]
/usr/lib64/libmyodbc5.so(ds_lookup+0x5d)[0x7f4760555ced]
/usr/lib64/libmyodbc5.so(MySQLConnect+0xc6)[0x7f47605394c6]
/lib64/libodbc.so.2(SQLConnect+0xa63)[0x7f4767f2b3b3]
isql[0x4028a9]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f47673003d5]
isql[0x402c39]
======= Memory map: ========
The ODBC configuration is as follows:
==> /etc/odbc.ini <==
[asterisk-connector]
Description= MySQL connection to 'asterisk' database
Driver= MySQL
Database= asterisk
Server= localhost
User= asterisk
Password= secretpasswd
Port= 3306
Socket= /var/lib/mysql/mysql.sock
==> /etc/odbcinst.ini <==
# Driver from the mysql-connector-odbc package
# Setup from the unixODBC package
[MySQL]
Description = ODBC for MySQL
Driver64 = /usr/lib64/libmyodbc5w.so
Setup64 = /usr/lib64/libodbcmyS.so
FileUsage = 1
# odbcinst -j
unixODBC 2.3.1
DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /root/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8
At this point I feel like I have compared both servers to the last bit on their drives and scanned the internet for similar issues, and I have no idea what to do anymore.
SOLVED:
This issue was caused because a MySQL ODBC connector was being used for a incompatible MariaDB database.
Solved by downloading the correct driver (in my case http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64//mysql-connector-odbc-8.0.15-1.el7.x86_64.rpm) and editing the odbcinst.ini file as follows:
[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=1
[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1
Lots of thanks to @Pimp Juice IT and my co-worker!
I hope this helps others who experience this issue.
linux centos mysql odbc
asked Feb 10 at 14:30
OlivierOlivier
63
|
show 2 more comments
I'm running into an 'invalid pointer' with ODBC on a CentOS 7 machine while developing a new Asterisk (PBX) configuration.
A previous server with identical set-up (unixODBC version 2.3.1) works fine. But when I re-install everything on a new server, I get the following error while testing the ODBC connection.
# isql -v asterisk-connector
*** Error in `isql': munmap_chunk(): invalid pointer: 0x0000000001cb2728 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7f5d4)[0x7f476735d5d4]
/usr/lib64/libmyodbc5.so(MySQLGetPrivateProfileStringW+0x104)[0x7f47605563c4]
/usr/lib64/libmyodbc5.so(ds_lookup+0x5d)[0x7f4760555ced]
/usr/lib64/libmyodbc5.so(MySQLConnect+0xc6)[0x7f47605394c6]
/lib64/libodbc.so.2(SQLConnect+0xa63)[0x7f4767f2b3b3]
isql[0x4028a9]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f47673003d5]
isql[0x402c39]
======= Memory map: ========
The ODBC configuration is as follows:
==> /etc/odbc.ini <==
[asterisk-connector]
Description= MySQL connection to 'asterisk' database
Driver= MySQL
Database= asterisk
Server= localhost
User= asterisk
Password= secretpasswd
Port= 3306
Socket= /var/lib/mysql/mysql.sock
==> /etc/odbcinst.ini <==
# Driver from the mysql-connector-odbc package
# Setup from the unixODBC package
[MySQL]
Description = ODBC for MySQL
Driver64 = /usr/lib64/libmyodbc5w.so
Setup64 = /usr/lib64/libodbcmyS.so
FileUsage = 1
# odbcinst -j
unixODBC 2.3.1
DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /root/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8
At this point I feel like I have compared both servers to the last bit on their drives and scanned the internet for similar issues, and I have no idea what to do anymore.
SOLVED:
This issue was caused because a MySQL ODBC connector was being used for a incompatible MariaDB database.
Solved by downloading the correct driver (in my case http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64//mysql-connector-odbc-8.0.15-1.el7.x86_64.rpm) and editing the odbcinst.ini file as follows:
[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=1
[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1
Lots of thanks to @Pimp Juice IT and my co-worker!
I hope this helps others who experience this issue.
linux centos mysql odbc
asked Feb 10 at 14:30
OlivierOlivier
63
What's the output that shows when you runodbcinst -q -d? Also if you put the username and password in the command rather than in theodbc.inifile, does that make any difference for your result when you run? I assume you confirmed the asterisk SQL login exists already and has been granted access to the DB it needs to access, right?
– Pimp Juice IT
Feb 10 at 15:53
Thanks for your input!odbcinst -q -dshows only one configured driver:[MySQL]I didn't try providing the parameters to the isql command, but I get the same result when I do# isql -v asterisk-connector asterisk secretpasswdIn MySQL CLI everything works fine.
– Olivier
Feb 10 at 17:05
Does usingServer= 127.0.0.1in the ini config file versuslocalhostmake any difference for your result? Not sure if the MySQL service needs restarted or not after making such changes, but if you can, in the name of thoroughness, that's what I'd do after setting and before testing the change.
– Pimp Juice IT
Feb 10 at 17:08
Wow, hadn't even thought of that! I just tried everything again, at first no difference, but withisql -v asterisk-connector asterisk secretpasswdI now getSegmentation fault
– Olivier
Feb 10 at 17:27
If I don't provide the username/password, I just get the samemunmap_chunk(): invalid pointererror
– Olivier
Feb 10 at 17:28
|
show 2 more comments
I'm running into an 'invalid pointer' with ODBC on a CentOS 7 machine while developing a new Asterisk (PBX) configuration.
A previous server with identical set-up (unixODBC version 2.3.1) works fine. But when I re-install everything on a new server, I get the following error while testing the ODBC connection.
# isql -v asterisk-connector
*** Error in `isql': munmap_chunk(): invalid pointer: 0x0000000001cb2728 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7f5d4)[0x7f476735d5d4]
/usr/lib64/libmyodbc5.so(MySQLGetPrivateProfileStringW+0x104)[0x7f47605563c4]
/usr/lib64/libmyodbc5.so(ds_lookup+0x5d)[0x7f4760555ced]
/usr/lib64/libmyodbc5.so(MySQLConnect+0xc6)[0x7f47605394c6]
/lib64/libodbc.so.2(SQLConnect+0xa63)[0x7f4767f2b3b3]
isql[0x4028a9]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f47673003d5]
isql[0x402c39]
======= Memory map: ========
The ODBC configuration is as follows:
==> /etc/odbc.ini <==
[asterisk-connector]
Description= MySQL connection to 'asterisk' database
Driver= MySQL
Database= asterisk
Server= localhost
User= asterisk
Password= secretpasswd
Port= 3306
Socket= /var/lib/mysql/mysql.sock
==> /etc/odbcinst.ini <==
# Driver from the mysql-connector-odbc package
# Setup from the unixODBC package
[MySQL]
Description = ODBC for MySQL
Driver64 = /usr/lib64/libmyodbc5w.so
Setup64 = /usr/lib64/libodbcmyS.so
FileUsage = 1
# odbcinst -j
unixODBC 2.3.1
DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /root/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8
At this point I feel like I have compared both servers to the last bit on their drives and scanned the internet for similar issues, and I have no idea what to do anymore.
SOLVED:
This issue was caused because a MySQL ODBC connector was being used for a incompatible MariaDB database.
Solved by downloading the correct driver (in my case http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64//mysql-connector-odbc-8.0.15-1.el7.x86_64.rpm) and editing the odbcinst.ini file as follows:
[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=1
[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1
Lots of thanks to @Pimp Juice IT and my co-worker!
I hope this helps others who experience this issue.
linux centos mysql odbc
asked Feb 10 at 14:30
OlivierOlivier
63
I'm running into an 'invalid pointer' with ODBC on a CentOS 7 machine while developing a new Asterisk (PBX) configuration.
A previous server with identical set-up (unixODBC version 2.3.1) works fine. But when I re-install everything on a new server, I get the following error while testing the ODBC connection.
# isql -v asterisk-connector
*** Error in `isql': munmap_chunk(): invalid pointer: 0x0000000001cb2728 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7f5d4)[0x7f476735d5d4]
/usr/lib64/libmyodbc5.so(MySQLGetPrivateProfileStringW+0x104)[0x7f47605563c4]
/usr/lib64/libmyodbc5.so(ds_lookup+0x5d)[0x7f4760555ced]
/usr/lib64/libmyodbc5.so(MySQLConnect+0xc6)[0x7f47605394c6]
/lib64/libodbc.so.2(SQLConnect+0xa63)[0x7f4767f2b3b3]
isql[0x4028a9]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f47673003d5]
isql[0x402c39]
======= Memory map: ========
The ODBC configuration is as follows:
==> /etc/odbc.ini <==
[asterisk-connector]
Description= MySQL connection to 'asterisk' database
Driver= MySQL
Database= asterisk
Server= localhost
User= asterisk
Password= secretpasswd
Port= 3306
Socket= /var/lib/mysql/mysql.sock
==> /etc/odbcinst.ini <==
# Driver from the mysql-connector-odbc package
# Setup from the unixODBC package
[MySQL]
Description = ODBC for MySQL
Driver64 = /usr/lib64/libmyodbc5w.so
Setup64 = /usr/lib64/libodbcmyS.so
FileUsage = 1
# odbcinst -j
unixODBC 2.3.1
DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /root/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8
At this point I feel like I have compared both servers to the last bit on their drives and scanned the internet for similar issues, and I have no idea what to do anymore.
SOLVED:
This issue was caused because a MySQL ODBC connector was being used for a incompatible MariaDB database.
Solved by downloading the correct driver (in my case http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64//mysql-connector-odbc-8.0.15-1.el7.x86_64.rpm) and editing the odbcinst.ini file as follows:
[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=1
[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1
Lots of thanks to @Pimp Juice IT and my co-worker!
I hope this helps others who experience this issue.
linux centos mysql odbc
linux centos mysql odbc
asked Feb 10 at 14:30
OlivierOlivier
63
asked Feb 10 at 14:30
OlivierOlivier
63
edited Feb 26 at 12:07
Olivier
asked Feb 10 at 14:30
OlivierOlivier
63
asked Feb 10 at 14:30
OlivierOlivier
63
asked Feb 10 at 14:30
OlivierOlivier
63
63
What's the output that shows when you runodbcinst -q -d? Also if you put the username and password in the command rather than in theodbc.inifile, does that make any difference for your result when you run? I assume you confirmed the asterisk SQL login exists already and has been granted access to the DB it needs to access, right?
– Pimp Juice IT
Feb 10 at 15:53
Thanks for your input!odbcinst -q -dshows only one configured driver:[MySQL]I didn't try providing the parameters to the isql command, but I get the same result when I do# isql -v asterisk-connector asterisk secretpasswdIn MySQL CLI everything works fine.
– Olivier
Feb 10 at 17:05
Does usingServer= 127.0.0.1in the ini config file versuslocalhostmake any difference for your result? Not sure if the MySQL service needs restarted or not after making such changes, but if you can, in the name of thoroughness, that's what I'd do after setting and before testing the change.
– Pimp Juice IT
Feb 10 at 17:08
Wow, hadn't even thought of that! I just tried everything again, at first no difference, but withisql -v asterisk-connector asterisk secretpasswdI now getSegmentation fault
– Olivier
Feb 10 at 17:27
If I don't provide the username/password, I just get the samemunmap_chunk(): invalid pointererror
– Olivier
Feb 10 at 17:28
|
show 2 more comments
What's the output that shows when you runodbcinst -q -d? Also if you put the username and password in the command rather than in theodbc.inifile, does that make any difference for your result when you run? I assume you confirmed the asterisk SQL login exists already and has been granted access to the DB it needs to access, right?
– Pimp Juice IT
Feb 10 at 15:53
Thanks for your input!odbcinst -q -dshows only one configured driver:[MySQL]I didn't try providing the parameters to the isql command, but I get the same result when I do# isql -v asterisk-connector asterisk secretpasswdIn MySQL CLI everything works fine.
– Olivier
Feb 10 at 17:05
Does usingServer= 127.0.0.1in the ini config file versuslocalhostmake any difference for your result? Not sure if the MySQL service needs restarted or not after making such changes, but if you can, in the name of thoroughness, that's what I'd do after setting and before testing the change.
– Pimp Juice IT
Feb 10 at 17:08
Wow, hadn't even thought of that! I just tried everything again, at first no difference, but withisql -v asterisk-connector asterisk secretpasswdI now getSegmentation fault
– Olivier
Feb 10 at 17:27
If I don't provide the username/password, I just get the samemunmap_chunk(): invalid pointererror
– Olivier
Feb 10 at 17:28
What's the output that shows when you run
odbcinst -q -d? Also if you put the username and password in the command rather than in the odbc.ini file, does that make any difference for your result when you run? I assume you confirmed the asterisk SQL login exists already and has been granted access to the DB it needs to access, right?– Pimp Juice IT
Feb 10 at 15:53
What's the output that shows when you run
odbcinst -q -d? Also if you put the username and password in the command rather than in the odbc.ini file, does that make any difference for your result when you run? I assume you confirmed the asterisk SQL login exists already and has been granted access to the DB it needs to access, right?– Pimp Juice IT
Feb 10 at 15:53
Thanks for your input!
odbcinst -q -d shows only one configured driver: [MySQL] I didn't try providing the parameters to the isql command, but I get the same result when I do # isql -v asterisk-connector asterisk secretpasswd In MySQL CLI everything works fine.– Olivier
Feb 10 at 17:05
Thanks for your input!
odbcinst -q -d shows only one configured driver: [MySQL] I didn't try providing the parameters to the isql command, but I get the same result when I do # isql -v asterisk-connector asterisk secretpasswd In MySQL CLI everything works fine.– Olivier
Feb 10 at 17:05
Does using
Server= 127.0.0.1 in the ini config file versus localhost make any difference for your result? Not sure if the MySQL service needs restarted or not after making such changes, but if you can, in the name of thoroughness, that's what I'd do after setting and before testing the change.– Pimp Juice IT
Feb 10 at 17:08
Does using
Server= 127.0.0.1 in the ini config file versus localhost make any difference for your result? Not sure if the MySQL service needs restarted or not after making such changes, but if you can, in the name of thoroughness, that's what I'd do after setting and before testing the change.– Pimp Juice IT
Feb 10 at 17:08
Wow, hadn't even thought of that! I just tried everything again, at first no difference, but with
isql -v asterisk-connector asterisk secretpasswd I now get Segmentation fault– Olivier
Feb 10 at 17:27
Wow, hadn't even thought of that! I just tried everything again, at first no difference, but with
isql -v asterisk-connector asterisk secretpasswd I now get Segmentation fault– Olivier
Feb 10 at 17:27
If I don't provide the username/password, I just get the same
munmap_chunk(): invalid pointer error– Olivier
Feb 10 at 17:28
If I don't provide the username/password, I just get the same
munmap_chunk(): invalid pointer error– Olivier
Feb 10 at 17:28
|
show 2 more comments
1 Answer
1
active
oldest
votes
SOLVED:
This issue was caused because a MySQL ODBC connector was being used for a incompatible MariaDB database.
Solved by downloading the correct driver (in my case http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64//mysql-connector-odbc-8.0.15-1.el7.x86_64.rpm)
and editing the odbcinst.ini file as follows:
[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=1
[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1
Lots of thanks to @Pimp Juice IT and my co-worker!
I hope this helps others who experience this issue.
answered Feb 26 at 12:09
OlivierOlivier
63
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404151%2finvalid-pointer-with-odbc-on-centos-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
SOLVED:
This issue was caused because a MySQL ODBC connector was being used for a incompatible MariaDB database.
Solved by downloading the correct driver (in my case http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64//mysql-connector-odbc-8.0.15-1.el7.x86_64.rpm)
and editing the odbcinst.ini file as follows:
[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=1
[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1
Lots of thanks to @Pimp Juice IT and my co-worker!
I hope this helps others who experience this issue.
answered Feb 26 at 12:09
OlivierOlivier
63
add a comment |
SOLVED:
This issue was caused because a MySQL ODBC connector was being used for a incompatible MariaDB database.
Solved by downloading the correct driver (in my case http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64//mysql-connector-odbc-8.0.15-1.el7.x86_64.rpm)
and editing the odbcinst.ini file as follows:
[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=1
[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1
Lots of thanks to @Pimp Juice IT and my co-worker!
I hope this helps others who experience this issue.
answered Feb 26 at 12:09
OlivierOlivier
63
add a comment |
SOLVED:
This issue was caused because a MySQL ODBC connector was being used for a incompatible MariaDB database.
Solved by downloading the correct driver (in my case http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64//mysql-connector-odbc-8.0.15-1.el7.x86_64.rpm)
and editing the odbcinst.ini file as follows:
[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=1
[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1
Lots of thanks to @Pimp Juice IT and my co-worker!
I hope this helps others who experience this issue.
answered Feb 26 at 12:09
OlivierOlivier
63
SOLVED:
This issue was caused because a MySQL ODBC connector was being used for a incompatible MariaDB database.
Solved by downloading the correct driver (in my case http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64//mysql-connector-odbc-8.0.15-1.el7.x86_64.rpm)
and editing the odbcinst.ini file as follows:
[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=1
[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1
Lots of thanks to @Pimp Juice IT and my co-worker!
I hope this helps others who experience this issue.
answered Feb 26 at 12:09
OlivierOlivier
63
answered Feb 26 at 12:09
OlivierOlivier
63
answered Feb 26 at 12:09
OlivierOlivier
63
answered Feb 26 at 12:09
OlivierOlivier
63
63
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404151%2finvalid-pointer-with-odbc-on-centos-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What's the output that shows when you run
odbcinst -q -d? Also if you put the username and password in the command rather than in theodbc.inifile, does that make any difference for your result when you run? I assume you confirmed the asterisk SQL login exists already and has been granted access to the DB it needs to access, right?– Pimp Juice IT
Feb 10 at 15:53
Thanks for your input!
odbcinst -q -dshows only one configured driver:[MySQL]I didn't try providing the parameters to the isql command, but I get the same result when I do# isql -v asterisk-connector asterisk secretpasswdIn MySQL CLI everything works fine.– Olivier
Feb 10 at 17:05
Does using
Server= 127.0.0.1in the ini config file versuslocalhostmake any difference for your result? Not sure if the MySQL service needs restarted or not after making such changes, but if you can, in the name of thoroughness, that's what I'd do after setting and before testing the change.– Pimp Juice IT
Feb 10 at 17:08
Wow, hadn't even thought of that! I just tried everything again, at first no difference, but with
isql -v asterisk-connector asterisk secretpasswdI now getSegmentation fault– Olivier
Feb 10 at 17:27
If I don't provide the username/password, I just get the same
munmap_chunk(): invalid pointererror– Olivier
Feb 10 at 17:28