Typically once netplan configurations are written to /etc/netplan these will be persistent over reboots. Although I have seen issues where the netplan apply doesnt complete as expected when the interface is active. I have found adding --debug to the apply to be useful to see what is really happening
sudo netplan --debug apply
You've run squid with the wrong user, which created files with wrong permissions.
squid: ERROR: Could not read pid file
You need to run with sudo: sudo squid -z.
fatal: ipc::mem::segment::create failed to shm_open(/squid-cf__metadata.shm): 13 permission denied
You need to remove Squid's .shm files from /dev/shm or assign the right permissions.
I have made some checks.
Your private key is in a wrong format.
vsftpd expects it to be a PEM encoded PKCS#8 format private key.
You have it as PEM encoded PKCS#1 format private key. To convert it into the correct format, use the following commands:
openssl pkcs8 -topk8 -nocrypt -in wildcard.key -out wildcard_new.key
mv -f ...
Here are some of the contents of /etc/apparmor.d/usr.sbin.mysqld change your directories respectively.
# Last Modified: Tue Jun 19 17:37:30 2007
Python 2.7.14 (default, Sep 27 2017, 12:15:00)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import base64
Bacula requires that the storage daemon and director must be at the same major version.
Anyway for reference, here a reply from bacula mailing list and bacula release note:
bacula-dir and bacula-sd must always be the same version.
I don't have enough reputation to post comments, so I will try to do my best here to provide some instructions on how to get SSL working on Apache 2.4. What happens when you try to access the website via HTTPS?
To activate SSL on a Apache, first of all, run the following command (I don't see it mentioned in your question):
I also recommend ...
Have you actually measured the performance and found it degraded? You may actually find it's improved, although the difference may not be very large.
The Dell PowerVault MD3860i seems to be an active/passive (also known as asymmetric, or ALUA) style storage system: it has two storage controllers, and each of the disks are considered "owned by" one of the ...
I saw a link to Why is sendmail calling dns_getcanonname for domains of non-recipients in the To: header? in the sidebar and it turned out to have the solution. We needed to add FEATURE(nocanonify', canonify_hosts') in sendmail.mc and that appears to have stopped the additional lookups; the mail that was previously failing to be delivered has now gone ...
Well, the Apache has to serve something when someone accesses it via https://websiteB.com. So it uses the content it has, from websiteA.
This is explained in detail in the Apache documentation, here a quote from it:
Apache automatically discriminates on the basis of the HTTP Host header supplied by the client whenever the most specific match for an IP ...
Yes, compiling a deb package is how you can install a single build to many hosts.
Many ways to distribute and install this package, including maintaining your own private apt repo.
If open source, yes you can create a public PPA and use that as your apt repo. Any distribution welcomes package maintainers.
Not certain, but I you need to do something with arp_filter, and/or maybe some of the other arp flags as well.
arp_filter - BOOLEAN
0 - (default) The kernel can respond to arp requests with addresses from other interfaces. This may seem wrong but it usually makes sense, ...
You are missing the SAN record in the certificate.
Generate certificate again with the following commands:
openssl req -newkey rsa:4096 -nodes -keyout $basename.key -subj "/CN=monitoring.example.com" -out $basename.csr
openssl x509 -req -extfile <(printf "subjectAltName=DNS:monitoring.example.com") -...
Take your host offline and stop accepting mail entirely, I'd say, would solve the problem entirely. You're on the Internet. Having random garbage thrown at your server all day is a part of that.
The useful tool fail2ban, normally used to ban ssh attackers, also has some postfix related jails that you can enable, which will automatically ban certain spammers ...
You may create Azure VMs with anything that speaks the API, including Azure CLI or various automation tools. You may access the VM over any SSH client, including OpenSSH or PuTTY. Azure docs have how to guides for Linux, macOS, or Windows (other platforms are possible).
Whether you use a workstation, developer environment, or bastion host to do this, and on ...
I've been able to fix it by checking existing partitions on the system
root@icinga2:/etc/icinga2/conf.d# sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
NAME FSTYPE SIZE MOUNTPOINT LABEL
loop0 squashfs 91M /snap/core/6350
loop1 squashfs 89.4M /snap/core/6818
└─sda2 ext4 40G /
If you don't have a passphrase, you can just as well not bother to encrypt your data in the first place, because anyone who can get access to the server with the data will also be able to use the key.
If you for some reason want to pretend to be secure while not actually being it, you can use the argument --passphrase='' to gpg. But you shouldn't do that.
I came to the answer with the help of the following:
The error/access logs of nginx - @wombie
This stack overflow answer which explains the difference between the root and alias very well
official nginx documentation
I was able to achieve my goal by updating the last location block to serve the Angular application from the /app/ route and directed nginx ...
The answer is incredibly simple.
I forgot I left a permament redirect rule in my apache2.conf - this caused the infinite loop. Deleting that line from apache config fixed my problem. Thanks to everyone involved.
If you want to run any application on Linux in a limited resource environment you should make sure that you understand how memory on Linux actually works. Sounds harsh, but it really is the only way to understand what is happening behind the curtain.
If the OOM killer gets triggered at all it means you ran out of memory in the first place. If that happens ...
I was spinning my wheels on this one for a bit but make sure you have a complete private key file. Turned out I had a couple of lines missing from mine.
The command to check your private key is:
openssl rsa -in /etc/httpd/certs/server.key -check
replace /etc/httpd/certs/server.key with the full path to your server's private key and if it's all good you'...
This approach is not recommended at all... It is still valid answer even after the years...
This is because of waiting for the domain name resolving. Active directory is DNS based service and it is used for discovery of the nodes with proper roles... There is not direct relation between Active Directory, DHCP and other AD roles.
use case for ...
I believe the problem is the presence of gmail.com and companydomain.com in mydestination.
In the mailx command the last argument is the recipient address. As those domains are listed in mydestination what happens is that you're sending the mails to your local server, which fails because those users don't exist locally.
Let's break down these requirements a bit.
First, in order to require public keys and password to provide, you need to modify your /etc/ssh/sshd_config by adding this line:
This way, everyone must have a public key, and must be able to provide their password upon login.
To make ...
I suppose you'd have to find a statically linked program (like busybox if you have busybox-static installed or something) with which you could move it back, or else boot from a rescue disk, like an ubuntu live CD or someting, and do it from there.
Upgrading to Ubuntu Kernel 4.15.0-48 fixed this issue.
Afterwards I found the changelog entry that had the solution here, where it says:
kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in ext4_check_descriptors()
I had a similar issue, and per this answer, the solution was removing the 'any' user.
It seems that MySQL sees a difference between a user connecting via localhost and 127.0.0.1, which is part of the issue if I understand it correctly.
FTP passive mode needs connections to ephemeral ports on the FTP server since the actual data transfer is done over different TCP connections.
You could try with some FTP helper (ip_conntrack_ftp) which inspects the FTP control channel and extracts the ports to only open these connections. But this will usually not work with implicit FTPS (port 990) since ...
I have found a solution to the problem.
It appears that Chrome in headless mode needs specific fonts installed for non-Latin characters. While this can be solved of course by installing a multitude of fonts, it would be a headache to install fonts for websites that support a lot of languages.
Luckily there are modern font packs available that cover nearly ...
Problem: Above mentioned instance outbound internet connectivity is restricted.
Your local machine/laptop/desktop ---> Internet ---> ssh into your GCP your. ( In bound for the GCP machine.)
Your firewall at GCP and Iptable in GCP machine must be allowing incoming connections to the GCP machine.
GCP machine ---> git clone ---> ...
It sounds like someone has messed with the (virtual) tty settings that are best left alone in the 21st century, unless of course you're actually using an antique physical terminal from a computer museum...
You should be able to get the tty on the remote server into a usable state with the command (run on the remote server, immediately after logging in):
The config you have provided is providing a PTR record for 126.96.36.199.168.192.in-addr.arpa. You either want to modify the zone statement (remove the 6.1 at the beginning), or the relative name in the zone file (try @ instead of 6.1).
Decide if you will be managing a local repo of updates. Which would allow for more control of both when updates happen and what gets Internet access.
You probably want to use GCP's mirror, us-central1.gce.archive.ubuntu.com (replace us-central1 with your region).
Configure firewall to allow egress from the downloading systems. IPs and not names, but a ...
if your host behind NAT, then blocking ip in INPUT will not work. you have to choose FORWARD instead.
for example, I'm using Asterisk in Docker, So blocking INPUT will not work. I made jail role like this:
enabled = true
filter = asterisk
action = iptables-allports[chain=FORWARD, name=asterisk, protocol=all, blocktype=DROP]
logpath = /home/...
This is a new feature that is currently in preview and only available for VMs running in Azure.
Also note, since the feature is preview it is not to be used for production workloads as it is still being actively developed.
first run sudo apt autoremove and see it will help another issue I can see is sudo: unable to resolve host ip-XX-XXX-XX-XX: Resource temporarily unavailable try to fix these and retry. I think some stale config or resources forcing mysql changes beware if it is production and check what it is removing before accepting changes.
I've had this kind of troubles a few times on different zimbra version and it was always related to syslog.
Please check which syslog version is running (or if it's running at all) and eventually try to switch between syslog-ng or rsyslog depending on your OS version and release.
Details of the naming scheme are in the source code: udev/udev-builtin-net_id.c. Some common schemes are PCI physical, PCI hotplug, and onboard. Your enp interface suggests physical.
Stripping out exotic and irrelevant bits from the comments leaves these rules:
* Two character prefixes based on the type of interface:
* en — Ethernet
* Type of ...
Local originated packets don't pass through nat/PREROUTING chain. To make request to 127.0.0.1:5000 success you should add same DNAT rule into nat/OUTPUT chain:
iptables -t nat -A OUTPUT \
-d 127.0.0.1 -p tcp --dport 5000 \
-j DNAT --to 10.30.8.191:443
It also requires the changing of net.ipv4.conf.lo.route_localnet variable:
sysclt -w net....
There's two steps to changing the grub configuration in Ubuntu:
The first is to edit /etc/default/grub(instead of /boot/grub/grub.cfg); the second is to run update-grub to make the changes. You don't want to edit /boot/grub/grub.cfg directly in case you make mistakes. update-grub will do everything you need to generate the correct kernel arguments and ...
Investigating initrd and comparing with a server that worked, two obvious differences appeared through upgrading Ubuntu:
This is an old-times relict of renaming network interfaces in Ubuntu. It has to be deleted.
This was set-up shadowing /lib/udev/rules.d/80-net-setup-link....
For some reason this solved it (not entirely sure why now cause i'm sure i had done this. maybe a restart helped it:
sudo fdisk /dev/sda
*defaults. Press enter all the way through*
That created sda1 under sda, so i followed with
sudo mkfs.ext4 -F /dev/sda1