78

In my case, the error appears everytime I update my Linux kernel. It disappears when I restart the computer. I am using Arch Linux.


35

This worked for me: apt install -t jessie-backports openjdk-8-jre-headless ca-certificates-java REF: https://unix.stackexchange.com/questions/342403/openjdk-8-jre-headless-depends-ca-certificates-java-but-it-is-not-going-to-be


22

First you need to add jessie-backports repo. echo "deb http://http.debian.net/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list install commands sudo apt-get update sudo apt-get install -t jessie-backports openjdk-8-jre-headless switch to new java sudo /usr/sbin/update-java-alternatives -s java-1.8.0-openjdk-amd64 ...


17

As the error message says lsb_release command is installed but lsb module isn't. Use this command to solve the problem: apt-get install lsb-core I suggest to use lsb_release -a instead of lsb_release. It shows more useful output.


16

Update 2016/08/08: nginx in jessie-backports (version 1.9.10-1~bpo8+3 was built against openssl >= 1.0.2~. Getting ALPN working now if running jessie just requires the packages out of jessie-backports, no need anymore to pull packages out of stretch. -- Original answer: Well, here goes my answer, according to the comments: In my opinion, there aren't ...


15

So you want to backup all your drive without all those nasty mistakes and also filter out all the /proc and other temporary folders? An option is to mount the root folder onto another folder within the filesystem, like this: $ cd /mnt $ mkdir drive $ mount --bind / drive This will give you all the files there are on your drive that are not deemed ...


11

Another method is to install OpenSSL 1.0.2 from jessie-backports and use Ubuntu 16.04 LTS builds from nginx's own repository. That way you're at least using an OpenSSL package built for Jessie. Add to /etc/apt/sources.list: # jessie-backports, from stretch-level but with no dependencies deb http://httpredir.debian.org/debian/ jessie-backports main contrib ...


10

In Linux everything is a file. It's possible via rsync, but there are things to be aware of, that are (at best) difficult to get around. You should think about replication first, especially for databases. Also this is a good idea to set up proxy / load balancer in front of your primary server, so you can easly switch back and forth with your primary and ...


8

I would use the service command because it is more consistent across different distributions. So of the commands you mentioned, the variant I would go for is: service networking restart And I would definitely run it inside a screen session or by other means ensure that it won't fail to complete in case you lost connection with the shell in which you typed ...


8

You are right about backup files being hard links and it is safe to just delete the backup directory. Hard links are just pointers, so if a file have two hard links then the space occupied by this file will only be reclaimed by OS when both links are deleted.


8

It's actually very simple. Your screenshot shows that your disk-2 is not attached to your VM instance. It should look like this And now compare to what you posted. So what you need to do is this: Head to "VM Instances" Click on your Instance In the top click on Edit Scroll down to "Additional disks" section and click Add Select your disk from the drop ...


7

You've booted your system with OVH's custom kernel, which is built to OVH's specifications, and may not be suitable for running software you want to run. Change your dedicated server configuration to boot from the kernel installed on the hard drive provided by your Linux distribution.


7

The trouble with this kind of question is that Q&A is not great for doing remote diagnostics. You have basically chucked a bunch of information at the internet and screamed HALP!. You are trying to force us to go into tech support mode and to hold your hand through a series of reverse Q&A till we can diagnose your problem for you. That is not Q&A ...


7

Sounds like it might be the post-logrotate reload? If so, it's nothing to worry about as its a non-disruptive reload.


7

Use the following command to enable samba: $ sudo systemctl enable smbd.service nmbd.service Synchronizing state for smbd.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d smbd defaults Executing /usr/sbin/update-rc.d smbd enable Synchronizing state for nmbd.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d ...


7

From time to time you may notice that some addresses give a defer error: retry time not reached for any host. 1Ruz3Y-0005TQ-Ek == email@domain.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host So, you need to find out what smtp server is used to manage address.com’s email. To do this — use the host command or more advanced dig, ...


7

"I read that upgrading Debian is not as easy as upgrading a Ubuntu, for example." - avoid to read more from this source simply use stretch word in /etc/apt/sources.list instead of testing, then you'll always have stretch whether it is stable yet or not.


7

It's better to upgrade to php7. Install php7.x-fpm and use the mpm_event (or mpm_worker) module: apt-get install php7.x-fpm # install the php-fpm a2enmod proxy_fcgi a2enconf php7.x-fpm a2dismod php7.x # disables mod_php. a2dismod mpm_prefork a2enmod mpm_event # enable event MPM. You could also enable mpm_worker.


6

Presumably you're installing from the Jessie Debian repositories. Debian Jessie, being the latest stable release of Debian, only serves packages which it deems to be stable. You can read more about this here. Currently, Debian Jessie (stable) ships with Subversion 1.8.10-6+deb8u1 whilst Debian Stretch (testing) ships with Subversion 1.9.2-2. Once the ...


6

This happens to me when the physical machine reboots. My machines run Ubuntu, ranging from 12.04 to 16.04. I resolve it by restarting supervisor as a service. sudo service supervisor stop sudo service supervisor start (This somehow works a lot better than simply using 'restart') Obviously this is not an ideal fix if you depend on Supervisor to start ...


6

Theres a couple of things going on here. If you call a systemd service with an @ in it, its a signal to start an instance rather than main service. Putting @9.5-main is telling it the instance parameters to use. The postgres service file you are seeing is nothing more than a placeholder. There is a directory on the system (its normally somewhere in /run) ...


6

With systemd, there is a new functionality called tmpfiles.d(5) that can be used to create files or directories on boot outside of the .service file. Openvpn and ejabberd are both using this, so that's why the directories in /var/run are still created even if they are not started on boot. The tmpfiles configuration files are stored in /usr/lib/tmpfiles.d/


5

That's due to CloudFlare(CDN provider of IETF) choosing ECDSAP256SHA256 as their signature algorithm. Dnsmasq has implemented ECDSA since 2.69, however it was broken and not fixed until 2.73 which was released in March 2015. Thus, you'll need a newer dnsmasq or patched version to resolve it correctly. From the dnsmasq change log in the 2.73 section: Fix ...


5

As it was already pointed out, Debian 8 Jessie comes with systemd init system by default, which behaves differently than older SysV init system. To get your startup messages back you need to make following changes: Add systemd.show_status=1 to the kernel options list. The easiest way to do so is to add to the /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="...


5

You're missing the first slash after the pipe. |/usr/sbin/rotatelogs


5

You can do this my configuring iptables to 'mark' the messages e.g. iptables -A INPUT -s 192.0.2.0/24 -j LOG --log-prefix='[iptables] ' Which will cause a log message that is prefixed with the text [iptables] Now you can configure your rsyslog to send these messages to a particular log file by adding a suitable entry to it's configuration e.g. :msg,...


5

The default Debian 8 systemd sshd unit is in /lib/systemd/system/ssh.service and is pretty simple. All you would need to do is something like cp /lib/systemd/system/ssh.service /etc/systemd/system/ssh_sftp.service then edit your file to be something like this. [Unit] Description=OpenBSD Secure Shell server After=network.target auditd.service ...


5

Edit /etc/ssh/sshd_config and add root at the of line which is started with AllowGroups. The line should be like this: AllowGroups sudo sshuser root Restart ssh service by following command: service ssh restart


5

I came across this question while researching a similar behaviour so I thought I'd post the answer for the benefit of anyone else who is similarly puzzled. Both config files need to use the same value for the virtual_router_id, as this is how keepalived knows that status messages are for the same virtual router. In the config above, they have different ...


5

Issues I see: Your use of refile From the documentation: If the string begins with "refile:", then the remainder of the string is presumed to specify a file that contains a set of patterns, one per line, and their associated values. The pattern is taken as the start of the line to the first whitespace, and the portion after that whitespace is taken as ...


Only top voted, non community-wiki answers of a minimum length are eligible