Re: latest upgrade to systemd 252.12-1 error about invalid attributes /var/log/journal and slow sshd connections

On Sat, Jul 15, 2023 at 1:09 PM David Mehler wrote: > > [...] > > "2. "I noticed that when I change UsePAM yes to UsePAM no then this > issue is resolved." > > BINGO! I flipped that UsePAM setting to no and the problem has gone away. If you need a datapoint about UsePAM... I've been setting it

Re: latest upgrade to systemd 252.12-1 error about invalid attributes /var/log/journal and slow sshd connections

On Sat 15 Jul 2023, at 17:52, David Mehler wrote: [...] > Regarding the original issue of the systemd upgrade and the invalid > attributes [...] here is the output that I've got: > [...] > Cannot set file attributes for '/var/log/journal', maybe due to > incompatibility in speci

Re: latest upgrade to systemd 252.12-1 error about invalid attributes /var/log/journal and slow sshd connections

etc/systemd/networkd.conf ... Installing new version of config file /etc/systemd/pstore.conf ... Installing new version of config file /etc/systemd/sleep.conf ... Installing new version of config file /etc/systemd/system.conf ... Installing new version of config file /etc/systemd/user.conf ... Cannot s

Re: latest upgrade to systemd 252.12-1 error about invalid attributes /var/log/journal and slow sshd connections

On Sat 15 Jul 2023, at 13:09, Gareth Evans wrote: > > 2. "I noticed that when I change UsePAM yes to UsePAM no then this > issue is resolved." > > There may be security (or other) issues with (2). See, for example:

Re: latest upgrade to systemd 252.12-1 error about invalid attributes /var/log/journal and slow sshd connections

hat seems relevant for a few lines before/after the wait. To view the systemd journal, see man journalctl You may however like to install rsyslog to get /var/log/syslog back. Not sure if it's retro-active though. HTH Gareth

Re: latest upgrade to systemd 252.12-1 error about invalid attributes /var/log/journal and slow sshd connections

> On 12 Jul 2023, at 15:12, David Mehler wrote: > > Hello, > > I'm running Debian 12 on a vps. I just upgraded it and am now > apparently running the latest systemd version 252.12-1. I saw an error > about invalid attributes on /var/log/journal then it said ignorin

latest upgrade to systemd 252.12-1 error about invalid attributes /var/log/journal and slow sshd connections

Hello, I'm running Debian 12 on a vps. I just upgraded it and am now apparently running the latest systemd version 252.12-1. I saw an error about invalid attributes on /var/log/journal then it said ignoring. I've seen others with this error but only in reference as far as I can tell to the btrfs

Re: /var/log/journal/ size question

* 2022-04-21 10:08:04+0800, Henrik S. wrote: > The dir /var/log/journal/ on my debian host increases quite quickly. > why this happens? Do you know how to suppress it? User can control log sizes with /etc/systemd/journald.conf file but systemd manages them automatically quite intelligently

Re: /var/log/journal/ size question

On Thu, Apr 21 2022 at 10:08:04 AM, Henrik S wrote: > The dir /var/log/journal/ on my debian host increases quite quickly. > why this happens? Do you know how to suppress it? > That's the storage for the logs maintained by journald. You can manage these logs by editing /et

/var/log/journal/ size question

The dir /var/log/journal/ on my debian host increases quite quickly. why this happens? Do you know how to suppress it? Thanks.

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

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

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

t;> > > 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 40

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

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

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

: 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 / > > > dr

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

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? > > > > > &g

Re: Upgrading buster => bullseye. Canonicalization of /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

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal. APPEARS SOLVED.

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

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal. APPEARS SOLVED.

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

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

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 > drwx

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

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

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

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 r

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

post-inst scripts again, and produce the same errors again. 2) With systemd in a possibly messed-up state, rebooting is risky. I would focus on fixing the underlying issue, starting with looking at the things that it complained about. ls -ld / /var /var/log /var/log/journal

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

