3 Replies Latest reply on Nov 26, 2014 8:48 AM by mhahn

    edison_config.service and journal.logs

    deium

      edison_config.service  adds approx. 471 bytes to the system journals every 10 to 11 seconds.

      Nov 19 02:25:37 ebob2 su[387]: + ??? root:root

      Nov 19 02:25:48 ebob2 systemd[1]: edison_config.service holdoff time over, scheduling restart.

      Nov 19 02:25:48 ebob2 systemd[1]: Stopping The Edison status and configuration service...

      Nov 19 02:25:48 ebob2 systemd[1]: Starting The Edison status and configuration service...

      Nov 19 02:25:48 ebob2 systemd[1]: Started The Edison status and configuration service.

      Nov 19 02:25:48 ebob2 su[391]: Successful su for root by root

      Nov 19 02:25:48 ebob2 su[391]: + ??? root:root

      Nov 19 02:25:58 ebob2 systemd[1]: edison_config.service holdoff time over, scheduling restart.

       

      each 6.25M journal file is filled in just 3:08 hours

       

      -rw-r-----    1 root     systemd-   6553600 Nov 19 17:46 system.journal

      -rw-r-----    1 root     systemd-   6553600 Nov 18 22:58 system@64a4b06504404d598025e561b6b00035-00000000000095db-000508276b38c2d9.journal

      -rw-r-----    1 root     systemd-   6553600 Nov 19 02:06 system@64a4b06504404d598025e561b6b00035-000000000000aef9-0005082a08c6cfd3.journal

      -rw-r-----    1 root     systemd-   6553600 Nov 19 05:13 system@64a4b06504404d598025e561b6b00035-000000000000c884-0005082ca840abba.journal

      -rw-r-----    1 root     systemd-   6553600 Nov 19 08:22 system@64a4b06504404d598025e561b6b00035-000000000000e1a3-0005082f4730fdd7.journal

      -rw-r-----    1 root     systemd-   6553600 Nov 19 11:30 system@64a4b06504404d598025e561b6b00035-000000000000fadd-00050831e942a2a7.journal

      -rw-r-----    1 root     systemd-   6553600 Nov 19 14:39 system@64a4b06504404d598025e561b6b00035-0000000000011418-000508348bf0a841.journal

      -rw-r-----    1 root     systemd-   6553600 Nov 19 17:46 system@64a4b06504404d598025e561b6b00035-0000000000012d4d-000508372d52d425.journal

       

      This of course can be eliminated by the user killing the service with

      systemctl disable edison_config.service and/or

      editing /etc/systemd/journald.conf and uncommenting and setting SystemMaxUse=25M (is not holding to this restraint)

       

      but this should probably be fixed at the image level as it quickly burns out space on an already space limited root partition.

       

      Symptoms include unable to ping google.com after wifi connection

      - receives DNS from wifi router on dhcp but then can not update /etc/resolv.conf as root partition is read only after being maxed out.

       

      Did I win a free Edison?