IGHOR

unraid-api restart and unregister/register didn't help

Any help please?

Nov 17 23:14:14 UnraID kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Nov 17 23:14:14 UnraID kernel: rcu: 3-...!: (1 ticks this GP) idle=ac2/1/0x4000000000000000 softirq=998187647/998187647 fqs=0 Nov 17 23:14:14 UnraID kernel: (detected by 2, t=98437 jiffies, g=1948964373, q=40) Nov 17 23:14:14 UnraID kernel: Sending NMI from CPU 2 to CPUs 3: Nov 17 23:14:14 UnraID kernel: NMI backtrace for cpu 3 Nov 17 23:14:14 UnraID kernel: CPU: 3 PID: 29087 Comm: kworker/3:1 Tainted: P O 5.10.28-Unraid #1 Nov 17 23:14:14 UnraID kernel: Hardware name: Gigabyte Technology Co., Ltd. P43T-ES3G/P43T-ES3G, BIOS F8 01/12/2012 Nov 17 23:14:14 UnraID kernel: Workqueue: events dbs_work_handler Nov 17 23:14:14 UnraID kernel: RIP: 0010:rb_erase+0x10e/0x24e Nov 17 23:14:14 UnraID kernel: Code: 48 89 02 4d 85 c9 74 0b 48 83 cf 01 49 89 39 48 89 08 c3 f6 00 01 48 89 08 75 01 c3 31 c9 48 8b 77 08 48 39 ce 74 7e f6 06 01 <75> 20 4c 8b 46 10 48 89 f8 31 c9 48 83 c8 01 4c 89 47 08 48 89 7e Nov 17 23:14:14 UnraID kernel: RSP: 0018:ffffc9000011cf10 EFLAGS: 00000002 Nov 17 23:14:14 UnraID kernel: RAX: ffffc90000573ea8 RBX: ffffc90009a6fdf0 RCX: ffffc9000390bdf0 Nov 17 23:14:14 UnraID kernel: RDX: ffff888417d9f0a0 RSI: ffffc900036d3d08 RDI: ffffc90000573ea8 Nov 17 23:14:14 UnraID kernel: RBP: ffff888417d9f0a0 R08: 0000000000000000 R09: ffff888103afda00 Nov 17 23:14:14 UnraID kernel: R10: ffff888191241310 R11: ffff888417da2400 R12: ffff888417d9f080 Nov 17 23:14:14 UnraID kernel: R13: 0000000000000000 R14: ffffc90009a6fdf0 R15: ffff888417d9f040 Nov 17 23:14:14 UnraID kernel: FS: 0000000000000000(0000) GS:ffff888417d80000(0000) knlGS:0000000000000000 Nov 17 23:14:14 UnraID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 17 23:14:14 UnraID kernel: CR2: 00007f336ddb1538 CR3: 0000000196244000 CR4: 00000000000006e0 Nov 17 23:14:14 UnraID kernel: Call Trace: Nov 17 23:14:14 UnraID kernel: <IRQ> Nov 17 23:14:14 UnraID kernel: timerqueue_del+0x2c/0x3c Nov 17 23:14:14 UnraID kernel: __remove_hrtimer+0x28/0x7d Nov 17 23:14:14 UnraID kernel: __hrtimer_run_queues+0x96/0x10b Nov 17 23:14:14 UnraID kernel: hrtimer_interrupt+0x8d/0x15b Nov 17 23:14:14 UnraID kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Nov 17 23:14:14 UnraID kernel: asm_call_irq_on_stack+0x12/0x20 Nov 17 23:14:14 UnraID kernel: </IRQ> Nov 17 23:14:14 UnraID kernel: sysvec_apic_timer_interrupt+0x71/0x95 Nov 17 23:14:14 UnraID kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Nov 17 23:14:14 UnraID kernel: RIP: 0010:acpi_os_write_port+0x15/0x26 Nov 17 23:14:14 UnraID kernel: Code: 33 04 25 28 00 00 00 74 05 e8 a0 2f 32 00 31 c0 48 83 c4 10 c3 83 fa 08 89 f0 77 05 89 fa ee eb 17 83 fa 10 77 06 89 fa 66 ef <eb> 0c 83 fa 20 77 05 89 fa ef eb 02 0f 0b 31 c0 c3 48 8b 47 08 48 Nov 17 23:14:14 UnraID kernel: RSP: 0018:ffffc90003a6fd88 EFLAGS: 00000246 Nov 17 23:14:14 UnraID kernel: RAX: 0000000000000136 RBX: ffff888100d1f000 RCX: ffff8881008ae100 Nov 17 23:14:14 UnraID kernel: RDX: 0000000000000880 RSI: 0000000000000136 RDI: 0000000000000880 Nov 17 23:14:14 UnraID kernel: RBP: ffff888100d1f000 R08: 0000000000000000 R09: 0000000000000000 Nov 17 23:14:14 UnraID kernel: R10: 8080808080808080 R11: 000000000000001b R12: ffff888417daad30 Nov 17 23:14:14 UnraID kernel: R13: 0000000000000001 R14: 000000000000000c R15: 00000000001e8480 Nov 17 23:14:14 UnraID kernel: ? acpi_cpufreq_cpu_exit+0x3f/0x3f [acpi_cpufreq] Nov 17 23:14:14 UnraID kernel: acpi_cpufreq_target+0xd9/0x173 [acpi_cpufreq] Nov 17 23:14:14 UnraID kernel: ? cpufreq_freq_transition_begin+0xdd/0xfc Nov 17 23:14:14 UnraID kernel: ? acpi_cpufreq_cpu_exit+0x3f/0x3f [acpi_cpufreq] Nov 17 23:14:14 UnraID kernel: __cpufreq_driver_target+0x181/0x217 Nov 17 23:14:14 UnraID kernel: od_dbs_update+0x132/0x16a Nov 17 23:14:14 UnraID kernel: dbs_work_handler+0x30/0x57 Nov 17 23:14:14 UnraID kernel: process_one_work+0x13c/0x1d5 Nov 17 23:14:14 UnraID kernel: worker_thread+0x18b/0x22f Nov 17 23:14:14 UnraID kernel: ? process_scheduled_works+0x27/0x27 Nov 17 23:14:14 UnraID kernel: kthread+0xe5/0xea Nov 17 23:14:14 UnraID kernel: ? __kthread_bind_mask+0x57/0x57 Nov 17 23:14:14 UnraID kernel: ret_from_fork+0x22/0x30

