Rainer Dorsch:
But to my surprise even on a fresh install of the jessie image
/etc/machine-id is already broken:
root@scw-790923:~# cat /etc/machine-id
9d1b906dd5ea40359e2071d29c12aabe
71f
root@scw-790923:~#
But it seems the systemd version in jessie seems to be more tolerant
against
On Saturday 10 December 2016 16:35:50 Michael Biebl wrote:
> Am 10.12.2016 um 13:38 schrieb Rainer Dorsch:
>
> > root@scw:~# cat /etc/machine-id 26da2c29c6a545fd9af95d29ca9b5a5a 6df
> > root@scw:~#
> >
> > Not sure how the 6df ended in /etc/machine-id, but after removing
> > that things seem to
Am 10.12.2016 um 13:38 schrieb Rainer Dorsch:
> root@scw:~# cat /etc/machine-id 26da2c29c6a545fd9af95d29ca9b5a5a 6df
> root@scw:~#
>
> Not sure how the 6df ended in /etc/machine-id, but after removing
> that things seem to have settled:
> I upgraded from a fresh jessie installation (image from
On Friday 09 December 2016 22:16:42 Jonathan de Boyne Pollard wrote:
> Rainer Dorsch:
> > [ 20.704584] systemd[1]: Initializing machine ID from D-Bus machine ID.
> >
> > [ 20.916182] systemd-journald[2136]: Failed to open runtime journal:
> > Invalid argument
> >
>
> You need to look at at least
On Friday 09 December 2016 22:43:29 Michael Biebl wrote:
> Am 04.12.2016 um 16:18 schrieb Rainer Dorsch:
> > The system is hosted at scaleway, i.e. it is not a Debian kernel, which
> > is running.
>
> What kernel is that?
I wrote before it is a hosted machine @scaleway. They claim a KVM setup,
Rainer Dorsch:
[ 20.704584] systemd[1]: Initializing machine ID from D-Bus machine ID.
[ 20.916182] systemd-journald[2136]: Failed to open runtime journal:
Invalid argument
You need to look at at least two files, /var/lib/dbus/machine-id and
/etc/machine-id . They should contain only a
Am 04.12.2016 um 16:18 schrieb Rainer Dorsch:
> The system is hosted at scaleway, i.e. it is not a Debian kernel, which
> is running.
What kernel is that? Can you check if all requirements as outlined in
/usr/share/doc/systemd/README.gz are fulfilled?
--
Why is it that all of the instruments
Hi Jonathan,
many thanks for your response.
On Tuesday 06 December 2016 00:04:04 Jonathan de Boyne Pollard wrote:
> Rainer Dorsch:
>
> > I think this then results in errors during an apt-get upgrade:
>
> It does indeed. It is systemd-journald that resides at the server end
> of /dev/log on
Rainer Dorsch:
> I think this then results in errors during an apt-get upgrade:
It does indeed. It is systemd-journald that resides at the server end
of /dev/log on a systemd operating system. Quite a lot of other stuff
will break for you if you don't have a running systemd-journald,
hey rainer
yeah i wouldn't go with sid, it's fun to play around with yet not for a server
install.
sysinit vs systemd is up to you. i haven't had a problem with systemd, it's
just another thing that you have to read about to get the hang of it.
you will have to forgive me for not reading all
On Mon, Dec 05, 2016 at 07:07:45PM +0100, Rainer Dorsch wrote:
> > take a look at this forum for all of the discussions on sysinit vs systemd.
> >
>
> Hmm...do you suggest to go to sysvinit? Hmmm...
On Mon, Dec 05, 2016 at 07:07:45PM +0100, Rainer Dorsch wrote:
> Jessie is also using systemd (?).
Yes, jessie is the first release to use systemd by default. (It was
available in wheezy as a "technology preview" only.) You're also
allowed to run jessie using sysvinit, but this is not the
Hi emetib,
On Monday 05 December 2016 08:47:55 emetib wrote:
> quick question for you.
>
> if you wanted to have stretch, why did you install jessie and then upgrade
> instead of just installing stretch?
>
> https://www.debian.org/devel/debian-installer/
scaleway offered jessie and sid as
On Mon, Dec 05, 2016 at 08:47:55AM -0800, emetib wrote:
> if you wanted to have stretch, why did you install jessie and then upgrade
> instead of just installing stretch?
Because until the stretch installer is ready for prime time, that is
the safest way to get stretch.
>
quick question for you.
if you wanted to have stretch, why did you install jessie and then upgrade
instead of just installing stretch?
https://www.debian.org/devel/debian-installer/
i've personally found it's better to just install the testing image right away
instead of doing a dist-upgrade.
On Sunday 04 December 2016 16:47:48 emetib wrote:
> On Sunday, December 4, 2016 at 5:10:04 PM UTC-6, deloptes wrote:
>
> > /dev/log
> ?
>
> try and take a look at 'journalctl -b 0'
> that might give some info or you can look at '/var/log/messages' and/or
> '/var/log/syslog'. those last two
On Sunday, December 4, 2016 at 5:10:04 PM UTC-6, deloptes wrote:
> /dev/log
?
try and take a look at 'journalctl -b 0'
that might give some info or you can look at '/var/log/messages' and/or
'/var/log/syslog'. those last two kind of depends on how your systemd is set
up.
take care
em
Rainer Dorsch wrote:
> The system is hosted at scaleway, i.e. it is not a Debian kernel, which is
> running.
would you mind if we know what is the kernel and the systemd version?
I don't think it is a kernel issue though.
You see your systemd-journal fails to start so you don't provide /dev/log
Hi,
on a fresh jessie install, upgraded to stretch I get
root@scw:~# systemctl status systemd-journald.service
● systemd-journald.service - Journal Service
Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor
preset: enabled)
Active: failed (Result: exit-code)
19 matches
Mail list logo
