salvdordalisdad

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About salvdordalisdad

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. D'oh! Rookie error! Very grateful for that. Increased my understanding by one notch... Thank you.
  2. Hi Guys, Not sure it's a bug, but just updated from 6.8.3 to 6.9.2 Was advised to post it here to let you (dlandon) know. 1st thing I noticed which was OK but now isn't quite working is on the "Main" tab. Under the SMB / NFS / ISO shares section, the orange buttons labelled "Add Remote NFS/SMB share" and "Add ISO File Share" had disappeared & a debug line was displayed instead. So I deleted my two NFS shares & the buttons re-appeared. But if I add a NFS share back again, the "add" buttons disappear and I get this line of debug instead:
  3. Hi Guys, Not sure it's a bug, but just updated from 6.8.3 to 6.9.2 1st thing I noticed which was OK but now isn't quite working is on the "Main" tab. Under the SMB / NFS / ISO shares section, the orange buttons labelled "Add Remote NFS/SMB share" and "Add ISO File Share" had disappeared & a debug line was displayed instead. So I deleted my two NFS shares & the buttons re-appeared. But if I add a NFS share back again, the "add" buttons disappear and I get this line of debug instead: Fatal error: Uncaught Error: Call to undefined function _()
  4. Hi, I have a script which updates my DDNS, and uses dig which now throws library errors. Nothing has been updated in a while, so I'm not sure why it's suddenly broken. Tested on my primary & backup systems & both the same result. So I'm trying to understand why & fix it, so I ended up here. I tried your "fix" updating those two libraries, but both those links say "404 file not found". So I looked closer & used the ones which are there on the slackware repository, but I think that was a bad idea as it hasn't fixed dig or nslookup & gives more
  5. Hi, I have a script which updates my DDNS, and uses dig which now throws library errors. Nothing has been updated in a while, so I'm not sure why it's suddenly broken. Tested on my primary & backup systems & both the same result. So I'm trying to understand why & fix it, so I ended up here. I tried your "fix" updating those two libraries, but both those links say "404 file not found". So I looked closer & used the ones which are there on the slackware repository, but I think that was a bad idea as it hasn't fixed dig or nslookup & gives more
  6. So with no answers, I'm forced to learn a bit about dockers & write my own! Interesting, so far I've built a basic --dns test & it worked just like the docker website said it would, so I don't know why this one doesn't do that... It'll take me a while to get to grips with it allthen there will be an u[date here.
  7. OOh - just found this how-to-find-out-a-bit-more-about-the-network command (from the unraid CLI): docker network inspect br0.333 [ { "Name": "br0.333", "Id": "c71ca99f22b0b386afe6f48b269c6f61c7fd88f4905a1721a3b20ad585f35c54", "Created": "2019-07-07T23:02:56.253031071+01:00", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.200.0/24",
  8. Well, that was interesting, you're most helpful, thanks, much appreciated...(who noticed the "advanced" button before?!)(excellent!) The interesting part is - it didn't work - but in an interesting way... Added command line options but only some of them worked. Tried using the recommended syntax & it didn't work, nothing made it into the resolv.conf file. Then I tried more options like this line: --dns=10.0.0.10 --dns=10.0.0.11 --dns-search=example.com The dns values did NOT make it into the resolv.conf, but the dns-search value DID get propagated, how interes
  9. Hi Guys, Just hitting a whole bunch of dead ends. I've googled and found some partial answers, but they don't relate, so asking here optimistically... Using docker with host mode = AOK, the docker absorbs the /etc/resolv.conf config from the unraid host. 1.1.1.1 etc. and can resolve names. However - same docker using a vlan via bridged network interface br0:333 (vlan id 333) has only one entry in the /etc/resolv.conf file of 127.0.0.11 That doesn't resolve, but traffic flow is fine - ping works to the outside world. I can add /etc/hosts entries &
  10. well, isn't that interesting... That port 80 was listening was a clue. but it's not obvious from the unraid docker settings why it's not set right. The "Advanced settings" shows 2 options for port acces using http. (and 2 for https, not that I will use that indoors). The first one isn't adjustable very much, but the second one works! I set the first one to 9999, which clearly doesn't work, as there's nowt listening on 9999 internally. I set the second one t6o "container port 80", and "host port 99" Yup, that worked...well, mostly. http://host:99 opens the bl
  11. So I'm doing some more basic diags, and learning a lot! tcpdump (from the nerd pack) shows the incoming connections, to 172.168.0.2:metagram (I looked it up & it is TCP port 99), so that's reasonably good - it means the container config in unraid is correct. Then I thought I'd check the open (listening) ports inside the docker (I didn't know I could do that 3 hours ago!). netstat -lntup shows the only ports listenign are 0.0.0.0:443 127.0.0.1:9000 0.0.0.0:80 So that doesn't really help either, as it kinda shows it's not listening on port 99...
  12. Hi Chaps, I too can't seem to access heimdall...unraid 6.7, about 14x freshly deleted & reinstalled, even with default settings...always get "unable to connect" I did see a similar post to my issue, with the comment "you've configured it wrong", so I checked. bridge mode, port 99, all the default values as far as I can tell. (there are not that many tbh) It was working OK, on my demo unraid license, but then I started all over from scratch, and now it refuses point blank. I've even deleted all my dockers (only 6, so nbd, but configured, so slightly wasted effort),
  13. Hi Guys, I've been bashing my head on this one for a while now, so it's turned into a bit of a saga (as my old Viking chum used to say - really!). Started with a Dell R510 with H200, and found the (well documented) problem there. So tried to flash it & failed, now that H200 is invisible, no bios comes up in any machine ;-( So I bought a pre-flashed IT-mode LSI controller, so after 3 months I've now got a working Unraid with 9 SAS drives, great! Tried to fill the last 3 disk slots & failed. Lights stay on permanently, and the drives don't show up in Unraid. I fo