Here is one more. Saved a few minutes after crash julynas-diagnostics-20211117-2226.zip

It happened again, few times just now. Looks like there was no crashes. Here is logs julynas-diagnostics-20210714-1149.zip

most likely he read this thread

Yes, I did exactly this. I was expecting to do it once only thats why I made no scripts for that. I hope I'll not need to do it and plugin dev will release update, or plugin dev share his build steps. Anyway I'm with unRAID for a long time, and if it is really needed I can make automated updates for this plugin.

It not written, you need to replace result binaries in the previous version of txz package.

You need to use manual config only

You need to find out those values for your ups default.battery.voltage.high = default.battery.voltage.low = default.battery.voltage.nominal =

I think nut can't get those values from some UPS And driver calculate it by voltage, and if you calibrate nut and define high/low voltages it will show % and runtime left

I tested and it survived reboot, also here is updated file with some fixes. How to install: 1) copy the attached file and replace it in the folder /boot/config/plugins/nut 2) reboot It will remain to be the same plugin, but with newer nut v2.7.4.1 for usb devices only. Once plugin dev update it officially, it will be upgraded natively nut-2.7.4.20200318-x86_64-1.txz

I think you need just copy the file 'nut-2.7.4.1.20210620-x86_64-1.txz' attached in my message to folder /boot/config/plugins/nut And reboot server, it may use latest version of nut instead of old one. If it not works this way, replace existing nut-2.7.4... file in folder /boot/config/plugins/nut by my file and reboot

I fixed it, maybe it is just enough to put the file to this folder /boot/config/plugins/nut Or replace existing one. Anyway if extracted to root, it starts working instantly. So everything is working fine with nut compiled from latest sources. There should be nothing that stops plugin dev to release an update. Here is a right commands to compile nut to run on unRAID: apt update && apt install ca-certificates freeipmi git libusb-dev autoconf automake make libtool python --no-install-recommends -y git clone --depth 1 https://github.com/networkupstools/nut.git && cd nut ./autogen.sh ./configure --enable-strip --runstatedir=/var/run/nut --with-pidpath=/var/run/nut --with-usb --datarootdir=/usr/share/nut --bindir=/usr/bin --sbindir=/usr/sbin --prefix=/ --sysconfdir=/etc/nut --libexecdir=/usr/libexec/nut --libdir=/usr/lib64 --with-drvpath=/usr/libexec/nut && make -j `nproc` && make install nut-2.7.4.1.20210620-x86_64-1.txz

Actually latest compilation of nut is working. It is possible parsing problem in the plugin code, not nut itself In command line it works root@unRAID:/# upsc [email protected] battery.voltage: 27.30 device.type: ups driver.flag.noscanlangid: enabled driver.flag.novendor: enabled driver.name: nutdrv_qx driver.parameter.langid_fix: 0x0409 driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0000 driver.parameter.protocol: hunnox driver.parameter.synchronous: no driver.parameter.vendorid: 0001 driver.version: 2.7.4.1 driver.version.data: Hunnox 0.01 driver.version.internal: 0.30 input.frequency: 49.6 input.voltage: 217.0 input.voltage.fault: 0.0 output.voltage: 220.0 ups.beeper.status: disabled ups.delay.shutdown: 60 ups.delay.start: 0 ups.load: 13 ups.productid: 0000 ups.status: OL ups.temperature: 29.0 ups.type: offline / line interactive ups.vendorid: 0001

I built latest nut sources for unRAID with usb support only. Here is steps to build it on ubuntu/debian: apt update && apt install ca-certificates freeipmi git libusb-dev autoconf automake make libtool python --no-install-recommends -y git clone --depth 1 https://github.com/networkupstools/nut.git && cd nut ./autogen.sh ./configure --enable-strip --with-usb --datarootdir=/usr/share/nut --bindir=/usr/bin --sbindir=/usr/sbin --prefix=/ --sysconfdir=/etc/nut --libexecdir=/usr/libexec/nut --runstatedir=/var/run/nut --libdir=/usr/lib64 --with-drvpath=/usr/libexec/nut && make -j `nproc` && make install

I see, it is Weblate docker and nut under another name. Thanks. I'll try to stop it and wait for another issue if happens. Anyway this docker state is 'Uptime: 7 days (healthy)' but I had this issue today.

Also there is always free memory, I don't know what is the reason of 'out of memory' message.

I don't have a nut docker, and nut is disabled in the settings. What is UWS?

Possibly that is related to my issue https://forums.unraid.net/topic/106201-server-has-run-out-of-memory-and-processes-celery-killed on which I got no help. Can you please explain more about your suggestion, since I'm not sure I understand it. Which containers are you suggesting to stop?

What do you mean by "it's running hogwild"? And how it supposed to solve problem? I did restart my server many times and it happens time to time since half year or so.

any help?

Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the unRaid forums It is happening few times per week since I updated to 6.9.0 (and every next release). Please help julynas-diagnostics-20210417-0024.zip

Thats awesome! Thanks!