[SOLVED] 0x08063781 in LocalHost::LocalHost() () - errors
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I have two Centos 8.6 VMs. Both are created with same templates, so they are supposed to be identical, unless something was changed later which I can't figure. As per application team, same code is working on some set of server, but on another set of servers, so they are pointing, something is different or wrong on OS or library or config level.
appuser is supposed to run gdb on tcsid and then issue "run" command. It is suppsed to create a unique key for this host. Below are two example. I picked one server from working set of servers and one server from non-working set of servers. I do not know, how this application or code works, but trying to find if I can get some clue which may be different on OS level.
hostname, hostnamectl seems to be same and in same format.
Working server -->
Code:
[root@phl003 ~]# su - appuser
(18:09:41) PROD SITE=XA | phl003:appuser> cd /opt/tcs/corebaser-14.14.1/bin
(18:09:50) PROD SITE=XA | phl003:bin> gdb tcsid
GNU gdb (GDB) Red Hat Enterprise Linux 8.2-19.el8
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from tcsid...(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/tcs/corebaser-14.14.1/bin/tcsid
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
79f1fd490796b5e2636478efdddc92521c10572f9c555a74582f8a7ebb9eess779555bf9e3c77dbff3566827c8044bf6
[Inferior 1 (process 1374472) exited normally]
Missing separate debuginfos, use: yum debuginfo-install tcs-corebaser-14.14.1-71557.202310081822.BC43o.i686
(gdb)
Non-working server -->
Quote:
[root@oyr003 ~]# su - appuser
(18:09:39) PROD SITE=YA | oyr003:appuser> cd /opt/tcs/corebaser-14.14.1/bin
(18:09:45) PROD SITE=YA | oyr003:bin> gdb tcsid
GNU gdb (GDB) Red Hat Enterprise Linux 8.2-19.el8
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from tcsid...(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/tcs/corebaser-14.14.1/bin/tcsid
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Program received signal SIGILL, Illegal instruction.
0x08063781 in LocalHost::LocalHost() ()
Missing separate debuginfos, use: yum debuginfo-install tcs-corebaser-14.14.1-71557.202310081822.BC43o.i686
(gdb)
Can someone help me with, what to look to do further troubleshooting ?
so you need to compare all the libs, one by one, need to find which one is different.
use ldd to find them. Also you need to check the binary itself and the config files.
you might try strace to find what's going on or what went wrong (probably helps).
Why do you need gdb to run it? Does it work without gdb?
so you need to compare all the libs, one by one, need to find which one is different.
use ldd to find them. Also you need to check the binary itself and the config files.
you might try strace to find what's going on or what went wrong (probably helps).
Why do you need gdb to run it? Does it work without gdb?
I tried to capture all rpms (rpm -qa > /var/tmp/all-rpms.txt) and compare, both have same and no difference.
/opt/tcs/corebaser-14.14.1/bin/tcsid checksum is same on working as well as non-working
I do not know, why they use gdb. It is their (apps team) standard procedure I guess. Maybe it was written in such way.
For strace, should I run it as "strace gdb tcsid". How there is way to do strace on "run" ? Maybe that can give some clue, but how to run it ?
yes, exactly that way, but probably you need to add some flags:
Code:
strace -o output.txt -f <some command>
it should work exactly the same way, just it will be slower.
gdb is a debugger and run means the simple execution of that app, therefore gdb <app>; run is more or less equal to just run <app> without gdb. I don't really see the reason to use gdb. Anyway, you can try it without it to see at least if that will do the same.
But I'm not really sure if gdb and strace work together.
You can use ldd /opt/tcs/corebaser-14.14.1/bin/tcsid to find the required libs and you can also compare them.
You can also use the output of strace to see the files opened, so you will know what should be compared.
After changing the feature on underlying blade and reboot of this VM (not reboot, but power off and power on), everything worked fine. Thanks for your efforts and help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.