Carlos Vega's questions

I was reading this article about how to do a full system backup using rsync. This article assumes you have another machine with a similar linux system. What if is not the case? How different would be the procedure in order to do a full machine backup (including other mounted drives) in a way that if my hard drive breaks, I would just need to boot from my external backup drive?

I'm not sure about the excluding patterns used.

Thanks in advance.

I'm trying to add a wikimedia site on my server, which already has another site (which doesn't use PHP) on it. I want to put it on a different folder like www.hostname.com/wiki but it would be wonderful to have two different conf files to avoid mixing stuff. At the moment I'm trying to put this wikimedia site on a different port, the 81, and having some issues.

My nginx.conf looks like this:

user  nginx;
worker_processes  1;

error_log  /var/log/nginx/error.log;
#error_log  /var/log/nginx/error.log  notice;
#error_log  /var/log/nginx/error.log  info;

pid        /run/nginx.pid;

events {
    worker_connections  1024;
}

http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;
    sendfile        on;
    keepalive_timeout  65;
    index   index.html index.htm index.php;
    include /etc/nginx/conf.d/*.conf;

}

And on the conf.d folder I have two files:

site.conf which looks like this:

server {
    listen 80;

    server_name hostname.com;

    auth_basic "Restricted Access";
    auth_basic_user_file /etc/nginx/htpasswd.users;

    location /kibanaadmin/ {
        proxy_pass http://localhost:5601/;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }

    root /usr/share/nginx/html/pruebas/site;
    index index.php index.html index.htm;

    try_files $uri $uri/ /index.php?$args;

    location ~ \.php$ {
        try_files $uri =404;
        fastcgi_pass unix:/var/run/php-fpm/php-fpm.sock;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }
}

And wiki.conf file:

server {

        listen 81;

        server_name hostname.com;

        root /usr/share/nginx/html/tests/mediawiki;

        client_max_body_size 5m;
        client_body_timeout 60;

        index index.html index.htm index.php;

        location / {
                try_files $uri $uri/ @rewrite;
                autoindex on;
                index index.html index.html index.php;
        }

        location @rewrite {
                rewrite ^/(.*)$ /index.php?title=$1&$args;
        }

        location ^~ /maintenance/ {
                return 403;
        }

        location ~ \.php$ {
                autoindex on;
                include fastcgi_params;
                fastcgi_pass unix:/tmp/phpfpm.sock;
        }

        location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
                try_files $uri /index.php;
                expires max;
                log_not_found off;
        }

        location = /_.gif {
                expires max;
                empty_gif;
        }

        location ^~ /cache/ {
                deny all;
        }

        location /dumps {
                root /usr/share/nginx/html/tests/mediawiki/local;
                autoindex on;
        }
}

I noticed two different problems:

The first one is that when I try to get a php file I get a 502 Bad Gateway and on the error.log I get this message:

2015/07/15 10:56:57 [crit] 16306#0: *6 connect() to unix:/var/run/php-fpm/php-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: 111.222.333.444, server: hostname.com, request: "GET /info.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm/php-fpm.sock:", host: "hostname.com"

I checked my php config and I'm think is correct, I don't know if it's a nginx config problem or a PHP.

The second problem is that when I go to hostname.com:81 I get and 403 Forbidden (my other site in hostname.com:80 works with no issues) and this log message:

2015/07/15 10:59:15 [error] 16306#0: *9 directory index of

"/usr/share/nginx/html/pruebas/" is forbidden, client: 111.222.333.444, server: hostname.com, request: "GET / HTTP/1.1", host: "hostname.com:81"

My main question is: How can I manage to have the wikimedia site on the port 80 as well as my site but using two conf files of nginx to do it (If is not possible, how can I do it with just one file) and properly config the PHP stuff in nginx?

Note: I think is not a permissions problem because I gave the same to the wikimedia site as the other site has. I'm using Centos 7.1. Thank you in advance.

Our server runs offline and we need to install lot of yum packages, like oracle-jdk, elasticsearch, nginx, etc.

Is there any way to download the rpm dependencies so we can install them offline in the server?

I have a cloudera cluster with HDFS and Hue services and I'm trying to unify the authentication using LDAP.

I have my LDAP server running thanks to 389-ds (not sure if is the best way) and I can log into Hue with users from the LDAP server. When I login for first time, Hue creates the home directory in the HDFS.

But is not using the UID I set when I added the user to the LDAP server. It wouldn't be a problem if I just access the HDFS via Hue but I also have a machine with the HDFS mounted via NFS.

I'm also having problems to add LDAP authentication in the machine with the NFS mount. I can do su username (username being a user in the LDAP server) and the system adds a home directory, but I cannot authenticate via SSH using LDAP users. I need this to avoid adding local users too.

My main question is: How to force HDFS or Hue to use the same UID I set when I create LDAP users.

More details:

I have configured LDAP in cloudera for both Hue and Hadoop (not sure if the latter is using it properly) I know I could, maybe, change the UID a posteriori to the one set by Hue at the first login, but is more a workaround than a clean solution.

Pictures:

In this example, potato user has an uid 10104, but if I do ls -la /users/potato in the NFS mount, it says that the folder belongs to a user with uid 3312528423.

I have problems trying to install a new CDH5 cluster with cloudera. Using parcels everything goes fine except when oozie's sharedlib is installed. It fails uploading due to end of time-out.

Then I tried using packages but is worse. The cluster install fails downloading packages: "Operation too slow... trying another mirror... no more mirrors to try... giving up"

Downloading Packages: http://archive.cloudera.com/cdh5/redhat/6/x86_64/cdh/5/RPMS/noarch/bigtop-utils-0.7.0%2Bcdh5.2.0%2B0-1.cdh5.2.0.p0.40.el6.noarch.rpm: [Errno 12] Timeout on http://archive.cloudera.com/cdh5/redhat/6/x86_64/cdh/5/RPMS/noarch/bigtop-utils-0.7.0%2Bcdh5.2.0%2B0-1.cdh5.2.0.p0.40.el6.noarch.rpm: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds') Trying other mirror.

Error Downloading Packages: bigtop-utils-0.7.0+cdh5.2.0+0-1.cdh5.2.0.p0.40.el6.noarch: failure: RPMS/noarch/bigtop-utils-0.7.0+cdh5.2.0+0-1.cdh5.2.0.p0.40.el6.noarch.rpm from cloudera-cdh5: [Errno 256] No more mirrors to try.

END (1) remote package bigtop-utils could not be installed, giving up

I just need to install HDFS, Hue and, of course, its dependencies. Do you know what could be the reason of the time-out error? Maybe it has something to do with the cloudera servers and that today are slow.

Also, is there any other way to install oozie's sharedlib as a workaround of this?

UPDATE:

At the time of writing this I could install the cluster, via parcels, correctly. Anyway, I would like to know the answer to this questions.