Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 24

Thread: Slow boot time

  1. #11
    Untangle Ninja jcoehoorn's Avatar
    Join Date
    Mar 2010
    Location
    York, NE
    Posts
    1,841

    Default

    For my money, it's likely a bad Debian driver. Try installing a hyper-visor (vmware etc) first and setting it up as a VM. If the hyper-visor boots, Untangle should work well. This can be a bit of a pain mapping interfaces, but otherwise can work great.
    Sandy Toes likes this.
    Five time Microsoft ASP.Net MVP managing a Lenovo RD330 / E5-2420 / 16GB with Untangle 16.2 to protect 500Mbits for ~450 residential college students and associated staff and faculty

  2. #12
    Newbie
    Join Date
    Mar 2021
    Posts
    3

    Default

    Quote Originally Posted by donhwyo View Post
    Last time I saw slow booting was something about "A start job is running for Raise network interfaces". It was a bug and fixed.

    What are you seeing in the logs?
    "A start job is running for Raise network interfaces" takes about 35 sec.
    Haven't fully looked at the logs yet.

  3. #13
    Untangle Ninja
    Join Date
    May 2008
    Posts
    1,526

    Default

    35 seconds is not that bad I don't think. ifupdown2 might fix that if it ever gets implemented. What do
    Code:
    [root @ homeuntangle] ~ # systemd-analyze
    and
    Code:
    systemd-analyze blame
    show?

    Don't know if they still do support in the 14 day trial anymore. Might be worth a try. Click the help button to the right lower part of this page.
    Last edited by donhwyo; 04-01-2021 at 07:10 PM.

  4. #14
    Untangle Ninja
    Join Date
    May 2008
    Posts
    1,526

    Default

    I said 35 seconds seems normal because mine showed 46 seconds. You must have something else going on also.

    After more looking at other systems I think network startup is slower than any other. Slow network start on boot has been around since switching over to systemd as far as I can tell. Maybe early 2019. I am not an expert on systemd but my proxmox server, with far more complicated networking starts networking much faster. If openvswitch is why it is faster maybe that should be looked into. It also would give many more networking options.

    Untangle
    Code:
    [root @ homeuntangle] ~ # systemd-analyze critical-chain
    The time after the unit is active or started is printed after the "@" character.
    The time the unit takes to start is printed after the "+" character.
    
    graphical.target @1min 9.229s
    └─multi-user.target @1min 9.228s
      └─untangle-vm.service @46.561s +22.666s
        └─network-online.target @46.521s
          └─network.target @46.472s
            └─networking.service @1.091s +45.379s
              └─ifupdown-pre.service @510ms +557ms
                └─systemd-udev-trigger.service @313ms +191ms
                  └─systemd-udevd-kernel.socket @299ms
                    └─system.slice @286ms
                      └─-.slice @285ms
    proxmox

    Code:
    root@pve:~# systemd-analyze critical-chain
    The time after the unit is active or started is printed after the "@" character.
    The time the unit takes to start is printed after the "+" character.
    
    graphical.target @8min 27.516s
    └─multi-user.target @8min 27.516s
      └─pve-guests.service @1min 16.107s +7min 11.407s
        └─pve-ha-lrm.service @1min 15.007s +1.093s
          └─pveproxy.service @1min 12.580s +2.421s
            └─pvedaemon.service @1min 800ms +11.774s
              └─pve-cluster.service @59.175s +1.540s
                └─rrdcached.service @58.002s +1.164s
                  └─remote-fs.target @57.941s
                    └─remote-fs-pre.target @57.938s
                      └─open-iscsi.service @57.797s +136ms
                        └─iscsid.service @57.405s +383ms
                          └─network-online.target @57.402s
                            └─network.target @57.170s
                              └─networking.service @54.349s +2.816s
                                └─openvswitch-switch.service @49.722s +4.618s
                                  └─openvswitch-nonetwork.service @46.949s +2.762s
                                    └─apparmor.service @46.025s +911ms
                                      └─local-fs.target @45.925s
                                        └─R10\x2d4x2TB.mount @1min 35.895s
                                          └─local-fs-pre.target @3.391s
                                            └─dm-event.service @6.559s
                                              └─systemd-journald.socket @2.789s
                                                └─-.mount @2.775s
                                                  └─system.slice @2.775s
                                                    └─-.slice @2.775s
    Summarizing
    Code:
    proxmox
    
    network-online.target @57.402s
                           └─network.target @57.170s
                             └─networking.service @54.349s +2.816s
                               └─openvswitch-switch.service @49.722s +4.618s
                                 └─openvswitch-nonetwork.service @46.949s +2.762s
    
    proxmox takes 10.453 to start networking
    
    Untangle
    
      └─untangle-vm.service @46.561s +22.666s
        └─network-online.target @46.521s
          └─network.target @46.472s
            └─networking.service @1.091s +45.379s
              └─ifupdown-pre.service @510ms +557ms
                └─systemd-udev-trigger.service @313ms +19
                
    Untangle takes 46.011 seconds
    Other less complicated debian buster vm's start in less than 5 seconds.

    I know startup time is not a primary consideration but this seems excessive.

    Thanks

  5. #15
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    25,859

    Default

    Code:
    [root @ untangle] ~ # systemd-analyze critical-chain
    The time after the unit is active or started is printed after the "@" character.
    The time the unit takes to start is printed after the "+" character.
    
    graphical.target @26.950s
    └─multi-user.target @26.950s
      └─stunnel4.service @469ms +5.704s
        └─basic.target @465ms
          └─sockets.target @465ms
            └─uuidd.socket @465ms
              └─sysinit.target @464ms
                └─swap.target @464ms
                  └─dev-disk-by\x2duuid-b50abf89\x2d124f\x2d405e\x2d8f3f\x2dcc33d8fc8d95.swap @453ms +10ms
                    └─dev-disk-by\x2duuid-b50abf89\x2d124f\x2d405e\x2d8f3f\x2dcc33d8fc8d95.device @440ms
    Use hardware that isn't China junk?
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  6. #16
    Untangle Ninja
    Join Date
    May 2008
    Posts
    1,526

    Default

    It is a dell r715 poweredge server. Not new but top of the line not too long ago. Well maybe longer in computer years. LOL

  7. #17
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    25,859

    Default

    Quote Originally Posted by donhwyo View Post
    It is a dell r715 poweredge server. Not new but top of the line not too long ago. Well maybe longer in computer years. LOL
    That's surprising... mine is one of my appliances but it's a positively ancient design (in computer years), almost 10 years old now running an i3 CPU.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  8. #18
    Untangle Ninja
    Join Date
    May 2008
    Posts
    1,526

    Default

    Not so surprising since your appliance was designed to handle networking. Also probably why Untangle never noticed either.

    The op is also on a hp 620. That may be a server too. To busy to look it up now.
    Last edited by donhwyo; 04-02-2021 at 11:34 AM.

  9. #19
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    25,859

    Default

    Quote Originally Posted by donhwyo View Post
    Not so surprising since your appliance was designed to handle networking. Also probably why Untangle never noticed either.

    The op is also on a hp 620. That may be a server too. To busy to look it up now.
    The advantages of the appliances are exclusively in simplified BIOSs and extra PCIe lanes to handle heavy network IO. Yes, I expect them to have improved boot times relative to actual servers... but that advantage is tied up in the BIOS's boot speed, not the OS. I expect your Dell to take longer to do Dell things before it even tries to crank up the OS. The actual OS boot times for both platforms should be approximate, which is what we're measuring here.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  10. #20
    Untangle Ninja
    Join Date
    May 2008
    Posts
    1,526

    Default

    The hp 620 may also be a laptop.

Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2