Re: initrd sizes mushroomed several months ago

[David Wright]

On Wed 01 Feb 2023 at 00:50:07 (-0500), Felix Miata wrote:
> David Wright composed on 2023-01-31 22:56 (UTC-0600):
> > On Tue 31 Jan 2023 at 18:31:15 (-0500), Felix Miata wrote:
> >> David Wright composed on 2023-01-28 09:10 (UTC-0600):
> >>> On Sat 28 Jan 2023 at 03:15:11 (-0500), Felix Miata wrote:
>  
>  I thought only Windows was like that, but apparently not always. I keep 
>  my
>  initramfs configuration set to =dep.
>   
> >>> And is that the reason behind, and cure for, your mushrooming initrd
> >>> size complaint in 
> >>> https://lists.debian.org/debian-user/2022/11/msg00331.html
>   
> >> More detail follows:
>  
> >> # inxi -S --vs
> >> inxi 3.3.24-00 (2022-12-10)
> >> System:
> >>   Host: big31 Kernel: 6.0.0-6-amd64 arch: x86_64 bits: 64 Desktop: Trinity
> >> Distro: Debian GNU/Linux bookworm/sid
> >> # ls -Gg /etc/initramfs-tools/initramfs.conf
> >> -rw-r--r-- 1 1582 Sep 12 04:21 /etc/initramfs-tools/initramfs.conf
> >> # diff -u1 /etc/initramfs-tools/.initramfs.conf.07dpkg-dist 
> >> /etc/initramfs-tools/initramfs.conf
> >> --- /etc/initramfs-tools/.initramfs.conf.07dpkg-dist2022-06-20 
> >> 16:54:17.0 -0400
> >> +++ /etc/initramfs-tools/initramfs.conf 2022-09-12 04:21:09.0 -0400
> >> @@ -19,3 +19,3 @@
>  
> >> -MODULES=most
> >> +MODULES=dep
> >> # ls -Gg /boot/initrd.img-5.16.0-6* /boot/initrd.img-5.19* 
> >> /boot/initrd.img-6*
> >> -rw-r--r-- 1  7554203 Apr 22  2022 /boot/initrd.img-5.16.0-6-amd64
> >> -rw-r--r-- 1  8324160 Sep 12 04:26 /boot/initrd.img-5.19.0-1-amd64
> >> -rw-r--r-- 1 34597945 Nov  2 17:57 /boot/initrd.img-5.19.0-2-amd64
> >> -rw-r--r-- 1 23955561 Jan 31 17:58 /boot/initrd.img-6.0.0-6-amd64
> 
> I think 6.0's is smaller because that upgrade cycle is when I installed zstd
> before the newer kernel. It's specified by default in initramfs.conf, but the
> upgrades from 11 to 12 here have only been including libzstd1, which 
> apparently
> is not used for initrd construction.

That's relatively easy to confirm with something like:

  $ dd if=/boot/initrd.img-6.0.0-6-amd64 skip= | file -

where  is given by the last line from:

  $ cpio -t < /boot/initrd.img-6.0.0-6-amd64

