d hee's questions

My AMD Ryzen Linux system has ECC memory that purposely bought.

edac-util shows I have ecc, if I am reading correctly:

mc0: 0 Uncorrected Errors with no DIMM info
mc0: 0 Corrected Errors with no DIMM info
mc0: csrow0: 0 Uncorrected Errors
mc0: csrow0: mc#0csrow#0channel#0: 0 Corrected Errors
mc0: csrow1: 0 Uncorrected Errors
mc0: csrow1: mc#0csrow#1channel#0: 0 Corrected Errors
mc0: csrow2: 0 Uncorrected Errors
mc0: csrow2: mc#0csrow#2channel#0: 0 Corrected Errors
mc0: csrow3: 0 Uncorrected Errors
mc0: csrow3: mc#0csrow#3channel#0: 0 Corrected Errors
edac-util: No errors to report.

But edac-ctl shows drivers not loaded:

edac-ctl: drivers not loaded.

Why does edac-util not need drivers or recognize drivers while edac-util does?

Note....was not sure if I should ask this here or in linux stack. Since most linux users won't be using ecc I thought I would ask here.

Note 2.... yes, my motherboard supports ECC. I made sure.

I am trying to get redirections back to index.html when foo parameter is given after cloudshareimage/foo instead of a 404....with foo removed. Or any other parameter for that matter.

Any idea why this is not working on nginx?

server {
        listen   80; 
        server_name  www.cloudshareimage.com cloudshareimage.com;

        access_log  /var/log/nginx/cloudimageshare.log;

  client_header_buffer_size 128;

  expires -1;
  access_log /var/log/nginx/cloudimageshare.log;

  root /var/www/cloudshareimage/app/static/;
  error_page 404 = @notfound;

        location / {
           error_page 404 = @notfound;
        }

        location @notfound {
            return 301 /;
        }

}

 - - [27/Mar/2020:07:54:50 -0500] "GET /foo HTTP/1.1" 404 233 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36"

What is the difference between -cpu host and -cpu max? It seems to me that they are the same

Or another way asked.... what is the difference between all supported host features vs all features supported by the accelerator?

I am assuming that the accelerator would also be the host features since you can only use one option here.

From man page:

x86 host KVM processor with all supported host features
x86 max Enables all features supported by the accelerator in the current host

I have Ubuntu server on Google Cloud/Compute Engine that works with no issues. I can ssh into it from command line or I ssh into it from the Google Cloud dashboard console.

When I take a snapshot of it to clone the server, I can not ssh into the new clone. The ssh daemon does not seem to be listening. I can not even ssh into it from the Google Cloud dashboard.

Does anyone know why?

From serial console(Note- I edited the sha256 in the paste):

Mar 20 20:16:19 qa-for-work cloud-init[1042]: Generating public/private ed25519 key pair.
Mar 20 20:16:19 qa-for-work cloud-init[1042]: Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.
cloud-init[1042]: Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.
Mar 20 20:16:20 qa-for-work cloud-init[1042]: Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub.
[  110.667373] cloud-init[1042]: Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub.
Mar 20 20:16:20 qa-for-work cloud-init[1042]: The key fingerprint is:
[  110.667475] cloud-init[1042]: The key fingerprint is:
Mar 20 20:16:20 qa-for-work cloud-init[1042]: SHA256:u6ros 4MQtfpO5GM root@qa-for-work
[  110.667560] cloud-init[1042]: SHA256:u6ros 1GtaVy4MQtfpO5GM root@qa-for-work
Mar 20 20:16:20 qa-for-work cloud-init[1042]: The key's randomart image is:
[  110.667644] cloud-init[1042]: The key's randomart image is:
Mar 20 20:16:20 qa-for-work cloud-init[1042]: +--[ED25519 256]--+
[  110.667775] cloud-init[1042]: +--[ED25519 256]--+
Mar 20 20:16:20 qa-for-work cloud-init[1042]: | o*o..=+o...     |
[  110.667864] cloud-init[1042]: | o*o..=+o...     |
Mar 20 20:16:20 qa-for-work cloud-init[1042]: | o.o.o.+...      |
[  110.667939] cloud-init[1042]: | o.o.o.+...      |
Mar 20 20:16:20 qa-for-work cloud-init[1042]: |  o . ...o .     |
[  110.668037] cloud-init[1042]: |  o . ...o .     |
Mar 20 20:16:20 qa-for-work cloud-init[1042]: |   = . .. +      |
[  110.668116] cloud-init[1042]: |   = . .. +      |
Mar 20 20:16:20 qa-for-work cloud-init[1042]: |  + = o S  .     |
[  110.668192] cloud-init[1042]: |  + = o S  .     |
Mar 20 20:16:20 qa-for-work cloud-init[1042]: | o + o + .       |
[  110.668275] cloud-init[1042]: | o + o + .       |
Mar 20 20:16:20 qa-for-work cloud-init[1042]: |o + o   E        |
[  110.668349] cloud-init[1042]: |o + o   E        |
Mar 20 20:16:20 qa-for-work cloud-init[1042]: |.*.+ . + o       |
[  110.668503] cloud-init[1042]: |.*.+ . + o       |
Mar 20 20:16:20 qa-for-work cloud-init[1042]: |ooB+o...o        |
[  110.668596] cloud-init[1042]: |ooB+o...o        |
Mar 20 20:16:20 qa-for-work systemd[1]: Started Initial cloud-init job (metadata service crawler).
Mar 20 20:16:20 qa-for-work cloud-init[1042]: +----[SHA256]-----+
[  110.668946] cloud-init[1042]: +----[SHA256]-----+
Mar 20 20:16:20 qa-for-work ntpdate[1023]: adjust time server 169.254.169.254 offset 0.361638 sec
Mar 20 20:16:20 qa-for-work systemd[1]: Reached target Network is Online.
Mar 20 20:16:20 qa-for-work systemd[1]: Reached target Cloud-config availability.
Mar 20 20:16:20 qa-for-work systemd[1]: Startup finished in 7.356s (kernel) + 1min 42.350s (userspace) = 1min 49.706s.

