BCinBC

Members
  • Posts

    32
  • Joined

  • Last visited

1 Follower

Converted

  • Location
    Vancouver, Canada
  • Personal Text
    [Bellerophon] unRAID 6.11.5- Lenovo ThinkStation P410
    Intel E5-2620 v4, 64GB multibit-ECC | 2 * 512GB NVMe Cache [RAID 1],
    2 * 512GB NVMe for download, scratch, etc.| Quadro P4000
    14 drives of various sizes, 12TB parity*2 , 100 TB effective capacity.

Recent Profile Visitors

1024 profile views

BCinBC's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I've actually done the switch way from MACVLAN and it doesn't seem to be as bad this time, for some reason. Bridging with a fixed IP address (about 3 or 4 dockers) seems to work fine... so far. Although, my network monitoring is freaking out a bit, as a bunch of services with dedicated MAC addresses have "gone offline." They work, just it's not the same MAC address responding.
  2. I've tried this more than once and it just ends in tears. I have about 25 containers and a bunch of them don't seem to work in ipvlan. I guess I'll try it again.
  3. I use an external Syslog server on a Synology. I've attached, HTML and CSV format. For a full day or so. Bellerohon Crash 2024-03-24.zip
  4. I've had more than a few crashes with this hardware, ever since I updated to 6.12.8 from 6.12.6. I've swapped over to different hardware than the original crashes save 1 Quad AIC NVME card with 4 * NVMe The HDD's the USB Key. The system will run for up to about a week then it crashes hard. It will respond to pings but everything else appears non-responsive, no SSH. All dockers and VM's gone. System changes from previous failing platform: Same model of motherboard (different one, older BIOS version) Different Intel CPU Different RAM (Still ECC but from 2 * 32 to 4 * Different P4000. Different LSI controller, different SATA breakout cables Different Power supply Different Intel 10GBE NIC Also one bug on these Lenovo P410 Workstation motherboards, a Restart/Reboot always results in a shutdown. I will revert to .6 in the interim. bellerophon-diagnostics-20240323-2051.zip
  5. Is there any documentation on how to configure the Watchdog timer? I have searched the forums and looked briefly through the system options. I'm not sure I want to enable in the command line if it's supported somewhere else.
  6. Thanks for that! Now I know why it got "fixed!" I have had CA Auto Update running for ages, but once I did the reboot maybe the the fix kicked in? I've been up about 6 days now and the issue is certainly gone now.
  7. I found, that recently, all kinds of dockers were getting Zero Byte downloads and non-removable updates. i.e. You'd update it, it wouldn't really do anything but restart the container. Then when you checked it again, it wanted another upgrade. I rebooted the server and this went away. If it happens again I'll definitely file a bug report. It had been up for maybe 45+ days?
  8. I tried to install this on my server so that I could remotely access various dockers. However when I activated ZT the main IP address of my management interface disappeared. The only way I could access the server's management interface and all of the various devices on it was only by using ZeroTier even within my own network. Is it supposed to do this? I would like to be able to connect to the server within my own network as well as be able to remotely access it with say an Android Phone.
  9. I found that changing the docker networking mode from Host to Bridge and manually mapping all of the ports needed, It's been rock solid ever since. As soon as I advanced to the new version that had the new network code it was unstable. This seems to affect only a very small group of people but I see it hit the forum every few weeks. From My plex forum post: https://forums.plex.tv/t/plex-server-not-worked-since-1-13-4-5271-200287a06/312196/12?u=bobertc
  10. Custom: br0 Needed for Unifi, & PiHole. It also seemed to kill Splunk, which is just a Bridge connection. So how does one create a new External IP for a docker with 6.6?
  11. Did anyone else have their bridge configuration disappear? I had a few dockers with fixed IP addresses and they suddenly lost Bridge:0. I'm assuming that this happened with the new bridge utils I saw mentioned in the package updates. I had to undo and redo the settings after backing down to 6.5.3. Love the new UI look though. I posted a bug report.
  12. I was wondering why a bunch of my dockers were failing. Any of them that used BR0, bridge 0 have stopped working. There's no option that I could find in Settings-Networking or Settings - Docker to enable the bridge mode again to allow a Docker to have it's own "host" IP again. I tried to change the networking to Bridge 0 and there's no option so therefore I have to revert for now. (Really nice interface though) I also had to toggle the settings off and on to revert back to the old bridge settings.
  13. It also happened to me on an Ubuntu install on an ESXi server, completely outside of docker. I've been running Plex in my environment for 4-5 years without issue on all kinds of platforms, mostly Linux. This version, I cannot go to as the server cannot phone home to Plex properly. I'll try it on Bare metal if someone really would like me to. It may be "environmental" too. I was thinking of trying it on a second network under pfSense instead of the Ubiquiti ER-X it is now.
  14. https://forums.plex.tv/t/plex-server-only-online-for-30-seconds-every-7-minutes-or-so/293805 Sorry link isn't working on my phone client. That's what I opened with Plex.
  15. I tried it, it didn't fix anything for me. I went back to 1.13.2, all still working there.