upgrade from Magento 2.2.6 to 2.3.1 CLI command error

When upgrading from 2.2.6 to 2.3.1. I am following the command line upgrade as explained here. All, was well and the commands ran just as they should have until I ran the following command.

php bin/magento setup:upgrade 

Upon running this command I am seeing the following error. Please advise me on how can I go about solving this error.

Error

How to use the move command on Windows, to move all files inside a folder when using quotation symbol?

I currently have these two folders:

  • oldFolder

    • news
      • info.json
  • newFolder

    • news
      • info.json

I want to use the move command, to move all files in the oldFolder to the new Folder. I have tried this: move "G:\Program Files (x86)\oldFolder\" "G:\Program Files (x86)\newFolder\", but this actually move the entire oldFolder inside newFolder.

So, I have tried this: move "G:\Program Files (x86)\oldFolder\*.*" "G:\Program Files (x86)\newFolder\", but this gave me this error: The syntax of the file, directory, or volume name is incorrect.

An idea?

Regards

OpenVPN – Linux Route add command failed

I’m using OpenVPN in my environment and I upgraded my testing server just the other day and after the update (Using Debian and apt), my OpenVPN Configuration no longer works.

I receive the error “linux route add command failed”, the reason appears to be in relation to the RTNETLINK: File Exists. I have searched every article on the web trying all the solutions, however none of them have been successful.

Below are my configuration files:

server.conf

