physikal

Members
  • Posts

    49
  • Joined

  • Last visited

Everything posted by physikal

  1. Anyone else getting the error: ERROR contact:service ping satellite failed {"Satellite ID":
  2. Ok good to know. Are these trim errors going to blow anything up in the future? or it's just saying it's unable to trim and going from there? Also, someone in another thread recommended installing one of these: Amazon.com: I/O CREST 2 Port SATA III PCI-e 2.0 x1 Controller Card Asmedia ASM1061 Non-Raid with Low Profile Bracket SY-PEX40039: Electronics and plugging the drives into that. If I shut the server down completely and install this, then move the drives to this...will that destroy my array because I moved the cache drives? Or will unraid detect all that on it's own? Or should I go through the process of completely moving cache to array, removing cache drives, shut down, install card, plug drives into the card, boot back up and reconfigure cache? Thanks for the quick response!
  3. I'm actually running into this same exact problem...if connecting to SATA ports isn't an option do I need to switch back to spinning disks for my cache instead of SSD's? Or can the SSD's run fine w/o trim?
  4. Any chance the jar file issue will be resolved? @hernandito
  5. Any thoughts on creating a container for this? https://github.com/upfiring/upfiring-update/releases Hope all is well @Jcloud !
  6. It's just really odd that it's showing as it came from an old IP address I had assigned via my ISP. Not an internal address.
  7. yeah doing this now, thanks a ton for the info. I'm also rebuilding any old VM's I had that were hosting game servers under that 50.106.16.89 ISP assigned address. I'm also digging through my FW to see if I can get a mac address of that address being used internally and seeing if it matches any of my mac addresses on my internal network. Wish I had a clear smoking gun on which machine was compromised.
  8. also I should clarify, blue means closed. So it confirmed closed.
  9. But it's port 179? And I have no vmware installs in my home lab.
  10. No it's 179/bgp - which is odd.
  11. yeah I 100% agree it's not a long term solution. Just to buy me some time while I investigate and rebuild some VM's that could be compromised.
  12. I thought so as well. What's odd is the 50.106.16.89 address was an old address I had from my ISP, and when I checked my fw I saw 1 active session on port 6895 to an Amazon IP (Assuming AWS).
  13. yes I do have a QNAP device actually. I'll check that out I guess. I've turned on geoblocking on my fw for the time being.
  14. I'm seeing this in my system logs: Jan 14 00:23:31 Tower nginx: 2019/01/14 00:23:31 [error] 4984#4984: *1158237 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:31 Tower nginx: 2019/01/14 00:23:31 [error] 4984#4984: *1158237 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:33 Tower nginx: 2019/01/14 00:23:33 [error] 4984#4984: *1158248 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:33 Tower nginx: 2019/01/14 00:23:33 [error] 4984#4984: *1158248 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:34 Tower nginx: 2019/01/14 00:23:34 [error] 4984#4984: *1158255 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:35 Tower nginx: 2019/01/14 00:23:35 [error] 4984#4984: *1158255 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:35 Tower nginx: 2019/01/14 00:23:35 [error] 4984#4984: *1158261 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:37 Tower nginx: 2019/01/14 00:23:37 [error] 4984#4984: *1158261 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:39 Tower nginx: 2019/01/14 00:23:39 [error] 4984#4984: *1158275 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:39 Tower nginx: 2019/01/14 00:23:39 [error] 4984#4984: *1158275 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" Jan 14 00:23:40 Tower nginx: 2019/01/14 00:23:40 [error] 4984#4984: *1158278 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/" What's interesting is I'm 99% sure my unRAID box is not externally accessible. So that concerns me. Any ideas on this?
  15. I was previously on 6.5 and I had no issues with my VM's when Parity check would kick off, now every time parity kicks off I get alerts from software that is running on the VM non-stop the entire time parity check is running (~20hrs). The thing that gets me is it shouldn't even be in the parity check since this VM is running directly from an unassigned drive. I wouldn't think parity check would impact that. Any thoughts? Thanks!
  16. I'm looking at DR scenarios and am curious if there is a guide out there on how to backup unraid as well as restore in the event of a flash drive (unraid OS) failure? Basically if my flash drive that unraid is installed on fails...I don't want to lose all my array config which I would imagine would cause a loss of data....how do I prevent this. Thanks!
  17. What's the process for migrating a VM from an Unassigned HDD to an Unassigned SSD? Is there a guide somewhere? Thanks!
  18. @Jcloud so is your repo going to have an update soon that fixes a lot of this and works w/ the main repo? Or are we supposed to remove yours and start over with the main repo again? I"m asking because something is definitely not right. My peers is still really low and I'm not getting additional data as frequent as I used to on the other repo. Thanks!