Displaying 7 results from an estimated 7 matches for "journactl".
Did you mean:
journalctl
2016 Jul 29
2
centos7: ntpd not started on boot
...[2296]: 0.0.0.0 c012 02 freq_set kernel
8.993 PPM
Jul 29 10:29:46 simpil1 ntpd[2296]: 0.0.0.0 c61c 0c clock_step -0.180109 s
Jul 29 10:29:46 simpil1 ntpd[2296]: 0.0.0.0 c614 04 freq_mode
Jul 29 10:29:47 simpil1 ntpd[2296]: 0.0.0.0 c618 08 no_sys_peer
I see nothing ntpd related /var/log/messages or journactl during the
boot phase. Seems like no attempt is made to start it at all.
Is there something that need to be done besides enabling it with systemctl?
Regards
.....Volker
2016 Jul 29
0
centos7: ntpd not started on boot
...set kernel
> 8.993 PPM
> Jul 29 10:29:46 simpil1 ntpd[2296]: 0.0.0.0 c61c 0c clock_step -0.180109 s
> Jul 29 10:29:46 simpil1 ntpd[2296]: 0.0.0.0 c614 04 freq_mode
> Jul 29 10:29:47 simpil1 ntpd[2296]: 0.0.0.0 c618 08 no_sys_peer
>
> I see nothing ntpd related /var/log/messages or journactl during the
> boot phase. Seems like no attempt is made to start it at all.
>
> Is there something that need to be done besides enabling it with systemctl?
>
> Regards
> .....Volker
>
>
> _______________________________________________
> CentOS mailing list
> CentOS...
2020 Aug 12
0
Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)
...be the problem because when I took out the second line, nut-server service wouldn’t fail, but then clients couldn’t connect.
> That is odd, indeed. And yes, it is certainly a permission issue but on
> the journal files which reside below /var/log , not on the config files
>
> Start with journactl -x as it might say more about the error. And maybe
> verify if any log file is defined by the nut-server unit.
I tried journalctl -x and got a huge list, couldn’t even find where nut-service was in there. I tried...
sudo journalctl -x | grep "nut-server"
sudo journalctl -x | grep “er...
2020 Aug 12
3
Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)
555 gives no write access to the dir, and the files are covered by their
own perms, so I fail to see any relevance to your comment - sorry . . .
640 is decent for files, not so much for directories - as noted, the
fields mean different things on dirs . . .
From the man pages:
The letters rwxXst select file mode bits for the affected
users: read
(r), write (w), execute (or
2019 Jan 11
3
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
On Friday, January 11, 2019 1:39 PM, Rowland Penny via samba <samba at lists.samba.org> wrote:
> There doesn't seem to be anything really wrong there,the only really
> difference between your named.conf and mine is that I have:
>
> dnssec-validation no;
> dnssec-enable no;
> dnssec-lookaside no;
> listen-on-v6 { none; };
> listen-on port 53
2020 Aug 12
4
Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)
Thanks Manuel. I’m following that guide but am now stuck when checking to make sure the nut-sever and nut-client are up and working. I got this:
proton at proton:~$ service nut-server status
nut-server.service - Network UPS Tools - power devices information server
Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)
Active: failed (Result:
2015 Nov 10
21
[Bug 92892] New: KDE Plasma locks up: Nouveau reports error "resource sanity check" "unable to handle kernel paging request"
...and spot the second kernel backtrace.
With slightly older kernel versions I also get these kernel backtraces in the
system log (journalctl), but I do NOT experience whole desktop lockups. With
even older kernel versions, I do not get these types of kernel backtraces.
These are the lines from when journactl indicates a similar backtrace for the
first time: (The installed kernel must have been 4.2.3 as far as I can
determine through inspecting the package install history logfile.)
----- Kernel 4.2.3:
------------------------------------------------------------
Okt 27 15:42:10 linux-5rjk kernel: resourc...