Jump to content

witalit

Members
  • Posts

    211
  • Joined

  • Last visited

Posts posted by witalit

  1. I went through the long process recently of trying to get Graylog and Elasticsearch running in dockers. I got there in the end after hours of troubleshooting but now I have noticed an issue with docker in general which causes a problem with Graylog I guess if the dockers don't restart in the right order. 

     

    Everyday around 5AM they all seem to restart not just those dockers basically all of them.. Logs don't really show much that I can understand is anyone able to advise what it could possibly be? Diags attached.

     

    Thanks in advance!

    unraid-diagnostics-20231227-1143.zip

  2. On 5/26/2023 at 5:06 AM, CraziFuzzy said:

    quick update - it seems the errors I was seeing were due to folder permissions.  For some reason the folders that the containers create don't get set with permissions that those same containers can access.  chmod 777'ing them got the containers to all start up.. I think.. so far... now to actually learn how to USE graylog...

     

    How has it been for you? I am struggling to setup graylog also but all the guides I follow seem to be outdated or not have any fixes for the numerous issues I see. 

  3. 18 hours ago, Hoopster said:

    I am glad that worked for you (others as well), but it is certainly not normal or expected. 

     

    Have you tried a reboot after it came up and did it take that long again?  If so, your configuration should be checked as something is not right.

     

    Yes looks like you are right, I just rebooted again and have the same issue. Samba comes up as I can access shares but not able to get to Web GUI again.

     

    Edit: 5-10 mins wait and gui is accessible now, probably more normal right?

  4. Updated to 6.9.0 with success. At first I thought it went horribly wrong as the Web Gui would not load... spent an hour troubleshooting.. got fed up left it. Come back 45 mins later and nothing was wrong, I guess there was a delay before web GUI was live.. impatient most likely. 

     

    Just in case anyone else panics, give it some time after the update to try access Web GUI.

  5. 2 hours ago, johnnie.black said:

    Same users have issues getting a DHCP address with latest release, try setting a static address.

    As easy as that.. :). Working fine now after a reboot, guess I can just keep it static anyways. Thanks to Squid and Johnnie for the help here. 

     

    Has this been reported as a bug at all?

     

    Cheers

  6. Replaced Flash disk just in case. Boots fine after I deleted network.cfg, rebooted and it stays. IP assigned from DHCP then I turn off Bonding and it drops I can no longer contact server. 

     

    I restart Network service via IPMI, can get back on box. What I have noticed now is both my eth0 and eth1 have the same MAC Address? See below, last image is what my MAC should be for IPMI nic.

     

    image.thumb.png.26b774b238e573fd38ce68e423d1010e.png

     

    image.thumb.png.669e9b65fa2d44a63682db720589d304.png

     

    image.thumb.png.76b138ba6a2d3973641a1a9900f151e7.png

     

     

  7. So I upgraded my CPU and after first boot I see my server has no IPv4 address. Looked at some old threads and deleted my network.cfg, it reboots I get an IP all fine. If I then reboot the system it once again is unable to set an IP. 

     

    I have attached my diags if anyone can assist? Never had this issue before can't see why upgrading the CPU would cause this issue, I did notice my BIOS time was 1 hour behind updated that yet issue still occurs. 

     

    Thanks

    unraid-diagnostics-20200422-1428.zip

×
×
  • Create New...