Sim1

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by Sim1

  1. Hey so I have an issue right now where I am trying to upgrade my nodered docker container, but when I try to do so within the container (manage palette), I get the following error: 2022-06-12T19:40:17.485Z [err] npm ERR! Your cache folder contains root-owned files, due to a bug in 2022-06-12T19:40:17.485Z [err] npm ERR! 2022-06-12T19:40:17.485Z [err] previous versions of npm which has since been addressed. 2022-06-12T19:40:17.485Z [err] npm ERR! 2022-06-12T19:40:17.485Z [err] npm 2022-06-12T19:40:17.485Z [err] ERR! To permanently fix this problem, please run: 2022-06-12T19:40:17.485Z [err] npm ERR! sudo chown -R 1000:1000 "/data/.npm" 2022-06-12T19:40:17.496Z [err] 2022-06-12T19:40:17.496Z [err] npm ERR! A complete log of this run can be found in: 2022-06-12T19:40:17.496Z [err] npm ERR! 2022-06-12T19:40:17.496Z [err] /data/.npm/_logs/2022-06-12T19_40_17_488Z-debug.log When I go into the command line, I can see the files within the appdata folder for the docker are owned by multiple different users, including "root" , "nobody", and my personal username. My question is, which user is the best-practice owner for these files in node red? I'm having some difficulties figuring out how to order the item that they said was the error in bash, so I was also wondering if it is ok to just do chown -R within the command line for the folders within the appdata folder?
  2. Hey so I have an issue right now where I am trying to upgrade my nodered docker container, but when I try to do so within the container, I get the following error: 2022-06-12T19:40:17.485Z [err] npm ERR! Your cache folder contains root-owned files, due to a bug in 2022-06-12T19:40:17.485Z [err] npm ERR! 2022-06-12T19:40:17.485Z [err] previous versions of npm which has since been addressed. 2022-06-12T19:40:17.485Z [err] npm ERR! 2022-06-12T19:40:17.485Z [err] npm 2022-06-12T19:40:17.485Z [err] ERR! To permanently fix this problem, please run: 2022-06-12T19:40:17.485Z [err] npm ERR! sudo chown -R 1000:1000 "/data/.npm" 2022-06-12T19:40:17.496Z [err] 2022-06-12T19:40:17.496Z [err] npm ERR! A complete log of this run can be found in: 2022-06-12T19:40:17.496Z [err] npm ERR! 2022-06-12T19:40:17.496Z [err] /data/.npm/_logs/2022-06-12T19_40_17_488Z-debug.log When I go into the command line, I can see the files within the appdata folder for the docker are owned by multiple different users, including "root" , "nobody", and my personal username. My question is, which user is the best-practice owner for these files in node red? I'm having some difficulties figuring out how to order the item that they said was the error in bash, so I was also wondering if it is ok to just do chown -R within the command line for the folders within the appdata folder?
  3. Ok so a little update here - no more logs, but I think I found the culprit, though I am not entirely sure why it is occurring. So I also use my unRAID server to host a zwave docker, and the server is not in an optimal position for the z wave stick, so I have had it connected to the server via usb over ethernet. The USB over eth female end has a power supply, which appears to supply 5 V power to allow for USB to be transmitted over what would normally be too long of a run for USB (or so I understand). I believe that this power supply was the culprit for a couple of reasons. 1. Whenever the server would shutdown, it would cause an odd continuous alarm sound, that would not resolve with unplugging both of the power supplies (the new server chassis came with a redundant PSU) and would only resolve when removing the implicated USB. 2. [Most Importantly] When the system would start up with the USB connected, the system would not recognize the drives. When the usb was disconnected, then it would seem to recognize all of the drives without issue. Also interestingly, when I disconnected the power supply part of the USB over ethernet, the USB device still worked normally. My theory is that there was something from the USB power supply that was essentially backfeeding into the motherboard in some fashion that affected the HBA card enough to prevent it from recognizing the drives. I don't have some massive insight into the issue, but only wanted to post this as a potential solution to people who might be having the same issue down the road.
  4. OK I'll post logs when the card fails to be recognized on startup. I know about disk 10. Getting a replacement drive has been a bit of a saga including one drive from Amazon with a bogus warranty that I had to return and another drive that failed preclear...
  5. Here are the diagnostics mediaserver-diagnostics-20220501-2056.zip
  6. So I recently upgraded my server to use a backplane (specifically a supermicro BPN-SAS2-846EL1). I am running an IBM 1015 card flashed to IT mode. I previously had been using a SAS to sata cable for my drives, but now have the backplane connected with two of the SAS-SAS cables. The issue I am having is that since switching to use the backplane I am having some start up issues. Essentially, it seems to be a dice role as to whether the HBA card/backplane get recognized by unraid on boot up. If it is not recognized, then essentially unraid will show all drives as missing, however, if it is recognized, then it works perfectly, including hotswap features, and read/write speeds are excellent. I'm not really sure exactly what to make of it. Since the backplane is working well when recognized, I would assume that the issue is more likely to be related to the HBA, and I'm not sure if I need to get a new HBA, or whether it could be something simpler, like the cable configuration is wrong (I have both cable slots for the card connected to J0 and J1 on the backplane). Either way, it's kind of frustrating because it means anytime I do a reboot right now, I have to deal with the possibility of troubleshooting the server for a while, just rebooting it until the backplane is properly recognized, after which it will be extremely stable. Thanks for any insight on this in advance.