Zeroshell 3.8.0 released today

Home Page Forums Network Management ZeroShell Zeroshell 3.8.0 released today

This topic contains 19 replies, has 0 voices, and was last updated by  saraara 9 months ago.

Viewing 15 posts - 1 through 15 (of 21 total)
  • Author
    Posts
  • #44837

    saraara
    Member

    Zeroshell 3.8.0 has been released today.

    Is it safe to upgrade without loosing configuration settings? What improvements has been added?

    Fulvio can you please reply?

    #54484

    reaperz
    Member

    I upgraded several different routers to 3.8.0 and works fine.

    But do not, I repeat DO NOT INSTALL 64-bit kernel!

    After choosing “64-Bit Kernel 4.9.36 ” to boot, my routers did not come up.

    Needed physical intervention.

    #54485

    DrmCa
    Participant

    I would wait at least a few months

    #54486

    pLastUn
    Participant

    I have a 64-bit kernel running.
    32-bit is not good, consumes a lot of RAM!

    #54487

    pLastUn
    Participant

    @drmca wrote:

    I would wait at least a few months

    Fulvio writes “The upgrading to this release is recommended.”

    #54488

    cdpearce
    Participant

    Was the bad 64-bit experience running on raw hardware? Or in some VM environment? I am running ZS on raw hardware.

    Out of interest, what is the recovery procedure if it fails to boot? How easy is it to get the system to boot from the other kernel slot with the known-good system? I haven’t needed to try it yet, and would rather figure out how before the system is broken instead of afterwards!

    #54489

    DrmCa
    Participant

    @plastun wrote:

    @drmca wrote:

    I would wait at least a few months

    Fulvio writes “The upgrading to this release is recommended.”

    Over my 25 year IT career I heard and ignored many recommendations to upgrade, which saved me from having too much gray hair and wasting too much time and $$ on recovering from downtime.

    If you are looking for the latest example, look no further than .NET 4.7 fiasco with Exchange, which is not only affecting Exchange actually.

    OMG, the above memory utilization is horrible. I’ve never been over 126 MB in the last 10 or so years, even after a year of uptime. And I’ve always been running a 32 bit kernel.

    #54490

    reaperz
    Member

    @cdpearce wrote:

    Was the bad 64-bit experience running on raw hardware? Or in some VM environment? I am running ZS on raw hardware.

    Out of interest, what is the recovery procedure if it fails to boot? How easy is it to get the system to boot from the other kernel slot with the known-good system? I haven’t needed to try it yet, and would rather figure out how before the system is broken instead of afterwards!

    I am currently managing total of 6 Zeroshell routers. 5 of them are physical, 1 in virtualbox. All currently running 3.8.0, 32-bit. Memory usage currently between 90 and 120MB. 2 failed upgrade routers were physical.

    Recovery procedure was simple: connect keyboard and display, restart router. And then select previous kernel from boot menu. Later uninstall problematic 64-bit kernel package from web interface.

    DrmCa: I am also usually “if it works, don fix it” kind of IT-guy. But I have had so good experience with upgrading Zeroshell before, so I mistakenly expected it to work out fine this time too.

    Mistake was also running kernel upgrade in 2 routers at the same time. Should have just upgraded my home router and seen it did not work. Would have saved me driving around the city on friday evening 😀

    I won’t touch this 64-bit kernel until next release.

    If it matters, then my upgrade path was:

    3.7.1 (4.4.39) –> 4.4.39 64-bit kernel –> 4.9.27 64-bit kernel –> 3.80 (4.9.36) –> 4.9.36 64-bit kernel (boot fail)

    #54491

    alpha_wall
    Member

    I just upgraded to 3.8 and the 64 bit kernel.
    The process was flawless and worked just fine, no big issue memory usage seems to be stable or actually slightly lower.

    #54492

    iulyb
    Member

    @drmca wrote:

    I would wait at least a few months

    I am stuck at 3.7.1 with 4.9.27-ZS , 32 bits.
    I tried 3.8 on a vbox dev env in order to compile apu drivers but dev env is still broken, I get segmentation fault error when I try to compile the kernel.

    As for memory utilization.. never paid attention:
    Memory 3629532 kB (5% used)

    #54493

    DrmCa
    Participant

    That’s around 177 MB and is pretty low.

    #54494

    Montikore
    Participant

    FYI, i faced a quite big issue : the update modified my admin password!!! (i had to boot a live linux to retrieve it), and transform all $ characters to _ characters…
    Don’t know about other characters…

    #54495

    mountainman
    Participant

    FWIW, I just upgraded to 3.8.0 from 3.6 using the package manager. No issues at all, if anything memory usage is slightly down and performance seems somewhat better (though it might just be a slow night). I did not install the 64 bit kernel.

    #54496

    sukupandachu
    Participant

    Hi group,

    I keep getting random reboots on my ZS, running on Proxmox host.
    version 3.8 keeps rebooting randomly.
    I have tried clean installs, and also upgrades.
    The results are the same.
    Everytime I go back to v3.7.1, it works again fine.

    The vm has the following features:
    2GB RAM
    5GB HDD
    2 x network devices Intel E1000 (vmbr0 and vmbr2)

    Disk details seem good, I can see available space:
    root@zs ~> df -h
    Filesystem Size Used Avail Use% Mounted on
    tmpfs 1011M 16M 996M 2% /
    /dev/sr0 275M 275M 0 100% /cdrom
    shm 1011M 0 1011M 0% /dev/shm
    /dev/vda4 4.0G 3.2G 580M 85% /DB
    /DB/_DB.002 4.0G 3.2G 580M 85% /Database

    Admin logs show the reboots follow no time_related pattern:
    00:14:24 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    01:07:01 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    04:27:08 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    06:16:46 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    12:20:54 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    12:48:09 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    12:57:58 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    15:40:36 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    16:41:11 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    17:47:12 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    20:02:51 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
    20:32:51 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0

    I cannot see a reason for reboot.
    Proxmox vm running the zeroshell does not report error either, it shows it’s up all the time.

    Do you recommend anywhere else to check?
    My workaround is to go back to v3.7.1, but might not be a safe choice.

    Any feedback would be kindly appreciated.

    #54497

    DrmCa
    Participant

    I’d downgrade and leave it, your config is way over what ZS needs, so the new kernel would be the only thing to blame.

Viewing 15 posts - 1 through 15 (of 21 total)

You must be logged in to reply to this topic.