On Sat, Feb 17 2024 at 01:34:05 PM, Lothar Braun wrote:
> Hi,
>
> I'm debugging a permission problem with the log files created by
> minidlna in /var/log/minidlna. I'm trying to use a different username
> to run minidlna and do not use the default user account minidlna.
On Sat, Feb 17, 2024 at 01:34:05PM +0100, Lothar Braun wrote:
> I'm debugging a permission problem with the log files created by minidlna in
> /var/log/minidlna. I'm trying to use a different username to run minidlna and
> do not use the default user account minidlna. The
On 2023-12-04 13:33:33 +0100, Vincent Lefevre wrote:
> On 2023-12-04 11:46:23 +, Adam Weremczuk wrote:
> > Is it a good idea to move it from /run/log/journal to e.g. /var/journal-log?
> >
> > I can't find a suitable option in /etc/systemd/journald.conf
See the
On 2023-12-04 11:46:23 +, Adam Weremczuk wrote:
> Is it a good idea to move it from /run/log/journal to e.g. /var/journal-log?
>
> I can't find a suitable option in /etc/systemd/journald.conf
>
> I recently increased SystemMaxUse and RuntimeMaxUse which quickly filled up
On Mon, Dec 04, 2023 at 11:46:23AM +, Adam Weremczuk wrote:
> Is it a good idea to move it from /run/log/journal to e.g. /var/journal-log?
>
> I can't find a suitable option in /etc/systemd/journald.conf
If you want to enable persistent journal storage (which by the way
Hi all,
Is it a good idea to move it from /run/log/journal to e.g. /var/journal-log?
I can't find a suitable option in /etc/systemd/journald.conf
I recently increased SystemMaxUse and RuntimeMaxUse which quickly filled
up all space.
I didn't realise that our cloud provider decide
eception
#module(load="imtcp")
#input(type="imtcp" port="514")
###
GLOBAL DIRECTIVES
###
#
# Set the default permissions for all log files.
#
$FileOwner root
$FileGroup adm
$FileCreateMode 0640
$DirCreateM
atch to work
> properly.
rsyslogd.conf controls what logfiles rsyslogd would generate:
*.* -/var/log/syslog
auth,authpriv.* /var/log/auth.log
cron.* /var/log/cron.log
daemon.*,local7.* -/var/log/daemon.log
kern.* -/var/lo
On Tue, 21 Nov 2023, John Covici wrote:
> hmmm, I looked at the release notes, but it does not say how to
> restore the old behavior, it just says many files are no longer
> necessary and lists them. I am using logwatch and that program seems
> to be effected, I would be OK, if I could get logwat
eb John Covici:
> > > Hi. I am using bookworm with latest updates and /var/log/syslog is
> > > empty, even though rsyslog is runniing. I am also using logwatch and
> > > not getting at least some responses I should get such as fail2ban.
> > > These may be sepa
Am 21.11.2023 um 05:15:24 Uhr schrieb John Covici:
> hmmm, I looked at the release notes, but it does not say how to
> restore the old behavior, it just says many files are no longer
> necessary and lists them.
Please post you syslog configuration.
:35 -0500,
Christoph Brinkhaus wrote:
>
> [1 ]
> Am Mon, Nov 20, 2023 at 05:01:50PM -0500 schrieb John Covici:
> > Hi. I am using bookworm with latest updates and /var/log/syslog is
> > empty, even though rsyslog is runniing. I am also using logwatch and
> > not gettin
Am Mon, Nov 20, 2023 at 05:01:50PM -0500 schrieb John Covici:
> Hi. I am using bookworm with latest updates and /var/log/syslog is
> empty, even though rsyslog is runniing. I am also using logwatch and
> not getting at least some responses I should get such as fail2ban.
> These may
Hi. I am using bookworm with latest updates and /var/log/syslog is
empty, even though rsyslog is runniing. I am also using logwatch and
not getting at least some responses I should get such as fail2ban.
These may be separate problems, but any help on those would be
appreciated. I saw a previous
at happening. If sudo will
> log, it logs the names and values of any environment you specify on
> its command line.
>
> Your options as far as I am aware:
Another (gross) one:
- Abuse variables that start with LC_, as sudo on Debian is by
default configured to preserve these. So yo
ed. How
> to change this?
You can either run "sudo -E" to push the entire environment through without
echoing any values in the sudo log, or play some games by re-invoking the
script with a clean environment. My environment with the BORG variables:
me% export BORG_REPO=/pa
loggued. How
> to change this ?
I don't think there is a way to stop that happening. If sudo will
log, it logs the names and values of any environment you specify on
its command line.
Your options as far as I am aware:
- Preserve your entire environment with sudo --preserve-env (no
spe
I use a script to run borg backup. For it to be able to backup files
that only root may read, i use sudo --preserv-env=BORG_REPO,BORG_PASSPHRASE.
However I see that in the logs the VALUE of the env variable is loggued.
How to change this ?
to an Elo
USB touchscreen monitor. These 2 systems log continuously in Xorg.0.log
filling up the hard drive at a rate of ~1MB/min. Please see attached file
for an excerpt of the content dumped into Xorg.0.log.
Can anyone help me understand what's happening and how to fix/prevent this?
D
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
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
> incompati
d (on the ssh server machine)
also affected by authentication delays? This apparently suggests a
PAM issue."
In answer yes su on the ssh machine also has these delays. It is
looking like a pam issue.
"1. "I found that PAM was reading the file /var/log/btmp, which had
become
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:
https://unix.stackexchange.com/questions/673153/sshd-what-are-the-practical-e
u ssh from the other machine? Don't
forget to specify target port (with -p1234)
If PAM-related, then answers at the above link suggest:
1. "I found that PAM was reading the file /var/log/btmp, which had become huge
as a result of people trying to brute-force my server. This was lead
> 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
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
Le 18 juin 2023 Paul Gerdes a écrit :
> i get these messages:
> "grep: /var/log/Xorg.*: No such file or directory"
> "grep: /var/log/Xorg: No such file or directory"
>
> looks like there is no log file for X11
Did you also try to start X with startx from
On 2023-06-17, Paul Gerdes wrote:
> Hi i have a problem with Debian 12 after Installation.
> Every time i try to log in to the Desktop Environment or WM my Screen goes
> black. The PC completely freezes and i cant switch to another TTY.
Did you check X logs ? With something like
gre
Hi i have a problem with Debian 12 after Installation.
Every time i try to log in to the Desktop Environment or WM my Screen goes
black. The PC completely freezes and i cant switch to another TTY.
I reinstalled Debian 12 a few times via netinstall. Tried different Desktop
Environments and WMs
On 4/13/23, Lee wrote:
> you should probably start off with
> https://archive.nanog.org/sites/default/files/10_Roisman_Traceroute.pdf
> A Practical Guide to (Correctly)
> Troubleshooting with Traceroute
thank you, lbrtchx
On 4/12/23, Albretch Mueller wrote:
> I have found a few examples and "explanations" but in the cases of
> the examples I have seen by other people, like:
>
> https://serverfault.com/questions/733005/what-does-having-mean-in-the-command-traceroute-and-how-can-you-cope-wit
>
> It is not with ever
On 4/12/23, debian-u...@howorth.org.uk wrote:
> I was playing with the addresses listed by Albretch ...
On 4/12/23, David Wright wrote:
> After googling them, I gave Moxee a call. They answer to a subtly
> different name, but it's the same business: a Canadian/US company
> that's been family-own
On Wed 12 Apr 2023 at 20:18:19 (+0100), debian-u...@howorth.org.uk wrote:
> I was playing with the addresses listed by Albretch and found that
> 199.254.252.1 is interesting. whois says it belongs to "Alexandria Sash
> & Door (ASD-1)" and
> https://opencorporates.com/companies/us_wa/601161047 (via
On 13.04.2023 00:00, Albretch Mueller wrote:
Yes, but should it happen on every hop? In my case it happens while I
am trying to reach every site and from wherever I have the chance to
get some relatively decent Internet access?
There is a chance your trace packets were filtered (rate-limited),
Greg Wooledge wrote:
> On Wed, Apr 12, 2023 at 05:37:32PM +, Albretch Mueller wrote:
> > It is not with every site and it is mostly with one hop.
>
> > $ traceroute google.com
> > traceroute to google.com (172.217.0.174), 30 hops max, 60 byte
> > packets 1 _gateway (199.83.128.1) 6.687 m
On 4/12/23, Greg Wooledge wrote:
> unicorn:~$ traceroute www.google.com
> traceroute to www.google.com (142.250.190.4), 30 hops max, 60 byte packets
> 1 routerlogin.net (10.0.0.1) 0.413 ms 0.355 ms 0.415 ms
> 2 65-131-222-254.mnfd.centurylink.net (65.131.222.254) 38.070 ms 39.776
> ms 36
On Wed, Apr 12, 2023 at 05:37:32PM +, Albretch Mueller wrote:
> It is not with every site and it is mostly with one hop.
> $ traceroute google.com
> traceroute to google.com (172.217.0.174), 30 hops max, 60 byte packets
> 1 _gateway (199.83.128.1) 6.687 ms 6.660 ms 6.683 ms
> 2 199.83.
On Wed, Apr 12, 2023 at 05:37:32PM +, Albretch Mueller wrote:
> I have found a few examples and "explanations" but in the cases of
> the examples I have seen by other people, like:
Quoth the man page:
This program attempts to trace the route an IP packet would
follow to some internet hos
Le 12 avril 2023 Albretch Mueller a écrit :
> It is not with every site and it is mostly with one hop. I my case it
> is with all sites and once the packets reach the web (from hop 5 to
> 30), from wherever I connect to the Internet. Why would that happen
> and why would that -consistently- "happ
I have found a few examples and "explanations" but in the cases of
the examples I have seen by other people, like:
https://serverfault.com/questions/733005/what-does-having-mean-in-the-command-traceroute-and-how-can-you-cope-wit
It is not with every site and it is mostly with one hop. I my ca
On Mon, Feb 27, 2023 at 09:23:06AM -0300, Eduardo M KALINOWSKI wrote:
[...]
> Maybe putting a tiny tinfoil hat on the power cable?
tiny tinfoil ♥
Cheers
-
t
signature.asc
Description: PGP signature
On 26/02/2023 18:56, Albretch Mueller wrote:
I started using another power cable and so far so good, but I would
not be too happy too soon. It may sound more than half way off to you,
but it is physically possible and it has been actually demonstrated
that "they" have been hacking into computer
On Sun, Feb 26, 2023 at 09:56:46PM +, Albretch Mueller wrote:
> On 2/26/23, Stefan Monnier wrote:
> >> the drive has its own power cable and those kinds of failures have
> >> actually happened in research rooms in libraries [...]
> >Te problem is probably not coming from the electrical outle
On 2/26/23, Stefan Monnier wrote:
>> the drive has its own power cable and those kinds of failures have
>> actually happened in research rooms in libraries, which are rented by
>> VIPs for their own conferences ...; so, I doubt those electrical
>> outlets are also failing
>Te problem is probably
> [22565.451321] usb-storage 1-1:1.0: USB Mass Storage device detected
> [22565.451467] scsi host3: usb-storage 1-1:1.0
> [22566.457236] scsi 3:0:0:0: Direct-Access ST16000N M001G-2KK103
>PQ: 0 ANSI: 5
> [22566.457527] sd 3:0:0:0: Attached scsi generic sg2 type 0
IIUC you plug your dis
On 2/25/23 04:31, Albretch Mueller wrote:
On 2/25/23, to...@tuxteam.de wrote:
I can't make too much heads or tails of it, but I'd focus
my suspicions on the USB part. USB ports (both sides),
cable and especially the power source for the disk:
+1
does
it have a separate source, or does it
Albretch Mueller wrote:
> On 2/25/23, to...@tuxteam.de wrote:
> I am not using a USB enclosure per se, but a regular internal disk
> externally attached using a USB/power interface. I will test the USB
> cabling using a better looking, newer USB cable.
If you can swap the USB/SATA interface too
On 2/25/23, to...@tuxteam.de wrote:
> I can't make too much heads or tails of it, but I'd focus
> my suspicions on the USB part. USB ports (both sides),
> cable and especially the power source for the disk: does
> it have a separate source, or does it feed on the computer's
> USB?
the drive has
1
[22582.380548] XFS (sdb1): Unmounting Filesystem
[22582.380594] XFS (sdb1): log I/O error -5
[22582.380603] XFS (sdb1): xfs_do_force_shutdown(0x2) called from line
1211 of file fs/xfs/xfs_log.c. Return address = 9651f22d
[22582.380604] XFS (sdb1): Log I/O Error Detected. Shutting down filesy
On Sat, Feb 25, 2023 at 06:24:23AM +, Albretch Mueller wrote:
[...]
I can't make too much heads or tails of it, but I'd focus
my suspicions on the USB part. USB ports (both sides),
cable and especially the power source for the disk: does
it have a separate source, or does it feed on the compu
[22575.919197] XFS (sdb1): Ending recovery (logdev: internal)
[22575.932002] xfs filesystem being mounted at
/media/user/77d8da74-a690-481a-86d5-9beab5a8e842 supports timestamps
until 2038 (0x7fff)
[22582.368977] usb 1-1: USB disconnect, device number 21
[22582.380548] XFS (sdb1): Unmounting File
Am So., 14. Aug. 2022 um 16:42 Uhr schrieb Reco :
> whois, geoiplookup, even https://bgp.he.net .
> Whatever works, basically.
> Last one is my favorite as it shows all IP blocks assigned to AS.
> Really helpful with spammer nests such as outlook.com (AS8075) or
> DigitalOcean (AS14061).
>
> > Is
On 8/14/22, Matthias Böttcher wrote:
> Am So., 14. Aug. 2022 um 09:51 Uhr schrieb Reco :
>
>> Personally I don't use fail2ban for sshd. Because why bother with
>> userspace (written in python too, yuck) if the kernel does the same job?
>> I.e. block M$ AS, China Telecom AS and maybe add Eastern Eur
On Sun, 14 Aug 2022 16:07:03 +0200
Matthias Böttcher wrote:
> Am So., 14. Aug. 2022 um 09:51 Uhr schrieb Reco
> :
>
> > Personally I don't use fail2ban for sshd. Because why bother with
> > userspace (written in python too, yuck) if the kernel does the same
> > job? I.e. block M$ AS, China Telec
Hi.
On Sun, Aug 14, 2022 at 04:07:03PM +0200, Matthias Böttcher wrote:
> how do I block these ip ranges?
The usual way.
iptables -I INPUT -s -p tcp --dport 22 \
-m conntrack --ctstate NEW -j DROP
or, if the source IP is an actual IPv6 (a rare thing in my experience):
ip6tables
Am So., 14. Aug. 2022 um 09:51 Uhr schrieb Reco :
> Personally I don't use fail2ban for sshd. Because why bother with
> userspace (written in python too, yuck) if the kernel does the same job?
> I.e. block M$ AS, China Telecom AS and maybe add Eastern Europe to the
> mix, and you've just reduced t
Hi.
On Sun, Aug 14, 2022 at 09:16:25AM -0400, Stefan Monnier wrote:
> > In fact, I'd restrict allowed SSH algorithms like this:
> >
> > Ciphers chacha20-poly1...@openssh.com,aes256-...@openssh.com
> > MACs
> > hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,umac-128-...@
Hi.
On Sun, Aug 14, 2022 at 08:57:47AM +0200, Maurizio Caloro wrote:
> Thanks for you answer, yes add aggressive to mode, restart services and add
> to ssh_config
>
> Host *
> HostKeyAlgorithms +ssh-rsa,ssh-dss
> PubkeyAcceptedKeyTypes +ssh-rsa,ssh-dss
Please do not do this unles
On Sat, Aug 13, 2022 at 07:42:28PM +0200, Maurizio Caloro wrote:
>As /etc/fail2ban/filter.d/sshd.conf shows, "no matching host key type"
>messages are specifically ignored by Mode=normal.
>Try setting Mode=aggressive, it should catch those.
>
>Of course, DROPping ssh connections from AS28594 wou
Hi.
On Sat, Aug 13, 2022 at 07:42:28PM +0200, Maurizio Caloro wrote:
> how I can disable this?, I try solution with failban, but this want be
> help!?
>
> [sshd]
> Enable = true
> Mode = normal
As /etc/fail2ban/filter.d/sshd.conf shows, "no matching host key type"
messages are specifi
every 2-3 second this log will by appair inside auth log, and i cant place
this correctly from where this come?
Aug 13 19:25:26 Cruscotto sshd[257257]: Unable to negotiate with
200.218.251.153 port 34480: no matching host key type found. Their offer:
ecdsa-sha2-nistp256,ecdsa-sha2
* 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
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 editin
The dir /var/log/journal/ on my debian host increases quite quickly.
why this happens? Do you know how to suppress it?
Thanks.
On 2/25/22 17:34, Karel Gardas wrote:
hardware: amd64 + radeon R5? 230 + 2 monitors connected. One connected
to DVI, one to VGA. Monitor connected to VGA is on the left and rotated
to the portrait position.
- what I do to crash is:
- start Settings
- search for 'disp'
- select Display
t;
> you helped a lot. Indeed, I've moved all dot files and folders into
> backup and even problematic user is able to log in.
>
> However, first configuration step brings X11 to the knees, crashing and
> then I'm seeing login windows again. So I guess this is the r
Hi Cindy,
you helped a lot. Indeed, I've moved all dot files and folders into
backup and even problematic user is able to log in.
However, first configuration step brings X11 to the knees, crashing and
then I'm seeing login windows again. So I guess this is the real culpri
On 2/25/22, Karel Gardas wrote:
> On 2/25/22 13:29, Christian Britz wrote:
>> Hello Karel,
>>
>> please try it with a temporary clean profile.
>>
>
> thanks for the idea, indeed after creating a random new and clean user
> and attempt to log into the Plasma (X1
Hello Christian,
thanks for the idea, indeed after creating a random new and clean user
and attempt to log into the Plasma (X11) session I went in well.
On my problematic user I tried to rename some .cache and .config dirs to
remove possibility of corrupted config but this still does not
g into the X11/KDE-plasma.
> I simply log into, seeing KDE progress gear and then it returns back to
> login. My .xsession errors shows that KDE complains about connection to
> X server claiming perhaps this died.
>
> Anybody seen this? Is there any procedure how to better debug and re
Hello,
I'm using debian testing so not sure if this is the right ML, but after
Feb 24 update I'm no longer capable of logging into the X11/KDE-plasma.
I simply log into, seeing KDE progress gear and then it returns back to
login. My .xsession errors shows that KDE complains about
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
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 4096 Nov
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 owne
; > 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 /
&g
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
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 non-fr
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 direct
-ld / /var /etc /usr /var/lib /var/log
drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
drwxr-xr-x 132 root root 12288 Sep 29 09:34 /etc
drwxr-xr-x 14 root root 4096 Nov 11 2020 /usr
drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
drwxr-xr-x 50 root root 4096 Sep 27 19:28 /var/lib
drw
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
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 unconfigu
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
same
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
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.
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.
Tuxifan
Am 28. 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
>
&
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
On Sat 18 Sep 2021 at 08:43:50 (-0400), Greg Wooledge wrote:
> On Sat, Sep 18, 2021 at 12:54:36PM +0200, Roger Price wrote:
> > In site.local I found
> >
> > # The following is a space-separated list of where additional user home
> > # directories are stored, each must have a trailing '/'. Direc
On Sat, Sep 18, 2021 at 12:54:36PM +0200, Roger Price wrote:
> In site.local I found
>
> # The following is a space-separated list of where additional user home
> # directories are stored, each must have a trailing '/'. Directories added
> # here are appended to @{HOMEDIRS}. See tunables/home
On Sat, 18 Sep 2021, Klaus Singvogel wrote:
Roger Price wrote:
In Debian 11, evince has an appamor profile which floods the kernel log with
hundreds of messages of the style:
Not only at Debian 11, even Debian 10 has it.
[...]
(evince:2869): GVFS-WARNING **: 22:18:18.510: can't
Roger Price wrote:
> In Debian 11, evince has an appamor profile which floods the kernel log with
> hundreds of messages of the style:
Not only at Debian 11, even Debian 10 has it.
[...]
> (evince:2869): GVFS-WARNING **: 22:18:18.510: can't init metadata tree
> /mnt/home/rp
Hi.
On Fri, Sep 17, 2021 at 10:54:32PM +0200, Roger Price wrote:
> I solved the problem by switching to mupdf, but mupdf is not as complete as
> evince.
It's customary to add "YMMV" to such statements. Just saying.
> Is there some way of calming evince+appamor?
Pick whatever suits you:
In Debian 11, evince has an appamor profile which floods the kernel log with
hundreds of messages of the style:
[24216.325764] audit: type=1400 audit(1631892398.580:255): apparmor="DENIED"
operation="open" profile="/usr/bin/evince"
name="/mnt/home/rpr
I think this is some kind of parsing bug from the response from solr.
The number of pairs of errors returned is the same number of hits
received during the search. So if I do a search with 7 results turned
up, I get 7 pairs of errors.
Fixed with the following:
1) simplified config file by re
The bug I patched also threw a similar kind of error. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970692. But this
error is cropping up for every user on the system. A google search
turns up nothing on a uid other than '0'.
I don't know if this is another debian issue or a misconfig
I'm running debian bullseye. I've had issues running solr on debian in
the past due to some kind of bug. I was able to get solr working with
dovecot by upgrading the os.
After the upgrade, everything works perfectly fine and the search
feature in my client using solr now works. However, I get
On 15.08.21 15:46, Andrew M.A. Cater wrote:
I would suggest installing Debian 11 - just released - for two reasons:
Yes working with Bullseye.
happy weekend
Evelyn
OpenPGP_0x61776FA8E38403FB.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
On Sun, Aug 15, 2021 at 01:21:24PM +0200, Evelyn Pereira Souza wrote:
> On 15.08.21 10:52, to...@tuxteam.de wrote:
> > You also have a "2019 5k iMac"? Because that is very important in this
> > context.
>
> Here more details about my HW:
>
> # inxi -Fxz
> System:Host: norp Kernel: 4.19.0-17-a
On 15.08.21 10:52, to...@tuxteam.de wrote:
You also have a "2019 5k iMac"? Because that is very important in this
context.
Here more details about my HW:
# inxi -Fxz
System:Host: norp Kernel: 4.19.0-17-amd64 x86_64 bits: 64 compiler:
gcc v: 8.3.0
Console: tty 0 Distro: Debian
On 15.08.21 10:52, to...@tuxteam.de wrote:
On Sun, Aug 15, 2021 at 10:34:05AM +0200, Evelyn Pereira Souza wrote:
Hi
https://unix.stackexchange.com/questions/616926/debian-10-6-boots-to-black-screen-no-screens-foundee-in-log
same problem like this guy, but sadly no anser.
You also have a
1 - 100 of 2290 matches
Mail list logo
