This worked for me:
apt install -t jessie-backports openjdk-8-jre-headless ca-certificates-java
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.
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 ...
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 ...
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 ...
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 ...
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/
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 ...
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.
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 ...
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@example.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, ...
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.
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 ...
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 ...
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 ...
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.
"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.
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 ...
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
a2dismod php7.x # disables mod_php.
a2enmod mpm_event # enable event MPM. You could also enable mpm_worker.
kipmi0 is the kernel process used for interfacing with the IPMI controller on your server.
In my experience, if it's stuck using 100% CPU like this, it's because the interface between the server and the IPMI controller stack has locked up, and if you reset the IPMI stack it'll come right. Reasons for it locking up are pretty varied, but a common one I've ...
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 ...
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.
Description=OpenBSD Secure Shell server
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) ...
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:
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:
What you're looking for is bind mounts. See http://man7.org/linux/man-pages/man8/mount.8.html for details.
Here is a step by step guide to moving /home, /opt, /tmp, /usr, and /var to a single separate partition.
I am not responsible for any damage or loss of data caused by following this guide. As always, ensure all important data is backed up ...