* [ISSUE] Metalog bleeds onto tty1
@ 2023-08-18 9:01 shahab-vahedi
2023-08-18 9:02 ` shahab-vahedi
` (13 more replies)
0 siblings, 14 replies; 15+ messages in thread
From: shahab-vahedi @ 2023-08-18 9:01 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]
New issue by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/45653
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_1 x86_64 GenuineIntel uptodate hold rrrmdDDFFFFFF
### Package(s) Affected
metalog-20230719_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
TTY1 console should remain intact from the system level logs.
Version `20220214` is fine. I noticed this behavior on `20230719`. I never tried version `20230707` though.
### Actual behaviour
Below is a sample output of my default virtual console (`agetty-tty1`). What I do is:
1. Login to the system which results in logs being shown on the output.
2. doing a user level command (`ls`) which goes OK.
3. Repeating step 2 command with privilege (`doas`) which results in system level logging that ends up in the console.
4. Disabling the `metalog` service.
5. Repeating step 3 without any pollution.
```
Login: edie
Password:
Aug 18 09:55:11 [login] pam_unix(login:session): session opened for user edie(uid=1000) by edie(uid=0)
Aug 18 09:55:11 [login] pam_unix(login:session): session opened for user edie(uid=1000) by edie(uid=0)
Aug 18 09:55:11 [kernel] [ 2540.865203] elogind-daemon[1779]: New session 4 of user edie.
Last login: Fri Aug 18 09:46:38 on tty1
Aug 18 09:55:11 [login] LOGIN ON tty1 BY edie
Aug 18 09:55:11 [login] LOGIN ON tty1 BY edie
$ ls
a b
$ doas ls
doas (edie@laptop) password:
Aug 18 09:58:27 [doas] pam_unix(doas:session): session opened for user root(uid=0) by edie(uid=1000)
Aug 18 09:58:27 [doas] edie ran command ls as root from /home/edie/test
a b
Aug 18 09:58:27 [doas] pam_unix(doas:session): session closed for user root
$ doas sv stop metalog
Aug 18 09:58:55 [doas] pam_unix(doas:session): session opened for user root(uid=0) by edie(uid=1000)
Aug 18 09:58:55 [doas] edie ran command sv stop metalog as root from /home/edie/test
ok: down: metalog: 0s, normally up
$ doas ls
a b
```
### Steps to reproduce
1. Have the service enabled.
2. Drop into your default virtual console (agetty-tty1).
3. You're going to immediately see all the system logs polluted into the console's output.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
@ 2023-08-18 9:02 ` shahab-vahedi
2023-08-18 10:05 ` sgn
` (12 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: shahab-vahedi @ 2023-08-18 9:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 290 bytes --]
New comment by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1683597327
Comment:
@jovanlanik Could this be related to your earlier [comment](https://github.com/void-linux/void-packages/pull/44912#issuecomment-1625625388)?
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
2023-08-18 9:02 ` shahab-vahedi
@ 2023-08-18 10:05 ` sgn
2023-08-18 10:40 ` jovanlanik
` (11 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: sgn @ 2023-08-18 10:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 200 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1683678660
Comment:
Seems like the correct action is drop `-v` from the service.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
2023-08-18 9:02 ` shahab-vahedi
2023-08-18 10:05 ` sgn
@ 2023-08-18 10:40 ` jovanlanik
2023-08-18 15:05 ` shahab-vahedi
` (10 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: jovanlanik @ 2023-08-18 10:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
New comment by jovanlanik on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1683718365
Comment:
Yes, I don't see a reason to leave it as default. According to metalog it's for debugging:
```
-v, --verbose
Run in verbose mode (useful for debugging behavior).
```
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (2 preceding siblings ...)
2023-08-18 10:40 ` jovanlanik
@ 2023-08-18 15:05 ` shahab-vahedi
2023-08-18 15:06 ` shahab-vahedi
` (9 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: shahab-vahedi @ 2023-08-18 15:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
New comment by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1684054640
Comment:
I've removed the `-v` from my setup and the problem still persists.
```
--- /etc/sv/metalog/run.orig 2023-08-18 17:00:30.902350525 +0200
+++ /etc/sv/metalog/run 2023-08-18 17:01:13.284474084 +0200
@@ -1,4 +1,4 @@
#!/bin/sh
exec 1>&2
-[ -r conf ] && . ./conf
-exec metalog ${OPTS=-v}
+#[ -r conf ] && . ./conf
+exec metalog
```
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (3 preceding siblings ...)
2023-08-18 15:05 ` shahab-vahedi
@ 2023-08-18 15:06 ` shahab-vahedi
2023-08-21 8:28 ` shahab-vahedi
` (8 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: shahab-vahedi @ 2023-08-18 15:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
New comment by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1684054640
Comment:
I've removed the `-v` from my setup and the problem still persists.
```
--- /etc/sv/metalog/run.orig
+++ /etc/sv/metalog/run
@@ -1,4 +1,4 @@
#!/bin/sh
exec 1>&2
-[ -r conf ] && . ./conf
-exec metalog ${OPTS=-v}
+#[ -r conf ] && . ./conf
+exec metalog
```
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (4 preceding siblings ...)
2023-08-18 15:06 ` shahab-vahedi
@ 2023-08-21 8:28 ` shahab-vahedi
2023-08-21 8:28 ` shahab-vahedi
` (7 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: shahab-vahedi @ 2023-08-21 8:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
New comment by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1685884112
Comment:
I found the culprit: The `exec 2>&1` added by this [commit](https://github.com/void-linux/void-packages/commit/351646d5bd739c5767561058967af455834ffc3b). I don't know what the rationale behind that commit was, but undoing it, fixes the problem for me.
```
--- /etc/sv/metalog/run.orig
+++ /etc/sv/metalog/run
@@ -1,5 +1,4 @@
#!/bin/sh
-exec 2>&1
exec 1>&2
[ -r conf ] && . ./conf
exec metalog ${OPTS=-v}
```
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (5 preceding siblings ...)
2023-08-21 8:28 ` shahab-vahedi
@ 2023-08-21 8:28 ` shahab-vahedi
2023-08-21 8:28 ` shahab-vahedi
` (6 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: shahab-vahedi @ 2023-08-21 8:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
New comment by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1684054640
Comment:
I've removed the `-v` from my setup and the problem still persists.
```
--- /etc/sv/metalog/run.orig
+++ /etc/sv/metalog/run
@@ -1,4 +1,4 @@
#!/bin/sh
exec 2>&1
exec 1>&2
-[ -r conf ] && . ./conf
-exec metalog ${OPTS=-v}
+#[ -r conf ] && . ./conf
+exec metalog
```
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (6 preceding siblings ...)
2023-08-21 8:28 ` shahab-vahedi
@ 2023-08-21 8:28 ` shahab-vahedi
2023-08-21 15:48 ` aryandb
` (5 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: shahab-vahedi @ 2023-08-21 8:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 217 bytes --]
New comment by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1684054640
Comment:
I've removed the `-v` from my setup and the problem still persists.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (7 preceding siblings ...)
2023-08-21 8:28 ` shahab-vahedi
@ 2023-08-21 15:48 ` aryandb
2023-08-21 15:48 ` aryandb
` (4 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: aryandb @ 2023-08-21 15:48 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
New comment by aryandb on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1686582742
Comment:
I added `-B` option to daemonized it and my problem did go away.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (8 preceding siblings ...)
2023-08-21 15:48 ` aryandb
@ 2023-08-21 15:48 ` aryandb
2023-08-26 20:41 ` gc-user
` (3 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: aryandb @ 2023-08-21 15:48 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
New comment by aryandb on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1686582742
Comment:
I added `-B` option to daemonized it and my problem did go away.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (9 preceding siblings ...)
2023-08-21 15:48 ` aryandb
@ 2023-08-26 20:41 ` gc-user
2023-08-31 15:46 ` shahab-vahedi
` (2 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: gc-user @ 2023-08-26 20:41 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1694497960
Comment:
Thanks for finding the cause (and the solution)!
And yes, that error was there in 20230707, too. I was hoping at the time that the 20230719 was the fix for that bug, but it wasn't so I went back to 20220214.
I didn't report the bug, because I thought it was just me / my system / some "wrong setting" I made - and also, because it would have been a bit hard for me to describe the phenomenon in a way a dev would understand what I mean... :-)
I edited the file as per your post and will see during the next boot if it works for me too, but I'll assume it will.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (10 preceding siblings ...)
2023-08-26 20:41 ` gc-user
@ 2023-08-31 15:46 ` shahab-vahedi
2023-08-31 15:47 ` [ISSUE] [CLOSED] " shahab-vahedi
2023-08-31 17:52 ` gc-user
13 siblings, 0 replies; 15+ messages in thread
From: shahab-vahedi @ 2023-08-31 15:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
New comment by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1701292661
Comment:
> I edited the file as per your post and will see during the next boot if it works for me too, but I'll assume it will.
Now the fix is [merged](https://github.com/void-linux/void-packages/commit/b55cfee29117803250d48746b9f71bf5dc13687d). The new package `metalog-20230719_2` should work fine.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [ISSUE] [CLOSED] Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (11 preceding siblings ...)
2023-08-31 15:46 ` shahab-vahedi
@ 2023-08-31 15:47 ` shahab-vahedi
2023-08-31 17:52 ` gc-user
13 siblings, 0 replies; 15+ messages in thread
From: shahab-vahedi @ 2023-08-31 15:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]
Closed issue by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/45653
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_1 x86_64 GenuineIntel uptodate hold rrrmdDDFFFFFF
### Package(s) Affected
metalog-20230719_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
No to the best of my knowledge.
### Expected behaviour
TTY1 console should remain intact from the system level logs.
Version `20220214` is fine. I noticed this behavior on `20230719`. I never tried version `20230707` though.
### Actual behaviour
Below is a sample output of my default virtual console (`agetty-tty1`). What I do is:
1. Login to the system which results in logs being shown on the output.
2. Perform a user level command (`ls`) which goes OK.
3. Repeating step 2 command with privilege (`doas`) which results in system level logging that ends up in the console.
4. Disabling the `metalog` service.
5. Repeating step 3 without any pollution.
```
Login: edie
Password:
Aug 18 09:55:11 [login] pam_unix(login:session): session opened for user edie(uid=1000) by edie(uid=0)
Aug 18 09:55:11 [login] pam_unix(login:session): session opened for user edie(uid=1000) by edie(uid=0)
Aug 18 09:55:11 [kernel] [ 2540.865203] elogind-daemon[1779]: New session 4 of user edie.
Last login: Fri Aug 18 09:46:38 on tty1
Aug 18 09:55:11 [login] LOGIN ON tty1 BY edie
Aug 18 09:55:11 [login] LOGIN ON tty1 BY edie
$ ls
a b
$ doas ls
doas (edie@laptop) password:
Aug 18 09:58:27 [doas] pam_unix(doas:session): session opened for user root(uid=0) by edie(uid=1000)
Aug 18 09:58:27 [doas] edie ran command ls as root from /home/edie/test
a b
Aug 18 09:58:27 [doas] pam_unix(doas:session): session closed for user root
$ doas sv stop metalog
Aug 18 09:58:55 [doas] pam_unix(doas:session): session opened for user root(uid=0) by edie(uid=1000)
Aug 18 09:58:55 [doas] edie ran command sv stop metalog as root from /home/edie/test
ok: down: metalog: 0s, normally up
$ doas ls
a b
```
### Steps to reproduce
1. Have the service enabled.
2. Drop into your default virtual console (`agetty-tty1`).
3. You're going to immediately see all the system logs polluted into the console's output.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: Metalog bleeds onto tty1
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
` (12 preceding siblings ...)
2023-08-31 15:47 ` [ISSUE] [CLOSED] " shahab-vahedi
@ 2023-08-31 17:52 ` gc-user
13 siblings, 0 replies; 15+ messages in thread
From: gc-user @ 2023-08-31 17:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/45653#issuecomment-1701506933
Comment:
Thanks. I noticed the update among others during the day. Haven't since rebooted, but I'm sure it's fine, just as the workaround worked fine.
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2023-08-31 17:52 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-18 9:01 [ISSUE] Metalog bleeds onto tty1 shahab-vahedi
2023-08-18 9:02 ` shahab-vahedi
2023-08-18 10:05 ` sgn
2023-08-18 10:40 ` jovanlanik
2023-08-18 15:05 ` shahab-vahedi
2023-08-18 15:06 ` shahab-vahedi
2023-08-21 8:28 ` shahab-vahedi
2023-08-21 8:28 ` shahab-vahedi
2023-08-21 8:28 ` shahab-vahedi
2023-08-21 15:48 ` aryandb
2023-08-21 15:48 ` aryandb
2023-08-26 20:41 ` gc-user
2023-08-31 15:46 ` shahab-vahedi
2023-08-31 15:47 ` [ISSUE] [CLOSED] " shahab-vahedi
2023-08-31 17:52 ` gc-user
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).