You are not logged in.
Hi, I upgraded a couple of days ago on the 11th to systemd system, I am using 86_64 awesome DE, I ran Syu yesterday and this morning I found mplayer was acting poorly so I went to check pacman.log to see what was updated. Pacman.log hadn't logged since the 11th when I upgraded, although I would like to figure out mplayer, I am more interested in the log files. I also found that my boot log file is not recording boot information from the same time although the errors.log has information in it.
thanks in advance for any help you may give.
--jerry
Last edited by jk121960 (2012-11-14 21:15:45)
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
Did you read the Systemd wiki entry? Systemd logs to /var/log/journal, but that will not help you much, since the logs seem to be saved in some binary format. You can access the logs with journalctl.
Offline
OK but does it also log pacman.log? And it seems like I still get information in the errors.log.
thanks
--jerry
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
here too, since exactly the same date, the pacman no longer make new entraces to the /var/log/pacman.log
and the journalctl not show any pacman related
any more can comfirm this for make a formal bug report??
Well, I suppose that this is somekind of signature, no?
Offline
pacman still logs to pacman.log so you'll need to figure out what's up there. Are you using the journal in conjunction with syslog?
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
I am using pure systemd so how would I check? I followed the wiki setting everything up.
thanks for you help.
--jerry
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
To be more precise, did you follow this: Journald in conjunction with syslog
pacman.log is working here.
To know or not to know ...
... the questions remain forever.
Offline
To be more precise, did you follow this: Journald in conjunction with syslog
pacman.log is working here.
Yes and here is the status
syslog-ng.service - System Logger Daemon
Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled)
Active: active (running) since Wed, 2012-11-14 00:58:57 CST; 14h ago
Docs: man:syslog-ng(8)
Main PID: 591 (syslog-ng)
CGroup: name=systemd:/system/syslog-ng.service
└ 591 /usr/sbin/syslog-ng -F
thanks for your help
--jerry
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
I went back over the settings with systemd, I booted and it's fine now. Maybe something didn't come up right. But it's good now.
thanks for all your help
--jerry
Arch Awesome, Ranger & Vim the coding triple threat.
Offline
It's worth noting that pacman.log is written by pacman directly as a regular file, not by any syslog or systemd-related component. So when pacman.log doesn't work, you really don't need to check those other things.
Offline
no
i not using syslog
I using only the journald from systemd
and the /var/log/pacman.log not have any new entry despite the resent instalation of skype
Well, I suppose that this is somekind of signature, no?
Offline
Do you have a separate /var partition? Is it mounted r/w?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
yep separate var partition
I use: /dev/sda6 /var jfs defaults,noatime 0 2
and: /dev/sda7 /var/cache/pacman jfs defaults,noatime 0 2
Well, I suppose that this is somekind of signature, no?
Offline
So is /var mounting correctly?
# systemctl status var.mount
$ mount | grep /var
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline