3rd Party Software Won't Run, Install kdump to troubleshoot?
Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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.
3rd Party Software Won't Run, Install kdump to troubleshoot?
So I'm working with an outside vendor to install their software on a mix of RHEL 5/6 and mix of x32 and x86_64 servers.
The software will install, however it will start and all of the sudden their daemon stops working. The daemon doesn't have an entry under /etc/init.d, however the software does install to /opt.
Their tech support recommends installing kdump to try and troubleshoot. I thought that was only to troubleshoot the kernel?
Would it be worth to install kdump in order to troubleshoot?
It still depends on you, on your knowledge. You need to learn how to use it and need to understand what's happening. Personally I would request more support.
a mix of rhel5 and 6 ( should be the up to date rhel 5.11 and 6.7 ) and 32 and 64 bit
that's a mess
Quote:
they kept telling me its SELinux fault. It wasn't.
10 years ago SE might have been a issue
back in 2005/6 SE was a bit new
NOT today ,
i take it you have read through the logs to find the errors
and you have ran "strace" on the program to see where it is faulting ( if applicable )
with a mixed ARCH of 32 and 64 bit
Are ALL the prerequisites installed ?
you did use yum to install the rpm's ??? right ?
How are you installing them ?
the same as above for the rhel5 and 6 mixing
are the el5 and el6 local repos set up like for the x86 and 64_x86 ?
basically is all the other rpm's installed as needed for
rhel5-32
rhel5-64
rhel6-32
rhel6-64
Personally I think kdump should always be present. But not many agree.
I don't see how it would help if you aren't getting kernel oops to trigger the dump. You could use sysrq keys to force one, but why ?. Can you stand to have a reboot at the time of the failure ?.
Do you have debugging info available for that kernel(s) ?. Does the vendor if you are going to ship the dump file offsite ?.
So I'm working with an outside vendor to install their software on a mix of RHEL 5/6 and mix of x32 and x86_64 servers.
The software will install, however it will start and all of the sudden their daemon stops working. The daemon doesn't have an entry under /etc/init.d, however the software does install to /opt.
Their tech support recommends installing kdump to try and troubleshoot. I thought that was only to troubleshoot the kernel?
Would it be worth to install kdump in order to troubleshoot?
Is their software includes kernel module(s) or it just user space exes?
So I'm revisiting this again, as I continue to get errors and try to troubleshoot. I've noticed that /var/log/messages is filling up with the following:
Code:
[root@server varonis]# tail -f /var/log/messages
2016-03-18T12:27:38.541532-05:00 server vrns_mond: Failed running /opt/varonis/vrns_mond - Operation not permitted
2016-03-18T13:24:35.987242-05:00 server vrns_mond: Failed running /opt/varonis/vrns_mond - Operation not permitted
2016-03-18T13:25:08.575069-05:00 server vrns_mond: Failed running /opt/varonis/vrns_mond - Operation not permitted
2016-03-18T13:25:41.172268-05:00 server vrns_mond: Failed running /opt/varonis/vrns_mond - Operation not permitted
2016-03-18T13:26:13.762016-05:00 server vrns_mond: Failed running /opt/varonis/vrns_mond - Operation not permitted
2016-03-18T13:26:46.373314-05:00 server vrns_mond: Failed running /opt/varonis/vrns_mond - Operation not permitted
2016-03-18T13:27:18.982556-05:00 server vrns_mond: Failed running /opt/varonis/vrns_mond - Operation not permitted
2016-03-18T13:27:51.585849-05:00 server vrns_mond: Failed running /opt/varonis/vrns_mond - Operation not permitted
The software is installed under /opt/varonis and I'm kicking it off as Root
Code:
-rwxr-x--- 1 root varonis 4129 Oct 31 2012 vrns_mon.sh
There is nothing out of the ordinary with SELinux and neither with acls.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.