Distribution Manager Errors

For background purposes, I am attempting to install XWiki on a Ubuntu 16.04 server, hosted by digitalocean. My linux background is still pretty low, but I know about enough to make me dangerous. I have been following this guide using tomcat8 and pgsql/mysql, and keep running into issues when installing the standard flavor through the distribution manager.

Following completion of install, tomcat appears to be operating properly.

Image URL

Note: All extensions can be added to the end of https://i.imgur.com/
I am only able to include two links due to being a new member.

8JR93gA.png

This is the first ‘error’ I run into. When I get to the flavor step, nothing shows up. I have to click ‘Let the wiki be empty’ and go back to flavors in order to see them.

Image URL

PIz5qgg.png
FacSnHn.png
kNIltlv.png

The installer goes through, and appears to download the extensions required for the flavor install without any issues.

Image URL

BZJoQ5s.png

Once it begins installing everything, I get this error. It isn’t always at the same point, but every time I have tried to install I get the same results. I have tried this many times now, more than I can count, and always end up with this error. I am not confident that

Image URL

6qiNb6S.png

The only thing I have done different from the guide, was add -Djava.security.egd=file:/dev/./urandom to JAVA_OPTS.

I am pulling at straws here, and I think that it is mainly due to my inexperience with linux. If anyone out there knows what is going on, or has advice I would really appreciate it. I have tried searching for logs on the server, but honestly don’t know where they would be. I have looked online and found file paths, but nothing that has returned info that makes sense of what is going on. I am going to leave everything as is for now so if anyone needs additional data just let me know and I will do my best to get it for you.

I usually get this when the javascript is broken by something external (disabled with something like Noscript or with a browser cache issue even if those are not supposed to happen anymore since we generate different URL to pull js/css for each version of XWiki).

So according to your screenshot the install itself seems to run fine on the background but the browser cannot access the server to refresh the progress anymore (but it’s the first time I see this specific error).

The Tomcat 8 log can be found in /var/log/tomcat8/catalina.out.

You can find a summary of important files on http://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/InstallationViaAPT/#HOverviewoftheimportantfiles.

Here is my Catalina.out. As far as the install goes, are you saying that the install most likely continued without issues? If I reboot the server and relaunch the page, the manager starts again and goes back through the install steps. It seems like I can do this twice before everything breaks. I haven’t done that this time though.

catalina out.txt (48.4 KB)

I was just saying the error you get does not seems to be related to the install process itself which look OK in your screenshot. But if your client cannot access the server anymore it’s probably not a great sign for anything running in that server.

Here is the cause: java.lang.OutOfMemoryError: Java heap space. You most probably skipped http://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/InstallationViaAPT/#HMemory

Here is my output of the tomcat8 file. I will try and increase the ram to 2gb and see if that helps.

tomcat8.txt (1.9 KB)

1024 should be enough (that’s usually what I use).

You can use

ps aux | grep java

to make sure this setup was actually applied to the running instance.

I used the command you posted, and when going back into the distribution manager I received the same error.

However, after it failed I accessed the page again and it said the standard flavor was installed. I went through the rest of the steps and everything appears to be working properly. The only thing that I have changed, was when I went to increase the memory, I had to increase the droplet size from 1gb to 2gb. Im not sure if that was the cause of my troubles, but was the only major thing I changed during the install.

Thanks for all the help, and I will be sure to update once I have a chance to run through the install again.

The command I gave you does not “do” anything. It’s giving your the parameters that were used to start Java so that you can make sure that’s the expected ones.

Ahh okay. I still have quite a bit to learn.