> > I was under the impression that mushrooming occurred after 17, yet
> > your 19…1 is small again.
>  
> > It's a simple matter to
>  
> >   $ ls[]initramfs -l /boot/initrd.img-5.19.0-2-amd64 [corrected typo]
>  
> > for 19…1 and 19…2, and compare their contents. Are there more modules
> > included in the second one, or has each module expanded in size?
> > Or is something included in the initrd that's unexpected? Has someone
> > replaced busybox by ~250 different binaries? These are the obvious
> > things to investigate.
>  
> Unexpected: giant firmware increase. :(
> 
> # lsinitramfs initrd.img-5.19.0-1-amd64 | grep mwar | wc -l
> 1
> # lsinitramfs initrd.img-5.19.0-2-amd64 | grep mwar | wc -l
> 655
> # lsinitramfs initrd.img-6.0.0-6-amd64 | grep mwar | wc -l
> 655
> #
> 
> I'm not aware of whatever controls whether mountains of firmware
> are stuffed into initrds or not. I can't make enough sense of what
> /usr/share/initramfs-tools/ contains to know if there's something
> in it that controls.

Well, it's certainly odd that you require 654 extra firmware files
to boot 5.19.0-2-amd64 as opposed to 5.19.0-1-amd64, so if there
are no stray files in /etc/initramfs/conf.d/, then something else
in the initrd is most likely the cause.

I haven't seen any response from you to The Wanderer's post about
the initramfs-tools upgrade. (Note that there are two packages,
including the -core.) That's why, having replied to that post and
yours, I didn't post any of my further researches, including
those I've repeated and reported here.

You could check your /var/log/apt/history* files on both your
systems and see if the initramfs-tools were upgraded between
12 Sep and 2 Nov (amd64) and 8 May and 2 Aug (686).

If that's so, it might be productive to compare the contents of
the older and newer versions of initramfs-tools* to see what's
changed. I think they're both full of entirely non-binary
scripts etc.

> Grepping busy in all three produces same result.

$ lsinitramfs initrd.img-6.0.0-6-amd64 | grep busy | wc -l

is futile, and will yield "1".

$ lsinitramfs initrd.img-6.0.0-6-amd64 | grep busy

is just as futile, and will yield "usr/bin/busybox".

You need to run:

$ lsinitramfs -l initrd.img-6.0.0-6-amd64 | grep busy

and check the first number given in the output, here "247":

  $ lsinitramfs -l /boot/initrd.img-5.10.0-21-amd64 | grep busy
  -rwxr-xr-x 247 root root0 Jul 25  2021 usr/bin/busybox
  $ 

IOW most of the functionality of 247 individual binaries has been built
into the single binary, busybox, which has 247 hard links.

> Installed sizes in /lib/modules vary nominally, 0.1MiB between the
> two 5.19s, 468.9MiB & 468.8MiB, 452.4MiB for 6.0, 426.8 for 5.16, so it
> doesn't look like installed firmware would have changed significantly.

I don't und

Re: ASCII formatting for plain text email

[David Wright]

On Tue 31 Jan 2023 at 23:06:44 (+0100), Pierre Willaime wrote:
> Le 31/01/2023 à 21:14, Greg Wooledge a écrit :
> > A .signature file is only written once, so it doesn't matter how
> > tedious it is to produce the desired formatting.  That said, I would
> > imagine relatively few people have octothorpe boxes around text in their
> > .signature files these days.  Even back in the 1990s, that would have
> > been considered a bit on the tacky side.
> 
> Of course, I misspoke about the signature. I often see *some* formatting
> (such as some text aligned to the left and some other text aligned to
> the right, same line).
> 
> But you are right, .signature file is only written once and I am looking
> for a simple way to write email with some minimal ASCII formatting. This
> is why I am looking for an automatic solution.
> 
> I do not want to do ASCII art, I am only searching a simple way to do
> something close to the debian-annouce emails.
> 
> 
> The Debian Project   https://www.debian.org/
> Updated Debian 11: 11.6 releasedpr...@debian.org
> December 17th, 2022https://www.debian.org/News/2022/20221217
> 
> 
> How this header is generated?

No idea. I guess you might ask someone who generates them.

> So do someone knows:
> 
> 
> 1- a simple way to draw a line (without pressing 72 times on "-")
> ---

I would type ESC 7 2 -
which does, and reflects, the same as C-u 72 -, but is less awkward
to type.

> 2- a simple way to align some text to the right (that is to say to
> automatically calculate how many spaces are needed to fill the gap
> between the text on the left an the text on the right for 72 characters
> line.

That's beyond my paygrade: I don't do conditionals or computations
in emacs. So how would I tackle it to make it a little less painful:

First, I'd type the dashes, which give your eye the alignment to use.
Next, I'd type the left and right parts, but making sure that there
were two spaces between them.

I would define a macro, or preferably have defined it already and
bound it to some keystroke (it needs to be a single keystroke to
be sensible):
C-e C-r SPACE SPACE RETURN SPACE C-e
Every time you execute the macro, the line will lengthen by one.
The macro should be as easy to use whether you lengthen each line
as you type it, or leave it all to the end of the block.

If you're completely ham-fisted, you'd need the inverse macro,
which would have the last SPACE replaced by C-d. That macro would
be bound so that you couldn't easily repeat it by accident, as
it's destructive. (It will search backwards for /any/ double space.)

> 3- a simple way to do boxes (no present in debian-annouce header)

I thought I'd already covered that in
https://lists.debian.org/debian-user/2023/01/msg00792.html
but the buffer has to be in the correct mode to get octotherps
rather than comment characters appropriate to some other
language that emacs thinks the buffer contains.

(I'm assuming the ELPA people have got automated linedrawing
characters covered. I've never ventured there.)

Cheers,
David.

Re: No USB with qemu+macOS+USB+iPads

[stand...@gmx.net]

didier...@gmail.com schrieb am Dienstag, 31. Januar 2023 um 23:10:05 UTC+1:
> Hello, 
> 
> You will probably find the dedicated Qemu doc helpful: 
> https://www.qemu.org/docs/master/system/devices/usb.html 

Thanks, I know it, but nothing of these works for me. I also tred virt-manager 
without success.

I think there ist another  problem which I don't see.

Re: Fw: locating blocked port

[Jeffrey Walton]

On Wed, Feb 1, 2023 at 5:24 PM  wrote:
>
> [...]
> Begin forwarded message:
>
> Date: Wed, 1 Feb 2023 06:09:32 -0500
> From: Haines Brown 
> To: debian-u...@howorth.org.uk
> Subject: Re: locating blocked port
>
> On Tue, Jan 31, 2023 at 10:09:28PM +, debian-u...@howorth.org.uk
> wrote:
> > Haines Brown wrote:
> > >   $ jabref
> ...
> > > 15:43:56.628 [AWT-EventQueue-0] INFO  net.sf.jabref.JabRefMain -
> > > Arguments passed on to running JabRef instance. Shutting down.
> >
> > The last line there seems to imply there is already another instance
> > of jabref running. Is that the case? What does
> >
> > $ ps -fe | grep jabref
> >
> > show, for example?
>
> Yes indeed. It showed two instances of jabref. I killed the processes
> and now
>
>   $ ps -fe | grep jabref
>   haines3597  3160  0 06:02 pts/100:00:00 grep jabref
>
> So I should be able to start jabref:
>
>   $ jabref
>   06:04:08.576 [AWT-EventQueue-0] WARN
> net.sf.jabref.logic.remote.server.RemoteListenerServerLifecycle -
>   Port is blocked
>   java.net.BindException: Address already in use
>   ...
>   06:04:08.591 [AWT-EventQueue-0] INFO  net.sf.jabref.JabRefMain -
> Arguments passed on to running JabRef instance. Shutting down.
>
> It seems that the jabref command i starts jabref twice. Hoewver the
> $ ps -fe command does not show them

After you kill an instance of jabref, the socket may be in a linger
state. I.e., SO_LINGER socket option in C.
https://duckduckgo.com/?q=so_linger+socket+option .

You should be able to check the source code to see if jabref is using
the option. 
https://docs.oracle.com/javase/7/docs/api/java/net/StandardSocketOptions.html#SO_LINGER
.

The short of it is, if the option is being used, then you should wait
about 2 minutes before you try to start the program again.

Jeff

Monthly FAQ for Debian-user list

[Andrew M.A. Cater]

Debian-user is a mailing list provided for support for Debian users,
and to facilitate discussion on relevant topics. 

Some guidelines which may help explain how the list works:

* The language on this mailing list is English. There may be other mailing 
  lists that are language-specific, for example, debian-user-french 

* It is common for users to be redirected here from other lists, for example,
  from debian-project. It is also common for people to be posting here when 
  English is not their primary language. Please be considerate.

* The list is a Debian communication forum. As such, it is subject to both 
  the Debian mailing list Code of Conduct and the main Debian Code of Conduct
  https://www.debian.org/MailingLists/#codeofconduct
  https://www.debian.org/code_of_conduct

* This is a fairly busy mailing list and you may have to wait for an
  answer - please be patient. Please post answers back to the list so
  others can benefit; private conversations don't benefit people who
  may be following along on the list or reading the archives later.

* Help and advice on this list is provided by volunteers in their own time.
  It is common for there to be different opinions or answers provided.

 * Please try to stay on topic. Arguments for the sake of it are not
   welcome here. Partisan political / religious / cultural arguments
   do not belong here either. Debian's community is world wide; do not
   assume others will agree with your views or need to read them on a
   Debian list.

* There is an FAQ on the Debian wiki derived from some questions asked on this
  list at https://wiki.debian.org/FAQsFromDebianUser

* One question that comes up on almost all Debian lists from time to time is of
  the form: 

  "I have done something wrong / included personal details in an email.
   Could you please delete my name / details / remove the mail"

Practically, this is impossible: the mailing lists are archived, potentially
cached by Google and so on.

Unfortunately, there is nothing much we can do to ensure that all copies
anywhere on the Internet are deleted. Asking to do this may only serve to
draw further attention - the so-called "Streisand effect"
See:  https://en.wikipedia.org/wiki/Streisand_effect

Problems?
=

Complaints about inappropriate behaviour should be referred to the
Debian Community Team .

Inappropriate behaviour on the list may lead to warnings; repeated bad
behaviour may lead to temporary or permanent bans for offenders.

Fw: locating blocked port

[debian-user]

Haines Brown sent a reply directly to me instead of the list in
response to the post I made. I advised him to send his reply to the
list instead. He didn't, he just forwarded me another copy of his
reply. So here's his reply so anybody that's interested can read it. I
expect Haines may end up in my bitbucket soon.

Begin forwarded message:

Date: Wed, 1 Feb 2023 06:09:32 -0500
From: Haines Brown 
To: debian-u...@howorth.org.uk
Subject: Re: locating blocked port


On Tue, Jan 31, 2023 at 10:09:28PM +, debian-u...@howorth.org.uk
wrote:
> Haines Brown wrote:  
> >   $ jabref  
...
> > 15:43:56.628 [AWT-EventQueue-0] INFO  net.sf.jabref.JabRefMain -
> > Arguments passed on to running JabRef instance. Shutting down.  
> 
> The last line there seems to imply there is already another instance
> of jabref running. Is that the case? What does
> 
> $ ps -fe | grep jabref
> 
> show, for example?  

Yes indeed. It showed two instances of jabref. I killed the processes
and now

  $ ps -fe | grep jabref
  haines3597  3160  0 06:02 pts/100:00:00 grep jabref

So I should be able to start jabref:

  $ jabref
  06:04:08.576 [AWT-EventQueue-0] WARN  
net.sf.jabref.logic.remote.server.RemoteListenerServerLifecycle - 
  Port is blocked
  java.net.BindException: Address already in use
  ...
  06:04:08.591 [AWT-EventQueue-0] INFO  net.sf.jabref.JabRefMain - 
Arguments passed on to running JabRef instance. Shutting down.

It seems that the jabref command i starts jabref twice. Hoewver the 
$ ps -fe command does not show them

-- 

 Haines Brown 
 /"\
 \ /  ASCII Ribbon Campaign
  Xagainst HTML e-mail 
 / \

Re: ASCII formatting for plain text email

[Pierre-Elliott Bécue]

Greg Wooledge  wrote on 01/02/2023 at 16:00:59+0100:

> On Wed, Feb 01, 2023 at 02:40:30PM -, Curt wrote:
>> On 2023-02-01, The Wanderer  wrote:
>> >
>> > Can you double-check what (Debian) package that's in? I'm not finding
>> > any package or file named anything like either of those two things, in
>> > current Debian testing and stable.
>> 
>> You use the built-in package manager: 'M-x package-install RET 
>> ascii-art-draw RET'.
>
> ... what in the HELL is that?  An emacs command?  Does emacs have its
> own packages?

Yes, (m)elpa et al.

Actually quite useful, because many features are not debian-packaged
(yet?).

-- 
PEB

Re: OT: Charities (a rant)

[Jeffrey Walton]

On Wed, Feb 1, 2023 at 9:59 AM Stefan Monnier  wrote:
>
> > I use Amazon Smile with SPI so my shopping benefits open source.
>
> Of course, it benefits Amazon first and foremost :-)
>

The program is going away.
https://www.cnn.com/2023/01/19/tech/amazon-smile-shut-down/index.html

My guess is, it was cutting too deep into corporate profits.

Jeff

Re: Syslog/Rsyslog/Systemctl issue

[Greg Wooledge]

On Wed, Feb 01, 2023 at 03:39:05PM +0100, Freyja wrote:
> But I've found that some processes were complaining that selinux filesystem
> was not mounted.

> I know I've disabled apparmor and selinux in the past because too many
> processes were blocked by them

I don't know much about SELinux.  If that's the underlying issue here,
you're going to need help from someone who knows SELinux.

Overall, the fact that you got it working by restarting various things
long after boot time makes it sound like things are not happening in
the right order *at* boot time.

Just as one *possible* example, a program that's supposed to create
the directory /run/systemd/journal won't be able to do that until the
/run file system is mounted.  If the mounting of /run is happening
later than expected (due to SELinux or whatever), it might cause things
like systemd-journald to fail to start at boot time.

Tracking down the exact causes of these types of issues is *very*
difficult, especially due to the non-sequential nature of systemd's
boot process.  It tries to do as many things as possible in parallel,
which is great for speed, but a massive headache when trying to
troubleshoot a problem.

But it sounds like you've at least got some inkling of where the
problem is.  I don't know what an "selinux filesystem" is, but if you
need it to be mounted, or running, or whatever, before other things can
go, then you'll need to look at the dependency relationships of your
"selinux" unit with respect to other units.  Make sure everything runs
at the correct time.

Re: ASCII formatting for plain text email

[The Wanderer]

On 2023-02-01 at 10:00, Greg Wooledge wrote:

> On Wed, Feb 01, 2023 at 02:40:30PM -, Curt wrote:
>
>> On 2023-02-01, The Wanderer  wrote:
>>
>> >
>> > Can you double-check what (Debian) package that's in? I'm not finding
>> > any package or file named anything like either of those two things, in
>> > current Debian testing and stable.
>> 
>> You use the built-in package manager: 'M-x package-install RET 
>> ascii-art-draw RET'.
> 
> ... what in the HELL is that?  An emacs command?

Yes.

> Does emacs have its own packages?

Apparently so. I didn't expect that, but I can't say I'm especially
surprised.

I do think it would have been appropriate to specify that, but in the
initial reply at least there *was* mention of emacs in the quoted
context, so I can see why that might not have been done. For this
response, there wasn't any mention of emacs at all - and in that case it
would *definitely* have been appropriate to specify e.g. "the package
manager built in to emacs" instead of just "the built-in package
manager", since the default context at hand (by virtue of where this
conversation is taking place) is "Debian".

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: ASCII formatting for plain text email

[Greg Wooledge]

On Wed, Feb 01, 2023 at 02:40:30PM -, Curt wrote:
> On 2023-02-01, The Wanderer  wrote:
> >
> > Can you double-check what (Debian) package that's in? I'm not finding
> > any package or file named anything like either of those two things, in
> > current Debian testing and stable.
> 
> You use the built-in package manager: 'M-x package-install RET ascii-art-draw 
> RET'.

... what in the HELL is that?  An emacs command?  Does emacs have its
own packages?

Re: locating blocked port

[Greg Wooledge]

This ENTIRE THREAD is a gigantic cautionary tale for developers.  This is
why trying to minimize the amount of information present in your error
messages is NOT helpful.

The Microsoft paradigm of "don't show technical details in error messages
because it will scare the users" is bullshit.  But to be fair, at least
most Windows applications with useless error messages have a button that
you can click to get more details.

Of course, that can't happen when you're writing error text to stderr and
aborting.  In those cases, whatever you write, that's it.  That's all the
user gets.

A stack trace showing WHERE an error occurs is only useful for you, the
developer.  It's not useful for the end user.  The end user needs to
know WHAT went wrong, and to the extent possible, WHY it went wrong.

If you can't open a file, don't just say "can't open file".  Give the NAME
of the file, and the operating system's reason why the file couldn't be
opened.

If you can['t listen on a port, don't just say "can't listen on my port".
Ssy WHAT PORT you're trying to listen on.

...

Now, let's try to accomplish something.

I did a Google search for "jabref documentation", but that was a
non-starter.  The documentation is written for end users who are not
experiencing trouble just *running* the thing.  It's full of pretty
pictures that I'm sure are helpful for someone else.

Next, I did a Google search for "net.sf.jabref.logic.remote.server.Remote
port number".  This led me to
 which discusses this
issue, or at least a very similar issue.

One of the comments on that page says:

  Quick fix would be not to define 6050 as hard coded port as default but
  using defaults.put(REMOTE_SERVER_PORT, 6000+((int) Math.random()*1000);
  for a range between port 6000 and 6999

So maybe it's trying to use port 6050.

I'd advise the OP to read that page, or at least skim it.  The issue that
the bug reporter was experiencing was caused by attempts to run multiple
instances of jabref on the same computer (by multiple users).  This raises
the possibility that the OP is also trying to run multiple simultaneous
instances of jabref, possibly without knowing it.

Of course it's also possible that something else, totally unrelated to
jabref, is using the port in question.

 tells us that thie port is
also (possibly) used by "ARCserve agent", "Brightstor Arcserve Backup"
and "Nortel Software" in addition to a possible use by X11, if for some
reason you've got over 50 displays opened.

Re: OT: Charities (a rant)

[Stefan Monnier]

> I use Amazon Smile with SPI so my shopping benefits open source.

Of course, it benefits Amazon first and foremost :-)


Stefan

Re: Syslog/Rsyslog/Systemctl issue

[Freyja]

Ok,

Instead of just creating the folders, I've reinstalled some packages:

--
❯ apt-get install --reinstall  systemd systemd-sysv libsystemd0 
dbus-user-session

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 4 reinstalled, 0 to remove and 3 not 
upgraded.

Need to get 376 kB/5,090 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.fr.debian.org//debian bullseye/main amd64 libsystemd0 
amd64 247.3-7+deb11u1 [376 kB]

Fetched 376 kB in 1s (645 kB/s)
(Reading database ... 204034 files and directories currently installed.)
Preparing to unpack .../libsystemd0_247.3-7+deb11u1_amd64.deb ...
Unpacking libsystemd0:amd64 (247.3-7+deb11u1) over (247.3-7+deb11u1) ...
Setting up libsystemd0:amd64 (247.3-7+deb11u1) ...
(Reading database ... 204034 files and directories currently installed.)
Preparing to unpack .../systemd_247.3-7+deb11u1_amd64.deb ...
Unpacking systemd (247.3-7+deb11u1) over (247.3-7+deb11u1) ...
Setting up systemd (247.3-7+deb11u1) ...
(Reading database ... 204034 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_247.3-7+deb11u1_amd64.deb ...
Unpacking systemd-sysv (247.3-7+deb11u1) over (247.3-7+deb11u1) ...
Preparing to unpack .../dbus-user-session_1.12.24-0+deb11u1_amd64.deb ...
Unpacking dbus-user-session (1.12.24-0+deb11u1) over (1.12.24-0+deb11u1) ...
Setting up systemd-sysv (247.3-7+deb11u1) ...
Setting up dbus-user-session (1.12.24-0+deb11u1) ...
Processing triggers for libc-bin (2.31-13+deb11u5) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for dbus (1.12.24-0+deb11u1) ...
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

Restarting services...
 systemctl restart clamav-daemon.service ossec.service 
smartmontools.service squid.service ssh.service tor@default.service 
transmission-daemon.service

Service restarts being deferred:
 systemctl restart unattended-upgrades.service

No containers need to be restarted.

No user sessions are running outdated binaries.
--

It helped!
The folders have been recreated:

--
❯ ls -la /run/systemd/journal/socket
srw-rw-rw- 1 root root 0 Feb  1 15:44 /run/systemd/journal/socket

❯ ls -lad /run/systemd/journal/
drwxr-xr-x 2 root root 120 Feb  1 15:44 /run/systemd/journal/

--

I was even able to start most of the failing process but two:

--
❯ systemctl --failed
  UNIT LOAD   ACTIVE SUB    DESCRIPTION
● systemd-udevd-control.socket loaded failed failed udev Control Socket
● systemd-udevd-kernel.socket  loaded failed failed udev Kernel Socket

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
2 loaded units listed.
--

However journalctl still stucks on 24th Oct:
--
❯ journalctl -b
-- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon 
2022-10-24 14:14:33 CEST. --

-- No entries --
--

Le 01/02/2023 à 15:32, Charles Curley a écrit :

On Wed, 1 Feb 2023 13:26:58 +0100
Freyja  wrote:


For /run/systemd/journal/socket this is another story.
The folder journal does not exist at all.

Well, that could be a problem. On one of my computers:

root@jhegaala:~# ll /run/systemd/journal/socket
srw-rw-rw- 1 root root 0 Jan 25 09:55 /run/systemd/journal/socket=
root@jhegaala:~# ll -d /run/systemd/journal/
drwxr-xr-x 3 root root 200 Jan 25 09:55 /run/systemd/journal//
root@jhegaala:~#

You might try rebuilding the directory /run/systemd/journal/ with
appropriate permissions and manually restarting the relevant services.
(The services should rebuild the sockets for you.)

Re: ASCII formatting for plain text email

[Curt]

On 2023-02-01, The Wanderer  wrote:
>
> Can you double-check what (Debian) package that's in? I'm not finding
> any package or file named anything like either of those two things, in
> current Debian testing and stable.

You use the built-in package manager: 'M-x package-install RET ascii-art-draw 
RET'.

>The Wanderer
>
> The reasonable man adapts himself to the world; the unreasonable one
> persists in trying to adapt the world to himself. Therefore all
> progress depends on the unreasonable man. -- George Bernard Shaw
>
>
> --hGCJdb4M3Un9Q2DPGx5HntuduPChnXD3c
> Content-Type: application/pgp-signature; name="signature.asc"
> Content-Description: OpenPGP digital signature
> Content-Disposition: attachment; filename="signature.asc"
>
>
> --hGCJdb4M3Un9Q2DPGx5HntuduPChnXD3c--
>
>


-- 

Re: Syslog/Rsyslog/Systemctl issue

[Freyja]

I don't remember all the steps I've made.
I tried so many things.

But I've found that some processes were complaining that selinux 
filesystem was not mounted.
Mounted the filesystem with the command "cat /etc/systemd/system.conf" 
and it helped starting some process.


That time, even if the filesystem is mounted, the services do not want 
to start :/


I guess my systemd.conf is default
--
❯ cat /etc/systemd/system.conf
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See systemd-system.conf(5) for details.

[Manager]
#LogLevel=info
#LogTarget=journal-or-kmsg
#LogColor=yes
#LogLocation=no
#LogTime=no
#DumpCore=yes
#ShowStatus=yes
#CrashChangeVT=no
#CrashShell=no
#CrashReboot=no
#CtrlAltDelBurstAction=reboot-force
#CPUAffinity=1 2
#NUMAPolicy=default
#NUMAMask=
#RuntimeWatchdogSec=0
#RebootWatchdogSec=10min
#ShutdownWatchdogSec=10min
#KExecWatchdogSec=0
#WatchdogDevice=
#CapabilityBoundingSet=
#NoNewPrivileges=no
#SystemCallArchitectures=
#TimerSlackNSec=
#StatusUnitFormat=description
#DefaultTimerAccuracySec=1min
#DefaultStandardOutput=journal
#DefaultStandardError=inherit
#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s
#DefaultTimeoutAbortSec=
#DefaultRestartSec=100ms
#DefaultStartLimitIntervalSec=10s
#DefaultStartLimitBurst=5
#DefaultEnvironment=
#DefaultCPUAccounting=no
#DefaultIOAccounting=no
#DefaultIPAccounting=no
#DefaultBlockIOAccounting=no
#DefaultMemoryAccounting=yes
#DefaultTasksAccounting=yes
#DefaultTasksMax=15%
#DefaultLimitCPU=
#DefaultLimitFSIZE=
#DefaultLimitDATA=
#DefaultLimitSTACK=
#DefaultLimitCORE=
#DefaultLimitRSS=
#DefaultLimitNOFILE=1024:524288
#DefaultLimitAS=
#DefaultLimitNPROC=
#DefaultLimitMEMLOCK=
#DefaultLimitLOCKS=
#DefaultLimitSIGPENDING=
#DefaultLimitMSGQUEUE=
#DefaultLimitNICE=
#DefaultLimitRTPRIO=
#DefaultLimitRTTIME=
--

I have no idea what is this "."...
I know I've disabled apparmor and selinux in the past because too many 
processes were blocked by them



Le 01/02/2023 à 14:40, David a écrit :

On Thu, 2 Feb 2023 at 00:07, Freyja  wrote:


I've already tried to solve this issue in December with some success

Hi, could you describe in detail what you did?

Can you also post the output of:
   cat /etc/systemd/system.conf

Also, a small thing I happened to notice:


root in /var/log
❯ ls -la journal/
total 44
drwxr-sr-x+  3 root systemd-journal  4096 Aug 19  2021 .
drwxr-xr-x. 33 root root12288 Feb  1 06:25 ..

^
On my system I do not have the '.' character in column 11
which you show in your output line that I have quoted
immediately above. I don't know anything about that or
if is relevant, just mentioning it in case someone else
can comment on that.

Command
   info -f coreutils -n 'What information is listed'
says:
  Following the file mode bits is a single character that specifies
  whether an alternate access method such as an access control list
  applies to the file.  When the character following the file mode
  bits is a space, there is no alternate access method.  When it is a
  printing character, then there is such a method.

  GNU ‘ls’ uses a ‘.’ character to indicate a file with a security
  context, but no other alternate access method.

Re: ASCII formatting for plain text email

[The Wanderer]

On 2023-02-01 at 09:22, Curt wrote:

> On 2023-01-31, Pierre Willaime  wrote:
>
>> Hi,
>>
>> --
>> Warning: I hope you will forgive me for this email not really related to
>> debian. I just think people from this community could likely have good
>> advice about this question.
>> --
>>
>> I would like to format plain text emails to increase readability and
>> information separation. The idea is to go beyond markdown and to have
>> more visible elements. For example I am looking for a convenient way to
>> "draw" some ASCII boxes such as
>>
>> #
>> ## some title here ##
>> #
>>
>> (I am using emacs comment-box feature in a buffer to do this and I
>> replace ; by #, I suppose there is nicer way to do this).
>>
>> I often see email signature using this kind of formatting.
>>
>> Do you know dedicated tools or text editor to do such things the easy
>> way on an everyday basis?
>>
>>
>> Have a nice day
> 
> I haven't read all the answers, so I may be redundant (so to speak):
> 
> You can you use the 'ascii-art-to-string' function in the 'ascii-art-draw'
> package. You first create a string with the text you wish to surround
> with a box, then call the function on that string.

Can you double-check what (Debian) package that's in? I'm not finding
any package or file named anything like either of those two things, in
current Debian testing and stable.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Syslog/Rsyslog/Systemctl issue

[Charles Curley]

On Wed, 1 Feb 2023 13:26:58 +0100
Freyja  wrote:

> For /run/systemd/journal/socket this is another story.
> The folder journal does not exist at all.

Well, that could be a problem. On one of my computers:

root@jhegaala:~# ll /run/systemd/journal/socket
srw-rw-rw- 1 root root 0 Jan 25 09:55 /run/systemd/journal/socket=
root@jhegaala:~# ll -d /run/systemd/journal/
drwxr-xr-x 3 root root 200 Jan 25 09:55 /run/systemd/journal//
root@jhegaala:~# 

You might try rebuilding the directory /run/systemd/journal/ with
appropriate permissions and manually restarting the relevant services.
(The services should rebuild the sockets for you.)

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: locating blocked port

[davenull]

Hello

On 2023-01-31 16:05, Haines Brown wrote:

I have an  application that refuses to start because  its port is
blocked. But I have difficulty knowing what port it is

   $ java -jar /usr/local/share/JabRef/JabRef-3.2.jar &
  [1] 4831
  haines@lenin:~$ Jan 31, 2023 8:36:39 AM
net.sf.jabref.logic.remote.server.Remote
  ListenerServerLifecycle open
  WARNING: Port is blocked
  java.net.BindException: Address already in use
at java.base/sun.nio.ch.Net.bind0(Native Method)
at java.base/sun.nio.ch.Net.bind(Net.java:555)
at java.base/sun.nio.ch.Net.bind(Net.java:544)
at 
java.base/sun.nio.ch.NioSocketImpl.bind(NioSocketImpl.java:643)

at java.base/java.net.ServerSocket.bind(ServerSocket.java:388)
at 
java.base/java.net.ServerSocket.(ServerSocket.java:274)

at
net.sf.jabref.logic.remote.server.RemoteListenerServer.(RemoteListenerServer.java:40)
at
net.sf.jabref.logic.remote.server.RemoteListenerServerThread.(RemoteListenerServerThread.java:33)
at
net.sf.jabref.logic.remote.server.RemoteListenerServerLifecycle.open(RemoteListenerServerLifecycle.java:41)
at net.sf.jabref.JabRef.start(JabRef.java:137)
at net.sf.jabref.JabRefMain.main(JabRefMain.java:8)

  Arguments passed on to running JabRef instance. Shutting down.

How do I know from this what port the java application tried to use?

I try:

  $ strings $(which jabref) | wc -l
56

  So I try:

$ sudo ss -pt state listening 'sport = :56'
Recv-Q   Send-QLocal Address:Port   Peer Address:Port Process

  This seems a null return. Dores this mean jabref is not using port
  56?



If ss, or lsof, or any other tool that shows used ports doesn't show 
port 56 being used. Then it's not being used. Or in your case, since 
you're filtering ss output to only listening TCP ports, IF it being 
used, it might be on a different state that "listening".
Or it could be UDP, but I'm assuming you except jabref to use a TCP 
port, thus the use of '-t' option (Disclaimer, I don't what protocols 
jabref uses)


However I'm not sure what makes you think jabref is trying to use 
(either TCP or UDP) port 56. It your example you didn't show or tell 
what to tried to determine it's supposed to use that specific port. wc 
-l counts lines and have nothing to do with port numbers. So


$ command | wc -l

Returns the number of lines outputted by "command" (whatever before 
pipe). In your case, "strings $(which jabref)" outputs 56 lines.


"sudo lsof -i" as a sudoer user, or "lsof -i" as root (elevated 
privileges required to trace used ports) should list processes/commands 
using ports, for both listening and established.
OR just "sudo ss -pt state listening" without specifying a source port 
to see all the listening port to use used ports, then compare it to 
'whatever port number' jabref's documentations says the software uses.


Also, starting jabref with strace, using the network filter, something 
like "sudo strace -f -e trace=network 
$InsertHereWhateverCommandYouUseToStartJabref", should help you to see 
what port it's trying to use.

Re: ASCII formatting for plain text email

[Curt]

On 2023-01-31, Pierre Willaime  wrote:
> Hi,
>
> --
> Warning: I hope you will forgive me for this email not really related to
> debian. I just think people from this community could likely have good
> advice about this question.
> --
>
> I would like to format plain text emails to increase readability and
> information separation. The idea is to go beyond markdown and to have
> more visible elements. For example I am looking for a convenient way to
> "draw" some ASCII boxes such as
>
> #
> ## some title here ##
> #
>
> (I am using emacs comment-box feature in a buffer to do this and I
> replace ; by #, I suppose there is nicer way to do this).
>
> I often see email signature using this kind of formatting.
>
> Do you know dedicated tools or text editor to do such things the easy
> way on an everyday basis?
>
>
> Have a nice day
>
>

I haven't read all the answers, so I may be redundant (so to speak):

You can you use the 'ascii-art-to-string' function in the 'ascii-art-draw'
package. You first create a string with the text you wish to surround
with a box, then call the function on that string.

Re: locating blocked port

[Henning Follmann]

On Tue, Jan 31, 2023 at 03:51:20PM -0500, Haines Brown wrote:
> On Tue, Jan 31, 2023 at 12:13:03PM -0500, Henning Follmann wrote:
>  
> > I think this is just futile. Why would you do all this painful stuff,
> > which might not get you close to what you really want - running that app.
> 
> Are you implying the problem should not occur?

No, apparently the problem occurs. However (and this might sound harsh)
someone who seems to just run a command she/he found somewhere (on the
internet?). You clearly did not understand what that command was doing,
because I do not believe you think the number of text strings in a program
in any way relates to an port that program listens to.
So I am saying base on that I made the judgement that you will not get
anywhere by running strace, and the advise given to you was not a good one.
Also I do not understand why you are so focused on finding that port.
I would go to the documentation of this Project and start looking at that.
https://docs.jabref.org/

And it even has a faq section for linux.
That might be a good start.
 

>  
> > For now I just assume you installed jabref via the debian packaging system?
> > Please just try to start jabref through the system menu.
> 
> Yes, I did a normal # aptitude install of jabref. I don't have a 
> desktop manager but my window manager has an applications menu. I've 
> never used it but I look for jabref and its not in the mentu. The 
> jabref command is in my path and so I simply do:

well, what you say you did differs from the original post. There you called
java with a path to the jar.
You will find also in the faq section an answer why that might be a bad
idea.

BTW. The offical debian package of this application is quite old (I think
it is 3.8). You might download the newest version from that project site.
That versin comes with a embedded jre. Maybe try that.


-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Syslog/Rsyslog/Systemctl issue

[David]

On Thu, 2 Feb 2023 at 00:07, Freyja  wrote:

> I've already tried to solve this issue in December with some success

Hi, could you describe in detail what you did?

Can you also post the output of:
  cat /etc/systemd/system.conf

Also, a small thing I happened to notice:

> root in /var/log
> ❯ ls -la journal/
> total 44
> drwxr-sr-x+  3 root systemd-journal  4096 Aug 19  2021 .
> drwxr-xr-x. 33 root root12288 Feb  1 06:25 ..
   ^
On my system I do not have the '.' character in column 11
which you show in your output line that I have quoted
immediately above. I don't know anything about that or
if is relevant, just mentioning it in case someone else
can comment on that.

Command
  info -f coreutils -n 'What information is listed'
says:
 Following the file mode bits is a single character that specifies
 whether an alternate access method such as an access control list
 applies to the file.  When the character following the file mode
 bits is a space, there is no alternate access method.  When it is a
 printing character, then there is such a method.

 GNU ‘ls’ uses a ‘.’ character to indicate a file with a security
 context, but no other alternate access method.

Re: Syslog/Rsyslog/Systemctl issue

[Freyja]

There is an interesting part: I've already tried to solve this issue in 
December with some success except for 2 systemd services (udevd-control 
& udevd-kernel).

It stopped again working the 25th of december.

--
I've found a journal related to 24th December in /var/log/journal:

root in /var/log
❯ ls -la journal/
total 44
drwxr-sr-x+  3 root systemd-journal  4096 Aug 19  2021 .
drwxr-xr-x. 33 root root    12288 Feb  1 06:25 ..
drwxr-sr-x+  2 root systemd-journal 20480 Dec 24 11:35 
ef72ee158c9d4ae68bd60ae8adbb20af


root in /var/log
❯ cd journal/ef72ee158c9d4ae68bd60ae8adbb20af/

root in log/journal/ef72ee158c9d4ae68bd60ae8adbb20af
❯ ls -la
total 98356
drwxr-sr-x+ 2 root systemd-journal    20480 Dec 24 11:35 .
drwxr-sr-x+ 3 root systemd-journal 4096 Aug 19  2021 ..
-rw-r-+ 1 root systemd-journal 75497472 Oct 24 14:14 system.journal
-rw-r-+ 1 root systemd-journal  8388608 Oct 24 14:14 user-1000.journal
-rw-r-+ 1 root systemd-journal  8388608 Oct 23 19:56 user-1014.journal
-rw-r-+ 1 root systemd-journal  8388608 Oct 24 14:14 user-1015.journal
--

And here are our logs from the 24th October.

Le 01/02/2023 à 13:26, Freyja a écrit :

Hi greg,

--
❯ df /run
Filesystem 1K-blocks  Used Available Use% Mounted on
tmpfs    1629236  3732   1625504   1% /run
--

For /run/systemd/journal/socket this is another story.
The folder journal does not exist at all.

--
❯ ls -la /run/systemd/
total 0
drwxr-xr-x 17 root    root 400 Jan 31 16:12 .
drwxr-xr-x 37 root    root    1100 Feb  1 06:25 ..
drwxr-xr-x  2 root    root  40 Jan 31 10:45 
ask-password
drwx--  2 root    root  80 Jan 31 17:31 
ask-password-block

drwxr-xr-x  8 root    root 680 Jan 31 16:08 generator
drwxr-xr-x  4 root    root 360 Jan 31 16:08 
generator.late
drwxr-xr-x  3 root    root 160 Jan 31 10:45 
inaccessible
srw-rw-rw-  1 root    root   0 Jan 31 10:45 
io.system.ManagedOOM

drwxr-xr-x  2 root    root  40 Jan 31 10:45 machines
drwxr-xr-x  5 systemd-network systemd-network  100 Jan 31 10:45 netif
srwxrwxrwx  1 root    root   0 Jan 31 10:45 notify
srwxrwxrwx  1 root    root   0 Jan 31 10:45 private
drwxr-xr-x  2 root    root  40 Jan 31 10:45 seats
drwxr-xr-x  2 root    root  40 Jan 31 10:45 sessions
drwxr-xr-x  2 root    root  40 Jan 31 10:45 shutdown
drwxr-xr-x  2 root    root  40 Jan 31 10:45 system
drwx--  2 root    root  40 Jan 31 10:45 unit-root
drwxr-xr-x  2 root    root    2060 Feb  1 13:09 units
drwxr-xr-x  2 root    root  60 Jan 31 10:45 userdb
drwxr-xr-x  2 root    root  40 Jan 31 10:45 users
--

I don't know why :/


Le 01/02/2023 à 13:22, Greg Wooledge a écrit :

On Wed, Feb 01, 2023 at 11:15:58AM +0100,deb...@sioban.net  wrote:

"journalctl -e" ends the 24th of October.
❯ journalctl -b
-- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon 2022-10-24
14:14:33 CEST. --
-- No entries --
❯ systemctl start systemd-journald.service
A dependency job for systemd-journald.service failed. See 'journalctl -xe'
for details.

On my system:

unicorn:~$ systemctl cat systemd-journald.service | grep -i require
Requires=systemd-journald.socket
# /proc//exe requires this capability. Thus if this capability is missing

unicorn:~$ systemctl cat systemd-journald.socket | grep Listen
ListenDatagram=/run/systemd/journal/socket
ListenStream=/run/systemd/journal/stdout

For you, that's at least *two* socket services that appear to be failing.
I suspect you've got something broken that's preventing these sockets
from being created, or being accessed.

Man, what I wouldn't give for a nice, clear "/run/systemd/journal/socket:
Permission denied" or "... No such file or directory" error!

/run is supposed to be mounted as a separate file system, entirely in
memory:

unicorn:~$ df /run
Filesystem 1K-blocks  Used Available Use% Mounted on
tmpfs1215596  1924   1213672   1% /run

And the ownerships and permissions on this socket are:

unicorn:~$ namei -l /run/systemd/journal/socket
f: /run/systemd/journal/socket
drwxr-xr-x root root /
drwxr-xr-x root root run
drwxr-xr-x root root systemd
drwxr-xr-x root root journal
srw-rw-rw- root root socket

If you've got anything different, that would be important.

Re: Syslog/Rsyslog/Systemctl issue

[Freyja]

Hi greg,

--
❯ df /run
Filesystem 1K-blocks  Used Available Use% Mounted on
tmpfs    1629236  3732   1625504   1% /run
--

For /run/systemd/journal/socket this is another story.
The folder journal does not exist at all.

--
❯ ls -la /run/systemd/
total 0
drwxr-xr-x 17 root    root 400 Jan 31 16:12 .
drwxr-xr-x 37 root    root    1100 Feb  1 06:25 ..
drwxr-xr-x  2 root    root  40 Jan 31 10:45 ask-password
drwx--  2 root    root  80 Jan 31 17:31 
ask-password-block

drwxr-xr-x  8 root    root 680 Jan 31 16:08 generator
drwxr-xr-x  4 root    root 360 Jan 31 16:08 
generator.late

drwxr-xr-x  3 root    root 160 Jan 31 10:45 inaccessible
srw-rw-rw-  1 root    root   0 Jan 31 10:45 
io.system.ManagedOOM

drwxr-xr-x  2 root    root  40 Jan 31 10:45 machines
drwxr-xr-x  5 systemd-network systemd-network  100 Jan 31 10:45 netif
srwxrwxrwx  1 root    root   0 Jan 31 10:45 notify
srwxrwxrwx  1 root    root   0 Jan 31 10:45 private
drwxr-xr-x  2 root    root  40 Jan 31 10:45 seats
drwxr-xr-x  2 root    root  40 Jan 31 10:45 sessions
drwxr-xr-x  2 root    root  40 Jan 31 10:45 shutdown
drwxr-xr-x  2 root    root  40 Jan 31 10:45 system
drwx--  2 root    root  40 Jan 31 10:45 unit-root
drwxr-xr-x  2 root    root    2060 Feb  1 13:09 units
drwxr-xr-x  2 root    root  60 Jan 31 10:45 userdb
drwxr-xr-x  2 root    root  40 Jan 31 10:45 users
--

I don't know why :/


Le 01/02/2023 à 13:22, Greg Wooledge a écrit :

On Wed, Feb 01, 2023 at 11:15:58AM +0100,deb...@sioban.net  wrote:

"journalctl -e" ends the 24th of October.
❯ journalctl -b
-- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon 2022-10-24
14:14:33 CEST. --
-- No entries --
❯ systemctl start systemd-journald.service
A dependency job for systemd-journald.service failed. See 'journalctl -xe'
for details.

On my system:

unicorn:~$ systemctl cat systemd-journald.service | grep -i require
Requires=systemd-journald.socket
# /proc//exe requires this capability. Thus if this capability is missing

unicorn:~$ systemctl cat systemd-journald.socket | grep Listen
ListenDatagram=/run/systemd/journal/socket
ListenStream=/run/systemd/journal/stdout

For you, that's at least *two* socket services that appear to be failing.
I suspect you've got something broken that's preventing these sockets
from being created, or being accessed.

Man, what I wouldn't give for a nice, clear "/run/systemd/journal/socket:
Permission denied" or "... No such file or directory" error!

/run is supposed to be mounted as a separate file system, entirely in
memory:

unicorn:~$ df /run
Filesystem 1K-blocks  Used Available Use% Mounted on
tmpfs1215596  1924   1213672   1% /run

And the ownerships and permissions on this socket are:

unicorn:~$ namei -l /run/systemd/journal/socket
f: /run/systemd/journal/socket
drwxr-xr-x root root /
drwxr-xr-x root root run
drwxr-xr-x root root systemd
drwxr-xr-x root root journal
srw-rw-rw- root root socket

If you've got anything different, that would be important.

Re: Syslog/Rsyslog/Systemctl issue

[Greg Wooledge]

On Wed, Feb 01, 2023 at 11:15:58AM +0100, deb...@sioban.net wrote:
> "journalctl -e" ends the 24th of October.

> ❯ journalctl -b
> -- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon 2022-10-24
> 14:14:33 CEST. --
> -- No entries --

> ❯ systemctl start systemd-journald.service
> A dependency job for systemd-journald.service failed. See 'journalctl -xe'
> for details.

On my system:

unicorn:~$ systemctl cat systemd-journald.service | grep -i require
Requires=systemd-journald.socket
# /proc//exe requires this capability. Thus if this capability is missing

unicorn:~$ systemctl cat systemd-journald.socket | grep Listen
ListenDatagram=/run/systemd/journal/socket
ListenStream=/run/systemd/journal/stdout

For you, that's at least *two* socket services that appear to be failing.
I suspect you've got something broken that's preventing these sockets
from being created, or being accessed.

Man, what I wouldn't give for a nice, clear "/run/systemd/journal/socket:
Permission denied" or "... No such file or directory" error!

/run is supposed to be mounted as a separate file system, entirely in
memory:

unicorn:~$ df /run
Filesystem 1K-blocks  Used Available Use% Mounted on
tmpfs1215596  1924   1213672   1% /run

And the ownerships and permissions on this socket are:

unicorn:~$ namei -l /run/systemd/journal/socket
f: /run/systemd/journal/socket
drwxr-xr-x root root /
drwxr-xr-x root root run
drwxr-xr-x root root systemd
drwxr-xr-x root root journal
srw-rw-rw- root root socket

If you've got anything different, that would be important.

Re: ASCII formatting for plain text email

[Jonathan Dowland]

On Tue, Jan 31, 2023 at 07:49:18PM +0100, Pierre Willaime wrote:

I would like to format plain text emails to increase readability and
information separation. The idea is to go beyond markdown and to have
more visible elements.


If you do this, please have some consideration for how screen readers
will handle your message. I am not an expert on them (and so I ask you
go and look elsewhere for information/confirmation) but I believe if you
use symbols which have a semantic meaning other than for drawing boxes,
you risk your message being unintelligible to screen reader users. On
the other hand there are unicode symbols that are specifically for
drawing boxes which, and again I stress please fact-check me here, will
not cause such problems.


--
Please do not CC me for listmail.

👱🏻  Jonathan Dowland
✎j...@debian.org
🔗   https://jmtd.net

Re: Web page management. Was: Re: Debian release criteria.

[Max Nikulin]

On 30/01/2023 10:32, Celejar wrote:

For those who may not be aware, the developer of uBlock Origin and
uMatrix, Raymond Hill, has ceased work on uMatrix:

https://github.com/uBlockOrigin/uMatrix-issues/issues/291#issuecomment-694988696


It is really sour. On a lot of sites, including github, high CPU usage 
in the case of disabled JavaScript caused by loading animations: CSS or 
gifs.

Re: Who pays Debian developement

[Pierre-Elliott Bécue]

Miles Fidelman  wrote on 31/01/2023 at 
20:53:46+0100:

> rhkra...@gmail.com wrote:
>> On Tuesday, January 31, 2023 05:34:49 AM Pierre-Elliott Bécue wrote:
>>> There are also individuals making such donations.
>>>
>>> That being said, these donations can't be used to pay a Developer for
>>> its work in the project.
>
> That being said, there are certainly developers out there, who are
> working on company time, to make contributions to Debian (and other)
> open source software.  And folks at places that host the work - like
> the OSU OSL - are certainly drawing salaries from their parent
> institutions.  I expect a lot of that work is grant funded.

I think you need to re-read my mail you're replying to.
-- 
PEB

Re: Who pays Debian developement

[Pierre-Elliott Bécue]

Hi,

rhkra...@gmail.com wrote on 31/01/2023 at 19:50:06+0100:

> On Tuesday, January 31, 2023 05:34:49 AM Pierre-Elliott Bécue wrote:
>> There are also individuals making such donations.
>> 
>> That being said, these donations can't be used to pay a Developer for
>> its work in the project. 
>
> Well that may be true in the case of certain Debian organizations, but
> I doubt there is any "universal" rule that would keep me from making a
> donation to some Debian organization specifically for the purpose of
> paying a developer for developing (or maintaining), for example, some
> specific package / software.

What is a Debian Organization?

-- 
PEB

Re: Syslog/Rsyslog/Systemctl issue

[debian]

Hi max,

"journalctl -e" ends the 24th of October.

--
Oct 24 14:14:33 shax systemd[1]: Stopped Update UTMP about System 
Boot/Shutdown.

Oct 24 14:14:33 shax systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Oct 24 14:14:33 shax systemd[1]: Stopped Create Volatile Files and 
Directories.
Oct 24 14:14:33 shax systemd[1]: Stopping Flush Journal to Persistent 
Storage...

--

--
❯ journalctl -b
-- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon 
2022-10-24 14:14:33 CEST. --

-- No entries --
--

systemd-journald.service reports error but unclear :/

--
❯ systemctl status systemd-journald.service
● systemd-journald.service - Journal Service
 Loaded: loaded (/lib/systemd/system/systemd-journald.service; static)
 Active: inactive (dead)
TriggeredBy: ● systemd-journald-dev-log.socket
 ● systemd-journald-audit.socket
 ● systemd-journald.socket
   Docs: man:systemd-journald.service(8)
 man:journald.conf(5)
--

--
❯ systemctl start systemd-journald.service
A dependency job for systemd-journald.service failed. See 'journalctl 
-xe' for details.

--

Le 01/02/2023 à 11:05, Max Nikulin a écrit :

On 31/01/2023 16:57, deb...@sioban.net wrote:

I'm contacting you because I'm clueless on what's happening.
Basically my issue is I don't have logs anymore :/

...

 > systemctl start rsyslog.service
A dependency job for rsyslog.service failed. See 'journalctl -xe' for 
details.



❯systemctl --failed
   UNIT    LOAD   ACTIVE SUB DESCRIPTION

...

● systemd-journald.socket loaded failed failed Journal Socket


This line looks suspicious. I would ensure at first that journald is 
running correctly. Rsyslog likely receives logs from journald.


Are logs available through the following commands (last entries and 
for current boot)?


journalctl -e
journalctl -b

Does

systemctl status systemd-journald.service

reports any errors?

Re: ASCII formatting for plain text email

[Max Nikulin]

On 01/02/2023 01:49, Pierre Willaime wrote:


I would like to format plain text emails to increase readability and
information separation.


The following message is result of ascii export from Emacs Org mode, the 
source file is attached. Export backend is customizable.


https://list.orgmode.org/87bktn8f3y@gnu.org/
[ANN] EmacsConf 2022 Call for Participation. Sun, 17 Jul 2022 20:00:01 -0400

Re: Syslog/Rsyslog/Systemctl issue

[Max Nikulin]

On 31/01/2023 16:57, deb...@sioban.net wrote:

I'm contacting you because I'm clueless on what's happening.
Basically my issue is I don't have logs anymore :/

...

 > systemctl start rsyslog.service
A dependency job for rsyslog.service failed. See 'journalctl -xe' for 
details.



❯systemctl --failed
   UNIT    LOAD   ACTIVE SUB    DESCRIPTION

...

● systemd-journald.socket loaded failed failed Journal Socket


This line looks suspicious. I would ensure at first that journald is 
running correctly. Rsyslog likely receives logs from journald.


Are logs available through the following commands (last entries and for 
current boot)?


journalctl -e
journalctl -b

Does

systemctl status systemd-journald.service

reports any errors?

Re: Instalación de tor mediante terminal

[Alex]

On Wed, 1 Feb 2023 05:23:35 +
tvcasaraf1 tvcadaraf1  wrote:

> Buenos días, soy usuario de Debian recientemente aunque anteriormente
> he usado ubuntu y Linux mint. Estoy intentando instalar tor y otros
> paquetes mediante terminal con usuario root y no funciona con dpkg -i
> ni con sido apt-get instalo. Me gustaría saber cómo instalar paquetes
> nuevos mediante terminal o snap que tampoco logro instalar.  Gracias
> de antemano.

Deberias poder instalarlo con apt-get install tor.

Tor project, sin embargo, recomiendan que lo descarges directamente
desde su repositorio: https://support.torproject.org/apt/

-- 
Current PGP KeyID: 11ADE4393600C1BDFFCBC0A598DE15942B08CA00

https://blueselene.com/pgp-archive/11ADE4393600C1BDFFCBC0A598DE15942B08CA00/key.pub

For up-to-date information on my crypto keys see
https://blueselene.com/crypto.html


pgpwqWTnlA1Rz.pgp
Description: OpenPGP digital signature