Core 8.0 x64, file not found, but file exist

[deodion]

I have an enterprise application x64,

Tried to run it, but it returns something like this:
-sh splunk: file not found

I have read around, its says need to check with ldd and/or file command to find out missing libraries and it has something todo with 32/64 bit thing


I will try the command in few hours later,


Thank you

[coreplayer2]

did you try just

Code: [Select]

splunk
or from the directory location of splunk

Code: [Select]

./splunk

[coreplayer2]

Also, don't try to mix 64 bit applications in a 32bit environment, it will not work.

If you run the application as described in my last post it will almost always tell you which libraries are missing if any are missing..

Perhaps the application needs Bash?

Some x86_64 precompiled  programs (from another linux system) may require this symlink so it can find required libraries

Code: [Select]

ln -s /lib /lib64

[coreplayer2]

I think you said new to linux??  ok some info for you regarding paths to a program.

Code: [Select]

echo $PATH  I'm sure I could explain this better; but entering this command will reveal all the locations where you can place a program and execute it simply by entering it's file name at the terminal.

Whereas

Code: [Select]

./program executes the program from the current directory

[deodion]

Tried ./splunk and splunk
Im aware about that,

Later I will try all other clues

[deodion]

Hello,

I use

Code: (bash) [Select]

ln -s /lib /lib64
Its working,

now I get: ps: invalid option -- 'p'

Code: (bash) [Select]

]ps: invalid option -- 'p'
BusyBox v1.25.1 (2017-03-14 16:33:32 UTC) multi-call binary.

Usage: ps [-o COL1,COL2=HEADER]

Show list of processes

        -o COL1,COL2=HEADER     Select columns for display
Done


Waiting for web server at http://127.0.0.1:8000 to be availableps: invalid option -- 'p'
BusyBox v1.25.1 (2017-03-14 16:33:32 UTC) multi-call binary.

Usage: ps [-o COL1,COL2=HEADER]

Show list of processes

        -o COL1,COL2=HEADER     Select columns for display
ps: invalid option -- 'p'
BusyBox v1.25.1 (2017-03-14 16:33:32 UTC) multi-call binary.
I can install and use BASH to solve this right?

[Misalf]

RE: ps: invalid option -- 'p'
I believe you need the full  procps.tcz .

[deodion]

After install procps.tcz

Its working but with flaw,
after start the program, it will start, but still showing ps: invalid option -- 'p'
and after that if execute another command, will show ps: invalid option -- 'p' again, and then the program will failed to run, leaving stale PID,

Code: (bash) [Select]

ps: invalid option -- 'p'
BusyBox v1.25.1 (2017-03-14 16:33:32 UTC) multi-call binary.

Usage: ps [-o COL1,COL2=HEADER]

Show list of processes

        -o COL1,COL2=HEADER     Select columns for display
Done



If you get stuck, we're here to help.
Look for answers here: http://docs.splunk.com

The Splunk web interface is at http://box:8000

tc@box:/mnt/sda1/tce/APPS/splunk/bin$ ./splunk status
ps: invalid option -- 'p'
BusyBox v1.25.1 (2017-03-14 16:33:32 UTC) multi-call binary.


[andyj]

Procps.tcz is a dependency of open-vm-tools.tcz, so if you are using open-vm-tools.tcz you would already have procps.tcz. But the problem here is probably that whatever is executing ps has the path hard coded to /bin/ps, which is the busybox version you see. You should either not use a path, or give the full path to the propcs version as /usr/local/bin/ps.

[coreplayer2]

I can install and use BASH to solve this right?

If you're referring to the last error in your screenshot, then no..

ls /lib/lib64 is not a valid path, try this instead

Code: [Select]

ls /lib64
If you're referring to the first error in your screenshot, then most likely yes..

[deodion]

Procps.tcz is a dependency of open-vm-tools.tcz, so if you are using open-vm-tools.tcz you would already have procps.tcz. But the problem here is probably that whatever is executing ps has the path hard coded to /bin/ps, which is the busybox version you see. You should either not use a path, or give the full path to the propcs version as /usr/local/bin/ps.

Hopefully the adjustment work is not hard and a lot,
I see it in web GUI, while its on its very-very fast, I like it,

If procps is onboot.lst does that mean still not using /usr/local/bin/ps?
So I still have to adjust the PATH?

[coreplayer2]

I can install and use BASH to solve this right?

If you're referring to the first error in your screenshot, then most likely yes..

A correction, try:

Code: [Select]

/opt/splunk/bin $ ./splunk start

[Rich]

Hi deodion
Do not adjust the path. If the application is calling  /bin/ps  then the application needs to be fixed. Do not make changes
to the  busybox  links in  /bin  as there may be system scripts that rely on the  busybox  version.

[coreplayer2]

Code: [Select]

/opt/splunk/bin $ ./splunk start

Splunk> Australian for grep.

Checking prerequisites...
        Checking http port [8000]: open
        Checking mgmt port [8089]: open
        Checking appserver port [127.0.0.1:8065]: open
        Checking kvstore port [8191]: open
        Checking configuration...  Done.
        Checking critical directories...        Done
        Checking indexes...
                Validated: _audit _internal _introspection _telemetry _thefishbucket history main summary
        Done
        Checking filesystem compatibility...  Done
        Checking conf files for problems...
        Done
        Checking default conf files for edits...
        Validating installed files against hashes from '/opt/splunk/splunk-6.6.2-4b804538c686-linux-2.6-x86_64-manifest'
        All installed files intact.
        Done
All preliminary checks passed.

Starting splunk server daemon (splunkd)... 
Done


Waiting for web server at http://127.0.0.1:8000 to be available....... Done


If you get stuck, we're here to help. 
Look for answers here: http://docs.splunk.com

The Splunk web interface is at http://box:8000

/opt/splunk/bin $

I had to change permissions/ownership and as a quick test replaced the symlink to ps (which Rich specifically said don't do..) but for the test, splunk appears to work.  So maybe splunk needs fixing?

permissions/ownership changes not required, my bad..

Code: [Select]

# export SPLUNK_HOME=/opt/splunk
# export PATH=$SPLUNK_HOME/bin:$PATHwas all that was needed..

[coreplayer2]

OK deodion

This ps path issue is an easy fix.

Simply edit /opt/splunk/bin/pid_check.sh  to add /usr/local/bin: to this path variable

Code: [Select]

line 43: PATH=/usr/xpg4/bin:/usr/local/bin:/usr/bin:/bin
After loading procps.tcz splunk will look in /usr/local/bin for ps -p