html > > /var/log/journal exists here. > > The command "systemd-tmpfiles --create --prefix /var/log/journal" gives > complaints similar to those in the transcript. > > Likely the solution is obvious once the problem is understood. What is > unsafe about t

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

html > > /var/log/journal exists here. What does it look like? ls -ld / /var /var/log /var/log/journal > The command "systemd-tmpfiles --create --prefix /var/log/journal" gives > complaints similar to those in the transcript. > > Likely the solution is obvious onc

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

. September 2021 17:55:59 MESZ schrieb pe...@easthope.ca: >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

Upgrading buster => bullseye. Canonicalization of /var/log/journal.

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 /va

Re: journal upgrade

stions > auxquelles j'ai répondu un peu au pif et je > soupçonne que les problèmes viennent de là. > Et évidemment je n'ai rien noté. > Est-ce qu'il existe un journal de cette procédure > ou une trace quelconque de mes réponses > à ces questions? > > Eric Elguero Tout à fai

journal upgrade

je n'ai rien noté. Est-ce qu'il existe un journal de cette procédure ou une trace quelconque de mes réponses à ces questions? Eric Elguero

Re: enable journal

On 2021-01-03 15:52, Felix Miata wrote: David Christensen composed on 2021-01-03 15:41 (UTC-0800): Again, not of much use (?). How do I get information out of the systemd journal? sudo mkdir /var/log/journal or turn it on in /etc/systemd/journald.conf. STFW 'systemd journal

Re: enable persistent journal (was: Nvidia Optimus, Debian 10...)

David Christensen composed on 2021-01-03 15:41 (UTC-0800): > Again, not of much use (?). How do I get information out of the systemd > journal? sudo mkdir /var/log/journal or turn it on in /etc/systemd/journald.conf. -- Evolution as taught in public schools, like re

Re: enable journal (was: Nvidia Optimus, Debian 10...)

David Christensen composed on 2021-01-03 15:41 (UTC-0800): > Again, not of much use (?). How do I get information out of the systemd > journal? sudo mkdir /var/log/journal or turn it on in /etc/systemd/journald.conf. -- Evolution as taught in public schools, like re

Re: systemctl y journal

El 2020-11-08 a las 18:50 +, MLP escribió: > La salida es larguísima: Porque es de varios días ;-) > root@debian:~# systemctl apache2 start > Unknown operation apache2. > root@debian:~# systemctl apache2.service start > Unknown operation apache2.service. Hum... ah, ya. Es al revés:

Re: systemctl y journal

11-08 07:16:52 CET; 12h > ago > Docs: https://httpd.apache.org/docs/2.4/ > Process: 1107 ExecStart=/usr/sbin/apachectl start (code=exited, > status=1/FAILURE) > > Warning: Journal has been rotated since unit was started. Log output is > incomplete or unavailable. Int

Re: systemctl y journal

El 2020-11-08 a las 18:11 +, MLP escribió: > Solicito ayuda pues no soy informático y por mucho que he buscado en la red > no doy encontrado la solución. El problema es este: > > systemctl --failed > UNIT LOAD ACTIVE SUBDESCRIPTION > ● apache2.service

systemctl y journal

Hola. Solicito ayuda pues no soy informático y por mucho que he buscado en la red no doy encontrado la solución. El problema es este: systemctl --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● apache2.service loaded failed failed The Apache HTTP Server ●

Re: Journal

Hi, 3 sept. 2020 à 14:29 de humberto.freitas...@gmail.com: > Just take a look at > Emacs > . It can > take care of everything you need. No kidding, everything or most of the > things lol ;). > Vim does the job as well. Just install VimWiki plugin [1]. You

Re: Journal

Bonsoir, 4 sept. 2020 à 23:38 de l0f...@tuta.io: > Hi, > > 3 sept. 2020 à 14:29 de humberto.freitas...@gmail.com: > >> Just take a look at > Emacs > . It can >> take care of everything you need. No kidding, everything or most of the >> things lol ;). >> >

Re: Journal

