local.bin

Members
  • Posts

    298
  • Joined

  • Last visited

Report Comments posted by local.bin

  1. On 5/28/2022 at 8:24 AM, bonienl said:

    Opening the log of a stopped container just shows what has been stored, but is not updated in real-time and the user is asked to close the window at their convenience.

     

    Is this the case?

     

    I ask, as I am unable to see why a docker failed to start, as the docker log opens and closes immediately.

     

    How do we access the log of that closed docker?

    • Thanks 1
  2. 5 minutes ago, limetech said:

    One of the bz files is bzmodules.  That file is loopback mounted readonly onto /lib/modules and consists of all the kernel loadable modules (ie, drivers).

     

    It just so happens that the first driver the kernel requires during startup is 'bonding'.  If bzmodules is corrupted then it can't load this driver and you see that message.

     

    Agreed this is confusing, we will add some code to detect this case and output a different message.

    Thanks for that :) but I have just found it,  it was eth1 fell out of the bond...????

     

    I have no idea how as i didn't change it myself, as its taken me a few hours to track it down.

     

    Apologies for the noise.

  3. 1 minute ago, bonienl said:

    Your errors messages indicate something is wrong with the bz* files on the USB stick (maybe bad download).

     

    You can try to revert to the previous version (see Tools -> Update OS)

    And afterwards update again (make sure the USB stick is error free)

     

    I cannot access the gui and have replaced all the bz files a couple of times now. Downloaded 6.7.2 as well.

  4. 3 minutes ago, heffe2001 said:

    I'm using a bonded pair of 10g ports on my HP server, and it's working just fine with RC3, so bonding is installed and working.

     

    Okay thanks for that :) at least I know it should work.... getting half a dozen RTNETLINK answers: File exists messages in the log, but not much else.

  5. 3 hours ago, local.bin said:

    My network leds go out and I cannot access the server.

     

    Went on rc for the login screen and now with a whole heap of grief, kicking myself .

     

     

    I have tracked it down to the bonding driver no longer existing and therefore not getting loaded.

     

    I have tried to insmod bonding and it does not exist?

  6. 2 minutes ago, dalben said:

    Yes. Stick it into a Windows pc and you have full access to the usb. 

    Thanks, I guess I meant more of which files need replacing.

     

    I remember it used to be just a couple of files to replace but there are 16 in 'previous'... safe to restore them all?

     

    Searching but can't seem to find it written anyway.

  7. 1 minute ago, Frank1940 said:

    Unless you are being subject to attacks by a three-letter agency or your server protects data for major bank or corporation, you don't need a fifty character password.   

     

    You pull your flash drive and in the config folder, delete both the passwd and shadow  files and you will have no passwords.

     

    BTW, you appear to be the guy where the network LED's are out.  I would suspect that your server never even booted. 

     

    Contractual docs for clients, call me paranoid.

     

    It boots and and the leds light and then after booting completes both ports go dead, no lights on the server or the switch.

     

    Is it possible to restore the 'previous' directory while accessing the stick outside of the server?

  8. 6 minutes ago, Frank1940 said:

    Come on people, where are your diagnostic files?  IF the GUI is not accessible, hook up a monitor and keyboard and use the console.   You type the following command at the console (or any terminal for that matter):

    
    diagnostics 

     

    If only I didn't have 50 character passwords :( :) 

     

    Can I ask, does the updater save the previous version on the stick, so I can manually copy over rc3 please?

  9. 2 hours ago, bonienl said:

    This issue results in many false positives, but still containers which have a true update, are updated.

    The -rc release of version 6.8 is imminent, just a little bit more patience 😊

     

    I guess I was meaning for those of us with servers in production :) and not wanting to go to release candidates.

     

    At least we'll have updated dockers every day :)