Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 4 subscribers
  • Views 2141 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HAL (Hardware Abstraction Layer) system daemon not running & Let's Encrypt certificate renewal failed

mfpck

Dear all,

Since a necessary reboot I get every hour the notification:

HAL (Hardware Abstraction Layer) system daemon not running

+ Let's Encrypt certificate renewal failed 

Any Ideas ?



This thread was automatically locked due to age.
  • 0

    Hallo,

    Reboot again?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    haha - should this windows rel. trick also work here...I will try this weekend ./

  • 0 in reply to mfpck

    Two reboots later the issue persists, + bonus errors > is my system dying and if why;

    fallback log:

    2021:03:25-00:34:50 utm [user:notice] rchal: conservative cpufreq governor could not be loaded
    2021:03:25-00:35:20 utm [user:notice] rchal: powersave cpufreq governor could not be loaded
    2021:03:25-00:35:20 utm [user:notice] rchal: userspace cpufreq governor could not be loaded
    2021:03:25-00:35:20 utm [user:notice] rchal: conservative cpufreq governor could not be loaded
    kernel messages:
    2021:03:25-00:33:19 utm kernel: [ 910.125816] hald[12675]: segfault at 746e6582 ip 0000000008054077 sp 00000000ffdc0f60 error 4 in hald[8048000+54000]
    2021:03:25-00:33:50 utm kernel: [ 940.374950] hald[12805]: segfault at 746e6582 ip 0000000008054077 sp 00000000ffdc45d0 error 4 in hald[8048000+54000]
    2021:03:25-00:34:20 utm kernel: [ 970.616111] hald[13058]: segfault at 746e6582 ip 0000000008054077 sp 00000000ffa007b0 error 4 in hald[8048000+54000]
    2021:03:25-00:34:50 utm kernel: [ 1000.856702] hald[13166]: segfault at 746e6582 ip 0000000008054077 sp 00000000fff0aea0 error 4 in hald[8048000+54000]
    2021:03:25-00:35:20 utm kernel: [ 1031.096268] hald[13581]: segfault at 746e6582 ip 0000000008054077 sp 00000000fff81dc0 error 4 in hald[8048000+54000]
    selfmond:
    2021:03:25-00:39:52 utm selfmonng[4603]: W triggerAction: 'cmd'
    2021:03:25-00:39:52 utm selfmonng[4603]: W actionCmd(+): '/etc/init.d/haldaemon restart'
    2021:03:25-00:39:52 utm selfmonng[4603]: W child returned status: exit='0' signal='0'
    2021:03:25-00:39:57 utm selfmonng[4603]: I check Failed increment hald_running counter 1 - 3
    2021:03:25-00:40:02 utm selfmonng[4603]: I check Failed increment hald_running counter 2 - 3
    2021:03:25-00:40:07 utm selfmonng[4603]: W check Failed increment hald_running counter 3 - 3
    2021:03:25-00:40:07 utm selfmonng[4603]: W NOTIFYEVENT Name=hald_running Level=INFO Id=144 suppressed
    2021:03:25-00:40:07 utm selfmonng[4603]: W triggerAction: 'cmd'
    2021:03:25-00:40:07 utm selfmonng[4603]: W actionCmd(-): '/etc/init.d/haldaemon restart'
  • 0 in reply to mfpck

    I don't know if these two issues are related.  If this is a home-use situation, your ISP may block the port 80 traffic that's necessary to renew a Let's Encrypt cert.

    As far as the "haldaemon restart" is concerned, that issue has never appeared before here.  Are you seeing any problem ecause of it?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Unfiltered HTML