Hi, 3 sept. 2020 à 14:29 de humberto.freitas...@gmail.com: > Just take a look at > Emacs > . It can > take care of everything you need. No kidding, everything or most of the > things lol ;). > Vim does the job as well. Just install VimWiki plugin [1]. You

Re: Journal

On Fri, 4 Sep 2020 09:40:07 +0100 Joe wrote: > On Thu, 3 Sep 2020 14:44:31 -0700 > David Christensen wrote: > > > On 2020-09-03 03:50, Joe wrote: > > > I've finally decided I have to keep a diary. > > > > > > In Debian are RoboJournal and Lifeograph. > > > > > > Neither of them actually

Re: Journal

On Thu, 3 Sep 2020 14:44:31 -0700 David Christensen wrote: > On 2020-09-03 03:50, Joe wrote: > > I've finally decided I have to keep a diary. > > > > In Debian are RoboJournal and Lifeograph. > > > > Neither of them actually function, at least in sid. Does anyone > > have any other ideas,

Re: Journal

On Thu, 3 Sep 2020 11:32:18 -0700 Bob McGowan wrote: > On 9/3/20 11:20 AM, Joe wrote: > > On Thu, 3 Sep 2020 11:11:56 -0400 > > Dan Ritter wrote: > > > > > >> Pelican is a static site generator. You write your content in > >> MarkDown or RST, and then Pelican compiles it into a website by >

Re: Journal

On 2020-09-03 03:50, Joe wrote: I've finally decided I have to keep a diary. In Debian are RoboJournal and Lifeograph. Neither of them actually function, at least in sid. Does anyone have any other ideas, apart from phpMyAdmin or Mysql Workbench? Understand that, depending upon jurisdiction,

Re: Journal

Oh, I should have mentioned that the general design goal was / is to build a combination of askSam and ZyIndex (old dos / Window programs) for LInux. On Thursday, September 03, 2020 04:44:14 PM rhkra...@gmail.com wrote: > On Thursday, September 03, 2020 06:50:36 AM Joe wrote: > > I've finally

Re: Journal

On Thursday, September 03, 2020 06:50:36 AM Joe wrote: > I've finally decided I have to keep a diary. > > In Debian are RoboJournal and Lifeograph. > > Neither of them actually function, at least in sid. Does anyone have any > other ideas, apart from phpMyAdmin or Mysql Workbench? I've seen the

Re: Journal

On 9/3/20 11:20 AM, Joe wrote: On Thu, 3 Sep 2020 11:11:56 -0400 Dan Ritter wrote: Pelican is a static site generator. You write your content in MarkDown or RST, and then Pelican compiles it into a website by applying a theme and CSS styles. Performance is high, because your webserver is

Re: Journal

On Thu, 3 Sep 2020 11:11:56 -0400 Dan Ritter wrote: > Pelican is a static site generator. You write your content in > MarkDown or RST, and then Pelican compiles it into a website by > applying a theme and CSS styles. > > Performance is high, because your webserver is only handing out >

Re: Journal

did not know that there is a feature in the ical that was implemented in KDE3 already. So when I open Kontact and go to Journal, I can write my memories down. I don't know how it looks like in KDE >= 4 or in Evolution

Re: Journal

Francisco M Neto wrote: > On Thu, 2020-09-03 at 08:15 -0400, Dan Ritter wrote: > > Joe wrote: > > > Neither of them actually function, at least in sid. Does anyone have any > > > other ideas, apart from phpMyAdmin or Mysql Workbench? > > > > If you want to publish a blog, I recommend Pelican.

Re: Journal

On Thu, 2020-09-03 at 08:15 -0400, Dan Ritter wrote: > Joe wrote: > > Neither of them actually function, at least in sid. Does anyone have any > > other ideas, apart from phpMyAdmin or Mysql Workbench? > > If you want to publish a blog, I recommend Pelican. If you don't > want to publish

Re: Journal

On Thu, Sep 03, 2020 at 11:50:36AM +0100, Joe wrote: > I've finally decided I have to keep a diary. > > In Debian are RoboJournal and Lifeograph. > > Neither of them actually function, at least in sid. Does anyone have any > other ideas, apart from phpMyAdmin or Mysql Workbench? > I guess you

