Jump to content

Fiservedpi

Members
  • Content Count

    102
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Fiservedpi

  • Rank
    Advanced Member
  • Birthday July 17

Converted

  • Location
    Earff

Recent Profile Visitors

382 profile views
  1. Gtx760, right I like to be in the most current build guess my card just isn't up to snuff
  2. Is there any way to roll back the driver version 'm getting the error my device is not compatible with this driver version. Do I have to rollback the whole Nvidia-unraid build? ** I should note the GPU appears to be working with-in my VM but am unable to Passthrough to any Dockers "No Cuda enabled devices available" Using built-in stream user interface -> Detected 24 CPUs online; setting concurrency level to 24. WARNING: You do not appear to have an NVIDIA GPU supported by the 430.14 NVIDIA Linux graphics driver installed in this system. For further details, please see the appendix SUPPORTED NVIDIA GRAPHICS CHIPS in the README available on the Linux driver download page at www.nvidia.com. -> Not installing a kernel module; skipping the "is an NVIDIA kernel module loaded?" test. -> Installing NVIDIA driver version 430.14. -> Skipping check for conflicting rpms. WARNING: The nvidia-uvm module will not be installed. As a result, CUDA will not function with this installation of the NVIDIA driver. WARNING: The nvidia-drm module will not be installed. As a result, DRM-KMS will not function with this installation of the NVIDIA driver. WARNING: You specified the '--no-kernel-module' command line option, nvidia-installer will not install a kernel module as part of this driver installation, and it will not remove existing NVIDIA kernel modules not part of an earlier NVIDIA driver installation. Please ensure that an NVIDIA kernel module matching this driver version is installed separately.
  3. Access to the docker the media lives on an Unmounted NAS
  4. Ok thanks @Squid it occurred to me that this appears during party check I'm going to be adding a new 3.5 hd today then run a party check to see if it happens again
  5. I'm experiencing this to have you figured out if this is normal or something nefarious? why would nginx be pub/disk messaging
  6. One Question. Have you exposed this server to the Internet in any fashion? = yes via port forwarding for plex, sab the majority 85% of error.log.1 is this repeated, looking into the nchan portion it seems to be some type of pub sub client that i have not installed i think there is something nefarious happening Jul 10 03:35:45 Tower nginx: 2019/07/10 03:35:45 [error] 7886#7886: MEMSTORE:01: can't create shared message for channel /disks Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [crit] 7886#7886: ngx_slab_alloc() failed: no memory Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: shpool alloc failed Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: nchan: Out of shared memory while allocating message of size 9960. Increase nchan_max_reserved_memory. Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: *2021857 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=2 HTTP/1.1", host: "localhost" Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: MEMSTORE:01: can't create shared message for channel /disks
  7. why not access the vm via VNC more secure than Port Forwarding
  8. root@Tower:~# ls -al /var/log/nginx total 6292 drwxr-x--- 2 nobody root 80 Jul 11 04:40 ./ drwxr-xr-x 10 root root 720 Jul 11 04:40 ../ -rw------- 1 nobody users 0 Jul 11 04:40 error.log -rw-r--r-- 1 root root 6439274 Jul 12 03:09 error.log.1 i was reading an article pertaining to an issue with Safari Here in another forum but i do not use Safari, pulled some of the data from errolog1 and googled it "shpool alloc failed" this concerns me google eludes to pertaining to gpu mining nicehash, why would nginx be trying to allocate to a "pool" or i t may have to do with AES Jul 10 03:35:45 Tower nginx: 2019/07/10 03:35:45 [error] 7886#7886: MEMSTORE:01: can't create shared message for channel /disks Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [crit] 7886#7886: ngx_slab_alloc() failed: no memory Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: shpool alloc failed Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: nchan: Out of shared memory while allocating message of size 9960. Increase nchan_max_reserved_memory. Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: *2021857 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=2 HTTP/1.1", host: "localhost" Jul 10 03:35:46 Tower nginx: 2019/07/10 03:35:46 [error] 7886#7886: MEMSTORE:01: can't create shared message for channel /disks
  9. Received this error today via email not sure what it's pertaining to besides the obvious something with nginx error: error setting owner of /var/log/nginx/error.log to uid 0 and gid 0: Operation not permitted tower-diagnostics-20190711-2120.zip
  10. have you made the iso share view able within the vm on mine i have a shared documents folder that syncs between the vm and shares
  11. Jul 6 12:35:07 BB-8 root: Installing testdisk-7.0 package... Jul 6 12:35:07 BB-8 nerdpack: Installing tinc-1.0.34 package... nerdpack is installing this package but soemthing is wrong, maybe update nerdpack remove nerdpack re-install , nerdpack, nerdpack, nerdpack ....... manually update this pack via web ui clear tinc log file doubt it's effecting anything though so you can just ignore it as well, or go to var/log and create the tinc file
  12. at the end of the docker name you just have to :tag [plex/arm86] .... something along those lines Edit the container and change the :latest tag to the new tag you want, you get the tags from the dockerhub page https://hub.docker.com/r/linuxserver/plex/
  13. worse comes to worse just run that cable out A window or what not like dont bother hiding/burying it try to make it blend in
  14. maybe related to a plugin can you post your diagnostic file