I am using Namecheap default DNS, where I bought the dns name. However, I am having a issue...

Typically, for AWS and Rackspace I would have:

A Record: foo.com 124.22.22.1
Cname:    www.example.com foo.com

But for Namecheap I have to use @ to show server root:

A Record: @ 124.22.22.1
Cname:    www.example.com example.com

With Namecheap DNS, http://example.com works but not www.example.com with ERR_NAME_NOT_RESOLVED. Any suggestions?

I am new to AWS and I have a t2 micro instance. I am only using it to host a static website with nginx.

What is really strange is the public ipaddress(which I use for SSH) is not the same as the eth0 ip address. Because of this, http traffic is not reaching the server when I use my ssh public ipaddress in the URL.

I am not using any customary security groups. Everything is default right now.

How do I get http traffic to the server when the public ip address is different than the eth0 address? Or how do I get the http traffic to reach my server? The nginx logs show not access.

I am getting connection reset with Nginx when the client has a slow connection. This is just a static http website...no back ends. Any ideas how to stop the connection resets on slow connections? I tried playing with the timeout values but haven't found success.

In the log, I see this error:

2015/09/21 17:11:57 [info] 8704#0: *44 client prematurely closed connection while sending response to client

events {
    worker_connections 128;
    use epoll;
}

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

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

    client_header_timeout 12s;
    client_body_timeout 12s;
    send_timeout 10s;
    keepalive_timeout 15s;

#   open_file_cache max=1s inactive=1s;
#open_file_cache max=500 inactive=600s;
#   open_file_cache_valid 300s;
    open_file_cache_errors on;

    expires 24h;
    client_max_body_size 20m;
    connection_pool_size 256;
    client_header_buffer_size 1k;
    large_client_header_buffers 4 2k;
    request_pool_size 4k;

    gzip on;
    gzip_min_length 1100;
    gzip_buffers 4 8k;
    gzip_types text/plain;

    output_buffers 1 32k;
    postpone_output 1460;

    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;


    ignore_invalid_headers on;
    server_tokens off;

    index index.html index.php;

If I make a ext4 filesystem and add about 20% of extra inodes, how would this effect the inode count if later I extend the filesystem? Would the extended filesystem also automatically add an extra 20% inodes? Or would it add a normal amount of inodes? Would the inodes be spread across the filesystem evenly after extending the filesystem?

I am experimenting with Apache and Option Indexes. I mv index.html to no_filename. When I went to www.dunno.com I got a forbidden webpage instead of the directory listing that I was expecting. Why is this? I have mod_autoindex installed and enabled in httpd.conf:

<VirtualHost *:80>
Servername www.dunno.com
DocumentRoot /var/www/web1
<Directory "/var/www/web1">
Options Indexes  
Order allow,deny
Allow from all
</Directory>
</VirtualHost>