On 10-Mar-2017, at 6:05 PM, Martin Perina <mperina@redhat.com> wrote:
Hi,
I've no idea how you managed to install Fedora 24 without configured journal (AFAIK it's enabled and configured on all Fedora by default for a long time). Please take a look at Fedora doc how to install and configure it properly.
Strange enough, I rebooted the box. And the command `journalctl -xe` works now.
Here is the traceback
+++# journalctl -xeMar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 systemd[2441]: Reached target Basic System. -- Subject: Unit UNIT has finished start-up-- Defined-By: systemd---- Unit UNIT has finished starting up.---- The start-up result is done.Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 systemd[2441]: Reached target Default. -- Subject: Unit UNIT has finished start-up-- Defined-By: systemd---- Unit UNIT has finished starting up.---- The start-up result is done.Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 systemd[2441]: Startup finished in 40ms. -- Subject: System start-up is now complete-- Defined-By: systemd---- All system services necessary queued for starting at boot have been-- successfully started. Note that this does not mean that the machine is-- now idle as services might still be busy with completing start-up.---- Kernel start-up required KERNEL_USEC microseconds.---- Initial RAM disk start-up required INITRD_USEC microseconds.---- Userspace start-up required 40077 microseconds.Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t: s0 msg='unit=user@0 comm="systemd" exe="/usr/lib/systemd/sy Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 systemd[1]: Started User Manager for UID 0. -- Subject: Unit user@0.service has finished start-up-- Defined-By: systemd---- Unit user@0.service has finished starting up.---- The start-up result is done.Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 sshd[2436]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 audit[2436]: USER_START pid=2436 uid=0 auid=0 ses=5 subj=system_u:system_r:sshd_t: s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_selinux,pam_ loginuid, Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 audit[2455]: CRYPTO_KEY_USER pid=2455 uid=0 auid=0 ses=5 subj=system_u:system_r:sshd_t: s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:f8:13:bf:91:46:1 Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 audit[2455]: CRYPTO_KEY_USER pid=2455 uid=0 auid=0 ses=5 subj=system_u:system_r:sshd_t: s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:0a:3c:13:40:e3:f Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 audit[2455]: CRYPTO_KEY_USER pid=2455 uid=0 auid=0 ses=5 subj=system_u:system_r:sshd_t: s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:79:9b:98:af:39:a Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 audit[2455]: CRED_ACQ pid=2455 uid=0 auid=0 ses=5 subj=system_u:system_r:sshd_t: s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 audit[2436]: USER_LOGIN pid=2436 uid=0 auid=0 ses=5 subj=system_u:system_r:sshd_t: s0-s0:c0.c1023 msg='op=login id=0 exe="/usr/sbin/sshd" hostname=72.163.220 Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 audit[2436]: USER_START pid=2436 uid=0 auid=0 ses=5 subj=system_u:system_r:sshd_t: s0-s0:c0.c1023 msg='op=login id=0 exe="/usr/sbin/sshd" hostname=72.163.220 Mar 10 13:14:34 fedora-ovirt-engine-1gb-blr1-01 audit[2436]: CRYPTO_KEY_USER pid=2436 uid=0 auid=0 ses=5 subj=system_u:system_r:sshd_t: s0-s0:c0.c1023 msg='op=destroy kind=server fp=SHA256:79:9b:98:af:39:a Mar 10 13:14:42 fedora-ovirt-engine-1gb-blr1-01 dhclient[2429]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10 (xid=0xa7d81577) Mar 10 13:14:52 fedora-ovirt-engine-1gb-blr1-01 dhclient[2429]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18 (xid=0xa7d81577) lines 1058-1107/1107 (END)+++
Anyway one of my colleagues noticed that mentioned 1GB in subject. Is it your RAM size? If so then please raise it to 4 GB, which is an absolute minimum to run engine (low memory may be the issue why engine process haven't started up).
Martin Perina
New to ovirt, I wanted to try out how the the ovirt engine manages the other node hosts. With that in mind, was the RAM thing an issue?
On Fri, Mar 10, 2017 at 12:04 PM, Tasdik Rahman <prodicus@outlook.com> wrote:
+++$ sudo su -# journalbash: journal: command not found...
Ahh sorry, it should be 'journalctl'
# journalctl -xeNo journal files were found.-- No entries --#+++
Thanks,Tasdik
On 10-Mar-2017, at 4:32 PM, Martin Perina <mperina@redhat.com> wrote:
journalctl -xe
Thanks,Tasdik