Re: Journal

On Thu, 3 Sep 2020 11:50:36 +0100 Joe wrote: > I've finally decided I have to keep a diary. > > In Debian are RoboJournal and Lifeograph. > > Neither of them actually function, at least in sid. Does anyone have > any other ideas, apart from phpMyAdmin or Mysql Workbench? > Crack open your

Re: Journal

need to get lots of stuff done, like my journal (with ORG mode), system administration, any SQL database (I usually use postgresql), email management, etc. All of it with just one tool. So good and it’s very old, it’s got already a lot of tests and until now it’s as solid as a software

Re: Journal

Joe wrote: > I've finally decided I have to keep a diary. > > In Debian are RoboJournal and Lifeograph. > > Neither of them actually function, at least in sid. Does anyone have any > other ideas, apart from phpMyAdmin or Mysql Workbench? If you want to publish a blog, I recommend Pelican. If

Journal

I've finally decided I have to keep a diary. In Debian are RoboJournal and Lifeograph. Neither of them actually function, at least in sid. Does anyone have any other ideas, apart from phpMyAdmin or Mysql Workbench? -- Joe

Re: Re. Re: high cpu load systemd-journal, nobody logs

after the systemd-journal use 100 %cpu. Ok, scratch that one hypothesis. It was a good one though, it just contradicted the reality :) > => i think it isnt the connection to the "client". > i disconnect the ethernet interface and the cpu load is still at 100% > > i doesnot

Re. Re: high cpu load systemd-journal, nobody logs

hello, i am again. i tcpdump the port. tcpdump -pni any -c1024 -s0 -w /tmp/journal.pcap tcp port 19531 i check the capture size after the cpu load is at 100%. but the size doesnt increase after the systemd-journal use 100 %cpu. => i think it isnt the connection to the "client".

Re: high cpu load systemd-journal, nobody logs

Hello, wow thanks for the answer, reco. i ve some more information. lsof -Pnp (pid from systemd-journal) lsof -Pnp 1424 systemd-j 1424 systemd-journal-gateway0r CHR1,3 0t0 1028 /dev/null systemd-j 1424 systemd-journal-gateway1u unix 0x625ea7cf 0t0 8805 type

Re: high cpu load systemd-journal, nobody logs

Hi. On Wed, Jul 01, 2020 at 09:48:00AM +0200, Nico Becker wrote: > Can somebody give me some hints? Sure. First, the poll(2) by itself is interesting, but useless if you don't know what file descriptors 3 and 5 are referring to. So, lsof -Pnp (pid from systemd-journal) Or at least:

high cpu load systemd-journal, nobody logs

hello, i use debian 9 stretch (arm) for an small embedded project. i install the systemd-journal-remote to read the log messages from the browser. all the time i get an very high cpu load from the systemd-journal. i think it is only if browse the syslog messages on http

Heads up: persistent journal has been enabled in systemd

Hi, with today's upload of systemd 244.1-2 I finally enabled persistent journal by default [1]. It has been a long requested feature. The package will create a directory /var/log/journal on upgrades and new installs, which enables persistent journal in so called auto mode. If you decide

Re: Linux Journal epub files

along the needed PDF files if that would help you. Note that I > > have no expressed permission from Linux Journal to do so. > > That's a kind offer, Nate. In the event that archive.org do *not* have > these all already (and I'm trying to verify), then it would be best IMHO > to

Re: Linux Journal epub files

permission from Linux Journal to do so. That's a kind offer, Nate. In the event that archive.org do *not* have these all already (and I'm trying to verify), then it would be best IMHO to arrange to get the PDFs to them. I can facilitate that, if you want. Please contact me off-list if you are happy

Re: Linux Journal epub files

On 9/9/19 8:55 AM, steve wrote: Le 09-09-2019, à 08:00:49 -0700, Marc Shapiro a écrit : I tried to get the items from the archives suggested by other posters, but did not find epubs.  The no login required link from LJ was dead by the time I got to it. It died fast.  That is why I have this

