Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bittorf:
logread is dying several times a day here. This is with r17950 and at least ath79 and mpc85xx and ramips.
Tue Nov 2 17:12:05 2021 kern.info kernel: [ 3745.330244] do_page_fault(): sending SIGSEGV to logread for invalid write access to 00000000 Tue Nov 2 17:12:05 2021 kern.info kernel: [ 3745.338789] epc = 77de87ac in libc.so[77d60000+a5000] Tue Nov 2 17:12:05 2021 kern.info kernel: [ 3745.343833] ra = 004017b3 in logread[400000+3000]
for checking if the log-service is healthy, we do regularly:
ubus call network.device status ubus call log read logread >/dev/null
The last call has (when failing) always RC = 139 with above message in log.
The text was updated successfully, but these errors were encountered:
the same with r18106 (after GCC11 fix).
relevant config settings are: system.@system[0].cronloglevel='9' system.@system[0].log_size='16'
system.@system[0].cronloglevel='9' system.@system[0].log_size='16'
and no memory pressure: root@ArcherC6U-stube:~ :) free total used free shared buff/cache available Mem: 121680 30692 67616 3684 23372 74188 Swap: 4092 0 4092
root@ArcherC6U-stube:~ :) free total used free shared buff/cache available Mem: 121680 30692 67616 3684 23372 74188 Swap: 4092 0 4092
Sorry, something went wrong.
No branches or pull requests
bittorf:
logread is dying several times a day here.
This is with r17950 and at least ath79 and mpc85xx and ramips.
Tue Nov 2 17:12:05 2021 kern.info kernel: [ 3745.330244] do_page_fault(): sending SIGSEGV to logread for invalid write access to 00000000 Tue Nov 2 17:12:05 2021 kern.info kernel: [ 3745.338789] epc = 77de87ac in libc.so[77d60000+a5000] Tue Nov 2 17:12:05 2021 kern.info kernel: [ 3745.343833] ra = 004017b3 in logread[400000+3000]
for checking if the log-service is healthy, we do regularly:
ubus call network.device status ubus call log read logread >/dev/null
The last call has (when failing) always RC = 139 with above message in log.
The text was updated successfully, but these errors were encountered: