9:22 a.m.
Ok, old school here, Saturday morning hacking. What is the new method
for managing system services? Could someone point me to some good
documentation? The reason I ask is nothing is being written to
/var/log/messages and /etc/init.d/ doesn't seem to be a viable option
anymore. I tried:
/sbin/service rsyslog status
Redirecting to /bin/systemctl status rsyslog.service
rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
Active: active (running) since Sat, 02 Mar 2013 09:50:50 -0500; 24min ago
Main PID: 2584 (rsyslogd)
CGroup: name=systemd:/system/rsyslog.service
└ 2584 /sbin/rsyslogd -n -c 5
Looks good but logger "test";ls -lt /var/log/messages shows:
-rw-------. 1 root root 0 Feb 24 10:48 /var/log/messages
I must be missing something. TIA.
- Tod
4:40 p.m.
On 03/02/2013 02:34 PM, G.Wolfe Woodbury wrote:
systemd provides a new command for some startup logging: journalctl
Just out of curiosity, I checked to see if that's active:
[root@khorlia joe]# systemctl status journalctl.service
journalctl.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Any thoughts? I'm not starting a new thread only because it's possible
that the OP here has the same issue.
5:08 p.m.
On 3-2-13 10:22:49 Tod Thomas wrote:
Ok, old school here, Saturday morning hacking. What is the new method
for managing system services?
That would be systemctl(1). See man systemctl.
Could someone point me to some good
documentation?
http://www.freedesktop.org/wiki/Software/systemd
The FAQ is maybe what you're looking for:
http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions
The reason I ask is nothing is being written to
/var/log/messages
Try this (probably as root unless you're in the adm group):
journalctl --this-boot --full
--
Garry T. Williams
6:31 p.m.
On 03/03/13 08:22, Joe Zeff wrote:
On 03/02/2013 03:45 PM, Ed Greshko wrote:
> man journalctl
Thanx; that hadn't occurred to me. Checking, I find that it depends on
syslog.socket.service, which also failed. I'll start a new thread for that because I
don't think it's related to the OP's question.
Also, just to be clear, it isn't.
"systemctl status journalctl.service"
it is
"systemctl status systemd-journald.service"
--
From now on, at least during winter time, Im going to blame all
spelling an grammar erros on the cat sitting on my chest every time I sit down at the
computer....
6:45 p.m.
On 03/03/13 08:37, Joe Zeff wrote:
On 03/02/2013 04:31 PM, Ed Greshko wrote:
> On 03/03/13 08:22, Joe Zeff wrote:
>> On 03/02/2013 03:45 PM, Ed Greshko wrote:
>>> man journalctl
>>
>> Thanx; that hadn't occurred to me. Checking, I find that it depends on
syslog.socket.service, which also failed. I'll start a new thread for that because I
don't think it's related to the OP's question.
>
> Also, just to be clear, it isn't.
>
> "systemctl status journalctl.service"
>
> it is
>
> "systemctl status systemd-journald.service"
>
>
>
That one's running OK. Still, I'm curious about why the other one's there
and failing.
What "other one"?
You said:
[root@khorlia joe]# systemctl status journalctl.service
journalctl.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Which is "correct" since there is no such thing as
/lib/systemd/system/journalctl.service
Isn't that what you talking about?
--
From now on, at least during winter time, Im going to blame all
spelling an grammar erros on the cat sitting on my chest every time I sit down at the
computer....
6:41 p.m.
Am 03.03.2013 01:37, schrieb Joe Zeff:
On 03/02/2013 04:31 PM, Ed Greshko wrote:
> On 03/03/13 08:22, Joe Zeff wrote:
>> On 03/02/2013 03:45 PM, Ed Greshko wrote:
>>> man journalctl
>>
>> Thanx; that hadn't occurred to me. Checking, I find that it depends on
syslog.socket.service, which also
>> failed. I'll start a new thread for that because I don't think it's
related to the OP's question.
>
> Also, just to be clear, it isn't.
>
> "systemctl status journalctl.service"
>
> it is
>
> "systemctl status systemd-journald.service"
>
That one's running OK. Still, I'm curious about why the other one's there
and failing
the other one is what?
[root@srv-rhsoft:~]$ systemctl status i-do-simply-not-exist.service
i-do-simply-not-exist.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
look at the reason, pretty clear
6:37 p.m.
On 3-2-13 14:40:39 Joe Zeff wrote:
On 03/02/2013 02:34 PM, G.Wolfe Woodbury wrote:
> systemd provides a new command for some startup logging: journalctl
Just out of curiosity, I checked to see if that's active:
[root@khorlia joe]# systemctl status journalctl.service
journalctl.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Any thoughts?
You're doing it wrong. :-)
The service name is "systemd-journald.service":
garry@vfr$ systemctl status systemd-journald.service
systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Sat 2013-03-02 17:13:09 EST; 2h 21min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 343 (systemd-journal)
Status: "Processing requests..."
CGroup: name=systemd:/system/systemd-journald.service
└─343 /usr/lib/systemd/systemd-journald
Mar 02 17:13:10 vfr systemd-journal[343]: Allowing runtime journal files to grow to
150.0M.
Mar 02 17:13:10 vfr systemd-journal[343]: Journal started
Mar 02 17:13:16 vfr systemd-journal[343]: Allowing system journal files to grow to
100.0M.
garry@vfr$
--
Garry T. Williams
6:37 p.m.
On 03/02/2013 04:31 PM, Ed Greshko wrote:
On 03/03/13 08:22, Joe Zeff wrote:
> On 03/02/2013 03:45 PM, Ed Greshko wrote:
>> man journalctl
>
> Thanx; that hadn't occurred to me. Checking, I find that it depends on
syslog.socket.service, which also failed. I'll start a new thread for that because I
don't think it's related to the OP's question.
Also, just to be clear, it isn't.
"systemctl status journalctl.service"
it is
"systemctl status systemd-journald.service"
That one's running OK. Still, I'm curious about why the other one's
there and failing.
6:24 p.m.
On 03/02/2013 03:52 PM, Tod Thomas wrote:
On 03/02/2013 05:40 PM, Joe Zeff wrote:
> On 03/02/2013 02:34 PM, G.Wolfe Woodbury wrote:
>> systemd provides a new command for some startup logging: journalctl
>
> Just out of curiosity, I checked to see if that's active:
>
> [root@khorlia joe]# systemctl status journalctl.service
> journalctl.service
> Loaded: error (Reason: No such file or directory)
> Active: inactive (dead)
>
> Any thoughts? I'm not starting a new thread only because it's
> possible that the OP here has the same issue.
Thanks, I got the same output you did :|
Ah! It is related, then. Good; let's both try to find out why
syslog.socket is failing.
6:05 p.m.
On 3-2-13 18:08:38 I wrote:
Try this (probably as root unless you're in the adm group):
journalctl --this-boot --full
Oh, it's been a while since I learned about the journal so I forgot to
mention that you can make its stuff persistent. You may be interested
in this:
http://0pointer.de/blog/projects/journalctl.html
I have been running without rsyslog since August last year (according
to journalctl ;-).
-- Logs begin at Sat 2012-08-04 08:41:45 EDT, end at Sat 2013-03-02
19:01:02 EST. --
--
Garry T. Williams
5:52 p.m.
On 03/02/2013 05:40 PM, Joe Zeff wrote:
On 03/02/2013 02:34 PM, G.Wolfe Woodbury wrote:
> systemd provides a new command for some startup logging: journalctl
Just out of curiosity, I checked to see if that's active:
[root@khorlia joe]# systemctl status journalctl.service
journalctl.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Any thoughts? I'm not starting a new thread only because it's
possible that the OP here has the same issue.
Thanks, I got the same output you did :|
5:45 p.m.
On 03/03/13 06:40, Joe Zeff wrote:
On 03/02/2013 02:34 PM, G.Wolfe Woodbury wrote:
> systemd provides a new command for some startup logging: journalctl
Just out of curiosity, I checked to see if that's active:
[root@khorlia joe]# systemctl status journalctl.service
journalctl.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Any thoughts? I'm not starting a new thread only because it's possible that the
OP here has the same issue.
man journalctl
--
From now on, at least during winter time, Im going to blame all
spelling an grammar erros on the cat sitting on my chest every time I sit down at the
computer....
4:34 p.m.
On 03/02/2013 10:22 AM, Tod Thomas wrote:
Ok, old school here, Saturday morning hacking. What is the new
method
for managing system services? Could someone point me to some good
documentation? The reason I ask is nothing is being written to
/var/log/messages and /etc/init.d/ doesn't seem to be a viable option
anymore. I tried:
/sbin/service rsyslog status
Redirecting to /bin/systemctl status rsyslog.service
rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
Active: active (running) since Sat, 02 Mar 2013 09:50:50 -0500; 24min ago
Main PID: 2584 (rsyslogd)
CGroup: name=systemd:/system/rsyslog.service
└ 2584 /sbin/rsyslogd -n -c 5
Looks good but logger "test";ls -lt /var/log/messages shows:
-rw-------. 1 root root 0 Feb 24 10:48 /var/log/messages
I must be missing something. TIA.
systemd provides a new command for some startup logging: journalctl
Also, the configuration for rsyslogd has probably changed, check the man
page?
--
G.Wolfe Woodbury
redwolfe(a)gmail.com
2:42 p.m.
On 02.03.2013 16:22, Tod Thomas wrote:
Ok, old school here, Saturday morning hacking. What is the new
method
for managing system services? Could someone point me to some good
documentation? The reason I ask is nothing is being written to
/var/log/messages and /etc/init.d/ doesn't seem to be a viable option
anymore. I tried:
/sbin/service rsyslog status
Redirecting to /bin/systemctl status rsyslog.service
rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
Active: active (running) since Sat, 02 Mar 2013 09:50:50 -0500; 24min ago
Main PID: 2584 (rsyslogd)
CGroup: name=systemd:/system/rsyslog.service
└ 2584 /sbin/rsyslogd -n -c 5
Looks good but logger "test";ls -lt /var/log/messages shows:
-rw-------. 1 root root 0 Feb 24 10:48 /var/log/messages
I must be missing something. TIA.
Maybe /var is full?
Mateusz Marzantowicz
4071
days inactive
4072
days old
14 comments
7 participants
participants (7)
-
Ed Greshko -
Garry Williams -
Gregory Woodbury -
Joe Zeff -
Mateusz Marzantowicz -
Reindl Harald -
Tod Thomas