Bert's questions

I'm using deployer (https://deployer.org/docs/6.x/tasks) to deploy my laravel application and it works like a charm. However, I want to make it more pretty. Why? Because I have background NodeJS processes running and at every deploy, they need to be restarted. Since there are 2 type of applications, the following is present in my deploy.php

task('post-deploy', [
    //'cron:install',
    'pm2:restart:qworker',
    'pm2:restart:echo',
    'cachetool:clear:opcache',
])->desc('After deploy tasks');

Now foir this to wotk, I had to make 2 tasks in recipes.php

desc('Restart QWorker');
task(
    'pm2:restart:qworker',
    function () {
        $option = get('pm2_qworker_name');

        run("pm2 restart ${option}");
    }
)->onHosts(getenv('SSH_HOST_1'));

desc('Restart Echo Servers');
task(
    'pm2:restart:echo',
    function () {
        $option = get('pm2_echo_name');

        run("pm2 restart ${option}");
    }
);

But I want to reduce this to one task only, but still being able to tell which process I wish to restart. My goal would look something like this in the deploy.php file

task('post-deploy', [
    //'cron:install',
    'pm2:restart --something',
    'pm2:restart --something2',
    'cachetool:clear:opcache',
])->desc('After deploy tasks');

Any ideas how to define this in recipes.php in only one task ?

We have a Laravel application and imagine the following: We have a slider with a play button that will start showing images on a slideshow. These images arrived from web cameras so obviously there are a lot of images. The load time of the page is horrible because it is trying to load ALL the images and often, even PHP runs out of memory trying to load all the images. Now, I can increase the amount of memory and execution time for PHP to keep doing it, but isn't there a more sophisticated way to load these images depending on where do I scroll the slider or press the play button?

Also, one thing to keep in mind: Showing the images are behind an auth system so, not anyone is allowed to watch any camera. It depends on the rules and the users settings, etc...

I've a Zabbix installation on my CentOS 7 server and the following happens:

