Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Nanobsd on alix sometimes 100% CPU

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    5 Posts 3 Posters 4.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • X
      xbipin
      last edited by

      can any1 plz let me know the commands or steps to perform to find out the process which causes a 100% CPU usage on nanobsd on alix coz im a complete newbie in BSD and linux.
      im currently running the 11th October 1.2.3 RC3 and i noticed a 100% CPU usage in the last 24hrs after a new install, initially it was normal but i guess after a few hours it started showing 100% CPU usage, what i noticed is any config change causes a 100% CPU and then it never returns to normal untill u reboot it

      one other thing is all my CF cards i use with alix i get these 2 lines in serial console
      WARNING: Expected rawoffset 0, found 63
      WARNING: Expected rawoffset 0, found 922383

      and also after a few reboots etc one of my CF card failed or so as the serial console started saying write failed, next 1 retry and this started coming when loading web configurator and pfsense would never boot up completely so i replaced it with another CF card and that worked fine but the rawoffset warning it still keep getting in serial console

      1 Reply Last reply Reply Quote 0
      • T
        tohil
        last edited by

        hi

        connect with ssh or serial.

        on the console try out:

        ps -aux
        top

        1 Reply Last reply Reply Quote 0
        • X
          xbipin
          last edited by

          on runnin gtop i see this

          28 process 69022 running, 26 slee 1.73,  0.79,  0.33    up 0+01:34:04  16:07:04
          CPU:     % user,     % nice,     % system,     % interrupt,     % idle
          Mem: 13.4Active,  0.0Inact, 285.4ired, 40K  1.3e, 23M Buf, 1 0.0Free
          Swap:

          PID USERNAME  THR PRI NICE   SIZE    RES STATE    TIME   WCPU COMMAND
          6542 root        1 118    0  3268K  1156K RUN      1:44 98.97% syslogd
           621 root        1   7    0 41736K 15680K accept   0:28 100.00% syslogd
           611 root        1   8    0 42760K 16164K nanslp   0:03  0.98% php
           603 root        1   4    0  5132K  2868K kqread   0:01  0.00% lighttpd
           945 root        1   8   20  3156K   796K nanslp   0:01  0.00% check_reload_st
           354 root        1  44    0  3312K  1492K select   0:00  0.00% hostapd
           482 root        1  44    0  3268K  1376K select   0:00  0.00% inetd
          1179 proxy       1 -58   20  3312K  1260K bpf      0:00  0.00% ftpsesame
           421 root        1 -58    0  5716K  2140K bpf      0:00  0.00% tcpdump
           675 nobody      1  44    0  3156K  1308K select   0:00  0.00% dnsmasq
           921 root        1  44    0  3188K  1160K select   0:00  0.00% miniupnpd
           286 root        1  44    0  4660K  1908K select   0:00  0.00% mpd
          6334 root        1  20    0  3508K  2192K pause    0:00  0.00% tcsh
           687 _ntp        1  44    0  3156K  1232K select   0:00  0.00% ntpd
           604 root        1   8    0 39688K  5020K wait     0:00  0.00% php
           615 root        1   8    0 39688K  5020K wait     0:00  0.00% php
           609 root        1   8    0 39688K  5020K wait     0:00  0.00% php

          and the culprit is
          6542 root        1 118    0  3268K  1156K RUN      1:44 98.97% syslogd
            621 root        1  7    0 41736K 15680K accept  0:28 100.00% syslogd

          which causes 100% CPU on any config change at all

          1 Reply Last reply Reply Quote 0
          • X
            xbipin
            last edited by

            i used
            kill -ABRT 6542
            to kill it and then everything back to normal

            1 Reply Last reply Reply Quote 0
            • G
              gloomrider
              last edited by

              @xbipin:

              one other thing is all my CF cards i use with alix i get these 2 lines in serial console
              WARNING: Expected rawoffset 0, found 63
              WARNING: Expected rawoffset 0, found 922383

              and also after a few reboots etc one of my CF card failed or so as the serial console started saying write failed, next 1 retry and this started coming when loading web configurator and pfsense would never boot up completely so i replaced it with another CF card and that worked fine but the rawoffset warning it still keep getting in serial console

              Your description of the bad CF card symptom (web configurator hangs for a long time then throws an error) was identical to mine.  I believe the rawoffset errors can be safely ignored.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.