Comment 12 for bug 159135

Revision history for this message
Daniel Hahler (blueyed) wrote :

Thanks for reporting back Papamatti.

The errors look like boinc was not running (anymore) in the post-start setup phase:
    boinc-client (6.12.33+dfsg-1.1) wird eingerichtet ...
     * Starting BOINC core client: boinc non-network local connections being added to access control list
                                                                         [ OK ]
     * Setting up scheduling for BOINC core client and children: chrt: failed to set pid 4075's policy: Kein passender Prozess gefunden
    chrt: failed to set pid 4075's policy: Kein passender Prozess gefunden
    chrt: failed to set pid 4075's policy: Kein passender Prozess gefunden
    /etc/init.d/boinc-client: 243: cannot create /proc/4075/oom_adj: Directory nonexistent
                                                                         [ OK ]
Does this still happen for you, e.g. when doing "sudo invoke-rc.d restart boinc-client"?