• Installed Zabbix Server with Frontend according to Official Install Guide (https://www.zabbix.com/download?zabbix=5.0&os_distribution=centos&os_version=7&db=mysql&ws=nginx)
• Copied the server.conf information directly into /etc/opt/rh/rh-nginx116/nginx/nginx.conf
• Acquired an SSL cert for a domain name, I wish to use
• Modified the NginX config to accept only 443 with the same settings

Result:

• In Google Chrome, I get a ERR_CONNECTION_RESET error

Workaround:

• If I enable the HTTP on port 80, via IP address I can access the frontend.

Desire:

• I want to make my Zabbix Frontend available via the domain name on HTTPS and not via IP on HTTP

The following setup works via IP and HTTP but with

• IP + HTTP
• Domain + HTTP
• Domain + HTTP

nginx.conf

# For more information on configuration, see:
#   * Official English Documentation: http://nginx.org/en/docs/
#   * Official Russian Documentation: http://nginx.org/ru/docs/

user nginx;
worker_processes auto;
error_log /var/opt/rh/rh-nginx116/log/nginx/error.log;
pid /var/opt/rh/rh-nginx116/run/nginx/nginx.pid;

# Load dynamic modules. See /opt/rh/rh-nginx116/root/usr/share/doc/README.dynamic.
include /opt/rh/rh-nginx116/root/usr/share/nginx/modules/*.conf;

events {
    worker_connections  1024;
}

http {
    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/opt/rh/rh-nginx116/log/nginx/access.log  main;

    sendfile        on;
    tcp_nopush      on;
    tcp_nodelay     on;
    keepalive_timeout  65;
    types_hash_max_size 2048;

    include       /etc/opt/rh/rh-nginx116/nginx/mime.types;
    default_type  application/octet-stream;

    # Load modular configuration files from the /etc/nginx/conf.d directory.
    # See http://nginx.org/en/docs/ngx_core_module.html#include
    # for more information.
    #include /etc/opt/rh/rh-nginx116/nginx/conf.d/*.conf;

server {
        listen          80;
        server_name     zabbix.mycompany.com;

        root    /usr/share/zabbix;

        index   index.php;

        location = /favicon.ico {
                log_not_found   off;
        }

        location / {
                try_files       $uri $uri/ =404;
        }

        location /assets {
                access_log      off;
                expires         10d;
        }

        location ~ /\.ht {
                deny            all;
        }

        location ~ /(api\/|conf[^\.]|include|locale) {
                deny            all;
                return          404;
        }

        location ~ [^/]\.php(/|$) {
                fastcgi_pass    unix:/var/opt/rh/rh-php72/run/php-fpm/zabbix.sock;
                fastcgi_split_path_info ^(.+\.php)(/.+)$;
                fastcgi_index   index.php;

                fastcgi_param   DOCUMENT_ROOT   /usr/share/zabbix;
                fastcgi_param   SCRIPT_FILENAME /usr/share/zabbix$fastcgi_script_name;
                fastcgi_param   PATH_TRANSLATED /usr/share/zabbix$fastcgi_script_name;

                include fastcgi_params;
                fastcgi_param   QUERY_STRING    $query_string;
                fastcgi_param   REQUEST_METHOD  $request_method;
                fastcgi_param   CONTENT_TYPE    $content_type;
                fastcgi_param   CONTENT_LENGTH  $content_length;

                fastcgi_intercept_errors        on;
                fastcgi_ignore_client_abort     off;
                fastcgi_connect_timeout         60;
                fastcgi_send_timeout            180;
                fastcgi_read_timeout            180;
                fastcgi_buffer_size             128k;
                fastcgi_buffers                 4 256k;
                fastcgi_busy_buffers_size       256k;
                fastcgi_temp_file_write_size    256k;
        }
}

server {
        listen          443 ssl;
        server_name     zabbix.mycompany.com;

        root    /usr/share/zabbix;

        ssl_certificate         /etc/letsencrypt/live/zabbix.mycompany.com/fullchain.pem;
        ssl_certificate_key     /etc/letsencrypt/live/zabbix.mycompany.com/privkey.pem;

        ssl_protocols   TLSv1.3;
        ssl_prefer_server_ciphers       on;
        ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:ECDHE-RSA-AES128-GCM-SHA256:AES256+EECDH:DHE-RSA-AES128-GCM-SHA256:AES256+EDH:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4";

        add_header      Strict-Transport-Security "max-age=63072000; includeSubdomains; preload";

        ssl_dhparam /etc/dhparam.pem;

        index   index.php;

        location = /favicon.ico {
                log_not_found   off;
        }

        location / {
                try_files       $uri $uri/ =404;
        }

        location /assets {
                access_log      off;
                expires         10d;
        }

        location ~ /\.ht {
                deny            all;
        }

        location ~ /(api\/|conf[^\.]|include|locale) {
                deny            all;
                return          404;
        }

        location ~ [^/]\.php(/|$) {
                fastcgi_pass    unix:/var/opt/rh/rh-php72/run/php-fpm/zabbix.sock;
                fastcgi_split_path_info ^(.+\.php)(/.+)$;
                fastcgi_index   index.php;

                fastcgi_param   DOCUMENT_ROOT   /usr/share/zabbix;
                fastcgi_param   SCRIPT_FILENAME /usr/share/zabbix$fastcgi_script_name;
                fastcgi_param   PATH_TRANSLATED /usr/share/zabbix$fastcgi_script_name;

                include fastcgi_params;
                fastcgi_param   QUERY_STRING    $query_string;
                fastcgi_param   REQUEST_METHOD  $request_method;
                fastcgi_param   CONTENT_TYPE    $content_type;
                fastcgi_param   CONTENT_LENGTH  $content_length;

                fastcgi_intercept_errors        on;
                fastcgi_ignore_client_abort     off;
                fastcgi_connect_timeout         60;
                fastcgi_send_timeout            180;
                fastcgi_read_timeout            180;
                fastcgi_buffer_size             128k;
                fastcgi_buffers                 4 256k;
                fastcgi_busy_buffers_size       256k;
                fastcgi_temp_file_write_size    256k;
        }
}

#    server {
#        listen       80 default_server;
#        listen       [::]:80 default_server;
#        server_name  _;
#        root         /opt/rh/rh-nginx116/root/usr/share/nginx/html;
#
#        # Load configuration files for the default server block.
#        include      /etc/opt/rh/rh-nginx116/nginx/default.d/*.conf;
#
#        location / {
#        }
#
#        error_page 404 /404.html;
#        location = /40x.html {
#        }
#
#        error_page 500 502 503 504  /50x.html;
#        location = /50x.html {
#        }
#
#        # proxy the PHP scripts to Apache listening on 127.0.0.1:80
#        #
#        #location ~ \.php$ {
#        #    proxy_pass   http://127.0.0.1;
#        #}
#
#        # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#        #
#        #location ~ \.php$ {
#        #    root           html;
#        #    fastcgi_pass   127.0.0.1:9000;
#        #    fastcgi_index  index.php;
#        #    fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
#        #    include        fastcgi_params;
#        #}
#
#        # deny access to .htaccess files, if Apache's document root
#        # concurs with nginx's one
#        #
#        #location ~ /\.ht {
#        #    deny  all;
#        #}
#    }
#

    # another virtual host using mix of IP-, name-, and port-based configuration
    #
    #server {
    #    listen       8000;
    #    listen       somename:8080;
    #    server_name  somename  alias  another.alias;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}


    # HTTPS server
    #
    #server {
    #    listen       443;
    #    server_name  localhost;

    #    ssl                  on;
    #    ssl_certificate      cert.pem;
    #    ssl_certificate_key  cert.key;

    #    ssl_session_timeout  5m;

    #    ssl_protocols  SSLv2 SSLv3 TLSv1;
    #    ssl_ciphers  HIGH:!aNULL:!MD5;
    #    ssl_prefer_server_ciphers   on;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}

}

Also, here is a part of my netstat -lntup command result

...
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      8267/nginx: master  
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      8267/nginx: master  
...

In a laravel project I have a storage folder and inside it, I have an app folder (normally). So the full path is: /var/www/html/myproject/storage/app

Now I have a file server and I wish to serve the app folder from there. Thus I've set up an NFS server and mounted the folder into /var/nfs/mounted/app folder and created a link (ln -s /var/nfs/mounted/app /var/www/html/myproject/storage/app)

With this the project works like a charm, all the files exist. However, git keeps telling me the files are commited for deletion. No matter what I've tried to put into .gitignore, I've been ignored (badum tsss) So far, the following was tried:

• /storage/*
• **/storage
• /storage/app
• /storage/app/*

Any other ideas?

I have currently 2 Virtual Private Servers with 3-3 Redis instances. What I want os, to spread them to 3 VPSs with 2-2-2 nodes each. How do I do that in a way, I can keep all my keys? I also want to reorganize the Masters and slaves to have one of each on a server.

Existing system

Server 1)

• 10.0.0.201:7101 (M)
• 10.0.0.201:7102 (S:7202)
• 10.0.0.201:7103 (M)

Server 2)

• 10.0.0.202:7201 (S:7101)
• 10.0.0.202:7202 (M)
• 10.0.0.202:7203 (S:7103)

What I want:

Server 1)

• 10.0.0.201:7101 (M)
• 10.0.0.201:7102 (S:7301)

Server 2)

• 10.0.0.202:7201 (M)
• 10.0.0.202:7202 (S:7102)

Server 3)

• 10.0.0.203:7301 (M)
• 10.0.0.203:7302 (S:7202)

Let's say you have 2 web servers. Both has NginX installed. You want to load balance the traffic between them. How do you do that in nginx.conf?

Server1:

http {
  upstream myproject {
    ip_hash;
    server 127.0.0.1:8000;
    server 10.0.0.2:8000;
  }

  server {
    listen 80;
    server_name www.domain.com;
    location / {
      proxy_pass http://myproject;
    }
  }
}

Server2:

http {
  upstream myproject {
    ip_hash;
    server 127.0.0.1:8000;
    server 10.0.0.1:8000;
  }

  server {
    listen 80;
    server_name www.domain.com;
    location / {
      proxy_pass http://myproject;
    }
  }
}

Should this work or is it a complete failure?

I'm banging my head against the wall now for 3 days and counting. I hope you can tell me what am I doing wrong.

I have a Redis cluster with 3 masters and 3 slaves. A NodeJS application wishes to use the redis to store and serve data quickly. All seemed fine, however, we experienced occasional drops in the application. Turns out, it frequently restarted itself. At the time of a restart, the following messages are logged by the application (not by redis)

2020-08-05 08:48 +02:00: events.js:288
2020-08-05 08:48 +02:00:       throw er; // Unhandled 'error' event
2020-08-05 08:48 +02:00:       ^
2020-08-05 08:48 +02:00: 
2020-08-05 08:48 +02:00: Error: connect EMFILE 10.0.0.201:7101 - Local (undefined:undefined)
2020-08-05 08:48 +02:00:     at internalConnect (net.js:917:16)
2020-08-05 08:48 +02:00:     at defaultTriggerAsyncIdScope (internal/async_hooks.js:311:12)
2020-08-05 08:48 +02:00:     at net.js:1007:9
2020-08-05 08:48 +02:00:     at processTicksAndRejections (internal/process/task_queues.js:79:11)
2020-08-05 08:48 +02:00:     at runNextTicks (internal/process/task_queues.js:66:3)
2020-08-05 08:48 +02:00:     at listOnTimeout (internal/timers.js:518:9)
2020-08-05 08:48 +02:00:     at processTimers (internal/timers.js:492:7)
2020-08-05 08:48 +02:00: Emitted 'error' event on Socket instance at:
2020-08-05 08:48 +02:00:     at emitErrorNT (internal/streams/destroy.js:92:8)
2020-08-05 08:48 +02:00:     at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
2020-08-05 08:48 +02:00:     at processTicksAndRejections (internal/process/task_queues.js:84:21)
2020-08-05 08:48 +02:00:     at runNextTicks (internal/process/task_queues.js:66:3)
2020-08-05 08:48 +02:00:     at listOnTimeout (internal/timers.js:518:9)
2020-08-05 08:48 +02:00:     at processTimers (internal/timers.js:492:7) {
2020-08-05 08:48 +02:00:   errno: 'EMFILE',
2020-08-05 08:48 +02:00:   code: 'EMFILE',
2020-08-05 08:48 +02:00:   syscall: 'connect',
2020-08-05 08:48 +02:00:   address: '10.0.0.201',
2020-08-05 08:48 +02:00:   port: 7101
2020-08-05 08:48 +02:00: }
2020-08-05 08:48 +02:00: events.js:288
2020-08-05 08:48 +02:00:       throw er; // Unhandled 'error' event
2020-08-05 08:48 +02:00:       ^
2020-08-05 08:48 +02:00: 
2020-08-05 08:48 +02:00: Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
2020-08-05 08:48 +02:00:     at ChildProcess.target.send (internal/child_process.js:679:16)
2020-08-05 08:48 +02:00:     at Worker.send (internal/cluster/worker.js:45:28)
2020-08-05 08:48 +02:00:     at Server.<anonymous> (/totally/secret/folder/structure/app.js:136:16)
2020-08-05 08:48 +02:00:     at Server.emit (events.js:311:20)
2020-08-05 08:48 +02:00:     at TCP.onconnection (net.js:1554:8)
2020-08-05 08:48 +02:00: Emitted 'error' event on Worker instance at:
2020-08-05 08:48 +02:00:     at ChildProcess.<anonymous> (internal/cluster/worker.js:29:12)
2020-08-05 08:48 +02:00:     at ChildProcess.emit (events.js:311:20)
2020-08-05 08:48 +02:00:     at internal/child_process.js:683:35
2020-08-05 08:48 +02:00:     at processTicksAndRejections (internal/process/task_queues.js:79:11) {
2020-08-05 08:48 +02:00:   code: 'ERR_IPC_CHANNEL_CLOSED'
2020-08-05 08:48 +02:00: }
2020-08-05 08:48 +02:00: WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
2020-08-05 08:48 +02:00: WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
2020-08-05 08:48 +02:00: WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
2020-08-05 08:48 +02:00: WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
2020-08-05 08:48 +02:00: WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
2020-08-05 08:48 +02:00: WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
2020-08-05 08:48 +02:00: WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
2020-08-05 08:48 +02:00: WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
2020-08-05 08:48 +02:00: WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
2020-08-05 08:48 +02:00: WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
2020-08-05 08:48 +02:00: (node:28699) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'emit' of undefined
2020-08-05 08:48 +02:00:     at /totally/secret/folder/structure/app.js:323:34
2020-08-05 08:48 +02:00:     at runMicrotasks (<anonymous>)
2020-08-05 08:48 +02:00:     at processTicksAndRejections (internal/process/task_queues.js:97:5)
2020-08-05 08:48 +02:00: (node:28699) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 530)
2020-08-05 08:48 +02:00: (node:28699) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2020-08-05 08:48 +02:00: (node:28699) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 201 error listeners added to [Cluster]. Use emitter.setMaxListeners() to increase limit

What I've tried so far is to disable either AOF or RDB but with no success, the occasional restarts still happen. What else could be the cause of this issue? The developers say the application simply cannot connect to Redis, thus failing. But that is impossible. Pinging the server and watching the uptime of the service confirms 100%, that the server itself is always reachable and available for the application. All 6 of them.

So I've found NginX's official tutorial, how to use NginX Plus as the proxy for the MariaDB Cluster. However, if I do this with my standard NginX (not the Plus edition) I constantly get the error nginx: [emerg] invalid URL prefix in /etc/nginx/conf.d/mariadb.conf:10

Here is the config

upstream db {
    server 10.0.0.101:3306;
    server 10.0.0.102:3306;
    server 10.0.0.103:3306;
}

server {
    listen 3306;
    location / {
        proxy_pass db;
        proxy_connect_timeout 1s;
    }
}

My question if this is only available on NginX Plus or I'm doing something wrong? I'm aware, that normally I need a prefix in the proxy_pass like https:// but in this case?

I have a Laravel project that needs PHP 7.1 but on the server, we use 7.2. We have separate nginx config files for each project and they all work fine.

I've decided to go laradock and serve PHP 7.1 for the project. Starts up like a charm out of the box, however... After I've built the docker images I get the following:

0 ✓ server /var/www/html/myproject.com/laradock $ docker-compose ps
           Name                          Command              State          Ports        
------------------------------------------------------------------------------------------
laradock_docker-in-docker_1   dockerd-entrypoint.sh           Up      2375/tcp, 2376/tcp  
laradock_php-fpm_1            docker-php-entrypoint php-fpm   Up      9000/tcp            
laradock_workspace_1          /sbin/my_init                   Up      0.0.0.0:2222->22/tcp

In my NginX config, I'm trying to rewrite the root location like:

fastcgi_pass 127.0.0.1:9000;

No luck, I get 2019/11/06 14:06:42 [error] 1287#1287: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 84.X.XX.207, server: myproject.com, request: "GET /item/show/24401 HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "myproject.com", referrer: "https://myproject.com/"

Any ideas what is happening? :(

UPDATE

I've tried again, this time with the IP address of the php-fpm docker image that I've got by executing nspect 9d15baXXXXXX | grep IPAddress

Now, the log looks like this:

2019/11/06 14:58:49 [error] 12391#12391: *2 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 84.2.XX.XXX, server: myproject.com, request: "GET /item/show/2350 HTTP/2.0", upstream: "fastcgi://192.168.XX.X:9000", host: "myproject.com", referrer: "https://myproject.com/"

Still a bit confused what is happening.

UPDATE #2

OK, I've figured out some stuff.

Firstly, the IP address of the PHP-FPM docker is good in the fastcgi_pass BUT, I MUST rewrite fastcgi_param SCRIPT_FILENAME. Normally I have $document_root$fastcgi_script_name there, but that is not the same as inside the docker. I had to modify it to /var/www/public$fastcgi_script_name. But now, this is getting more complicated, since now all I get is a browser error 500 message, so no logs in my NginX.

How should I debug this?

Here is what I wish to do in GitLab CI/CD: Whenever something is pushed into a specific branch I wish to have multiple scrips and CI/CD should decide which script should be run based on the pushed files list.

For example:

• IF anything changed in ./resources/assets/views/* then run SCRIPT1
• IF anything changed in ./database/* then run SCRIPT2
• etc...

Do you Lads have any idea for it?

I don't know if it is just me or anyone else came across this issue? I want to install PHP 7.1.14, so I've installed the REMI repository on my CentOS 7 and enabled the php71 repository. However, when I do a yum list php --showduplicates it shows me only the latest and one slightly older version. Do not tell me please that my only option is to install from source because that will be a pain in the *ss because then I have to build all the php modules from source as well and that is not an option. Is there another repository that contains all the sub-versions of a specific version like 7.1 ?

The situation: We have a 6 disk RAID6 array in our server. We forgot to keep a bigger space for the root partition and used up all remaining space. Now, if we extent the array with +1 disk and reconfigure the array, we can see that the sda have got an increased size compared to the previous data with lsblk, but I have no idea how to extend the root partition now. Anyone can tell me how can I do that?

I have a folder with about 1.5 million files and I need them to be copied to a secondary server as often as possible. What would you recommend because clearly standard rsync commands do not make it because just sending the incremental file list (while using rsync -Pcr options) takes about 30 minutes... and the file transfer about 10 seconds. How would you solve this issue fellow SysAdmins?

I currently use the following command with a 30 minute interval:

rsync -Pcr /var/primary/storage /var/secondary/ --log-file=/tmp/rsync.log

Note: The /var/primary/storage is a folder mounted to the secondary server via NFS

UPDATE:

I've also tried now the following command:

cp -aur /var/primary/storage /var/secondary/

But it is odd for me that the command asks me if I allow the overwriting of a destination file that has the exact same modified date as the source file. Isn't the update option supposed to watch it and copy by default if a source file is newer (or modified) than the destination file?

Server: XenServer 7.1

Management: XenCenter

Goal: Have a Scheduled Snapshot saved to an external drive connected to the server via USB

Issue: The server recognizes the external drive as a removable storage repository but I'm unable to find where to set it as a default location for snapshots.

This is rather interesting Guys! I have the following code in one of my webapplications NginX configuration:

    location /login {
            #access_log off;
            proxy_pass https://public;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header Host $host;
            proxy_set_header X-Forwarded-For        $proxy_add_x_forwarded_for;
            proxy_set_header X-SSL-Client-Verify    $ssl_client_verify;
            proxy_set_header X-Client-S-DN          $ssl_client_s_dn;
            allow   10.0.0.31;
            deny all;
    }

As you can see, I wish to deny all connections to the login interface but one IP address. This works like a charm and shows standard NginX 403 error message when I try to connect from another IP. Now comes the kicker. If I add a custom error message line THE WHOLE ALLOW/DENY OPTION IS BEING IGNORED!

I added:

    error_page 403 /40x.html;

OFC I've created a custom file to /usr/shar/nginx/html and the file exists. There is no error message in NginX but if I add the upper line to the webapplication config (or to the standard nginx.conf, doesn't matter) the rules I've set for allowed IPs and deny all is being ignored completely. What gives? Anyone has any idea how to give the users a custom NginX error page and keep the allow & deny options?

I have a VPS that we will be shutting down soon, so I want to create a full backup of it. I was thinking about rsync, because if I google linux and backup words, I constantly get hit by rsync, so why the hell not. :) However, here comes the kicker.

The backup machine where I want to backup the VPS in not accessible from the internet. So I can't just use what almost everybody suggests to SSH into the VPS, sudo rsync almost everything and as output mark the backup server. I want to run a bash command that does something similar to dd, so if I run rsync on the remote server, I could mark my local folder as output. Also I have to mention, that root ssh login is not allowed, so I can only SSH into the VPS as a user who can actually turn into sudo, but by default it is just a plain user.

I came up with the following rsync command:

sudo rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} /* /backup/machine/folder

And I wish to use it somehow like this dd command I've used for cloning but the opposite way:

dd if=/dev/sda bs=4096 | pv | ssh root@<<TargetServer-IP>> ”dd of=/dev/sda bs=4096”

I have a question, is it possible to add one host NIC to multiple Virtual machines in libvirt with both of them using it as bridged mode. I've ran out of NIC-s and I still have 2 VM-s who need bridged connection to the network. That is why I was thinking, if it is possible. I can't really experiment with it in my current environment, but I'm a fast learner. :) Please, make me smarter!

I have inherited a CentOS server where nodejs is installed from epel repository. However, I need a specific version of it, so I've installed nodejs repository but I can't update it from the new repository since it tells me the following:

Loaded plugins: fastestmirror
nodesource                                                                                                                                                                                    | 2.5 kB  00:00:00     
nodesource/x86_64/primary_db                                                                                                                                                                  |  38 kB  00:00:00     
Loading mirror speeds from cached hostfile
 * base: ftp.freepark.org
 * epel: mirror.imt-systems.com
 * extras: ftp.freepark.org
 * remi: mirror.23media.de
 * remi-php56: mirror.23media.de
 * remi-safe: mirror.23media.de
 * updates: ftp.freepark.org
Resolving Dependencies
--> Running transaction check
---> Package npm.x86_64 1:3.10.10-1.6.9.4.2.el7 will be updated
---> Package npm.x86_64 1:3.10.10-1.6.10.1.2.el7 will be an update
--> Processing Dependency: nodejs = 1:6.10.1-2.el7 for package: 1:npm-3.10.10-1.6.10.1.2.el7.x86_64
--> Running transaction check
---> Package nodejs.x86_64 1:6.9.4-2.el7 will be updated
--> Processing Dependency: nodejs(x86-64) = 1:6.9.4-2.el7 for package: 1:nodejs-devel-6.9.4-2.el7.x86_64
---> Package nodejs.x86_64 1:6.10.1-2.el7 will be an update
--> Running transaction check
---> Package nodejs-devel.x86_64 1:6.9.4-2.el7 will be updated
---> Package nodejs-devel.x86_64 2:6.10.2-2nodesource.el7.centos will be an update
--> Processing Dependency: nodejs(x86-64) = 2:6.10.2-2nodesource.el7.centos for package: 2:nodejs-devel-6.10.2-2nodesource.el7.centos.x86_64
epel/x86_64/filelists_db                                                                                                                                                                      | 7.7 MB  00:00:00     
--> Running transaction check
---> Package nodejs.x86_64 1:6.9.4-2.el7 will be updated
---> Package nodejs.x86_64 1:6.9.4-2.el7 will be updated
---> Package nodejs.x86_64 1:6.10.1-2.el7 will be an update
--> Processing Dependency: nodejs = 1:6.10.1-2.el7 for package: 1:npm-3.10.10-1.6.10.1.2.el7.x86_64
---> Package nodejs.x86_64 2:6.10.2-2nodesource.el7.centos will be an update
--> Finished Dependency Resolution
Error: Package: 1:npm-3.10.10-1.6.10.1.2.el7.x86_64 (epel)
           Requires: nodejs = 1:6.10.1-2.el7
           Removing: 1:nodejs-6.9.4-2.el7.x86_64 (@epel)
               nodejs = 1:6.9.4-2.el7
           Updated By: 2:nodejs-6.10.2-2nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.10.2-2nodesource.el7.centos
           Available: nodejs-6.0.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 6.0.0-1nodesource.el7.centos
           Available: nodejs-6.1.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 6.1.0-1nodesource.el7.centos
           Available: nodejs-6.2.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 6.2.0-1nodesource.el7.centos
           Available: nodejs-6.2.1-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 6.2.1-1nodesource.el7.centos
           Available: nodejs-6.2.2-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 6.2.2-1nodesource.el7.centos
           Available: 1:nodejs-6.3.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 1:6.3.0-1nodesource.el7.centos
           Available: 1:nodejs-6.3.1-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 1:6.3.1-1nodesource.el7.centos
           Available: 1:nodejs-6.4.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 1:6.4.0-1nodesource.el7.centos
           Available: 1:nodejs-6.6.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 1:6.6.0-1nodesource.el7.centos
           Available: 1:nodejs-6.7.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 1:6.7.0-1nodesource.el7.centos
           Available: 1:nodejs-6.10.1-2.el7.x86_64 (epel)
               nodejs = 1:6.10.1-2.el7
           Available: 2:nodejs-6.8.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.8.0-1nodesource.el7.centos
           Available: 2:nodejs-6.8.1-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.8.1-1nodesource.el7.centos
           Available: 2:nodejs-6.9.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.9.0-1nodesource.el7.centos
           Available: 2:nodejs-6.9.1-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.9.1-1nodesource.el7.centos
           Available: 2:nodejs-6.9.2-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.9.2-1nodesource.el7.centos
           Available: 2:nodejs-6.9.3-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.9.3-1nodesource.el7.centos
           Available: 2:nodejs-6.9.4-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.9.4-1nodesource.el7.centos
           Available: 2:nodejs-6.9.5-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.9.5-1nodesource.el7.centos
           Available: 2:nodejs-6.10.0-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.10.0-1nodesource.el7.centos
           Available: 2:nodejs-6.10.1-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.10.1-1nodesource.el7.centos
           Available: 2:nodejs-6.10.2-1nodesource.el7.centos.x86_64 (nodesource)
               nodejs = 2:6.10.2-1nodesource.el7.centos
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

How would you resolve this issue?

I've given the task to create two CentOS 7 servers where not only the databases will be replicated but also files. Now my problem is that there will be probably hundred-thousands of files if not a million of files with a wide variety of sizes from a few Kbytes to ~1 Gbyte.

I've read about

• incrion
• lysncd
• git-annex
• ChironFS

Now I wish to ask your experiences about any of these if you have been using it or currently using it. How is the performance doing with the file changes regarding to copies and deletions? I'm very affraid of using any rsync because my experience is that it is not very fast with a lot of small files, therefore I can't really use it for a real-time file replication. Or am I wrong? Please prove me wrong. :)

Or maybe I'll need a 3rd and 4th server as fileservers? If yes, then the question still remains: How to replicate the files between the two servers in realtime?

Cheers!

I wish to have a brainstorm with you all about Laravel 5 and it's mail function. The point is: I have multiple servers with CentOS 7 installed and using them as webservers for laravel 5 based sites. A few days before, I had to move a website from staging to production server. However, the mail function was not working at all.

On the staging site I had the mail driver set to sendmail and worked like a charm. On the other hand, the production server couldn't send a single mail via the website until I've set the mail driver to "mail" insted of "sendmail". Do you guys have any idea why is this happening? All the servers are using sendmail without a second thought but this particular server (doesn't differ from the others) aggrees only with "mail" as mail driver. Why could it be?