503 Service Unavailable

Web interface of vmware is not working (503 service unaviable). I can't restart service (/etc/init.d/vmware restart) coz I have two VMs running, and if I can't access to them after restart then I may have a bigger problem: Can't access to VMWare and also can't access VMs. VMs not are running without any problem.

Server is a CentOS 5.0 64bit on debian.

Also:

- By default I can't access to non SSL port (8222 port automatically forwards to SSL 8333 port). I changed the config file to try to access 8222 port non SSL, but need to restart service also).
- VMWare Server Console (from vmware server 1.0.6) does not work with VMWare 2.0
- I think I can use vmware virtual infrastructure client to access to server 2.0, but can't get the program.

Any ideas ?

Thank you :)

joh_aprAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

joh_aprAuthor Commented:
What I really need is to access to my the VMs under that server and hace control of them.
0
thetmanvnCommented:
You shouldn't worry about it if you perform right steps to change the config file.

Now run netstat -natp | grep LISTEN to verify if there a process of vmware server run and listen on port 8222 or 8333

If the 8333 is still LISTEN (It should run, 'cause you just changed the config file but not restart service to apply it) and you now can access it directly to it SSL port.
0
joh_aprAuthor Commented:
It is:

server:/etc/vmware/ssl# netstat -natp | grep LISTEN
tcp        0      0 0.0.0.0:902             0.0.0.0:*               LISTEN      5305/vmware-authdla
tcp        0      0 0.0.0.0:45383           0.0.0.0:*               LISTEN      2123/rpc.statd
tcp        0      0 0.0.0.0:8333            0.0.0.0:*               LISTEN      3103/vmware-hostd
tcp        0      0 0.0.0.0:9998            0.0.0.0:*               LISTEN      3227/perl
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      2112/portmap
tcp        0      0 127.0.0.1:8307          0.0.0.0:*               LISTEN      3103/vmware-hostd
tcp        0      0 192.168.1.1:53          0.0.0.0:*               LISTEN      2450/named
tcp        0      0 192.168.0.1:53          0.0.0.0:*               LISTEN      2450/named
tcp        0      0 94.23.237.9:53          0.0.0.0:*               LISTEN      2450/named
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      2450/named
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      26554/sshd
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      2450/named
tcp        0      0 0.0.0.0:8222            0.0.0.0:*               LISTEN      3103/vmware-hostd
tcp6       0      0 :::139                  :::*                    LISTEN      20843/smbd
tcp6       0      0 ::1:53                  :::*                    LISTEN      2450/named
tcp6       0      0 :::22                   :::*                    LISTEN      26554/sshd
tcp6       0      0 ::1:953                 :::*                    LISTEN      2450/named
tcp6       0      0 :::445                  :::*                    LISTEN      20843/smbd
server:/etc/vmware/ssl#

But when I try to log in I get the 503 Service Unavailable from the browser. So I can't acess to VMs console.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

thetmanvnCommented:
1./ Did you backup the config file before change?
2./ You can restart only vmware-hostd by first kill it process (For example, in your screen:
#kill -9 3103
(3103 is PID of vmware-hostd you list above)
3./ Start vmware-hostd again:
/usr/lib/vmware/bin/vmware-hostd -a -d -u /etc/vmware/hostd/config.xml    &

After done, check by netstat -natp | grep LISTEN again to see vmware-hostd running up again (should be different PID then), then try to access the web console




0
joh_aprAuthor Commented:
I get an error when I try to start the process:

server:/etc/vmware/ssl# /usr/lib/vmware/bin/vmware-hostd: error while loading shared libraries: libvmomi.so.1.0: cannot open shared object file: No such file or directory

I checked paths and seem to be fine.

Now what ?
0
thetmanvnCommented:
Ah, so there maybe the LD_LIBRARY_PATH was not run,

Try restart the web with the following command

/etc/init.d/vmware-mgmt restart


0
joh_aprAuthor Commented:
I did, but still not working:

menta:/etc/vmware/hostd# /etc/init.d/vmware-mgmt restart
Stopping VMware management services:
   VMware Virtual Infrastructure Web Access
   VMware Server Host Agent                                            done
Starting VMware management services:
   VMware Server Host Agent (background)                               done
   VMware Virtual Infrastructure Web Access
menta:/etc/vmware/hostd# /usr/lib/vmware/bin/vmware-hostd -a -d -u /etc/vmware/hostd/config.xml &
[1] 10560
menta:/etc/vmware/hostd# /usr/lib/vmware/bin/vmware-hostd: error while loading shared libraries: libvmomi.so.1.0: cannot open shared object file: No such file or directory

Also checked web acess, but nothing! :(
0
thetmanvnCommented:
As the result, it still didn't start the vmware-hostd

1./ Again, please check if vmware-hostd is running and kill it
2./ Add LD_LIBRARY_PATH by:
export    LD_LIBRARY_PATH=/usr/lib/vmware/vmacore:/usr/lib/vmware/hostd:/usr/lib/vmware/lib/libxml2.so.2:/usr/lib/vmware/lib/libexpat.so.0:/usr/lib/vmware/lib/libstdc++.so.6:/usr/lib/vmware/lib/libgcc_s.so.1:/usr/lib/vmware/lib/libcrypto.so.0.9.8:/usr/lib/vmware/lib/libssl.so.0.9.8
3./Check where SBINDIR of your vmware installation (assume /usr/sbin/ or /usr/lib/vmware/sbin/)
4./ Start the vmware hostd by: vmware-hostd in the SBINDIR (not the LIB dir /usr/lib/vmware/bin/vmware-hostd. Assume you find it was /usr/sbin) then
/usr/sbin/vmware-hostd -a -d -u /etc/vmware/hostd/config.xml   &

0
thetmanvnCommented:
Whenever you can restart your vmware server, you should modify the startup script for not getting the error anymore.
Follow the
http://webalution.com/techshare/2009/11/16/vmware-server-2-web-access-connection-loss-vmware-hostd-crash-workarounds/

Section SOLUTION #2 (Circumventing vmware-hostd library wrapping script –  RHEL 5.4, CentOS 5.4 & Ubuntu 9.10).

My step above is manually run the vmware-hostd without restart all the /etc/init.d/vmware services.
0
joh_aprAuthor Commented:
menta:/etc/vmware/hostd# export    LD_LIBRARY_PATH=/usr/lib/vmware/vmacore:/usr/lib/vmware/hostd:/usr/lib/vmware/lib/libxml2.so.2:/usr/lib/vmware/lib/libexpat.so.0:/usr/lib/vmware/lib/libstdc++.so.6:/usr/lib/vmware/lib/libgcc_s.so.1:/usr/lib/vmware/lib/libcrypto.so.0.9.8:/usr/lib/vmware/lib/libssl.so.0.9.8
menta:/etc/vmware/hostd# cd /usr/sbin/
menta:/usr/sbin# /usr/sbin/vmware-hostd -a -d -u /etc/vmware/hostd/config.xml   &
[1] 11430

Seems that hostd is started, but:

menta:/usr/sbin# netstat -natp | grep LISTEN
tcp        0      0 0.0.0.0:902             0.0.0.0:*               LISTEN      5305/vmware-authdla
tcp        0      0 0.0.0.0:45383           0.0.0.0:*               LISTEN      2123/rpc.statd
tcp        0      0 0.0.0.0:9998            0.0.0.0:*               LISTEN      3227/perl
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      2112/portmap
tcp        0      0 192.168.1.1:53          0.0.0.0:*               LISTEN      2450/named
tcp        0      0 192.168.0.1:53          0.0.0.0:*               LISTEN      2450/named
tcp        0      0 94.23.237.9:53          0.0.0.0:*               LISTEN      2450/named
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      2450/named
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      26554/sshd
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      2450/named
tcp6       0      0 127.0.0.1:8005          :::*                    LISTEN      11733/webAccess
tcp6       0      0 :::8009                 :::*                    LISTEN      11733/webAccess
tcp6       0      0 :::139                  :::*                    LISTEN      20843/smbd
tcp6       0      0 :::8308                 :::*                    LISTEN      11733/webAccess
tcp6       0      0 ::1:53                  :::*                    LISTEN      2450/named
tcp6       0      0 :::22                   :::*                    LISTEN      26554/sshd
tcp6       0      0 ::1:953                 :::*                    LISTEN      2450/named
tcp6       0      0 :::445                  :::*                    LISTEN      20843/smbd

Nothing.
0
joh_aprAuthor Commented:
Maybe I missunderstood something in your "SBINDIR " explanation, my main language is spanish ...
0
joh_aprAuthor Commented:
menta:/usr/sbin# locate vmware-hostd
/root/files/vmware-server-distrib/lib/bin/vmware-hostd
/root/files/vmware-server-distrib/sbin/vmware-hostd
/usr/lib/vmware/bin/vmware-hostd
/usr/sbin/vmware-hostd
/var/run/vmware-hostd-ticket
/var/run/vmware/vmware-hostd.PID
menta:/usr/sbin#
0
thetmanvnCommented:
ps -ef | grep vmware-hostd
 
 Checkt to see if vmware-hostd is running. As the result above, it seem vmware-hostd is running with PID 11430. And your SBINDIR is /usr/sbin.

Now recheck the netstat to verify port, if not LISTEN anything, you should revert config file to original and restart the vmware-hostd as the above. If it start successfully, then you must check the new config file for anything wrong configuration.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
joh_aprAuthor Commented:
Was little hard, but finally worked like a chaim !

Thanks ! :)
0
joh_aprAuthor Commented:
It finally worked ! very good ... and I will work on that reboot script.

Lots of thanks ! :)
0
joh_aprAuthor Commented:
I also added the line "export    LD_LIBRARY_PATH=/usr/lib/vmware/vmacore:/usr/lib/vmware/hostd:/usr/lib/vmware/lib/libxml2.so.2:/usr/lib/vmware/lib/libexpat.so.0:/usr/lib/vmware/lib/libstdc++.so.6:/usr/lib/vmware/lib/libgcc_s.so.1:/usr/lib/vmware/lib/libcrypto.so.0.9.8:/usr/lib/vmware/lib/libssl.so.0.9.8" to the init /etc/init.d/vmware
 script.

Will try to reboot tonight.

Thanks again :)
0
thetmanvnCommented:
Congrats and cheers,

T-Man
0
joh_aprAuthor Commented:
Okay, I decided to open a new ticket:

http://www.experts-exchange.com/Software/VMWare/Q_26183427.html

Thanks.
0
joh_aprAuthor Commented:
Hi, I oppened another ticket but have no reply. Is it possible to re-open this one and close the other one?

Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.