lampp on Centos - unable to stop/start - /opt/lampp/bin/gettext: error while loading shared libraries:...
up vote
2
down vote
favorite
I've a lampp 5.6.28 installed on Centos.
After a yum update, I was not able to stop/start lampp due to following errors:
[root@giunone2 lampp]# ./lampp stop
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
id: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/share/xampp/xampplib: line 11: test: -ne: unary operator expected
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: /opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
apachectl returned 127.
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: cat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
kill returned 1.
ISSUE SOLUTION
I've found that removing following line everything returned to work OK
export LD_ASSUME_KERNEL=2.2.5
centos
add a comment |
up vote
2
down vote
favorite
I've a lampp 5.6.28 installed on Centos.
After a yum update, I was not able to stop/start lampp due to following errors:
[root@giunone2 lampp]# ./lampp stop
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
id: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/share/xampp/xampplib: line 11: test: -ne: unary operator expected
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: /opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
apachectl returned 127.
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: cat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
kill returned 1.
ISSUE SOLUTION
I've found that removing following line everything returned to work OK
export LD_ASSUME_KERNEL=2.2.5
centos
Is there any reason not to use standard apache, php and mysql from CentOS?
– Romeo Ninov
Jul 20 '17 at 7:20
Those alternative Web stacks do not play well with the native OS package manager. They will give you more problems in the long run
– Rui F Ribeiro
Mar 31 at 9:59
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I've a lampp 5.6.28 installed on Centos.
After a yum update, I was not able to stop/start lampp due to following errors:
[root@giunone2 lampp]# ./lampp stop
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
id: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/share/xampp/xampplib: line 11: test: -ne: unary operator expected
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: /opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
apachectl returned 127.
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: cat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
kill returned 1.
ISSUE SOLUTION
I've found that removing following line everything returned to work OK
export LD_ASSUME_KERNEL=2.2.5
centos
I've a lampp 5.6.28 installed on Centos.
After a yum update, I was not able to stop/start lampp due to following errors:
[root@giunone2 lampp]# ./lampp stop
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
egrep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
id: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/share/xampp/xampplib: line 11: test: -ne: unary operator expected
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: /opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
apachectl returned 127.
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
XAMPP: cat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
/opt/lampp/bin/gettext: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
kill returned 1.
ISSUE SOLUTION
I've found that removing following line everything returned to work OK
export LD_ASSUME_KERNEL=2.2.5
centos
centos
edited Jul 20 '17 at 7:19
Romeo Ninov
5,02431627
5,02431627
asked Jul 20 '17 at 7:17
fman
1412
1412
Is there any reason not to use standard apache, php and mysql from CentOS?
– Romeo Ninov
Jul 20 '17 at 7:20
Those alternative Web stacks do not play well with the native OS package manager. They will give you more problems in the long run
– Rui F Ribeiro
Mar 31 at 9:59
add a comment |
Is there any reason not to use standard apache, php and mysql from CentOS?
– Romeo Ninov
Jul 20 '17 at 7:20
Those alternative Web stacks do not play well with the native OS package manager. They will give you more problems in the long run
– Rui F Ribeiro
Mar 31 at 9:59
Is there any reason not to use standard apache, php and mysql from CentOS?
– Romeo Ninov
Jul 20 '17 at 7:20
Is there any reason not to use standard apache, php and mysql from CentOS?
– Romeo Ninov
Jul 20 '17 at 7:20
Those alternative Web stacks do not play well with the native OS package manager. They will give you more problems in the long run
– Rui F Ribeiro
Mar 31 at 9:59
Those alternative Web stacks do not play well with the native OS package manager. They will give you more problems in the long run
– Rui F Ribeiro
Mar 31 at 9:59
add a comment |
3 Answers
3
active
oldest
votes
up vote
1
down vote
If any version of Redhat or Centos has a 9 in it (cat /etc/redhat-release) this issue will happen. As stated above, edit /opt/lampp/lampp and comment out export LD_ASSUME_KERNEL=2.2.5.
add a comment |
up vote
0
down vote
I had to do something which is a little different from the above---but I'm very, very grateful for the posts above. I tried the two fixes above but I got errors using CentOS 6.
XAMPP now starts and runs correctly for me when I commented out this entire section mentioned above in the /opt/lampp/lampp script---from "do we have that new red hat...." down to and including the "fi". COMMENT EVERY LINE and then try starting XAMPP stack.
add a comment |
up vote
-3
down vote
edit /opt/lampp/lampp
Comment line 436
#export LD_ASSUME_KERNEL=2.2.5
Uncomment line 437
echo "XAMPP: DISABLE PNTL..."
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
If any version of Redhat or Centos has a 9 in it (cat /etc/redhat-release) this issue will happen. As stated above, edit /opt/lampp/lampp and comment out export LD_ASSUME_KERNEL=2.2.5.
add a comment |
up vote
1
down vote
If any version of Redhat or Centos has a 9 in it (cat /etc/redhat-release) this issue will happen. As stated above, edit /opt/lampp/lampp and comment out export LD_ASSUME_KERNEL=2.2.5.
add a comment |
up vote
1
down vote
up vote
1
down vote
If any version of Redhat or Centos has a 9 in it (cat /etc/redhat-release) this issue will happen. As stated above, edit /opt/lampp/lampp and comment out export LD_ASSUME_KERNEL=2.2.5.
If any version of Redhat or Centos has a 9 in it (cat /etc/redhat-release) this issue will happen. As stated above, edit /opt/lampp/lampp and comment out export LD_ASSUME_KERNEL=2.2.5.
answered Sep 22 '17 at 16:21
Chris
111
111
add a comment |
add a comment |
up vote
0
down vote
I had to do something which is a little different from the above---but I'm very, very grateful for the posts above. I tried the two fixes above but I got errors using CentOS 6.
XAMPP now starts and runs correctly for me when I commented out this entire section mentioned above in the /opt/lampp/lampp script---from "do we have that new red hat...." down to and including the "fi". COMMENT EVERY LINE and then try starting XAMPP stack.
add a comment |
up vote
0
down vote
I had to do something which is a little different from the above---but I'm very, very grateful for the posts above. I tried the two fixes above but I got errors using CentOS 6.
XAMPP now starts and runs correctly for me when I commented out this entire section mentioned above in the /opt/lampp/lampp script---from "do we have that new red hat...." down to and including the "fi". COMMENT EVERY LINE and then try starting XAMPP stack.
add a comment |
up vote
0
down vote
up vote
0
down vote
I had to do something which is a little different from the above---but I'm very, very grateful for the posts above. I tried the two fixes above but I got errors using CentOS 6.
XAMPP now starts and runs correctly for me when I commented out this entire section mentioned above in the /opt/lampp/lampp script---from "do we have that new red hat...." down to and including the "fi". COMMENT EVERY LINE and then try starting XAMPP stack.
I had to do something which is a little different from the above---but I'm very, very grateful for the posts above. I tried the two fixes above but I got errors using CentOS 6.
XAMPP now starts and runs correctly for me when I commented out this entire section mentioned above in the /opt/lampp/lampp script---from "do we have that new red hat...." down to and including the "fi". COMMENT EVERY LINE and then try starting XAMPP stack.
answered Jan 24 at 0:09
boyd
1
1
add a comment |
add a comment |
up vote
-3
down vote
edit /opt/lampp/lampp
Comment line 436
#export LD_ASSUME_KERNEL=2.2.5
Uncomment line 437
echo "XAMPP: DISABLE PNTL..."
add a comment |
up vote
-3
down vote
edit /opt/lampp/lampp
Comment line 436
#export LD_ASSUME_KERNEL=2.2.5
Uncomment line 437
echo "XAMPP: DISABLE PNTL..."
add a comment |
up vote
-3
down vote
up vote
-3
down vote
edit /opt/lampp/lampp
Comment line 436
#export LD_ASSUME_KERNEL=2.2.5
Uncomment line 437
echo "XAMPP: DISABLE PNTL..."
edit /opt/lampp/lampp
Comment line 436
#export LD_ASSUME_KERNEL=2.2.5
Uncomment line 437
echo "XAMPP: DISABLE PNTL..."
edited Oct 20 '17 at 15:17
Stephen Rauch
3,308101328
3,308101328
answered Oct 18 '17 at 15:45
Gilton
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f379678%2flampp-on-centos-unable-to-stop-start-opt-lampp-bin-gettext-error-while-loa%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
Is there any reason not to use standard apache, php and mysql from CentOS?
– Romeo Ninov
Jul 20 '17 at 7:20
Those alternative Web stacks do not play well with the native OS package manager. They will give you more problems in the long run
– Rui F Ribeiro
Mar 31 at 9:59