Hi Eucalyptus Fans,
I am heavily evaluating Eucalyptus 1.6.x and 2.x on SLES11SP1x64 the last days.
Right now I got the FrontEnd Machine running fine - but when I connect to https://Front-End:8443 I geht a Directory Listing showing me:
Directory: /
META-INF/ ...
WEB-INF/ ...
extensions/ ...
themes/ ...
Any clue what this could be - or where to have a look at?
best regards, Christian
arg - euca_conf --register-walrus is also not working :(
bsa0773:~ # euca_conf --register-walrus 14.103.193.157
ERROR: you need to be on the CLC host and the CLC needs to be running.
I could bet that that's related to each other - so withou running webserver I can't register any new components :)
arg - euca_conf --register-walrus is also not working :(
bsa0773:~ # euca_conf --register-walrus 14.103.193.157
ERROR: you need to be on the CLC host and the CLC needs to be running.
I could bet that that's related to each other - so withou running webserver I can't register any new components :)
netstat -nlp | grep euc
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 17665/eucalyptus-cl
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 17665/eucalyptus-cl
tcp 0 0 0.0.0.0:8773 0.0.0.0:* LISTEN 17665/eucalyptus-cl
tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 17665/eucalyptus-cl
When I have one terminal open with "tail -f /var/log/eucalyptus/*" and then do on another the register I get this:
### SHELL1
bsa0773:~ # euca_conf --register-sc baumi 14.207.195.133
ERROR: you need to be on the CLC host and the CLC needs to be running.
###SHELL2
==> cloud-debug.log <==
11:07:56 TRACE [ReentrantListenerRegistry:SystemClockTimer] :1283857676269:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:RemoteBootstrapperClient:com.eucalyptus.event.ClockTick@7376d5d2:ReentrantListenerRegistry.fireEvent.68
11:07:56 TRACE [ReentrantListenerRegistry:SystemClockTimer] :1283857676270:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:LocalDatabaseBootstrapper:com.eucalyptus.event.ClockTick@7376d5d2:ReentrantListenerRegistry.fireEvent.68
11:07:56 TRACE [LocalDatabaseBootstrapper:SystemClockTimer] -> Ping database.
11:07:56 TRACE [ReentrantListenerRegistry:SystemClockTimer] :1283857676272:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:Dummy:com.eucalyptus.event.ClockTick@7376d5d2:ReentrantListenerRegistry.fireEvent.68
==> cloud-output.log <==
11:07:56 TRACE 130 entrantListenerRegistry| :1283857676269:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:RemoteBootstrapperClient:com.eucalyptus.event.ClockTick@7376d5d2:ReentrantListenerRegistry.fireEvent.68
11:07:56 TRACE 130 entrantListenerRegistry| :1283857676270:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:LocalDatabaseBootstrapper:com.eucalyptus.event.ClockTick@7376d5d2:ReentrantListenerRegistry.fireEvent.68
11:07:56 TRACE 230 calDatabaseBootstrapper| -> Ping database.
11:07:56 TRACE 130 entrantListenerRegistry| :1283857676272:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:Dummy:com.eucalyptus.event.ClockTick@7376d5d2:ReentrantListenerRegistry.fireEvent.68
#############
there's nothing else in the logs during this process ...
please help me - give me any hint
chris
PS: Some system info:
#rpm -qa | grep euc
euca-axis2c-1.6.0-1
eucalyptus-gl-2.0.0-1
eucalyptus-cloud-2.0.0-1
eucalyptus-2.0.0-1
eucalyptus-walrus-2.0.0-1
euca-rampartc-1.3.0-1
eucalyptus-sc-2.0.0-1
eucalyptus-cc-2.0.0-1
eucalyptus-common-java-2.0.0-1
euca2ools-1.3.1-1
* Whether you installed from source or used a package: Packages for OpenSuse latest version see above
* Distribution and architecture: SLES 11 SP 1 x64 Linux bsa0773 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux
* Hypervisor type: XEN - but I didn't get so far yet to use it :(
* Topology: Documented simple setup, using one FrontEnd and 3 Nodes
* Networking mode: System is the target, but not soo far now
* Anything else specific to the problem:
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth2: mtu 1500 qdisc mq master bond1 state UP qlen 1000
link/ether 00:1c:c4:16:00:86 brd ff:ff:ff:ff:ff:ff
3: eth3: mtu 1500 qdisc mq master bond1 state UP qlen 1000
link/ether 00:1c:c4:16:00:86 brd ff:ff:ff:ff:ff:ff
4: eth0: mtu 1500 qdisc mq master bond0 state UP qlen 1000
link/ether 00:1b:78:e3:ae:34 brd ff:ff:ff:ff:ff:ff
5: eth1: mtu 1500 qdisc mq master bond0 state UP qlen 1000
link/ether 00:1b:78:e3:ae:34 brd ff:ff:ff:ff:ff:ff
6: dummy0: mtu 1500 qdisc noqueue state UNKNOWN
link/ether 00:00:00:00:00:01 brd ff:ff:ff:ff:ff:ff
inet 1.1.1.1/32 brd 1.255.255.255 scope global dummy0
inet6 fe80::200:ff:fe00:1/64 scope link
valid_lft forever preferred_lft forever
7: bond0: mtu 1500 qdisc noqueue state UP
link/ether 00:1b:78:e3:ae:34 brd ff:ff:ff:ff:ff:ff
inet 14.207.195.133/17 brd 14.207.255.255 scope global bond0
inet6 fe80::21b:78ff:fee3:ae34/64 scope link
valid_lft forever preferred_lft forever
8: bond1: mtu 1500 qdisc noqueue state UP
link/ether 00:1c:c4:16:00:86 brd ff:ff:ff:ff:ff:ff
inet 14.103.193.157/17 brd 14.103.255.255 scope global bond1
inet6 fe80::21c:c4ff:fe16:86/64 scope link
Hello,
it seems that the CLC didn't really come up properly: the register commands interact with the CLC, and the error indicated that it couldn't find the CLC running. Also the fact that you are seeing a listing at the 8443 address, means that the CLC is not up. I have never seen the CLC been stucked so early in the starting process, so I'm not quite sure what is going on here. Which version of java are you using?
cheers
graziano
Hello Graziano,
thanks for the reply - hmm ... bad news so?
I got this
bsa0773:~ # java -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
bsa0773:~ #
My only option at the moment is a reinstall of the whole stack on the frontEnd ... i'll do that later today ...
Sorry I assumed that you had stopped the service first, do following to solve your problem:
/etc/init.d/eucalyptus-cloud stop
killall eucalyptus-cloud
rm -r /var/run/eucalyptus
mkdir /var/run/eucalyptus
chown eucalyptus.eucalyptus /var/run/eucalyptus
/etc/init.d/eucalyptus-cloud start
Hi - thanks for your patience, but I already installed eucalyptus 2.0 on sles11sp1 twice since this morning - I couldn't reproduce the Problem of this thread.
But I just don't get 2.0 running on the sles11sp1 frontend - 1.6 is working fine on another cluster :(
But that's offtopic in here - thanks for the help.
Hi Patrick,
I freshly installed again - look here: http://open.eucalyptus.com/forum/eucalyptus-20-sles11sp1-my-way
I got the same problem again and again. It's not there when I just installed, but after first boot. Please have a look at this thread ^^^^ as I describe my steps of the setup in detail there. Maybee I am missing something to make the system survive the reboot ...
Your workaround is of no use for me for this problem, after deleting the files a you posted the WebPage isn't there at all - "netstat -nlp | grep euc" is empty as well ... so that's really no solution for this specific problem.
Who can help me?
Chris
btw: the 1.6 on SLES11SP1 is no problem so far ...
Hi,
The web part is deployed in/var/run/eucalyptus/.
Note that the directory is owned by user and group eucalyptus
Directory listing:
/var/run/eucalyptus # ls -la
total 20
drwxr-xr-x 4 eucalyptus eucalyptus 4096 Sep 10 13:44 .
drwxr-xr-x 24 root root 4096 Sep 10 13:44 ..
-rw-r--r-- 1 root root 5 Sep 10 13:44 eucalyptus-cloud.pid
drwxr-xr-x 2 eucalyptus eucalyptus 4096 Sep 10 13:44 jsp
drwxr-xr-x 6 eucalyptus eucalyptus 4096 Sep 10 13:44 webapp
The jsp directory is empty but the webapp directory contains the contents of the root.war.
You can find the root.war in /var/lib/eucalyptus/webapps/
Have you set your JAVA_HOME environment before starting I did the following:
export JAVA_HOME==/usr/java/jdk1.6.0_21/
I also created softlink in =/usr/java/jdk1.6.0_21/bin to the jre looking like:
lrwxrwxrwx 1 root root 7 Sep 7 12:42 jre -> ../jre/
Try this while the eucalyptus-cloud is running:
cd /var/run/eucalyptus
mkdir -p webapp
cd webapp
jar xvf /var/lib/eucalyptus/webapps/root.war
cd ..
chown -R eucalyptus.eucalyptus webapp
Refresh the page in the browser.
I have also java in my path to be able to access the command tools.
Let me know if you succeed or not.
Regards,
Patrik
Hi again,
after I did the "rm -r /var/run/eucalyptus" as You suggested the webfrontend is empty and the services don't start.
After reinstalling the RPMs with " rpm --force -Uvh eucalyptus-2.0.0-1.x86_64.rpm eucalyptus-cc-2.0.0-1.x86_64.rpm eucalyptus-cloud-2.0.0-1.x86_64.rpm eucalyptus-common-java-2.0.0-1.x86_64.rpm eucalyptus-gl-2.0.0-1.x86_64.rpm eucalyptus-walrus-2.0.0-1.x86_64.rpm" and rebooting the services WORK *wtf*
Even after another reboot it still works then - I have no clue why, as after fresh installation it usually doesn't work with the 2.0 on SLES11SP1 ....
Chris
@Patrick:
bsa0773:~ # env | grep -i java
JAVA=/usr/local/jdk1.6.0_21/bin/java
JAVA_HOME=/usr/local/jdk1.6.0_21
what you mean by saying:
I also created softlink in =/usr/java/jdk1.6.0_21/bin to the jre looking like:
lrwxrwxrwx 1 root root 7 Sep 7 12:42 jre -> ../jre/
Please give me the link you use like:
ln -s /usr/local/jre1.x.x/bin/java /usr/bin/java
ln -s /usr/local/jre1.x.x/bin/java /bin/java
So - yes I suceeded, but not by applying your tips.
Basicaly I did:
Fresh install as described, with a directory listing,
deleting /var/run/eucalyptus
reinstalling the eucalyptus rpm with ---force
and all works ?!?
I have to reinstall fresh again to reproduce the "directory listing" problem and then try your fix ... stand by :)
Chris
PS: I am also doing this for all SLES11SP1 Users - where are they?
So... I reinstalled once again as described above - this time I deinstalled the SLES default jre with "rpm -e jre" before I did anything. But still my Problem: http://img823.imageshack.us/img823/2280/probbbbb.jpg
^^^ thats after I logged in using admin:admin ^^^
b1rules says... So... I reinstalled once again as described above - this time I deinstalled the SLES default jre with "rpm -e jre" before I did anything. But still my Problem: http://img823.imageshack.us/img823/2280/probbbbb.jpg
^^^ thats after I logged in using admin:admin ^^^
As I can now clearly reproduce this error here are a few errors from the logs:
==> /var/log/eucalyptus/cloud-error.log <==
at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
Here die Mail von einem Full Request which shows me the listing again:
14:46:37 TRACE [ReentrantListenerRegistry:SystemClockTimer] :1284475597451:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:LocalDatabaseBootstrapper:com.eucal
yptus.event.ClockTick@3d24916:ReentrantListenerRegistry.fireEvent.68
14:46:37 TRACE [LocalDatabaseBootstrapper:SystemClockTimer] -> Ping database.
14:46:37 TRACE [ReentrantListenerRegistry:SystemClockTimer] :1284475597452:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:Dummy:com.eucalyptus.event.ClockTic
k@3d24916:ReentrantListenerRegistry.fireEvent.68
==> /var/log/eucalyptus/jetty-request-2010_09_14.log <==
172.16.25.217 - - [14/Sep/2010:14:46:40 +0000] "GET / HTTP/1.1" 200 610 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100106 Ubuntu/9.10
(karmic) Firefox/3.5.7" "eucalyptus-session-id=ff33a951-71dc-4e53-b985-a98f6c8f56af"
172.16.25.217 - - [14/Sep/2010:14:46:44 +0000] "GET / HTTP/1.1" 200 610 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100106 Ubuntu/9.10
(karmic) Firefox/3.5.7" "eucalyptus-session-id=ff33a951-71dc-4e53-b985-a98f6c8f56af"
172.16.25.217 - - [14/Sep/2010:14:46:45 +0000] "GET / HTTP/1.1" 200 610 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100106 Ubuntu/9.10
(karmic) Firefox/3.5.7" "eucalyptus-session-id=ff33a951-71dc-4e53-b985-a98f6c8f56af"
172.16.25.217 - - [14/Sep/2010:14:46:46 +0000] "GET / HTTP/1.1" 200 610 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100106 Ubuntu/9.10 (karmic) Firefox/3.5.7" "eucalyptus-session-id=ff33a951-71dc-4e53-b985-a98f6c8f56af"
==> /var/log/eucalyptus/cloud-debug.log <==
14:46:47 TRACE [ReentrantListenerRegistry:SystemClockTimer] :1284475607449:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:RemoteBootstrapperClient:com.eucalyptus.event.ClockTick@4381c7e9:ReentrantListenerRegistry.fireEvent.68
14:46:47 TRACE [ReentrantListenerRegistry:SystemClockTimer] :1284475607450:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:LocalDatabaseBootstrapper:com.eucalyptus.event.ClockTick@4381c7e9:ReentrantListenerRegistry.fireEvent.68
14:46:47 TRACE [LocalDatabaseBootstrapper:SystemClockTimer] -> Ping database.
14:46:47 TRACE [ReentrantListenerRegistry:SystemClockTimer] :1284475607452:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:Dummy:com.eucalyptus.event.ClockTick@4381c7e9:ReentrantListenerRegistry.fireEvent.68
==> /var/log/eucalyptus/cloud-output.log <==
14:46:47 TRACE 130 entrantListenerRegistry| :1284475607449:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:RemoteBootstrapperClient:com.eucalyptus.event.ClockTick@4381c7e9:ReentrantListenerRegistry.fireEvent.68
14:46:47 TRACE 130 entrantListenerRegistry| :1284475607450:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:LocalDatabaseBootstrapper:com.eucalyptus.event.ClockTick@4381c7e9:ReentrantListenerRegistry.fireEvent.68
14:46:47 TRACE 230 calDatabaseBootstrapper| -> Ping database.
14:46:47 TRACE 130 entrantListenerRegistry| :1284475607452:ReentrantListenerRegistry:LISTENER_EVENT_FIRED:Dummy:com.eucalyptus.event.ClockTick@4381c7e9:ReentrantListenerRegistry.fireEvent.68
==> /var/log/eucalyptus/jetty-request-2010_09_14.log <==
172.16.25.217 - - [14/Sep/2010:14:46:46 +0000] "GET / HTTP/1.1" 200 610 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100106 Ubuntu/9.10 (karmic) Firefox/3.5.7" "eucalyptus-session-id=ff33a951-71dc-4e53-b985-a98f6c8f56af"
HI,
I had the same problem on Fedora 14.
Solution is to remove /var/run/eucalyptus/webapp directory and then restart eucalyptus-cloud and eucalyptus-cc services.
On another thread, people had the same problem on OpenSuse so I think its highly likely that its Eucalyptus bug.
http://open.eucalyptus.com/forum/eucalyptus-web-interface-front-end-got-broken-after-rebooting#comment-18055
Cheers
Omer