Re: Linux Journal epub files

On Mon, 9 Sep 2019 08:00:49 -0700, Marc Shapiro  wrote: I tried to get the items from the archives suggested by other posters, but did not find epubs.  The no login required link from LJ was dead by the time I got to it.  It died fast.  That is why I have this issue.  I suppose filling in

Re: Linux Journal epub files

Le 09-09-2019, à 08:00:49 -0700, Marc Shapiro a écrit : I tried to get the items from the archives suggested by other posters, but did not find epubs.  The no login required link from LJ was dead by the time I got to it.  It died fast.  That is why I have this issue.  I suppose filling in

Re: Linux Journal epub files

On 9/9/19 5:15 AM, Nate Bargmann wrote: * On 2019 08 Sep 14:56 -0500, Marc Shapiro wrote: I have Linux Journal in epub format up through June of 2018.  I didn't grab the others as they became available and by the time I realized that LJ was closing permanently, the archives were no longer

Re: Linux Journal epub files

* On 2019 08 Sep 14:56 -0500, Marc Shapiro wrote: > I have Linux Journal in epub format up through June of 2018.  I didn't grab > the others as they became available and by the time I realized that LJ was > closing permanently, the archives were no longer working.  Does anyone know >

Re: Linux Journal epub files

On 2019-09-09, Richard Owlett wrote: > On 09/08/2019 02:55 PM, Marc Shapiro wrote: >> I have Linux Journal in epub format up through June of 2018.  I didn't >> grab the others as they became available and by the time I realized that >> LJ was closing permanently, the ar

Re: Linux Journal epub files

On 09/08/2019 02:55 PM, Marc Shapiro wrote: I have Linux Journal in epub format up through June of 2018.  I didn't grab the others as they became available and by the time I realized that LJ was closing permanently, the archives were no longer working.  Does anyone know where I can find

Linux Journal epub files

I have Linux Journal in epub format up through June of 2018.  I didn't grab the others as they became available and by the time I realized that LJ was closing permanently, the archives were no longer working.  Does anyone know where I can find the newer issues (7/18 through end of publication

Re: systemd-journald failed to open runtime journal

Charlie S wrote: > I think there is a bug in systemd that is shown at upgrade of buster, so > it should be held back before any upgrade is attempted. Sorry for irony but I just thought - I think it is bug by itself :D

Re: systemd-journald failed to open runtime journal

On Sat, 26 Jan 2019 12:03:25 -0500 Liam Morland sent: > Hello, > > Recently, I have been getting floaded with console messages like this: > > systemd-journald failed to open runtime journal: cannot allocate > memory > > Rebooting puts a stop to it for a few hours

systemd-journald failed to open runtime journal

Hello, Recently, I have been getting floaded with console messages like this: systemd-journald failed to open runtime journal: cannot allocate memory Rebooting puts a stop to it for a few hours. Even when the messages are coming up, /proc/meminfo does not appear to show a lack of memory. Does

Re: journal swamped with gdm3-x-session messages

Roger Price wrote Mon, 29 Jan 2018 23:13:05 +0100 (CET): I rebooted stretch and now my journald is being swamped with the following message: /usr/lib/gdm3/gdm-x-session[2684]: Promise rejected after context unloaded: Message manager disconnected It's the Ghostery addon to Firefox 52.6.0.

Re: journal swamped with gdm3-x-session messages

Roger Price wrote Mon, 29 Jan 2018 23:13:05 +0100 (CET): I rebooted stretch and now my journald is being swamped with the following message: /usr/lib/gdm3/gdm-x-session[2684]: Promise rejected after context unloaded: Message manager disconnected I managed to get rid of this flood of

journal swamped with gdm3-x-session messages

I rebooted stretch and now my journald is being swamped with the following message: /usr/lib/gdm3/gdm-x-session[2684]: Promise rejected after context unloaded: Message manager disconnected A new message appears every few seconds. What is causing this? What have I done wrong? Any hint would