################################################# # Sample OpenVPN 2.0 config file for            # # multi-client server.                          # #                                               # # This file is for the server side              # # of a many-clients <-> one-server              # # OpenVPN configuration.                        # #                                               # # OpenVPN also supports                         # # single-machine <-> single-machine             # # configurations (See the Examples page         # # on the web site for more info).               # #                                               # # This config should work on Windows            # # or Linux/BSD systems.  Remember on            # # Windows to quote pathnames and use            # # double backslashes, e.g.:                     # # "C:\Program Files\OpenVPN\config\foo.key" # #                                               # # Comments are preceded with '#' or ';'         # #################################################  # Which local IP address should OpenVPN # listen on? (optional) ;local a.b.c.d  # Which TCP/UDP port should OpenVPN listen on? # If you want to run multiple OpenVPN instances # on the same machine, use a different port # number for each one.  You will need to # open up this port on your firewall. port 1194  # TCP or UDP server? ;proto tcp proto udp  # "dev tun" will create a routed IP tunnel, # "dev tap" will create an ethernet tunnel. # Use "dev tap0" if you are ethernet bridging # and have precreated a tap0 virtual interface # and bridged it with your ethernet interface. # If you want to control access policies # over the VPN, you must create firewall # rules for the the TUN/TAP interface. # On non-Windows systems, you can give # an explicit unit number, such as tun0. # On Windows, use "dev-node" for this. # On most systems, the VPN will not function # unless you partially or fully disable # the firewall for the TUN/TAP interface. ;dev tap dev tun  # Windows needs the TAP-Win32 adapter name # from the Network Connections panel if you # have more than one.  On XP SP2 or higher, # you may need to selectively disable the # Windows firewall for the TAP adapter. # Non-Windows systems usually don't need this. ;dev-node MyTap  # SSL/TLS root certificate (ca), certificate # (cert), and private key (key).  Each client # and the server must have their own cert and # key file.  The server and all clients will # use the same ca file. # # See the "easy-rsa" directory for a series # of scripts for generating RSA certificates # and private keys.  Remember to use # a unique Common Name for the server # and each of the client certificates. # # Any X509 key management system can be used. # OpenVPN can also use a PKCS #12 formatted key file # (see "pkcs12" directive in man page). ca /etc/openvpn/klackit/ca.crt cert /etc/openvpn/klackit/vpn.klackit.com.crt key /etc/openvpn/klackit/vpn.klackit.com.key  # This file should be kept secret  # Diffie hellman parameters. # Generate your own with: #   openssl dhparam -out dh2048.pem 2048 dh /etc/openvpn/klackit/dh.pem  # Network topology # Should be subnet (addressing via IP) # unless Windows clients v2.0.9 and lower have to # be supported (then net30, i.e. a /30 per client) # Defaults to net30 (not recommended) ;topology subnet  # Configure server mode and supply a VPN subnet # for OpenVPN to draw client addresses from. # The server will take 10.8.0.1 for itself, # the rest will be made available to clients. # Each client will be able to reach the server # on 10.8.0.1. Comment this line out if you are # ethernet bridging. See the man page for more info. server 10.8.0.0 255.255.255.0  # Maintain a record of client <-> virtual IP address # associations in this file.  If OpenVPN goes down or # is restarted, reconnecting clients can be assigned # the same virtual IP address from the pool that was # previously assigned. ifconfig-pool-persist ipp.txt  # Configure server mode for ethernet bridging. # You must first use your OS's bridging capability # to bridge the TAP interface with the ethernet # NIC interface.  Then you must manually set the # IP/netmask on the bridge interface, here we # assume 10.8.0.4/255.255.255.0.  Finally we # must set aside an IP range in this subnet # (start=10.8.0.50 end=10.8.0.100) to allocate # to connecting clients.  Leave this line commented # out unless you are ethernet bridging. ;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100  # Configure server mode for ethernet bridging # using a DHCP-proxy, where clients talk # to the OpenVPN server-side DHCP server # to receive their IP address allocation # and DNS server addresses.  You must first use # your OS's bridging capability to bridge the TAP # interface with the ethernet NIC interface. # Note: this mode only works on clients (such as # Windows), where the client-side TAP adapter is # bound to a DHCP client. ;server-bridge  # Push routes to the client to allow it # to reach other private subnets behind # the server.  Remember that these # private subnets will also need # to know to route the OpenVPN client # address pool (10.8.0.0/255.255.255.0) # back to the OpenVPN server. ;push "route 192.168.10.0 255.255.255.0" ;push "route 192.168.20.0 255.255.255.0"  # To assign specific IP addresses to specific # clients or if a connecting client has a private # subnet behind it that should also have VPN access, # use the subdirectory "ccd" for client-specific # configuration files (see man page for more info).  # EXAMPLE: Suppose the client # having the certificate common name "Thelonious" # also has a small subnet behind his connecting # machine, such as 192.168.40.128/255.255.255.248. # First, uncomment out these lines: client-config-dir /etc/openvpn/ccd ;route 192.168.40.128 255.255.255.248   # Then create a file ccd/Thelonious with this line: #   iroute 192.168.40.128 255.255.255.248 # This will allow Thelonious' private subnet to # access the VPN.  This example will only work # if you are routing, not bridging, i.e. you are # using "dev tun" and "server" directives.  # EXAMPLE: Suppose you want to give # Thelonious a fixed VPN IP address of 10.9.0.1. # First uncomment out these lines: ;client-config-dir ccd ;route 10.9.0.0 255.255.255.252 # Then add this line to ccd/Thelonious: #   ifconfig-push 10.9.0.1 10.9.0.2  # Suppose that you want to enable different # firewall access policies for different groups # of clients.  There are two methods: # (1) Run multiple OpenVPN daemons, one for each #     group, and firewall the TUN/TAP interface #     for each group/daemon appropriately. # (2) (Advanced) Create a script to dynamically #     modify the firewall in response to access #     from different clients.  See man #     page for more info on learn-address script. ;learn-address ./script  # If enabled, this directive will configure # all clients to redirect their default # network gateway through the VPN, causing # all IP traffic such as web browsing and # and DNS lookups to go through the VPN # (The OpenVPN server machine may need to NAT # or bridge the TUN/TAP interface to the internet # in order for this to work properly). push "redirect-gateway def1 bypass-dhcp"  # Certain Windows-specific network settings # can be pushed to clients, such as DNS # or WINS server addresses.  CAVEAT: # http://openvpn.net/faq.html#dhcpcaveats # The addresses below refer to the public # DNS servers provided by opendns.com. push "dhcp-option DNS 208.67.222.222" push "dhcp-option DNS 208.67.220.220"  # Uncomment this directive to allow different # clients to be able to "see" each other. # By default, clients will only see the server. # To force clients to only see the server, you # will also need to appropriately firewall the # server's TUN/TAP interface. ;client-to-client  # Uncomment this directive if multiple clients # might connect with the same certificate/key # files or common names.  This is recommended # only for testing purposes.  For production use, # each client should have its own certificate/key # pair. # # IF YOU HAVE NOT GENERATED INDIVIDUAL # CERTIFICATE/KEY PAIRS FOR EACH CLIENT, # EACH HAVING ITS OWN UNIQUE "COMMON NAME", # UNCOMMENT THIS LINE OUT. ;duplicate-cn  # The keepalive directive causes ping-like # messages to be sent back and forth over # the link so that each side knows when # the other side has gone down. # Ping every 10 seconds, assume that remote # peer is down if no ping received during # a 120 second time period. keepalive 10 120  # For extra security beyond that provided # by SSL/TLS, create an "HMAC firewall" # to help block DoS attacks and UDP port flooding. # # Generate with: #   openvpn --genkey --secret ta.key # # The server and each client must have # a copy of this key. # The second parameter should be '0' # on the server and '1' on the clients. tls-auth /etc/openvpn/klackit/ta.key 0 # This file is secret key-direction 0  # Select a cryptographic cipher. # This config item must be copied to # the client config file as well. # Note that 2.4 client/server will automatically # negotiate AES-256-GCM in TLS mode. # See also the ncp-cipher option in the manpage cipher AES-256-CBC auth SHA256  # Enable compression on the VPN link and push the # option to the client (2.4+ only, for earlier # versions see below) ;compress lz4-v2 ;push "compress lz4-v2"  # For compression compatible with older clients use comp-lzo # If you enable it here, you must also # enable it in the client config file. ;comp-lzo  # The maximum number of concurrently connected # clients we want to allow. ;max-clients 100  # It's a good idea to reduce the OpenVPN # daemon's privileges after initialization. # # You can uncomment this out on # non-Windows systems. user nobody group nogroup  # The persist options will try to avoid # accessing certain resources on restart # that may no longer be accessible because # of the privilege downgrade. persist-key persist-tun  # Output a short status file showing # current connections, truncated # and rewritten every minute. status openvpn-status.log  # By default, log messages will go to the syslog (or # on Windows, if running as a service, they will go to # the "\Program Files\OpenVPN\log" directory). # Use log or log-append to override this default. # "log" will truncate the log file on OpenVPN startup, # while "log-append" will append to it.  Use one # or the other (but not both). ;log         openvpn.log ;log-append  openvpn.log  # Set the appropriate level of log # file verbosity. # # 0 is silent, except for fatal errors # 4 is reasonable for general usage # 5 and 6 can help to debug connection problems # 9 is extremely verbose verb 3  # Silence repeating messages.  At most 20 # sequential messages of the same message # category will be output to the log. ;mute 20  # Notify the client that when the server restarts so it # can automatically reconnect. explicit-exit-notify 1  crl-verify crl.pem 

client.conf (I left the cert details out)

############################################## # Sample client-side OpenVPN 2.0 config file # # for connecting to multi-client server.     # #                                            # # This configuration can be used by multiple # # clients, however each client should have   # # its own cert and key files.                # #                                            # # On Windows, you might want to rename this  # # file so it has a .ovpn extension           # ##############################################  # Specify that we are a client and that we # will be pulling certain config file directives # from the server. client  # Use the same setting as you are using on # the server. # On most systems, the VPN will not function # unless you partially or fully disable # the firewall for the TUN/TAP interface. ;dev tap dev tun  # Windows needs the TAP-Win32 adapter name # from the Network Connections panel # if you have more than one.  On XP SP2, # you may need to disable the firewall # for the TAP adapter. ;dev-node MyTap  # Are we connecting to a TCP or # UDP server?  Use the same setting as # on the server. ;proto tcp proto udp  # The hostname/IP and port of the server. # You can have multiple remote entries # to load balance between the servers. remote 10.240.0.23 1194 ;remote my-server-2 1194  # Choose a random host from the remote # list for load-balancing.  Otherwise # try hosts in the order specified. ;remote-random  # Keep trying indefinitely to resolve the # host name of the OpenVPN server.  Very useful # on machines which are not permanently connected # to the internet such as laptops. resolv-retry infinite  # Most clients don't need to bind to # a specific local port number. nobind  # Downgrade privileges after initialization (non-Windows only) user nobody group nogroup  # Try to preserve some state across restarts. persist-key persist-tun  # If you are connecting through an # HTTP proxy to reach the actual OpenVPN # server, put the proxy server/IP and # port number here.  See the man page # if your proxy server requires # authentication. ;http-proxy-retry # retry on connection failures ;http-proxy [proxy server] [proxy port #]  # Wireless networks often produce a lot # of duplicate packets.  Set this flag # to silence duplicate packet warnings. ;mute-replay-warnings  # SSL/TLS parms. # See the server config file for more # description.  It's best to use # a separate .crt/.key file pair # for each client.  A single ca # file can be used for all clients. #ca ca.crt #cert client.crt #key client.key  # Verify server certificate by checking that the # certicate has the correct key usage set. # This is an important precaution to protect against # a potential attack discussed here: #  http://openvpn.net/howto.html#mitm # # To use this feature, you will need to generate # your server certificates with the keyUsage set to #   digitalSignature, keyEncipherment # and the extendedKeyUsage to #   serverAuth # EasyRSA can do this for you. remote-cert-tls server  # If a tls-auth key is used on the server # then every client must also have the key. tls-auth ta.key 1 key-direction 1  # Select a cryptographic cipher. # If the cipher option is used on the server # then you must also specify it here. # Note that 2.4 client/server will automatically # negotiate AES-256-GCM in TLS mode. # See also the ncp-cipher option in the manpage cipher AES-256-CBC auth SHA256  # Enable compression on the VPN link. # Don't enable this unless it is also # enabled in the server config file. #comp-lzo  # Set log file verbosity. verb 3  # Silence repeating messages ;mute 20  #script-security 2 #up /etc/openvpn/update-resolv-conf #down /etc/openvpn/update-resolv-conf 

