Ubuntu

This article solves the following challenge: 

Chrome on Ubuntu causes kernel panic

This article solves the following challenge: 
Chrome on Ubuntu causes kernel panic
This article solves the following challenge: 
Chrome on Ubuntu causes kernel panic
This article solves the following challenge: 
Chrome on Ubuntu causes kernel panic
This article solves the following challenge: 
Chrome on Ubuntu causes kernel panic
The freezing itself would be a classical hint pointing towards some problems with the driver of the used GPU. However there are several things one can do to avoid this very unpleasant system behavior. Chrome, like other modern browsers, has the possibility to fall back on other components besides the regular CPU when it comes to tasks that are not very suitable for it (e.g. graphical processing with the GPU). This option is called “hardware acceleration” and can be deactivated. To do that, you only have to go into the options menu of Chrome, expand the advanced settings and scroll down to the system settings. Uncheck the corresponding checkbox.
This solution works fine, but now Chrome can’t optimize its performance any more using the available hardware. Another option is to target the used graphical driver itself. Therefore open up the Ubuntu system settings, search for “Software & Updates”, switch to the tab called “Additional drivers” and wait for the list to be loaded. Look for the graphic card driver and try a “proprietary” one.
If this problem occurs with the 64 bit version of Chrome, another thing that can be tried, is to use the 32 bit one. I did not try this myself, but I have read, that it have solved the problem in some cases.
Evaluate complexity of present statement:
Select ratingCancelGuessingPassing knowledgeKnowledgeableExpert
No votes yet
Evaluate complexity of present statement:
Select ratingCancelGuessingPassing knowledgeKnowledgeableExpert
Your rating: 3 Average: 3 (1 vote)
Evaluate complexity of present statement:
Select ratingCancelGuessingPassing knowledgeKnowledgeableExpert
Your rating: 3 Average: 3 (1 vote)
Evaluate complexity of present statement:
Select ratingCancelGuessingPassing knowledgeKnowledgeableExpert
Your rating: 3 Average: 3 (1 vote)

Evaluate complexity of present statement:

Select ratingCancelGuessingPassing knowledgeKnowledgeableExpert

Your rating: 3 Average: 3 (1 vote)

First, we need to select the Ubuntu as the image on our server.
After installing Ubuntu, we need to configure DNS on out domain. In case our domain is www.domain.com, we need to point it's DNS settings to Digitalocean's server. At our domain registrar, we point our domain to:

• ns1.digitalocean.com
• ns2.digitalocean.com
• ns3.digitalocean.com
After configuring the DNS, we need to connect to our server with SSH command in terminal
• ssh username@yoursite.com -p definedport

After we are asked for the password, we will access our remote server.
When connected to the remote server, first thing we need to do is aces superuser privilege and instal nginx. We do it with the following command:

• sudo apt-get install nginx

After this step, nginx will be installed but not running. In order to start the nginx service, we type into the terminal

• sudo service nginx start

Our nginx is now up and running. Now we need to create a virtual host and a folder which will contain our file. We do it wit the command

• sudo mkdir -p /var/www/domain.com/public_html

We need to change the permissions, so that everyone can read our files, but only root use can modify them. We do it with chmod command:

• sudo chmod 755 /var/www

Nginx by default looks for the index.html file which we need to create, and put some content in it:

• sudo nano /var/www/domain.com/public_html/index.html

Now we need to create our virtual host file in nginx's site-available folder

• sudo cp /etc/nginx/sites-available/default /etc/nginx/sites-available/domain.com
• sudo nano /etc/nginx/sites-available/domain.com

Now we have our configuration opened in a tex editor, with some default values. Our new server requires the following configuration:

server {
listen 80; ## this is default HTTP port

root /var/www/domain.com/public_html;
index index.html index.htm index.php; ##this is the list of files nginx will search for

# Make site accessible from http://localhost/
server_name domain.com;
}

Now we save it and exit. We need to draw a parallel from available to enabled sites, so we do it with

• sudo ln -s /etc/nginx/sites-available/domain.com /etc/nginx/sites-enabled/domain.com

In the final step, we need to restart our nginx server to apply changes. We do it with

• sudo service nginx restart

.
At this point, our site should be up and running.
From what is seen here, configuring nginx is even easier in the beginning than configuring Apache.
For sites with a lot of workload and if we pay attention to our resources, it is a much better choice than Apache.

So here is one way to do it (on an Ubuntu box):

1. Open a terminal
2. Install "curl": sudo apt-get install curl
3. Find out the web-adresses of your respective REST services and their needed inputs
4. Issue the following (exemplary) command:
curl -v -s -H "X-Requested-Auth: Digest" --digest -u your_remotesystem_account:theverygoodpassword --form-string "workflowDefinitionId=full" -F "file=@media.zip" http://webappserver.tuwien.ac.at/ingest/addZippedMediaPackage &
5. Play around a bit to get the syntax/inputs right, check if the status of your webapp has changed, if not, retry
6. Be happy ;)

For Linux machines it is necessary to set the correct CA certificate as well. The installed certificates are stored at /etc/cert.
As many users are Using Ubuntu I give step-by-step instructions for this distribution. For other distros the steps are similar.

• Open the Network Connection Settings-dialogue either via "System Settings" or via the Network-Icon on the menu bar on top of the screen
• Select your eduroam-connection from the list of connections and choose "Edit"
• Choose the "Wi-Fi Security"-tab.
• Have a look at the "CA certificate"-settings. The certificate Deutsche_Telekom_Root_CA_2.pem has to be set. This can be done by just klicking on the button right of the label "CA certificate". The machine shall search in the right folder automatically. If not, choose /etc/cert

The attached picture shows the correctly filled in Settings dialogue.