Package Details: rasdaemon 0.6.5-4

Git Clone URL: https://aur.archlinux.org/rasdaemon.git (read-only, click to copy)
Package Base: rasdaemon
Description: Logging daemon for Platform Reliability, Availability and Serviceability (RAS), replacing mcelog
Upstream URL: https://pagure.io/rasdaemon
Licenses: GPL2
Submitter: grawity
Maintainer: eta-carinae
Last Packager: eta-carinae
Votes: 25
Popularity: 0.30
First Submitted: 2017-05-04 06:49
Last Updated: 2020-07-08 21:22

Latest Comments

1 2 Next › Last »

yochananmarqos commented on 2020-07-04 16:45

The url() should be https://pagure.io/rasdaemon

BStrauss3 commented on 2020-06-19 21:58

@eta-carinae : Just built it for a new machine - smooth... THANKS!!!!!

If anybody is having problems with the periodic block_rq_complete 'errors' that aren't errors, there was a thread on GitHub in the last couple days:

https://github.com/mchehab/rasdaemon/issues/17#issuecomment-646455597

At least for some machines, it's each empty slot in a card reader (SD, etc.) and the 7th message down has the command to make it STFU.

-----Burton

eta-carinae commented on 2020-05-26 16:44

Removed --enable-abrt-report as requested. Got a little too aggressive with experimental flags I guess. :)

BStrauss3 commented on 2020-05-24 15:53

Why is this package being built with

--enable-abrt-report

There is no abrt daemon for Arch, so this generates an "error" about 5 per minute. I've built it with this removed and we're down to a heartbeat every 3 seconds or so.

-----Burton

pancho commented on 2020-05-16 11:55

Stellar! ;-)

eta-carinae commented on 2020-05-16 09:55

pancho,

Thanks for the heads-up. I added your workaround and will report the problem upstream.

pancho commented on 2020-05-16 06:51

Hi there.

It seems that we've been hit by a change¹ in GCC 10. See the topic² for more details. It also affects pam_ssh, so I've managed to easily workaround it² by adding:

CFLAGS="$CFLAGS -fcommon" ./configure ...

This just reverts GCC to the pre-10 behavior.

Hope that it helps.

¹: https://gcc.gnu.org/gcc-10/porting_to.html

²: https://bbs.archlinux.org/viewtopic.php?id=255727

³: https://aur.archlinux.org/cgit/aur.git/commit/?h=pam_ssh&id=cb4ed823ece6b3316a7b4103135dec8d1711473c

eta-carinae commented on 2019-10-12 12:45

I get some of those disk errors, though not nearly as many. Also don't see any corresponding problems or errors outside of rasdaemon, so I'm not sure what to make of them. If they're causing people problems, I can disable the disk error feature in the PKGBUILD, but I think reporting this upstream is the best answer.

Ropid commented on 2019-10-12 08:50

Those new "experimental features" don't seem to be working right for me here. On certain boots, I get hundreds of the following errors recorded in ras-mc-ctl --errors:

Disk errors
1 2019-09-30 12:19:31 +0200 error: dev=0:2080, sector=192357784, nr_sector=256, error='unknown block error', rwbs='RA', cmd='', 
...
504 2019-10-11 21:02:08 +0200 error: dev=0:2048, sector=12986960, nr_sector=8, error='unknown block error', rwbs='R', cmd='', 

This does not happen on every boot, it only happens every three days or so.

While those errors are getting recorded by rasdaemon, I can't find any strange messages in journalctl or dmesg. The log messages there look fine with no errors or warnings.

eta-carinae commented on 2018-09-03 23:16

Because this was an orphaned package I took over and I didn't notice the change because I was using my own custom unit :). Fixed.