i915 0000:00:02.0: Device initialization failed (-12)
After upgrading the kernel to a newer kernel, OS won’t boot with a stacked message
After upgrading the kernel to a newer kernel, OS won’t boot with a stacked message
When you need to do fast fix for some module without to push it use option replace in go.mod For example, i want to check – my application will be work with changes in branch ? and add replace for that repo
By using Docker, Docker-registry, Ansible and own servers
First, add your user to group docker And restart Docker daemon If this not help, change acl for file access:
Simple manual for deleting all archives in Vault
Install all downloaded deb’s Reboot server/PC by command reboot After startup check the kernel version^ Test Wireguard on server Add repository for ubuntu 18.04 Make some changes to Firewall on server Simple script for generating key pairs and base cofigs for server and client Or download here: Put wg0.server as /etc/wireguard/wg0.conf on Server side and wg0.client on Client side in the same place Startup interface on machines For Android clients you can use config file as QR code
Connect to Mikrotik via SSH and start writing text below Set global VARs Make server and client CRT Create pool, profile, interface, firewall Goto menu Files in Mikrotik admin panel and download ca.crt + client.crt + client.key Then make file SomeName.ovpn with content: Put your key and crt and change host:port vars and file auth.cfg with this two files you can start client
Just add following lines to vhost.conf SSLEngine on SSLProtocol TLSv1.2 TLSv1.1 SSLProxyProtocol TLSv1.2 TLSv1.1 SSLHonorCipherOrder on SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:ECDHE-RSA-AES128-SHA:DHE-RSA-AES128-GCM-SHA256:AES256+EDH:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA25
Забавна программа якщо треба перенести якийсь текст на телефон, а під рукою нема ніяких штатних месенджерів echo "text_string" | qrencode -t UTF8 -o – █████████████████████████████ █████████████████████████████ ████ ▄▄▄▄▄ █▀▄█▀▄█ ▄▄▄▄▄ ████ ████ █ █ █▀▄█▀██ █ █ ████ ████ █▄▄▄█ █▀▀ ▄ █ █▄▄▄█ ████ ████▄▄▄▄▄▄▄█▄█ ▀ █▄▄▄▄▄▄▄████ ████ ▄▄▄ ▀▄▄ ██ ▄█▄▀ ▀▄▀████ █████▀▄▄▄█▄█▀█▀▄█▀▄▀█ ▄█████ ████▄▄▄▄█▄▄▄ ▀▄▄▀█ █▀▄█ ▀████ ████ ▄▄▄▄▄ █▄ ▄█▄ ██▀▀ ▄█████ ████ █ █ █ ▄ █▀▀ ▄▀ ▀▄▄████ ████ █▄▄▄█ █ ▄▀▀▄▀▄█▀▀ ██████ ████▄▄▄▄▄▄▄█▄▄█▄▄█▄█▄▄▄▄█████…
This is probably an issue with D-Bus and systemd. If the dbus service is restarted for some reason, you will also need to restart systemd-logind restart systemd-logind service: systemctl restart systemd-logindsystemctl restart systemd-logind I had this same issue on CentOS 7, because the messagebus was restarted (which is how the D-Bus service is called on CentOS).
Video on youtube Docs: http://helix.apache.org/0.7.1-docs/Tutorial.html Zookeeper: http://zookeeper.apache.org/doc/r3.3.3/zookeeperStarted.html