Hi everyone and for people dropping by having the same issue.
The problem is *solved* \o/
The issue was: missing /run/systemd/journal/socket
What solved the problem:
- apt-get install --reinstall systemd systemd-sysv libsystemd0
dbus-user-session
- /run/systemd/journal/socket and
> I've tried they sent me back here :/
>
> Le 02/02/2023 à 17:06, debian-u...@howorth.org.uk a écrit :
> >> On 01/02/2023 21:48, Freyja wrote:
> >>> Instead of just creating the folders, I've reinstalled some
> >>> packages:
> >> I would consider complete reinstall (install from scratch). It
I need to look deeper in your recommendations, I will try them as soon
as I can.
Le 02/02/2023 à 17:28, songbird a écrit :
debian-u...@howorth.org.uk wrote:
...
Maybe it's worth asking on the systemd-devel mailing list?
did you reinstall rsyslog? did you purge the configs for it
(back
I've tried they sent me back here :/
Le 02/02/2023 à 17:06, debian-u...@howorth.org.uk a écrit :
On 01/02/2023 21:48, Freyja wrote:
Instead of just creating the folders, I've reinstalled some
packages:
I would consider complete reinstall (install from scratch). It may be
faster even for a
Hi,
Both are installed but when I try to remove them it want to remove too
many packages :/
--
❯ dpkg -l |grep selinux
ii libselinux1:amd64
3.1-3 amd64 SELinux
runtime shared libraries
--
--
❯ apt-get remove libselinux1
Reading package
Are you using SELinux or AppApparmor ?
Have you tried disabling it?
OpenPGP_signature
Description: OpenPGP digital signature
debian-u...@howorth.org.uk wrote:
...
> Maybe it's worth asking on the systemd-devel mailing list?
did you reinstall rsyslog? did you purge the configs for it
(back them up if needed)? when i remove a package i have been
having troubles with i often purge it instead of uninstalling
it.
you
> On 01/02/2023 21:48, Freyja wrote:
> > Instead of just creating the folders, I've reinstalled some
> > packages:
>
> I would consider complete reinstall (install from scratch). It may be
> faster even for a person having experience with systemd
> troubleshooting. Something low level is
Max Nikulin wrote:
> On 01/02/2023 21:48, Freyja wrote:
>> Instead of just creating the folders, I've reinstalled some packages:
>
> I would consider complete reinstall (install from scratch). It may be
> faster even for a person having experience with systemd troubleshooting.
> Something low
This is only a solution I'll look at as last resort.
There is too much work on that server.
But I agree it's something I was already thought of.
But we are not on Windows there, we should be able to do something.
The only time I had to do this is because dpkg was totally broken for an
unknown
Deleted the folder, restarted and back to square 1.
--
❯ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● dbus.socket loaded failed failed D-Bus System
Message Bus Socket
● syslog.socket loaded failed failed Syslog
On Thu, Feb 02, 2023 at 02:27:33PM +0100, Freyja wrote:
> This [reinstalling] is only a solution I'll look at as last resort.
> There is too much work on that server.
>
> But I agree it's something I was already thought of.
>
> But we are not on Windows there, we should be able to do something.
This is only a solution I'll look at as last resort.
There is too much work on that server.
But I agree it's something I was already thought of.
But we are not on Windows there, we should be able to do something.
The only time I had to do this is because dpkg was totally broken for an
unknown
On 01/02/2023 21:48, Freyja wrote:
Instead of just creating the folders, I've reinstalled some packages:
I would consider complete reinstall (install from scratch). It may be
faster even for a person having experience with systemd troubleshooting.
Something low level is affected.
However I
Freyja wrote:
...
> 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 --
if you are not concerned about keeping the last journals for
any reason i would remove the
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
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
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
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
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
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
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
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
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.
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
Le 31/01/2023 à 19:29, Greg Wooledge a écrit :
Requires=syslog.socket
This is the only part of it that looks like a "dependency". Maybe
this is the thing that's breaking? You can try
"systemctl status syslog.socket" and see if it gives anything useful.
Here is the result:
❯ systemctl
On Tue, Jan 31, 2023 at 05:22:23PM +0100, Sioban wrote:
> Here is the output.
>
> ❯ systemctl cat rsyslog.service
That looks exactly like mine. So that's probably fine.
> Requires=syslog.socket
This is the only part of it that looks like a "dependency". Maybe
this is the thing that's
Here is the output.
❯ systemctl cat rsyslog.service
# /lib/systemd/system/rsyslog.service
[Unit]
Description=System Logging Service
Requires=syslog.socket
Documentation=man:rsyslogd(8)
Documentation=man:rsyslog.conf(5)
Documentation=https://www.rsyslog.com/doc/
[Service]
Type=notify
On Tue, Jan 31, 2023 at 03:52:32PM +0100, deb...@sioban.net wrote:
> ❯ df /var/log /var/log/journal
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/md24 46096212 1620728 42101496 4% /var/log
> /dev/md24 46096212 1620728 42101496 4% /var/log
OK, not out of
Hi Greg,
I'm sorry, I was unsure what kind of logs to give, thanks for giving me some
instructions.
❯ df /var/log /var/log/journal
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md24 46096212 1620728 42101496 4% /var/log
/dev/md24 46096212 1620728 42101496 4%
On Tue, Jan 31, 2023 at 11:09:59AM +0100, deb...@sioban.net wrote:
>
> Le 31/01/2023 à 11:08, Nicolas George a écrit :
> > deb...@sioban.net (12023-01-31):
> > > A dependency job for rsyslog.service failed. See 'journalctl -xe' for
> > > details.
> > Have you considered seeing journalctl -xe for
Le 31/01/2023 à 11:08, Nicolas George a écrit :
deb...@sioban.net (12023-01-31):
A dependency job for rsyslog.service failed. See 'journalctl -xe' for
details.
Have you considered seeing journalctl -xe for details?
Hi,
Yes, that was my first action.
The last line of log is from Oct 24 :/
deb...@sioban.net (12023-01-31):
> A dependency job for rsyslog.service failed. See 'journalctl -xe' for
> details.
Have you considered seeing journalctl -xe for details?
--
Nicolas George
Hi everyone,
I'm contacting you because I'm clueless on what's happening.
Basically my issue is I don't have logs anymore :/
I'm using rsyslog but since some times, I'm getting only this message
when I try to start it:
--
> systemctl start rsyslog.service
A dependency job for rsyslog.service
34 matches
Mail list logo