Re: RAID 5 array with journal device does not automatically assemble at boot

creating the initramfs. I tried that, but I did not see any difference. On 8. Nov 2017, at 21:58, deloptes <delop...@gmail.com> wrote: > According the docs [1,2] I overflew it is used only when creating an array. > [3] says explicitly create, build or grow. For manage you should >

Re: RAID 5 array with journal device does not automatically assemble at boot

Tobx wrote: > RAID assembling at boot only works when no journal device is involved. > I can't help much here, nothing to compare. I forgot to mention that md driver is compiled in the kernel in my case. > VERBOSE=false perhaps set to true and see what it says. > > Option

Re: RAID 5 array with journal device does not automatically assemble at boot

I was on 4.9.0-4 (Stretch), now tried with 4.13.0-0 but had no luck. I also tried it again on a clean Ubuntu-Server 17.10 with Kernel 4.13.0-16 and had exactly the same issue: RAID assembling at boot only works when no journal device is involved. > On 7. Nov 2017, at 20:04, deloptes <

Re: RAID 5 array with journal device does not automatically assemble at boot

Tobx wrote: > What am I missing? I don't know if it is related and I don't use raid5, but rather raid1, and in the past year or so I had experienced similar with our server. Now I run 4.12.10 and noticed in the changelog/release notes that there are a lot of fixes in the md stack. The issues are

RAID 5 array with journal device does not automatically assemble at boot

Hello, I try to get a RAID 5 array to assemble at boot with mdadm: # mdadm --create /dev/md/test --level=5 --raid-devices=3 --write-journal=/dev/sde1 /dev/sd[bcd]1 mdadm: Defaulting to version 1.2 metadata mdadm: array /dev/md/test started. # /usr/share/mdadm/mkconf > /etc/mdadm/mdadm.c

Re: log to journal only

Henning Follmann [2017-01-09 08:15:37-05] wrote: > right now the default behavior in stable is to log into /var/log and > into journal (located under /run/log/journal). > > I wonder if it safe to disable the "old" way of logging. And if so how > to do that. It's safe,

Re: log to journal only

On Mon, Jan 09, 2017 at 08:15:37AM -0500, Henning Follmann wrote: > I wonder if it safe to disable the "old" way of logging. And if so how > to > do that. Done that 2 days ago. No problems so far. I just removed rsyslog. Read: /usr/share/doc/systemd/README.Debian.gz Mattia

log to journal only

Hello, right now the default behavior in stable is to log into /var/log and into journal (located under /run/log/journal). I wonder if it safe to disable the "old" way of logging. And if so how to do that. -H -- Henning Follmann | hfollm...@itcfollmann.com

Re: strange journald *.journal file permissions

On 2015-07-09 02:43:25 +0200, Christian Seiler wrote: What would be interesting to see is the following: - remove the executable bit in the mask (= group permission bit since the files use ACLs) on those files - reboot - see if the bit is set again The x bit is re-added after reboot.

Re: strange journald *.journal file permissions

On 2015-07-07 13:35:00 +0200, Christian Seiler wrote: Am 2015-07-05 13:03, schrieb Vincent Lefevre: Can anyone explain these strange journald permissions? -rw-r-x---+ 1 root root16777216 2015-07-05 12:57:55 system.journal* -rw-r-x---+ 1 root systemd-journal 8388608 2015-07-05

Re: strange journald *.journal file permissions

root systemd-journal 8388608 2015-07-05 12:17:21 user-1000.journal* More precisely, why the bit x for the group? So when activating the persistent journal, README.Debian contains the following line: setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal Did you by any chance forget the -n when

Re: strange journald *.journal file permissions

then upgraded to unstable. unless you explicitly set ACLs on the directory, for example to let members of the 'adm' group access the journal (see the snippet in README.Debian I posted). There are ACL's on the directory, but I haven't set them. drwxr-sr-x+ 2 root systemd-journal 4096 2015-07-03 14

Re: strange journald *.journal file permissions

