Leondre
-
Posts
28 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Leondre
-
-
The FTBSkies container is causing this error to show up in the syslog when viewing the community apps tab because the icon url is broken.
-
1
-
-
Also started seeing this over the last few days.
Edit: Seems to show up when viewing the community apps tab.
Edit2: Coming from the FTBSkies container, icon url seems borked in it.
-
1
-
-
The dynamix ssd trim plugin causes the following to show up in the syslog when it runs. Two intel 545s (512gb) ssds are connected to a 9305-16i.
Feb 6 00:00:30 kernel: mpt3sas_cm0: log_info(0x31120b10): originator(PL), code(0x12), sub_code(0x0b10) Feb 6 00:00:31 kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03) Feb 6 00:00:31 kernel: sd 1:0:13:0: [sdo] tag#4557 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s Feb 6 00:00:31 kernel: sd 1:0:13:0: [sdo] tag#4557 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 Feb 6 00:00:31 kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03) Feb 6 00:00:31 kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03) Feb 6 00:00:32 kernel: sd 1:0:13:0: Power-on or device reset occurred Feb 6 00:00:32 kernel: mpt3sas_cm0: log_info(0x31120b10): originator(PL), code(0x12), sub_code(0x0b10) Feb 6 00:00:32 kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03) Feb 6 00:00:32 kernel: sd 1:0:0:0: [sdb] tag#4603 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s Feb 6 00:00:32 kernel: sd 1:0:0:0: [sdb] tag#4603 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00 Feb 6 00:00:33 kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03) Feb 6 00:00:33 kernel: sd 1:0:0:0: Power-on or device reset occurredExecuting 'fstrim -v /mnt/cache' or 'fstrim -a -v' manually or via userscripts works without any problems, so I guess I'll just do it that way.
-
On 10/1/2021 at 3:27 AM, AmokK said:
Thank you for your answer, I understand now why it can't work automatically, as it is a major postgres update.
I will stick to the 13.4 version for the moment, as the database upgrade procedure seems a little bit complicated, but I will study it thoroughly and try it later
I too use psql for nextcloud, and while I'm no db expert.. let alone psql, I just went through the process after fiddling with it for a while, only made complicated by docker really.
Just spin up 2 psql containers with separate appdata dirs, original being port 5432, new one 5433.
Mount a shared backup directory between them.
SSH into the OG psql, run 'pg_dumpall -U postgres > /backupdir/all.sql'
SSH into the NEW psql, recreate any users you had before (not entirely sure this needs to be done but I did), then run 'psql -U postgres -f /backupdir/all.sql'
Kill the old container, change the new container port to whatever the old one was, 5432 in this case.
Done
I'm sure someone will tell me why this is a horrible way to do it, but hey it worked.
-
2
-
-
My favorite feature is being able to add drives at will without needing to plan my whole build ahead of time.
What I would like to see in the future is official support for ssds as data/parity devices.
-
Happy user since 2016, my favorite thing about unraid is how I can easily add/change a drive at any time.
-
Getting this error after the last update. Have tried removing and readding the container
2019-03-21 18:12:14.674344 [info] System information Linux c57ea3329427 4.18.20-unRAID #1 SMP Fri Nov 23 11:38:16 PST 2018 x86_64 GNU/Linux
2019-03-21 18:12:14.697325 [info] PUID defined as '99'
2019-03-21 18:12:14.722696 [info] PGID defined as '100'
2019-03-21 18:12:14.797432 [info] UMASK defined as '000'
2019-03-21 18:12:14.822565 [info] Permissions already set for volume mappings
2019-03-21 18:12:14.845976 [info] Starting Supervisor...
2019-03-21 18:12:14,974 INFO Included extra file "/etc/supervisor/conf.d/jackett.conf" during parsing
2019-03-21 18:12:14,974 INFO Set uid to user 0 succeeded
2019-03-21 18:12:14,976 INFO supervisord started with pid 8
2019-03-21 18:12:15,977 INFO spawned: 'jackett' with pid 43
2019-03-21 18:12:15,978 INFO reaped unknown pid 9
2019-03-21 18:12:15,989 DEBG 'jackett' stderr output:
Cannot open assembly '/usr/lib/jackett/JackettConsole.exe': No such file or directory.
2019-03-21 18:12:15,995 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22496759541632 for <Subprocess at 22496759936496 with name jackett in state STARTING> (stdout)>
2019-03-21 18:12:15,995 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22496759539760 for <Subprocess at 22496759936496 with name jackett in state STARTING> (stderr)>
2019-03-21 18:12:15,995 INFO exited: jackett (exit status 2; not expected)
2019-03-21 18:12:15,995 DEBG received SIGCLD indicating a child quit
2019-03-21 18:12:16,996 INFO spawned: 'jackett' with pid 47
2019-03-21 18:12:17,007 DEBG 'jackett' stderr output:
Cannot open assembly '/usr/lib/jackett/JackettConsole.exe': No such file or directory. -
I've also been getting similar warnings to your first post, but haven't been able to figure out why. Hoping someone has at least a little info about these.
-
May 29 18:58:19 Tower nginx: 2018/05/29 18:58:19 [error] 2945#2945: *368203 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.193, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Main" May 29 18:58:19 Tower php-fpm[2919]: [WARNING] [pool www] child 24185 exited on signal 7 (SIGBUS) after 201.121514 seconds from start May 29 19:36:33 Tower nginx: 2018/05/29 19:36:33 [error] 2945#2945: *379713 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.193, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Main" May 29 19:36:33 Tower php-fpm[2919]: [WARNING] [pool www] child 2998 exited on signal 7 (SIGBUS) after 109.067894 seconds from start May 30 03:04:35 Tower nginx: 2018/05/30 03:04:35 [error] 2945#2945: *478509 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.193, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower", referrer: "http://tower/Main" May 30 03:04:35 Tower php-fpm[2919]: [WARNING] [pool www] child 19305 exited on signal 7 (SIGBUS) after 137.091318 seconds from startI get these showing up several times a week in my syslog. Nothing ever seems broken so I'm not sure if this is something I need to worry about or not. Anyone know what would be causing this?
No other warnings/errors accompany these.
-
Found this gem in the syslog today, would anyone be able to shed any light on why this would have happened? Nothing appears to be broken at the moment. Strangely the timestamp seems to match the only hardware change I've made to the machine in a very long time and that was just plugging in a hdmi cable to the onboard GPU, though I don't understand why that would cause it.
May 1 18:49:06 Tower kernel: irq 16: nobody cared (try booting with the "irqpoll" option) May 1 18:49:06 Tower kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.35-unRAID #1 May 1 18:49:06 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. Z270N-WIFI/Z270N-WIFI-CF, BIOS F5 07/06/2017 May 1 18:49:06 Tower kernel: Call Trace: May 1 18:49:06 Tower kernel: <IRQ> May 1 18:49:06 Tower kernel: dump_stack+0x5d/0x79 May 1 18:49:06 Tower kernel: __report_bad_irq+0x32/0xac May 1 18:49:06 Tower kernel: note_interrupt+0x1d4/0x225 May 1 18:49:06 Tower kernel: handle_irq_event_percpu+0x39/0x3f May 1 18:49:06 Tower kernel: handle_irq_event+0x31/0x4f May 1 18:49:06 Tower kernel: handle_fasteoi_irq+0x8c/0xf3 May 1 18:49:06 Tower kernel: handle_irq+0x1c/0x1f May 1 18:49:06 Tower kernel: do_IRQ+0x3b/0xbb May 1 18:49:06 Tower kernel: common_interrupt+0x7d/0x7d May 1 18:49:06 Tower kernel: </IRQ> May 1 18:49:06 Tower kernel: RIP: 0010:cpuidle_enter_state+0xe3/0x135 May 1 18:49:06 Tower kernel: RSP: 0018:ffffffff81c03ec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff7d May 1 18:49:06 Tower kernel: RAX: ffff88042ec20980 RBX: 0000000000000000 RCX: 000000000000001f May 1 18:49:06 Tower kernel: RDX: 00024e417ba40eef RSI: 0000000000020180 RDI: 0000000000000000 May 1 18:49:06 Tower kernel: RBP: ffff88042ec28800 R08: 0006b245a498f2dc R09: 0000000000000018 May 1 18:49:06 Tower kernel: R10: ffffffff81c03ea8 R11: 0000000000000000 R12: 0000000000000001 May 1 18:49:06 Tower kernel: R13: 00024e417ba40eef R14: ffffffff81c591f8 R15: 00024e417ba40215 May 1 18:49:06 Tower kernel: ? cpuidle_enter_state+0xbb/0x135 May 1 18:49:06 Tower kernel: do_idle+0x11a/0x179 May 1 18:49:06 Tower kernel: cpu_startup_entry+0x18/0x1a May 1 18:49:06 Tower kernel: start_kernel+0x3e4/0x3ec May 1 18:49:06 Tower kernel: secondary_startup_64+0xa5/0xb0 May 1 18:49:06 Tower kernel: handlers: May 1 18:49:06 Tower kernel: [<ffffffffa0000d50>] i801_isr [i2c_i801] May 1 18:49:06 Tower kernel: Disabling IRQ #16
root@Tower:~# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 44 0 0 0 0 0 0 0 IR-IO-APIC 2-edge timer 8: 18 0 0 0 0 0 0 0 IR-IO-APIC 8-edge rtc0 9: 0 0 0 0 0 0 0 0 IR-IO-APIC 9-fasteoi acpi 16: 100000 0 0 0 0 0 0 0 IR-IO-APIC 16-fasteoi i801_smbus 120: 0 0 0 0 0 0 0 0 DMAR-MSI 0-edge dmar0 121: 0 0 0 0 0 0 0 0 DMAR-MSI 1-edge dmar1 122: 0 0 0 0 0 0 0 0 DMAR-MSI 128-edge dmar0-prq 123: 3284078 0 0 0 0 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd 124: 16477549 0 0 0 0 0 0 0 IR-PCI-MSI 376832-edge ahci[0000:00:17.0] 125: 1 0 0 0 0 0 0 0 IR-PCI-MSI 3670016-edge eth0 126: 52832651 0 0 0 0 0 0 0 IR-PCI-MSI 524288-edge mpt2sas0-msix0 127: 69674258 0 0 0 0 0 0 0 IR-PCI-MSI 3670017-edge eth0-rx-0 128: 344802 0 0 0 0 0 0 0 IR-PCI-MSI 3670018-edge eth0-rx-1 129: 24255990 0 0 0 0 0 0 0 IR-PCI-MSI 3670019-edge eth0-tx-0 130: 51567192 0 0 0 0 0 0 0 IR-PCI-MSI 3670020-edge eth0-tx-1 131: 344802 0 0 0 0 0 0 0 IR-PCI-MSI 520192-edge eth1 NMI: 0 0 612 0 0 0 0 0 Non-maskable interrupts LOC: 216834455 258160260 164850430 119864597 302686535 281394935 129574123 109494595 Local timer interrupts SPU: 0 0 0 0 0 0 0 0 Spurious interrupts PMI: 0 0 612 0 0 0 0 0 Performance monitoring interrupts IWI: 2 0 27 0 0 0 0 0 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 50032888 12236939 68080807 52929105 1340832 1106603 66894393 43870617 Rescheduling interrupts CAL: 550854 629917 567107 604028 655691 654758 603215 618110 Function call interrupts TLB: 498074 577130 453380 446509 602377 601486 455888 487348 TLB shootdowns TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 0 0 0 0 Machine check exceptions MCP: 2106 2106 2106 2106 2106 2106 2106 2106 Machine check polls HYP: 0 0 0 0 0 0 0 0 Hypervisor callback interrupts ERR: 0 MIS: 0 PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event NPI: 0 0 0 0 0 0 0 0 Nested posted-interrupt event PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event -
Could be plex related, though nothing is not working as far as I can tell.
-
Anyone know what this is and what I would need to do to fix it?
Mar 20 09:46:37 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038 Mar 20 09:46:37 Tower kernel: IP: tcp_push+0x4e/0xee Mar 20 09:46:37 Tower kernel: PGD 800000038777e067 P4D 800000038777e067 PUD 385c36067 PMD 0 Mar 20 09:46:37 Tower kernel: Oops: 0002 [#1] PREEMPT SMP PTI Mar 20 09:46:37 Tower kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod bonding e1000e igb ptp pps_core i2c_algo_bit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd mpt3sas intel_cstate intel_uncore ahci libahci i2c_i801 intel_rapl_perf i2c_core raid_class scsi_transport_sas video backlight thermal acpi_pad button fan [last unloaded: pps_core] Mar 20 09:46:37 Tower kernel: CPU: 6 PID: 29298 Comm: docker-proxy Not tainted 4.14.26-unRAID #1 Mar 20 09:46:37 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. Z270N-WIFI/Z270N-WIFI-CF, BIOS F5 07/06/2017 Mar 20 09:46:37 Tower kernel: task: ffff8803f1b52b80 task.stack: ffffc90002134000 Mar 20 09:46:37 Tower kernel: RIP: 0010:tcp_push+0x4e/0xee Mar 20 09:46:37 Tower kernel: RSP: 0018:ffffc90002137d30 EFLAGS: 00010246 Mar 20 09:46:37 Tower kernel: RAX: 0000000000000000 RBX: 00000000000005a8 RCX: 0000000000000001 Mar 20 09:46:37 Tower kernel: RDX: 0000000000000001 RSI: 0000000000000040 RDI: ffff8803efa4cc80 Mar 20 09:46:37 Tower kernel: RBP: ffff8803f1b534a0 R08: 0000000000003890 R09: ffffffff8151db5d Mar 20 09:46:37 Tower kernel: R10: ffff8803efa4cdd8 R11: 0000000000000000 R12: ffff8803efa4cc80 Mar 20 09:46:37 Tower kernel: R13: 0000000000000000 R14: ffff88002e81e000 R15: 00000000ffffffe0 Mar 20 09:46:37 Tower kernel: FS: 000000c420056090(0000) GS:ffff88042ed80000(0000) knlGS:0000000000000000 Mar 20 09:46:37 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 20 09:46:37 Tower kernel: CR2: 0000000000000038 CR3: 000000039335a002 CR4: 00000000003626e0 Mar 20 09:46:37 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 20 09:46:37 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 20 09:46:37 Tower kernel: Call Trace: Mar 20 09:46:37 Tower kernel: tcp_sendmsg_locked+0xa53/0xbac Mar 20 09:46:37 Tower kernel: tcp_sendmsg+0x23/0x35 Mar 20 09:46:37 Tower kernel: sock_sendmsg+0x14/0x1e Mar 20 09:46:37 Tower kernel: sock_write_iter+0x70/0x86 Mar 20 09:46:37 Tower kernel: __vfs_write+0xe1/0x109 Mar 20 09:46:37 Tower kernel: vfs_write+0xc3/0x166 Mar 20 09:46:37 Tower kernel: SyS_write+0x48/0x81 Mar 20 09:46:37 Tower kernel: do_syscall_64+0xfe/0x107 Mar 20 09:46:37 Tower kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 20 09:46:37 Tower kernel: RIP: 0033:0x46f214 Mar 20 09:46:37 Tower kernel: RSP: 002b:000000c4204b4ab8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 Mar 20 09:46:37 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000046f214 Mar 20 09:46:37 Tower kernel: RDX: 0000000000008000 RSI: 000000c4205d4000 RDI: 0000000000000009 Mar 20 09:46:37 Tower kernel: RBP: 000000c4204b4b08 R08: 0000000000000000 R09: 0000000000000000 Mar 20 09:46:37 Tower kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Mar 20 09:46:37 Tower kernel: R13: 0000000000000000 R14: 0000000000455570 R15: 0000000000000000 Mar 20 09:46:37 Tower kernel: Code: d0 75 02 31 c0 41 89 f3 41 81 e3 00 80 00 00 74 1a 44 8b 8f 68 05 00 00 41 d1 e9 44 2b 8f 6c 06 00 00 44 03 8f 74 06 00 00 79 10 <80> 48 38 08 8b 8f 6c 06 00 00 89 8f 74 06 00 00 40 80 e6 01 74 Mar 20 09:46:37 Tower kernel: RIP: tcp_push+0x4e/0xee RSP: ffffc90002137d30 Mar 20 09:46:37 Tower kernel: CR2: 0000000000000038 Mar 20 09:46:37 Tower kernel: ---[ end trace b00939d58195ba58 ]---
-
After my server has been running for a few days the new >_ web terminal stops loading anything, like below. The same thing happens in every browser. Nothing else appears to be having any issues / system seems to be running smoothly. Any ideas?
-
Thanks for the tip, that does seem to have been the problem.
-
Every time TRIM runs I get the following error, sdi being my cache drive, does anyone have any more insight into this? Feb 4 00:18:50 Tower kernel: print_req_error: critical target error, dev sdi, sector 465608767 -
Unless I'm somehow doing this wrong it certainly hasn't fixed it for me.
-
Would you be able to enable the Exif and XMLReader PHP extensions?
-
It pulls the most up to date version every time it starts.
-
2017-03-08 12:00:32,759 DEBG 'deluge-web-script' stderr output: [ERROR ] 12:00:32 pluginmanagerbase:146 Unable to instantiate plugin! 2017-03-08 12:00:32,761 DEBG 'deluge-web-script' stderr output: [ERROR ] 12:00:32 pluginmanagerbase:147 Can't extract file(s) to egg cache The following error occurred while trying to extract file(s) to the Python egg cache: [Errno 13] Permission denied: '/home/nobody/.cache/Python-Eggs/Label-0.2-py2.7.egg-tmp' The Python egg cache directory is currently set to: /home/nobody/.cache/Python-Eggs Perhaps your account does not have write access to this directory? You can change the cache directory by setting the PYTHON_EGG_CACHE environment variable to point to an accessible directory.Since the last update I've been noticing this showing up in the logs. Do I need to do anything about this? As far as I can tell it seems to be working. I did try changing the directory but regardless of where it is something doesn't seem to have permissions.
-
I do not. The cards function fine when tested between two windows machines just as they are using a qsfp cable, I figured unraid would be able to do the same, is that not the case?
-
As far as I can tell from the user manual pertaining to this particular card mode change should be possible. Though even with these instructions I'm pretty lost.
-
Does anyone have experience using this with unraid? I've got it showing up as a pci device, however it is not showing up as an ethernet device so I don't see an interface. It looks like it can operate in either infiniband or ethernet modes, but swapping between the two is a bit beyond me in unraid at this point. Any tips?
06:00.0 InfiniBand [0c06]: Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s - IB QDR / 10GigE] [15b3:673c] (rev b0) Subsystem: Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s - IB QDR / 10GigE] [15b3:0022] Kernel driver in use: mlx4_core Kernel modules: mlx4_core -
Run long test then. You can run all in parallel.
The extended SMART test completed without error on all drives.
You can also try this: http://lime-technology.com/wiki/index.php/FAQ#How_To_Troubleshoot_Recurring_Parity_Errors
I attempted that but was unable to get the script to run. I'm not all that experienced in all this stuff so I probably screwed it up somehow. Getting "./md5_sdd.sh: /bin/bash^M: bad interpreter: No such file or directory"
Also you might find this old thread interesting. Don't think this has been reported recently but not sure if it was ever resolved.
https://lime-technology.com/forum/index.php?topic=38359.msg373934#msg373934
I actually did read through that thread before making this. It doesn't seem like it was ever resolved.
I also came across this older thread in my research, appears to be the same issue - https://lime-technology.com/forum/index.php?topic=44248
It looks like they are assuming the issue is with the AOC-SAS2LP-MV8, which I have. Like the above threads, it seems that the parity issues return if the disks spin down or if the machine is power cycled. Once a correcting parity check has been run I will not get errors again until one of those conditions is met. So at this point I guess I just need to replace that card.
-
Ran the short test on all drives, all returned 'Completed without error'.
[SUPPORT] AMP (Application Management Panel) - CorneliousJD Repo
in Docker Containers
Posted · Edited by Leondre
So I just lost my satisfactory save because apparently it stores the save file in "/home/amp/.config" rather than "/home/amp/.ampdata", which by default is not mapped by the template, so updating the container wiped that.