On Mi, 29 sep 21, 07:05:37, pe...@easthope.ca wrote:
> From: Greg Wooledge
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> >
> > ls -ld / /var /var/log /var/log/journal
>
> root@joule:/# ls -ld / /var /var/log
> drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
>
On Wed, Sep 29 2021 at 10:35:35 PM, David Wright
wrote:
> On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote:
>> On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
>> > From: Greg Wooledge
>> > Date: Tue, 28 Sep 2021 13:41:05 -0400
>> > > What does it look like?
On Wed, Sep 29, 2021 at 10:35:35PM -0500, David Wright wrote:
> Would it be sensible for the message to actually mention ownership,
> or can it apply to very different circumstances (beyond permissions,
> that is)? I've failed to find any other cause, but see a lot of
> people messing up their
>From my experience gnome-disks automatically chowns / to the executing user
>when creating a filesystem.
But I don't think Peter did that.
I'd rather say it's been caused by some installation script, those are usually
buggy when it comes to file ownership.
Peter, did you install anything via a
On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote:
> On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
> > From: Greg Wooledge
> > Date: Tue, 28 Sep 2021 13:41:05 -0400
> > > What does it look like?
> > >
> > > ls -ld / /var /var/log /var/log/journal
> >
> >
On Wed, 29 Sep 2021 08:01:00 -0700
pe...@easthope.ca wrote:
> root@joule:~# cat /etc/apt/sources.list
> #deb http://mirror.it.ubc.ca/debian/ bullseye main
> deb http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
> deb-src http://mirror.it.ubc.ca/debian/ bullseye main contrib
On Wed, Sep 29, 2021 at 02:35:10PM -0700, pe...@easthope.ca wrote:
> I can't explain why / was owned by me. According to the above it
> happened in the release upgrade two days ago.
No, that's not what that timestamp says. The timestamp in "ls -ld"
is the modification time (mtime) on the
From: Nils
Date: Tue, 28 Sep 2021 17:16:30 +
> Are you sure you still need these journals?
I don't know.
> ... my way to work around it would be to just delete those logs.
Did that and rebooted. System behaviour unchanged.
APPARENT SOLUTION
root@joule:/home/peter# ls -ld / /var
On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
> From: Greg Wooledge
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> >
> > ls -ld / /var /var/log /var/log/journal
>
> root@joule:/# ls -ld / /var /var/log
> drwxr-xr-x 18 peter peter 4096 Sep 27
From: Nils
Date: Tue, 28 Sep 2021 17:16:30 +
> Are you sure you still need these journals?
I don't know.
> ... my way to work around it would be to just delete those logs.
Did that and rebooted. System behaviour is unchanged.
plymouth-label was the last package reported
From: Greg Wooledge
Date: Tue, 28 Sep 2021 13:41:05 -0400
> What does it look like?
>
> ls -ld / /var /var/log /var/log/journal
root@joule:/# ls -ld / /var /var/log
drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
drwxr-xr-x 10 root root
On Tue, Sep 28, 2021 at 06:33:52PM +, Andrew M.A. Cater wrote:
> On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
> > Errors were encountered while processing:
> > systemd
> > libpam-systemd:i386
> > policykit-1
> > policykit-1-gnome
> > plymouth
> > mate-polkit:i386
>
On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
> Hi,
> Here the upgrade was completed except for the problem indicated in the
> following transcript.
>
> This page appears relevant.
> https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
>
>
On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
> Hi,
> Here the upgrade was completed except for the problem indicated in the
> following transcript.
>
> This page appears relevant.
> https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
>
>
Hi,
Are you sure you still need these journals? Might be some nasty bug and my way
to work around it would be to just delete those logs.
I mean, it's kind of a hacky solution but I'm absolutely sure this allows the
upgrade to continue.
Hope it's a viable solution to you,
Tuxifan
Am 28.
Hi,
Here the upgrade was completed except for the problem indicated in the
following transcript.
This page appears relevant.
https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
/var/log/journal exists here.
The command "systemd-tmpfiles --create --prefix
16 matches
Mail list logo
