NichollsGlen
-
Posts
12 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by NichollsGlen
-
-
Just found out that the only apps that show up in previous apps are the ones that were deleted/no longer present on system. Once they're gone, the previous apps shows everything from my user templates.
-
I am attempting to re-install all of my docker apps so I can reduce the size of my docker image. However, none of my apps are listed under Apps > Previous Apps. This is based on the following since I wasn't seeing too much traffic there:
Essentially, all of my templates are located in /boot/config/plugins/dockerMan/templates-user/ but I only see a couple of those in Apps > Previous Apps. I should note that all of my containers were downloaded through CA. What can I do to get Previous Apps to update with those templates to make my life easier when re-installing them?
-
Feel free to close this. I found some posts on Nvidia's support that are similar so I'm going to go that route for support as this doesn't seem like an issue with unRAID.
-
1
-
-
1 hour ago, trurl said:
As far as I know, they should all show up. Maybe there is something wrong with them?
Interesting... I installed all my containers through CA and haven't noticed any issues other than them not showing up there while trying to re-install to reduce the size of my docker image.
-
@trurl or anyone else know how to get all my templates in /boot/config/plugins/dockerMan/templates-user/ to show up in Previous Apps?
-
On 10/3/2019 at 2:46 PM, JPDom1 said:
Been experiencing random Kernal panics not knowing what is causing it. Finally tailed my syslog to get a capture when it crashed and got it.
I think this might be related to this container not 100% sure as i have also recently switched to a new system.
Crash attached below and it is the "FFMPEG" that gets my attention.
Although this crash is different to my others currently running a memtest will let it run over night.
System was up for 10 minutes before it crashed and my unmatic container is configured to scan every 5 minutes so this happened just after the scan.
TR4 1950X
64GB DDR4 Kingston 3000MHZ
Asus X399 Aorus Pro
P2000
Dell H310 x2 It mode
Lots of disks
Oct 3 21:34:04 Mufasa kernel: traps: ffmpeg[31800] general protection ip:152919c2051e sp:1529128aba60 err or:0 in libx265.so.169[1529196fd000+533000] Oct 3 21:34:04 Mufasa kernel: BUG: unable to handle kernel paging request at 0000000000003bc0 Oct 3 21:34:04 Mufasa kernel: PGD 0 P4D 0 Oct 3 21:34:04 Mufasa kernel: Oops: 0000 [#1] SMP NOPTI Oct 3 21:34:04 Mufasa kernel: CPU: 8 PID: 31779 Comm: ffmpeg Tainted: P O 4.18.20-unRAID # 1 Oct 3 21:34:04 Mufasa kernel: Hardware name: Gigabyte Technology Co., Ltd. X399 AORUS PRO/X399 AORUS PRO- CF, BIOS F1 10/01/2018 Oct 3 21:34:04 Mufasa kernel: RIP: 0010:__dec_node_state+0x0/0x53 Oct 3 21:34:04 Mufasa kernel: Code: 84 e0 81 65 44 88 01 c3 48 8b 3f 48 89 f8 48 c1 ef 38 83 e7 03 48 c1 e8 3a 48 69 ff 80 06 00 00 48 03 3c c5 00 65 ea 81 eb 8d <48> 8b 97 c0 3b 00 00 89 f6 b0 ff 48 8d 4c 32 01 65 0f c0 01 65 44 Oct 3 21:34:04 Mufasa kernel: RSP: 0018:ffffc900273e7b70 EFLAGS: 00010213 Oct 3 21:34:04 Mufasa kernel: RAX: 0000000000000037 RBX: ffffea001aa1f940 RCX: 000000001aa1f940 Oct 3 21:34:04 Mufasa kernel: RDX: 22ffea001aa1f908 RSI: 000000000000000c RDI: 0000000000000000 Oct 3 21:34:04 Mufasa kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff8806f6fb9380 Oct 3 21:34:04 Mufasa kernel: R10: ffff88107f2fc000 R11: ffff88103568afee R12: ffff8806f5492518 Oct 3 21:34:04 Mufasa kernel: R13: 80000006a87e5067 R14: ffffc900273e7c98 R15: ffffea001aa1f940 Oct 3 21:34:04 Mufasa kernel: FS: 0000152912b8bb20(0000) GS:ffff88103ca00000(0000) knlGS:000000000000000 0 Oct 3 21:34:04 Mufasa kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 3 21:34:04 Mufasa kernel: CR2: 0000000000003bc0 CR3: 0000000001e0a000 CR4: 00000000003406e0 Oct 3 21:34:04 Mufasa kernel: Call Trace: Oct 3 21:34:04 Mufasa kernel: page_remove_rmap+0x24d/0x29c Oct 3 21:34:04 Mufasa kernel: unmap_page_range+0x5da/0x88a Oct 3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x34/0x70 Oct 3 21:34:04 Mufasa kernel: unmap_vmas+0x4b/0x7f Oct 3 21:34:04 Mufasa kernel: exit_mmap+0xc8/0x16a Oct 3 21:34:04 Mufasa kernel: mmput+0x4d/0xe5 Oct 3 21:34:04 Mufasa kernel: traps: ffmpeg[32284] general protection ip:14e28c68b73e sp:14e28575a4c0 err or:0 Oct 3 21:34:04 Mufasa kernel: traps: ffmpeg[31226] trap invalid opcode ip:147bd24c0d55 sp:147bcb790428 er ror:0 in libx265.so.169[147bd236d000+533000] Oct 3 21:34:04 Mufasa kernel: do_exit+0x3b0/0x8b0 Oct 3 21:34:04 Mufasa kernel: do_group_exit+0x9a/0x9a Oct 3 21:34:04 Mufasa kernel: get_signal+0x417/0x44c Oct 3 21:34:04 Mufasa kernel: in libx265.so.169[14e28c637000+533000] Oct 3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x40/0x70 Oct 3 21:34:04 Mufasa kernel: do_signal+0x31/0x59d Oct 3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x40/0x70 Oct 3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x34/0x70 Oct 3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x40/0x70 Oct 3 21:34:04 Mufasa kernel: ? __switch_to_asm+0x40/0x70 Oct 3 21:34:04 Mufasa kernel: exit_to_usermode_loop+0x25/0x96 Oct 3 21:34:04 Mufasa kernel: prepare_exit_to_usermode+0x66/0x6d Oct 3 21:34:04 Mufasa kernel: retint_user+0x8/0x8 Oct 3 21:34:04 Mufasa kernel: RIP: 0033:0x1529197cfa64 Oct 3 21:34:04 Mufasa kernel: Code: Bad RIP value. Oct 3 21:34:04 Mufasa kernel: RSP: 002b:0000152912b86cc8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff02 Oct 3 21:34:04 Mufasa kernel: RAX: 0000000000000008 RBX: 0000152912b86e80 RCX: 0000000000000480 Oct 3 21:34:04 Mufasa kernel: RDX: 00001528ff35ff78 RSI: 0000000000000008 RDI: 0000152912b86e80 Oct 3 21:34:04 Mufasa kernel: RBP: 0000152912b86f10 R08: 0000152907d23f78 R09: 0000000000000480 Oct 3 21:34:04 Mufasa kernel: R10: 0000000000000020 R11: 0000000000000001 R12: 0000000000000008 Oct 3 21:34:04 Mufasa kernel: R13: 000055ac0aeb6b98 R14: 0000152912b87100 R15: 000055ac0b5a0048 Oct 3 21:34:04 Mufasa kernel: Modules linked in: macvlan nvidia_uvm(O) xt_CHECKSUM iptable_mangle ipt_REJ ECT ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod it87 h wmon_vid bonding edac_mce_amd nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) drm_kms_helper kvm crct10dif_pc lmul crc32_pclmul crc32c_intel ghash_clmulni_intel drm pcbc aesni_intel mpt3sas aes_x86_64 crypto_simd cry ptd agpgart atlantic raid_class scsi_transport_sas syscopyarea nvme ahci i2c_piix4 k10temp sysfillrect glu e_helper i2c_core sysimgblt ccp fb_sys_fops libahci wmi_bmof mxm_wmi nvme_core wmi button pcc_cpufreq acpi _cpufreq Oct 3 21:34:04 Mufasa kernel: CR2: 0000000000003bc0 Oct 3 21:34:04 Mufasa kernel: ---[ end trace 186181c9c6d6be3d ]--- Oct 3 21:34:04 Mufasa kernel: RIP: 0010:__dec_node_state+0x0/0x53 Oct 3 21:34:04 Mufasa kernel: Code: 84 e0 81 65 44 88 01 c3 48 8b 3f 48 89 f8 48 c1 ef 38 83 e7 03 48 c1 e8 3a 48 69 ff 80 06 00 00 48 03 3c c5 00 65 ea 81 eb 8d <48> 8b 97 c0 3b 00 00 89 f6 b0 ff 48 8d 4c 32 01 65 0f c0 01 65 44 Oct 3 21:34:04 Mufasa kernel: RSP: 0018:ffffc900273e7b70 EFLAGS: 00010213 Oct 3 21:34:04 Mufasa kernel: RAX: 0000000000000037 RBX: ffffea001aa1f940 RCX: 000000001aa1f940 Oct 3 21:34:04 Mufasa kernel: RDX: 22ffea001aa1f908 RSI: 000000000000000c RDI: 0000000000000000 Oct 3 21:34:04 Mufasa kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff8806f6fb9380 Oct 3 21:34:04 Mufasa kernel: R10: ffff88107f2fc000 R11: ffff88103568afee R12: ffff8806f5492518 Oct 3 21:34:04 Mufasa kernel: R13: 80000006a87e5067 R14: ffffc900273e7c98 R15: ffffea001aa1f940 Oct 3 21:34:04 Mufasa kernel: FS: 0000152912b8bb20(0000) GS:ffff88103ca00000(0000) knlGS:000000000000000 0 Oct 3 21:34:04 Mufasa kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 3 21:34:04 Mufasa kernel: CR2: 00001529197cfa3a CR3: 0000000001e0a000 CR4: 00000000003406e0 Oct 3 21:34:04 Mufasa kernel: Fixing recursive fault but reboot is needed!TIA,
@JPDom1 did you ever find a fix for this? I've been seeing very similar kernel panics every 15 or so days and not quite sure how to fix it.
-
Seemingly every 15 days, my unRAID server has a hiccup in the middle of the night and the GUI/terminal are inaccessible. When this happens, I have to do a hard reboot and receive no information about what exactly the problem is. I mirrored my syslog to flash and am seeing a kernel panic a couple days ago (on vacation so didn't notice until today). However, I am unable to determine what the problem actually is, so hopefully someone here will understand the logs better. I have attached the logs from July 28th when this happened last. This looks like there's an issue with nvidia-smi, but that's about as far as I've gotten with this.
Let me know if there's any other information needed.
-
5 hours ago, trurl said:
Your docker templates are on your flash drive in config/plugins/dockerMan/templates-user (assuming you haven't wiped them in some way).
Okay perfect, I see those now. Thanks for the tip!
5 hours ago, trurl said:It's also possible to "install" containers from the command line, and so no template would be created since the templates come from the webUI Add/Edit Container page. There are many ways the webUI can't manage a container created at the command line since there is no template for it to work with.
Hmmm, so I still don't see most of the templates in Previous Apps that I installed through CA. I see all of my templates (phew) in /boot/config/plugins/dockerMan/templates-user/ , but only a couple of them show up in Apps > Previous Apps... All of them are in Installed Apps but it'd be nice to see them in Previous Apps so I can set all of them up at the same time. Is there a way to import the XML in the Previous Apps or something so they show up there?
-
On 5/26/2017 at 8:56 AM, Squid said:
How do I move or recreate docker.img?
The easy way to move or recreate docker.img -
1 Go to Settings -> Docker -> Enable Docker, and set to No, then click the Apply button (this disables Docker support)
2 If recreating your docker.img file, then switch to Advanced View, then check off the box and press Delete, then skip to step 53 Using mc or any file manager or the command line, move docker.img to the desired location (/mnt/cache/docker.img is recommended)
4 In Settings -> Docker, change the path for Docker image to the exact location you just copied to
5 Now set Enable Docker back to Yes, and click the Apply button again (re-enabling Docker support)NOTE: If you have created any custom docker networks (eg through docker network create) you will need to recreate them after recreating your image and before reinstalling your applications
The standard way to move or recreate docker.img is to stop Docker support, delete the current image, re-enable Docker supportThe easiest way to reinstall your applications would be to go to the Apps Tab, Previous Apps Section. Then check off all of your previous applications and hit "Install"
Regarding your point about re-installing from the templates in Previous Apps, what do you do if the previous apps doesn't have all the docker containers? For reference, I checked previous apps before attempting to shrink my docker image and noticed that it does not contain any of my current templates for the 20+ containers I have in the Docker tab.
-
Sounds good, thanks for the guidance!
I don't know PHP and the simple changes I tried all caused the script to go haywire, so I ported and modified your script in Python - it can be found at https://github.com/GlenNicholls/unraid_parity_scripter . It uses JSON for the containers to stop when parity is running and containers to start when paused/stopped. I need to add some more stuff to make it generic such that it can be used out of the box in a generic environment, but your suggestions work.
-
I'm noticing a small issue with the script above. I am using the Parity Check Tuning plugin to ensure that parity only runs during specific hours like in the middle of the night. Because of this, I noticed that when the plugin pauses parity check, "mdResyncPos" variable Squid's script checks is >0 and so my stop script isn't being called. Is there something else I can have the script check that will reliably tell me that parity is actively running?
I've been polling that value while parity check is running and it looks like it might stay at a single value for quite a while so I don't think polling with a script would be very accurate.
unRAID server periodically fails requiring hard reboot
in General Support
Posted
I removed the CA plugin "Prometheus nvidia-smi Exporter" and it appears to have solved the issue as my server has now been up for 18 days. I'm not certain this plugin is the culprit, but it has stayed up longer than it has since installing that plugin. I'll update back if I still see the issues I described above.