I wish to emphasise that this configuration has not changed since I created it months ago and has been working perfectly fine ever since. I have not upgraded the VPN Server, only the testing server and afterwards, it failed.

Below is a picture of the routes before I attempt to start the VPN Connection

route -rt results

Please forgive my masking of the IP Addresses, do note they are the same.

Below is the error from OpenVPN when I attempt to connect.

OpenVPN error results

If anyone has any information in regards to this, it would be greatly appreciated.

Ubuntu server 18.04 command to delete contents of sub-folders ever 6 months

I have a folder that contains many different sub folders and files in the sub folder

home/customer/main/a home/customer/main/b (each letter a through z is a random variable folder name example: house,media, etc ) i want to be able to clean the files in the folder after one of those files have reached 6 months of age but leave the folder system intact. and have this automatically run once a month

GRUB installation – command line instead of menu

I am just trying to install Arch Linux. To do this, I followed the instructions in the tutorial except for the GRUB installation. This is how the installation looks like according to the tutorial:

pacman -S grub-bios os-prober freetype2 ttf-dejavu os-prober  #I have Windows grub-mkconfig -o /boot/grub/grub.cfg grub-install /dev/sda 

The grub-mkconfig -o /boot/grub/grub.cfg line didn’t want to be executed ( I was getting the error that “/boot/grub/grub.cfg” is not such file or directory ) so I skipped it. Then I went on following the tutorial, but when I finally rebooted the computer I found GRUB command line instead of menu.

Anyone can help me?