On 07/09/2015 12:17 AM, Vincent Lefevre wrote: FYI, I installed Jessie then upgraded to unstable. Ah, that explains it, see below: grep -r var/log/journal {/etc,/usr/lib}/tmpfiles.d /usr/lib/tmpfiles.d/systemd.conf:z /var/log/journal 2755 root systemd-journal - - /usr/lib/tmpfiles.d

Re: strange journald *.journal file permissions

Am 2015-07-05 13:03, schrieb Vincent Lefevre: Can anyone explain these strange journald permissions? -rw-r-x---+ 1 root root16777216 2015-07-05 12:57:55 system.journal* -rw-r-x---+ 1 root systemd-journal 8388608 2015-07-05 12:17:21 user-1000.journal* More precisely, why the bit x

Re: strange journald *.journal file permissions

On Sun 05 Jul 2015 at 13:03:25 +0200, Vincent Lefevre wrote: Can anyone explain these strange journald permissions? -rw-r-x---+ 1 root root16777216 2015-07-05 12:57:55 system.journal* -rw-r-x---+ 1 root systemd-journal 8388608 2015-07-05 12:17:21 user-1000.journal* More

strange journald *.journal file permissions

Can anyone explain these strange journald permissions? -rw-r-x---+ 1 root root16777216 2015-07-05 12:57:55 system.journal* -rw-r-x---+ 1 root systemd-journal 8388608 2015-07-05 12:17:21 user-1000.journal* More precisely, why the bit x for the group? -- Vincent Lefèvre vinc

systemd-journal eats 100% CPU + rsyslog bloated with messages - Jessie

Guys, Right after connecting via SSH and starting mc, my machine almost died. I seeing the following messages at the logs: http://pastebin.com/4zXYXSWe I need to kill gpm, or fallback to `sysvinit-core`, by removing systemd as init, to be able to use my system as usual. This systemd thing

Re: package recommendation for daily journal

On Tue, Jun 03, 2014 at 11:16:51PM -0700, Rusi Mody wrote: On Sunday, June 1, 2014 12:30:01 PM UTC+5:30, lina wrote: Hi, I am looking for a package, which can act as a smart diary or journal to help me remember the records of small things, such as obtain a licensed software

Re: package recommendation for daily journal

On Sunday, June 1, 2014 12:30:01 PM UTC+5:30, lina wrote: Hi, I am looking for a package, which can act as a smart diary or journal to help me remember the records of small things, such as obtain a licensed software, not installed yet, uninstall the harden-client. emacs' org mode

Re: package recommendation for daily journal

On Tue, Jun 03, 2014 at 11:16:51PM -0700, Rusi Mody wrote: On Sunday, June 1, 2014 12:30:01 PM UTC+5:30, lina wrote: Hi, I am looking for a package, which can act as a smart diary or journal to help me remember the records of small things, such as obtain a licensed software

Re: package recommendation for daily journal

On 2014-06-04, Tazman Deville tazmande...@gmx.com wrote: Here is a bash script for writing and managing a personal log, by Tony, who is also on this list. I'm surprised he didn't mention it himself. https://github.com/tonybaldwin/mylog read -p Shall we have a look in your a browser now?

Re: package recommendation for daily journal

On Wed, Jun 04, 2014 at 01:47:47PM +, Curt wrote: On 2014-06-04, Tazman Deville tazmande...@gmx.com wrote: Here is a bash script for writing and managing a personal log, by Tony, who is also on this list. I'm surprised he didn't mention it himself.

package recommendation for daily journal

Hi, I am looking for a package, which can act as a smart diary or journal to help me remember the records of small things, such as obtain a licensed software, not installed yet, uninstall the harden-client. Thanks ahead, lina

Re: package recommendation for daily journal

On Sun, Jun 01, 2014 at 02:52:36PM +0800, lina wrote: Hi, I am looking for a package, which can act as a smart diary or journal to help me remember the records of small things, such as obtain a licensed software, not installed yet, uninstall the harden-client. Thanks ahead, lina If you

  1   2   3   >